Repository navigation
Estate drift: canonical dogfood-gate.yml pins a broken (exit-127) a2ml-validate-action SHA estate-wide #85
Description
Activity
- added a parent issue
on May 17, 2026 Template-source half done. Pins bumped on
mainin all three canonical templates:- rsr-template-repo#56 (merged)
- v3-templater#75 (merged)
- reposystem#50 (merged)
All now pin
a2ml-validate-action@59145c7(off the exit-12786c6da6) andk9-validate-action@2d96f43.Remaining: re-sync consumers via the normal template-drift sweep (the proven bulk admin-merge mechanism — sibling pattern to #82/#83/#84). idaptik already done directly (idaptik#87). K9 consumers stay red until k9iser#8 regardless of pin.
- added 11 commits that reference this issue
on May 17, 2026 49 remaining items
- added 13 commits that reference this issue
on May 17, 2026 Consumer dogfood-pin re-sweep — complete
Template-source half landed earlier (rsr-template-repo#56 / v3-templater#75 / reposystem#50 — all 3 canonical
dogfood-gate.ymlpinned to a2ml59145c7/ k92d96f43).Final idempotent re-sweep run against all in-scope active
hyperpolymathconsumers carryingdogfood-gate.yml(content-diff against the canonical pins; only stale repos get a PR):- In-scope consumers swept: 223 (estate survey 232; 9 held back — see below).
- Residual drift found this pass: 0 — all 223 already carry both canonical pins (
SKIP-OK), confirming the earlier baseline (~79 merged + template-source) plus prior sweep runs fully remediated the consumer estate. 0DEFER/FAIL. - Spot-verified 5 consumers'
main(verisimiser, burble, hypatia, panll, gossamer) — all carrya2ml-validate-action@59145c7d1039fa3059b3ecacdb50ee23d7505898andk9-validate-action@2d96f43c538964b097d159ed3a56ba5b5ceca227. - Deliberately held back (scope):
idaptik(handled in idaptik#87, runner-blocked),idaptik-rescript13-staging,rescript-dom-mounter,stapeln— ReScript hands-off; plus the V-ecosystem repos per V-lang policy.affinescriptwas never in scope.
The earlier K9-side blocker (k9iser#8 — codegen emitting non-compliant K9) was resolved by k9iser#9 (merged 2026-05-18), so the only remaining template-drift dimension this issue tracked is now removed across the consumer estate.
Consumer pin-drift remediation complete and the K9-side root cause resolved upstream — closing.
Problem
The canonical
dogfood-gate.ymlin all three template sources pins stale validate-action SHAs:@86c6da6@cfa7f92@86c6da6@cfa7f92@86c6da6@cfa7f92a2ml-validate-action@86c6da6(2026-04-11) exit-127 crashes on the broken-multi-line-comment bug (line 152: ame/project: No such file or directory). It was fixed upstream by a2ml-validate-action#11 (f8517bb) and further by #12 (59145c7) which generalises the structural-identity exemption to the whole.machine_readable/tree.Net effect: any repo synced to the canonical template pin gets a red Dogfood Gate / A2ML job estate-wide — either an exit-127 crash (at
86c6da6) or false-positive identity errors on the canonical.machine_readable/tree (at any pin before #12).rsr-template-repoitself fails its own A2ML check under the pinned SHA.Surfaced while triaging idaptik#77; idaptik was fixed by pinning directly to
59145c7(idaptik#87) rather than to the broken canonical pin.Fix
In
rsr-template-repo,v3-templater,reposystem.github/workflows/dogfood-gate.yml:a2ml-validate-action@86c6da6→@59145c7d1039fa3059b3ecacdb50ee23d7505898 # maink9-validate-action@cfa7f92→@2d96f43c538964b097d159ed3a56ba5b5ceca227 # main(un-drift; not broken, just stale)Then re-sync consumers via the normal template-drift sweep.
Related
@7ee2e0fd… # main) breaks quality/lint estate-wide #82/Estate drift: canonical.machine_readable/root-allow.txtis stale — estate-rules 'Root shape allowlist' red on rsr-template-repo #83/Estate drift: estate-rules content scanners false-positive on policy ADRs (check-no-vlang / check-no-project-identifiers) #84.🤖 Generated with Claude Code