Skip to content

Operator visibility: per-kick outcomes, stale-reason labelling, pause provenance #18916

Closed
2 of 2 issues completed

Description

@clubanderson

Two visibility gaps keep causing operator mistakes. This issue tracks both as a series of small, independently mergeable PRs.

1. "Does this build contain PR #N?"

Today it is hard to tell what a hive is actually running: image tags move, builds appear untagged, digests and git ancestry are separate things, and "merged" has repeatedly been mistaken for "deployed".

Goal, on the hub hive list and on a hive's own version display:

  • the running commit and the release channel the hive follows
  • how many commits it is behind its channel head (reuse the existing behind-target machinery)
  • the newest tagged image commit and the newest merged commit shown separately, so the "latest merged, not yet built" gap is visible
  • a "contains" lookup: enter a PR number or commit SHA, get yes / no / unknown per hive, computed from the hive's reported commit and repository ancestry. A commit that cannot be resolved is always unknown, never a guess.

No new phone-home channel: the hive's already-reported commit and channel are reused, and any new outbound request is documented in src/docs/telemetry.md.

Series:

  • (a) shared ancestry resolver, hub read API, hive read API, openapi and API-reference updates
  • (b) UI on the hub hive list and the hive's own version display

2. Render evidence for UI PRs

Reviewers and agents keep reporting "not verified in a browser" on UI PRs. Extend the existing mobile-shots workflow so UI-touching PRs carry viewable render evidence: fixture-data screenshots of the affected dashboard sections at desktop and phone width, in light and dark themes, uploaded as an artifact and indexed in one sticky PR comment that is updated in place.

Constraints: runs only when dashboard sources or assets change, bounded by a named time budget, never fails the PR on screenshot flake (reports neutral with the reason), no secrets, no live data, no untrusted code under pull_request_target. Documented limit: fixtures are not live data.

Series:

  • (c) workflow, harness, sticky comment, and a doc on how to read the evidence

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 18, 2026
  2. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

    PR #18923 covers this issue: #18923

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

  3. 23 remaining items

  4. removed
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    on Nov 18, 2026
  5. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    🔒 Claimed by agent scanner (agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

    Claim history
    • 2026-11-18 16:34 UTC — claimed by scanner (agent on hive hosted-available-oke-11-placeholder-r05x)
  6. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    Consolidated finding. This was filed as a separate issue; it has the same subject as this one, so it was folded in here instead. Address it together with this issue.

    [scanner] Operator visibility: per-kick outcomes, stale-reason labelling, pause provenance

    Scanner verification: label request only.

  7. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed
    stage/020-claimedClaimed by the scanner or a relay contributor
    on Nov 18, 2026
  8. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    PR #18923 has merged (#18923) and referenced this issue with a non-closing Refs #18916 rather than a closing keyword.

    This issue remains open because the merged PR did not use Closes / Fixes / Resolves. If the fix should close it on merge, use a closing keyword in the PR body; use the opt-in hive: needs-confirmation marker only when the reporter genuinely must verify before closure.

  9. self-assigned this
    on Nov 18, 2026
  10. clubanderson commented on Nov 18, 2026

    @clubanderson
    MemberAuthor

    Claimed by the maintainer: a dispatched agent is working this, one PR to follow where code is needed. Please do not open a parallel PR.

  11. clubanderson commented on Nov 18, 2026

    @clubanderson
    MemberAuthor

    Every part of this series is delivered on v5. Closing by hand, with the evidence per part:

    Note: the body of this issue is a copy of the body of #18915 (the "does this build contain PR" and render-evidence series, already closed with #18918, #18925 and #18921). It does not describe this series, whose scope is the title and the PRs above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.hive/partially-addressedA merged PR addressed only part of this issue; remainder still actionable

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions