queen: reconcile issue state from PR linkage -- completed-but-open issues close one at a time, with evidence #9968

Part of the dispatch roadmap epic #9976. Industry reference and the measured gap are below.

Measured 2026-10-17: 508 open issues are skipped as completed every tick. The work is merged but the issue stayed open, so they pollute every count and every board. A bulk close was reverted by the owner on 2026-10-07; closing must be one issue at a time, each with the PR that did it.

Industry reference: a Kubernetes controller is a reconcile loop -- it compares desired with observed state and issues the smallest fix, idempotently, one object at a time, rate-limited.

User Scenarios

• As the Queen, when an open issue's work was merged by a PR that names it, I close it with a comment linking that PR and its merge commit.
• As the owner, I never see a bulk close: closes are rate-limited and each one carries its evidence.

Requirements

• close_decision(issue_open, linked_pr_merged, pr_names_issue, open_followups, is_epic) -> u8 with named reasons (close, keep-epic, keep-followup, keep-no-evidence).
• An epic or tracking issue is never closed by this rule.
• A CLOSES_PER_HOUR cap as a named constant, with its reason in a comment.

Success Criteria

• Tests for every reason, including an epic whose sub-issues are all done (stays open) and a PR that only says Refs #N (no close).
• Invariant: no close without a merged PR.
• 0 surviving mutants.

Rules for the bee

• Only .t27 is hand-written; the seal is tool-written (t27c seal --save after a fresh release build on the Railway lab). No .py, .rs, .ts, .sh or .yml edits.
• Every rule gets test blocks and at least one invariant; run tri mutate spec on the new file (on the lab) and kill every surviving mutant. The bar is specs/queen/dispatch.t27 in PR test(queen): kill the 39 surviving mutants of specs/queen/dispatch.t27 #9961: 0 survivors, 0 vacuous tests.
• Write the measured numbers that motivate the card into its header comment, as specs/queen/holds.t27 does.
• Wiring into the runtime (gHashTag/trios) is a separate step: it lands as generated code once gen-ts lowers pure function bodies (gen-ts: lower the bodies of pure functions, so a host imports a spec's rule instead of copying it #7871 / PR gen-ts: lower the bodies of pure functions #7872). Do not hand-write TypeScript here.

Boundary

• specs/queen/reconcile.t27
• .trinity/seals/queen_QueenReconcile.json