Two defects in the canonical .github/copilot-instructions.md surfaced while carrying it into PlexCleaner (ptr727/PlexCleaner #922) on 2026-08-15, against hub main at 0e84805. Both are in the file every fleet repo carries whole at intent fidelity, so each carrier inherits them.
-
The "A Shape Nothing Recognizes Blocks the Loop and Earns an Issue" step names the hub by slug in a non-verbatim section. Its first numbered item reads "File an issue on the hub, ptr727/ProjectTemplate, which hosts scripts/pr_review.py ...". The audit's carried: check flags a downstream copy that references the template repo by name outside a verbatim section, so a byte-faithful carry of the canonical trips it: audit.py --branch hub-resync-2026-08-15 PlexCleaner at df8f1a2 reported DRIFT carried: .github/copilot-instructions.md references the template repo by name or link outside its verbatim sections. PlexCleaner's copy reworded the step to "File an issue on the hub (the repository AGENTS.md "Fleet Bootstrap" names)", which clears the check and still routes the reader, and the canonical wants the same shape, or the check wants an exception for this file's runbook, whichever the rule intends. GOVERNANCE.md "Documentation Style Conventions" names a verbatim section that must name the hub to do its job as the exception, and this section is not verbatim.
-
The "Disproved Claims" section links GOVERNANCE.md#every-finding-ends-in-an-action, an anchor that does not exist. grep -n -i "every finding ends" GOVERNANCE.md on hub main at 0e84805 returns nothing, and the "PR Review Etiquette" section carries no such subheading. The sentence reads: [GOVERNANCE.md "Every Finding Ends in an Action"](../GOVERNANCE.md#every-finding-ends-in-an-action) closes a false finding by disproving it in the thread. Either the subheading was renamed or removed after the link was written, or it was meant to point at the pr-review-conduct Skill's "Every finding ends in one of five outcomes", which is where that rule text now lives. Either way the link resolves nowhere in every carrier, and no dead-anchor check catches it since dead-path reads paths rather than fragments.
Two defects in the canonical
.github/copilot-instructions.mdsurfaced while carrying it into PlexCleaner (ptr727/PlexCleaner #922) on 2026-08-15, against hubmainat0e84805. Both are in the file every fleet repo carries whole atintentfidelity, so each carrier inherits them.The "A Shape Nothing Recognizes Blocks the Loop and Earns an Issue" step names the hub by slug in a non-verbatim section. Its first numbered item reads "File an issue on the hub,
ptr727/ProjectTemplate, which hostsscripts/pr_review.py...". The audit'scarried:check flags a downstream copy that references the template repo by name outside a verbatim section, so a byte-faithful carry of the canonical trips it:audit.py --branch hub-resync-2026-08-15 PlexCleaneratdf8f1a2reportedDRIFT carried: .github/copilot-instructions.md references the template repo by name or link outside its verbatim sections. PlexCleaner's copy reworded the step to "File an issue on the hub (the repositoryAGENTS.md"Fleet Bootstrap" names)", which clears the check and still routes the reader, and the canonical wants the same shape, or the check wants an exception for this file's runbook, whichever the rule intends. GOVERNANCE.md "Documentation Style Conventions" names a verbatim section that must name the hub to do its job as the exception, and this section is not verbatim.The "Disproved Claims" section links
GOVERNANCE.md#every-finding-ends-in-an-action, an anchor that does not exist.grep -n -i "every finding ends" GOVERNANCE.mdon hubmainat0e84805returns nothing, and the "PR Review Etiquette" section carries no such subheading. The sentence reads:[GOVERNANCE.md "Every Finding Ends in an Action"](../GOVERNANCE.md#every-finding-ends-in-an-action) closes a false finding by disproving it in the thread. Either the subheading was renamed or removed after the link was written, or it was meant to point at thepr-review-conductSkill's "Every finding ends in one of five outcomes", which is where that rule text now lives. Either way the link resolves nowhere in every carrier, and no dead-anchor check catches it sincedead-pathreads paths rather than fragments.