Repository navigation
Synced stubs in ring repos carry a header naming v1-stable above a uses: line pinned to their ring — bots flag it and agents edit the stub to match #1297
Description
Problem
The sweep re-pins a synced stub's uses: line (and agent_ref) to the target repo's ring, but leaves the stub's header comment naming the template's channel. In a ring-0 or ring-1 repo the two then disagree inside one file.
standards/workflows/persona-mention.yml line 11 says the uses: ref is pinned to the `persona-mention/v1-stable` channel; standards/workflows/pr-review.yml line 12 says "You MUST NOT change: the @pr-review/v1-stable channel in the uses: line". After the sweep, TalkTerm and bmad-bgreat-suite (ring 1) have uses: …@persona-mention/v1-ring1 and …@pr-review/v1-ring1 under those headers.
Why it matters: review bots flag the mismatch on every ring-repo sync PR (CodeRabbit on petry-projects/bmad-bgreat-suite PR 500: "The header comment and the uses: ref disagree"; "Header comment contradicts the changed code"), and agent passes then "fix" it in the consumer repo. On petry-projects/TalkTerm PR 529 a pass committed fix(workflows): correct channel refs in headers; on petry-projects/bmad-bgreat-suite PR 497 a pass went the other way and re-pinned the uses: line itself to v1-stable to match the comment, moving a ring-1 repo off its ring. Either edit makes the stub drift from the template.
Acceptance criteria
- A synced stub never contains a header statement that contradicts its own
uses:pin. Prefer making the template headers tier-neutral ("pinned to this repo's ring channel for<agent>, set by the standards sweep") over teaching the sweep to rewrite comment text. - Apply it to every template under
standards/workflows/that names av<N>-stablechannel in a comment. stub_body_matches_templatestill treats a correctly swept stub as compliant, with a bats case for a ring-1 repo.- The template-drift consumers in
petry-projects/.github-private(template_stub_drift.sh) are checked against the changed templates beforestandards/v1-stableis next cut, per the standards-channel promotion notes.
Budget guard
Template comment wording and one test. If any template's header wording is load-bearing for a parser, list it and stop.
Activity
don-petry commentedon Oct 11, 2026
Dev-Lead Implementation Plan
Issue: #1297 — Synced stubs in ring repos carry a header naming v1-stable above a uses: line pinned to their ring
Scope
Rewrite the AGENTS header of every channel-pinned template under
standards/workflows/so it doesn't name a tier (it points at "this repo's ring channel for<agent>, set by the standards sweep" instead of<agent>/v<N>-stable). The sweep andstub_body_matches_templatestay as they are. Add a bats guard.Parser check (budget guard): no script in this repo parses the header wording.
is_pin_compliantstrips comments before reading theuses:ref, andring_repin_usesonly rewritesuses:/agent_ref:/checkout_ref:lines..github-private'stemplate_stub_drift.shbyte-compares the seed emission (N / N-1 / HEAD = AHEAD) and doesn't parse comments either.Implementation Checklist
add-to-project.yml,auto-rebase.yml,dependabot-rebase.yml,idea-enhancer.yml,idea-triage.yml,initiative-planner.yml,persona-mention.yml,pr-auto-review.yml,pr-review.yml,pr-review-mention.ymldev-lead.yml: the inline "moving dev-lead stable channel tag" comment has the same contradiction in ring repos, so make it tier-neutral tooTests to Write
test/scripts/deploy-standard-workflows/stub-header-tier-neutral.bats:<agent>/stableor<agent>/v<N>-stablechannel outside its pin linesstub_body_matches_templateand its header doesn't contradict its@…/v1-ring1pinTest Command
bats -r test/(plusbash .dev-lead/scripts/dev-lead-lint.sh)AC 4 follow-up
Before
standards/v1-stableis next cut, the repo-template rows oftemplate_stub_drift.shwill show the changed stubs as AHEAD/N-1 until the channel is promoted and repo-template is re-seeded. That is a warning only, and it is noted for the promoter.don-petry commentedon Oct 11, 2026
Dev-Lead: Implementation Complete — PR #1298
The implementation for issue #1297 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
e38513943e99bfc738da63225a397bcbef38590bmain: 12 file(s), +137/-21 linesReview happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks — not asserted here. If a later stage fails, this claim is retracted in place.
test: verify sweep processes all ring-managed stubs with stale headers
feat: implement issue #1297 — Synced stubs in ring repos carry a head…
test: verify sweep processes all ring-managed stubs with stale headers
fix: stub_has_stale_stable_header must be tier-aware to prevent contr…
test(reviews): render ring fixtures via ring_repin_uses so headers ar…