🐛 Hive/ClankeR PRs omit or suppress Closes/Fixes keywords so issues stay open after merge #10825

Evidence

Checked with gh pr view N --repo hivecommons/hive --json body,closingIssuesReferences,author,baseRefName,mergedAt on 2026-10-06.

All sampled PRs target v5, the repository default branch, so GitHub populates closingIssuesReferences only when the body uses a closing keyword.

User-visible consequence: non-closing Refs #N leaves GitHub's issue list and issue sidebar without a linked-PR indicator. The maintainer's is:issue state:open label:hive/likely-done screenshot shows #10820, #10795, #10774, and #10773 with no PR link icon even though merged PRs exist. Fixes/Closes/Resolves against the default branch are the relationship GitHub exposes as closingIssuesReferences and as the linked PR icon/sidebar entry.

Additional issue evidence for #10774 after #10778 merged:

• 2026-10-06T05:05:12Z github-actions posted <!-- hive-post-merge-refs-sweep: issue=10774 --> asking whether the issue could now be closed because PR 🐛 fix(rotation): race-free stale-lock takeover in codex_reset_redeem #10778 merged with non-closing Refs #10774.
• 2026-10-06T05:10:44Z hivecommons-hive posted Reporter-confirmation gate: ... leaving it open until the reporter confirms the symptom is gone.

Root cause

There are two affected paths:

1. Hosted/scanner bot path: src/pkg/policies/defaults/scanner-automerge.md:133 tells agents to use Closes #N, but src/pkg/github/pr_request_claims.go then calls humanFiledBugReason from validatePRRequestClaims and rewrites a human-filed bug's Closes/Fixes/Resolves #N to non-closing Refs #N. The rewrite is visible in 🐛 fix(rotation): race-free stale-lock takeover in codex_reset_redeem #10778 and was documented in src/docs/hive-open-pr.md / src/docs/labels-and-control-signals.md as deliberate reporter-confirmation behavior.
2. Contributor/ClankeR lane: src/pkg/dashboard/contribute_task_prompt.go (artifact trailer prompt from 8b267ad2f9) carried issue references/trailers but had no equivalent closing-keyword instruction. Contributor PRs are opened directly with gh pr create, so they also had no deterministic body post-check before submission.

Maintainer policy now desired: PR bodies should keep Fixes/Closes #N; if Hive wants reporter confirmation, that should be handled in Hive's close/verify path after merge, not by suppressing GitHub's PR closing relationship in the PR body.

Expected

For issue-backed Hive/ClankeR PRs targeting the default branch, the PR body should include a GitHub closing keyword (Closes #N, or Fixes #N for bugs) unless the PR is truly partial/tracker work and says why the issue remains open. That restores GitHub linked-PR sidebar/list linkage for every agent lane (hosted scanner/App-bot lanes and ClankeR/contributor lane). Human-filed bug reporter confirmation should be enforced by the issue close gate.