From the round-4 review of #216 (follows #236).
Where: .claude/skills/update-xmech-page/SKILL.md, step 11's rebuild recipe.
The recipe says to write revisions.json "from the audit's shas, commit dates and pinned_at_utc, keyed by Mech name". The real file nests the Mechs under mechs and keeps CLAW's sha under a top-level claw key, which "keyed by Mech name" gives no place to. The recipe also runs step 2 without setting SRC, which step 1's other block assigns, so in a fresh shell step 2 clones from /<Mech> and fails.
Fix:
- give the shape:
{"pinned_at_utc": …, "mechs": {<Mech>: {"repo", "sha", "commit_date"}}, "claw": <sha>};
- say to set
SRC as in step 1 before step 2.
From the round-4 review of #216 (follows #236).
Where:
.claude/skills/update-xmech-page/SKILL.md, step 11's rebuild recipe.The recipe says to write
revisions.json"from the audit's shas, commit dates andpinned_at_utc, keyed by Mech name". The real file nests the Mechs undermechsand keeps CLAW's sha under a top-levelclawkey, which "keyed by Mech name" gives no place to. The recipe also runs step 2 without settingSRC, which step 1's other block assigns, so in a fresh shell step 2 clones from/<Mech>and fails.Fix:
{"pinned_at_utc": …, "mechs": {<Mech>: {"repo", "sha", "commit_date"}}, "claw": <sha>};SRCas in step 1 before step 2.