Gap
PRs opened in this repo currently don't inherit the triage labels of the issues they close. As a result, PRs are invisible to the same is:open label:priority/p1 queries that surface the issues — they don't show up in priority-ordered review.
This was a silent failure mode in the recent batched-PR shipping (10 PRs in two batches, all merged-eligible after CR sign-off, none labeled).
What needs to happen
Codify the rule in CLAUDE.md so every fork that ships a PR mirrors the closing issue's labels onto the new PR as part of the gh pr create round, before pinging CodeRabbit. Mechanics already drafted; PR will land the section.
Acceptance
CLAUDE.md contains a ## PR labeling — mirror closing-issue labels (MANDATORY) section with the exact gh invocation, multi-close handling, and the same "before declaring done" checkpoint as the post-push CI watcher rule.- Section is referenced from the existing post-push / CR-loop sections so a reader following one workflow link finds the other.
Gap
PRs opened in this repo currently don't inherit the triage labels of the issues they close. As a result, PRs are invisible to the same
is:open label:priority/p1queries that surface the issues — they don't show up in priority-ordered review.This was a silent failure mode in the recent batched-PR shipping (10 PRs in two batches, all merged-eligible after CR sign-off, none labeled).
What needs to happen
Codify the rule in
CLAUDE.mdso every fork that ships a PR mirrors the closing issue's labels onto the new PR as part of thegh pr createround, before pinging CodeRabbit. Mechanics already drafted; PR will land the section.Acceptance
CLAUDE.mdcontains a## PR labeling — mirror closing-issue labels (MANDATORY)section with the exactghinvocation, multi-close handling, and the same "before declaring done" checkpoint as the post-push CI watcher rule.