[clubanderson]

Fixes #12144

Root cause of the stray #12025→#12005 closing link

claimsFromPR runs the branch-name heuristic whenever the title/body carry no closing keyword. PR #12025's branch is feat/12005-push, so issue 12005 became a strong claim (neither Closing nor Reference), and the body's explicit Refs #12005 (partial …) was dropped because the issue already had a strong claim. #12092 changed the link gate from claim.Closing to !claim.Reference, so on the first sweep after it deployed (17:41Z, two hours after Bob had removed Closes #12005 from the body) the branch-name claim got addCloseIssueReferences. Not a stale body or a stale memo — a grading bug.

Changes

pkg/github

• claimsFromPR: an explicit non-closing reference to the branch-name issue downgrades the branch-name claim to a reference claim. Closes #N still beats both; Refs #other still adds a separate weak claim.
• New Client.RetractHiveClosingIssueLink: for a reference claim the sweep looks up the PR's closingIssuesReferences and CONNECTED_EVENT timeline. If the pair is linked and the most recent connect actor is this hive's App account (appBotLogin, compared without [bot]), it runs removeCloseIssueReferences and forgets the ensure-memo so a later Closes #N edit re-links. A link made by a person — or seen by a PAT-authenticated hive that cannot tell its own links apart — is left alone and logged at Warn (not-hive-linked). Memoised per pair; failures are not memoised.
  • Decision: remove only App-made links. GitHub-derived keyword links never reach this path (the body would have graded the claim Closing), so every link seen here is a manual one; attributing it via the connect actor is the only way to avoid undoing a maintainer's deliberate sidebar link. ✨ keep unstick steps running in conserve API budget mode #12025→✨ re-run PRs red on a fixed shared-CI baseline, and stop shedding unstick sweeps under API budget pressure #12005 (actor hivecommons-hive) will be retracted on the next sweep after deploy — not run by hand.
• RepoWorkIssue (the nonActionableIssues entry a suppressed issue becomes) now carries linked_prs and claim_context; IssueLinkedPR gains reference.

Dashboard (static/index.html)

• New issueCoveringPR / issueCoveringPRBadge: the 🔗 pill is derived from linked_prs — hive's own claim evidence, the same source that applies 🐝 covered by PR — and used by both the actionable and the non-actionable pill renderers. Tooltip: "closes via PR #N" / "covered by PR #N (partial)" / "merged via PR #N". Exactly one badge per issue; several PRs → closing one primary, 🔗×2, rest in the tooltip. Non-actionable rows also get the issue:linked-pr filter kind. Reuses .repo-issue-plan.pill-icon and repoPillActionCluster; no inline styles or raw px (ratchet counts unchanged).

Tests: prclaims_branch_reference_12144_test.go (claim grading incl. the #12025 shape, retraction matrix, sweep retracts + never adds for reference claims, suppressed issue keeps linked_prs), repo_card_covering_pr_glyph_12144_test.go (node-executed badge assertions).

Docs: dashboard.md (Linked PR issue signals), dashboard-sections.md (Repositories pills), labels-and-control-signals.md (covered-by-PR row: link rule + retraction).

Live check before the change (/api/status on hive's hive): #12002 and #12005 both sat in nonActionableIssues with reason: Open external PR #N covers this issue and no linked_prs — which is why the label showed and the glyph did not.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kellyaa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#12158	✨ review: add review.shadow to record would_have_held for the review gate	same files	src/pkg/dashboard/static/index.html
#12079	🐛 evidence: capture CI conclusion at merge-eligibility time	same files	src/pkg/github/client.go
#12139	✨ dashboard settings: expose intent pattern lists and sentinel list keys	same files	src/pkg/dashboard/static/index.html
#12045	🐛 Stop task-list sweep hard-parking issues on prose needs-human	same files	src/docs/labels-and-control-signals.md
#12159	✨ dashboard: iPhone widget entry in the avatar menu deep-links into Scriptable	same files	src/pkg/dashboard/static/index.html
#12164	🌱 tokens: per-issue/PR/head-SHA launch attribution over the token collector	same files	src/pkg/dashboard/static/index.html
#12154	🌱 tokens: trajectory review — skip only on proven-idle agent state and not overdue, with skipped metrics	same files	src/pkg/dashboard/static/index.html

[hivecommons-hive]

hive/awaiting-ci: the only red check here, relative links and anchors resolve, is red on the v5 default branch itself (broken admin-mcp.md links from #12143). Tracked as shared incident #12162; fix in #12161. No change needed on this branch — deferring until the baseline is green, then the sweep merges on re-run.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1

[hivecommons-hive]

merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at 3483a91.

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback