Close Five Review Gaps in repo-worktree, drive-pr, pr-review-conduct, and backlog-burndown - #4166

Closes review gaps in four fleet skills, and gives the carried-table bound its reason in GOVERNANCE.md and the Copilot instructions.

Changes

• repo-worktree "Preparing Git Hooks" (Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 5). The pre-commit check is now one complete command: test -x and a grep for the framework's own header, on the shared hook path. A non-framework executable there no longer counts as the gate. It falls to the unchanged next bullet: "A missing or wrong shared hook is reported to the maintainer, not repaired from the worktree."
• drive-pr (Give Open Findings on a Peer-Merged Feature PR an Outcome in drive-pr #3697). A feature PR a peer merged mid-drive still owes an outcome for each open finding. That covers unresolved threads and every finding step 4 names, whether or not merge would refuse on it, since merge never runs there. Step 3's state=MERGED path and step 4's next=cleanup route both give those outcomes before cleanup runs. A fix lands as a fresh feature -> develop pass.
• GOVERNANCE.md "PR Review Etiquette", pr-review-conduct Merge Gate item 2, and .github/copilot-instructions.md (Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 3). Each gets two sentences on why the carried-table bound is the file set rather than file recency, per the maintainer's answer on Decide: Should pr-review-conduct's Merge Gate item 2 (and its summary in .github/copilot-instructions.md, plus table_cover in scripts/pr_review_rounds.py) accept a carried Copilot file table (`coverage=? #3746.
• backlog-burndown "The Promotion Boundary" step 5 (Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 4). The displaced pull request waits until the next round dispatches, and that round dispatches its fresh worker. That matches step 6 in an attended run, and the away-mode promotion path, which has no freeze.
• Generated copies under .github/skills/ and .claude-plugin/fleet-skills/ were regenerated with scripts/build_dist.py.

Item Dispositions

• Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 1 (session-handoff resume filter): already fixed. It was consolidated into Keep a Maintainer Comment That Quotes a Round Marker, and Keep blocked While a New Decision Waits #4013 item 1 and landed in Read a Handoff Round by Its Whole Shape, Confirm a Default Pick, and Write a Final Round Before close #4034. A comment now counts as a round only by its whole archived shape.
• Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 2 (unattended-handoff picker): stale. That skill was retired in Add an Away Mode to backlog-burndown and Retire unattended-handoff #3735 and no longer exists.
• Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 3: declined, as the maintainer decided on Decide: Should pr-review-conduct's Merge Gate item 2 (and its summary in .github/copilot-instructions.md, plus table_cover in scripts/pr_review_rounds.py) accept a carried Copilot file table (`coverage=? #3746. The reason sentences it asked for are added above.
• Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 4: it still stood on develop, since step 5's "then dispatches" read as a dispatch during the freeze. Fixed above.
• Triage Five CodeRabbit Findings on Carried Skills From a Downstream Resync #3620 item 5: it still stood on develop, since test -x accepted any executable. Fixed above.
• Name a Continuation's Base-Clone Switch as an Exception in repo-worktree's Base Branch Rule #3766: already resolved on develop. repo-worktree "The Base Branch" names "Creating a Worktree"'s return of the base clone to its own working branch as the second exception. It applies where a continuation finds the task branch checked out there. That landed in Fix the Base-Clone Conflict, the Missing Audit Flag, and the Layout #1685, so no edit was needed.
• Say Who Repairs a Missing Shared Git Hook, and How the Question Reaches the Maintainer #3869: parked behind decision Decide How a Missing or Wrong Shared Git Hook Is Repaired and How the Question Reaches the Maintainer #4167 and left out of this pull request's closing line. A draft of Say Who Repairs a Missing Shared Git Hook, and How the Question Reaches the Maintainer #3869's own proposal was taken back out of this branch. In it, the agent installs the hook in the base clone on the maintainer's yes. Each local review round found a new cost in that draft: chaining a foreign hook, a Husky.Net setting breaking other worktrees, a hook failing on branches without the config, and a dispatched worker either stalling its round or never reaching the maintainer. The decision issue lays out the options.

Verification

• scripts/build_dist.py --check reports the generated distributions current. spec/validate.py passes.
• The prose gate and repo_gate.py --check eol are clean on every commit.
• The hook check was run against a constructed repository. With no hook it exits 1, with a foreign executable 1, and with a framework-header hook 0. The header line was read from the pre-commit framework's own hook template on this host.

Closes on promotion: #3620, #3697, #3766

🤖 Generated with Claude Code