What
Three defects in text declared verbatim fidelity, which means every fleet repo carries it byte-exact and none of them can fix it locally without becoming drift the next spec/audit.py run reports.
1. A bare #1073 in GOVERNANCE.md, which resolves per-carrier
GOVERNANCE.md "Durable Knowledge and Self-Improvement" contains:
A worktree-isolation lapse met all three (the #1073 incident happened under prose the agent had already read, ...)
#1073 here means this repository's own issue, "Prevent one repo from modifying the state of another repo, force them to work in worktrees using safety hooks". GitHub renders a bare #N relative to the repository it is displayed in, so in a carrier it points at that carrier's own issue 1073.
The harm scales with the carrier's age. In ptr727/PhotoCleaner, currently at #98, it renders as a dead link. It becomes an actively wrong link to an unrelated PhotoCleaner issue the moment that repository reaches 1073, and it is silently wrong in every other carrier, each pointing somewhere different. Nothing in the fleet detects this: the section byte-matches the canonical, so the audit is satisfied.
Fully qualifying it (ptr727/ProjectTemplate#1073, or a full URL) fixes it in one edit here and re-vendors to every carrier.
2. A host-setup/ path in repo-worktree/SKILL.md with no hub qualifier
.agents/skills/repo-worktree/SKILL.md:142 (and the generated .github/skills/ copy) references host-setup/agent-safety/README.md as a bare path. No downstream repo has a host-setup/ directory, so it reads as a local path that is simply absent. The same file qualifies other hub-only paths correctly, so this one looks like an oversight rather than a convention.
3. Two unwrapped-line artifacts
.agents/skills/repo-worktree/SKILL.md:73, "Prose remains the only enforcement..." begins on its own source line with neither a blank line before it nor the preceding line filled..agents/skills/resync-a-repo/SKILL.md:48, an orphan two-word line, "to end,".
Cosmetic rather than misleading, but they ride into every carrier and are cheap to fix in the same pass.
Why These Are Grouped
All three share one property that makes them worth fixing centrally: a downstream repo that notices them cannot act. The files are verbatim, so a local fix diverges that carrier from the hub and is reported as drift, and the correct downstream disposition is to decline and route here. Each one therefore costs a decline in every carrier that re-vendors the file, indefinitely, until the hub changes.
Item 1 is the one worth prioritizing, since it is a wrong link rather than a formatting nit, and it gets worse over time rather than staying constant.
How This Surfaced
The #1073 reference was raised by Copilot as a suppressed finding against ptr727/PhotoCleaner#98, which re-vendored that GOVERNANCE.md section. The other two were found reviewing the same re-vendor. All verified against this repository at main f3b4cc9 (tag 2.0.526).
Answered and routed there rather than patched: ptr727/PhotoCleaner#98 (comment)
Audit run stamp: 2026-08-30T20:48:19Z | hub f3b4cc9
Not This Issue
#1119 is also about carried WORKFLOW.md/GOVERNANCE.md prose, on D1.6's file-finder sentence readability rather than on a reference that resolves wrongly.#1110 covers intent-tier checks having no mechanical floor, which is the reason nothing mechanical catches any of these.
What
Three defects in text declared
verbatimfidelity, which means every fleet repo carries it byte-exact and none of them can fix it locally without becoming drift the nextspec/audit.pyrun reports.1. A bare
#1073inGOVERNANCE.md, which resolves per-carrierGOVERNANCE.md"Durable Knowledge and Self-Improvement" contains:#1073here means this repository's own issue, "Prevent one repo from modifying the state of another repo, force them to work in worktrees using safety hooks". GitHub renders a bare#Nrelative to the repository it is displayed in, so in a carrier it points at that carrier's own issue 1073.The harm scales with the carrier's age. In ptr727/PhotoCleaner, currently at #98, it renders as a dead link. It becomes an actively wrong link to an unrelated PhotoCleaner issue the moment that repository reaches 1073, and it is silently wrong in every other carrier, each pointing somewhere different. Nothing in the fleet detects this: the section byte-matches the canonical, so the audit is satisfied.
Fully qualifying it (
ptr727/ProjectTemplate#1073, or a full URL) fixes it in one edit here and re-vendors to every carrier.2. A
host-setup/path inrepo-worktree/SKILL.mdwith no hub qualifier.agents/skills/repo-worktree/SKILL.md:142(and the generated.github/skills/copy) referenceshost-setup/agent-safety/README.mdas a bare path. No downstream repo has ahost-setup/directory, so it reads as a local path that is simply absent. The same file qualifies other hub-only paths correctly, so this one looks like an oversight rather than a convention.3. Two unwrapped-line artifacts
.agents/skills/repo-worktree/SKILL.md:73, "Prose remains the only enforcement..." begins on its own source line with neither a blank line before it nor the preceding line filled..agents/skills/resync-a-repo/SKILL.md:48, an orphan two-word line, "to end,".Cosmetic rather than misleading, but they ride into every carrier and are cheap to fix in the same pass.
Why These Are Grouped
All three share one property that makes them worth fixing centrally: a downstream repo that notices them cannot act. The files are
verbatim, so a local fix diverges that carrier from the hub and is reported as drift, and the correct downstream disposition is to decline and route here. Each one therefore costs a decline in every carrier that re-vendors the file, indefinitely, until the hub changes.Item 1 is the one worth prioritizing, since it is a wrong link rather than a formatting nit, and it gets worse over time rather than staying constant.
How This Surfaced
The
#1073reference was raised by Copilot as a suppressed finding against ptr727/PhotoCleaner#98, which re-vendored thatGOVERNANCE.mdsection. The other two were found reviewing the same re-vendor. All verified against this repository atmainf3b4cc9(tag2.0.526).Answered and routed there rather than patched: ptr727/PhotoCleaner#98 (comment)
Audit run stamp:
2026-08-30T20:48:19Z | hub f3b4cc9Not This Issue
#1119is also about carriedWORKFLOW.md/GOVERNANCE.mdprose, on D1.6's file-finder sentence readability rather than on a reference that resolves wrongly.#1110covers intent-tier checks having no mechanical floor, which is the reason nothing mechanical catches any of these.