Skip to content

Estate drift: canonical dogfood-gate.yml pins a broken (exit-127) a2ml-validate-action SHA estate-wide #85

@hyperpolymath

Description

@hyperpolymath

Problem

The canonical dogfood-gate.yml in all three template sources pins stale validate-action SHAs:

Template repo a2ml-validate-action k9-validate-action
rsr-template-repo @86c6da6 @cfa7f92
v3-templater @86c6da6 @cfa7f92
reposystem @86c6da6 @cfa7f92

a2ml-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-repo itself 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 # main
  • k9-validate-action@cfa7f92@2d96f43c538964b097d159ed3a56ba5b5ceca227 # main (un-drift; not broken, just stale)

Then re-sync consumers via the normal template-drift sweep.

Related

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    majorMajor / load-bearing workrequirements-targetTracked requirements-target item (joint-close)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions