…rse failure)

panic-attack rust-ci.yml + 42 other estate repos that pin
rust-ci-reusable.yml@cc5a372a have been failing with 0s-duration
"workflow file issue" parse errors since 2026-05-26 (when PR #45
introduced the thin-wrapper). cc5a372a IS reachable from
standards/main (verified via git merge-base --is-ancestor), so
this is NOT the orphan-SHA failure mode panic-attack#84 thought
it was fixing.

Empirical: every recent rust-ci run failed at parse time. The
reusable's content at cc5a372a is structurally fine. The simplest
hypothesis is that GH Actions has cached a bad resolution of this
specific SHA — repinning to a fresher merge-commit forces re-fetch.

822fa14e is the current HEAD of standards/main on the file
(standards#299, "pass --locked to cargo check/clippy/test").
Bumping forward to that brings the --locked safety along with
the unblock.

If 822fa14e also fails parse: the issue is not the SHA, and the
caller-side workflow file needs investigation (the workflow's
API-reported name field has been ".github/workflows/rust-ci.yml"
not "Rust CI", suggesting GH never parsed it successfully).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>