You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
(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
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.
🔒 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)
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.
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.
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.
Activity
🐛 Fix the hand-off UI harness for the stale-reason label (#18916)
🐛 Reach the kick observer registry through a checked type assertion (#…
✨ Show what each kick came to on the agent card and Activity Monitor …
hivecommons-hive commentedon Nov 18, 2026
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 ofor 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.🐛 Label the age, session and staleness of a replayed hand-off decline (…
✨ Record what each kick came to: durable per-kick outcome and GET /ap…
🐛 Reach the kick observer registry through a checked type assertion (#…
🐛 Keep pkg/dashboard free of a new package import; lower the comment-…
✨ Show who or what paused an agent, when and why, and who last resume…
🐛 Reach pause provenance through an adapter so pkg/dashboard takes no…
✨ Show what each kick came to on the agent card and Activity Monitor …
23 remaining items
hivecommons-hive commentedon Nov 18, 2026
🔒 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/unclaimto release, or/claimto take it over if you outrank the holder.Claim history
scanner(agent on hive hosted-available-oke-11-placeholder-r05x)hivecommons-hive commentedon Nov 18, 2026
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.
github-actions commentedon Nov 18, 2026
PR #18923 has merged (#18923) and referenced this issue with a non-closing
Refs #18916rather 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-inhive: needs-confirmationmarker only when the reporter genuinely must verify before closure.clubanderson commentedon Nov 18, 2026
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.
clubanderson commentedon Nov 18, 2026
Every part of this series is delivered on v5. Closing by hand, with the evidence per part:
reason_at,reason_age,reason_sessionandstale, in the "item not handed off" log line,GET /api/workflowsand the Settings "not started" display.pkg/kickoutcomeandGET /api/kick-outcomes.provider_backoff, no agent text quoted.PauseByandPausedByin the agent manager, the heartbeat fields, and the "paused by" line in the agent detail and hub hive list). The series did not define further criteria for it.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.
🌱 chore: top up v6 from v5 (2026-11-18) (#19100)