From the round-1 review of #216 (issue #174).
Where: .claude/skills/update-xmech-page/SKILL.md, steps 10 and 11.
Step 11 runs after the merge. Step 10 says to report and stop until the user gives the go-ahead, which can come after context compaction or in a new conversation. Shell variables don't persist between tool calls, and the scratchpad path contains the session id. The only record inside the snapshot, revisions.json, is in the directory being looked for, and neither the PR body nor the report carries the path.
Failure scenario: the merge is approved in a new session. Step 11 either stops at ${SNAP:?}, or points at the new session's scratchpad and removes nothing, so the 5.7 GB snapshot stays behind: the leak #174 set out to fix.
Fix: tell the refresh to put the snapshot's absolute path and size in the PR body and the report ("Snapshot: , 5.7 GB, remove after merge"), and have step 11 take the path from there.
From the round-1 review of #216 (issue #174).
Where:
.claude/skills/update-xmech-page/SKILL.md, steps 10 and 11.Step 11 runs after the merge. Step 10 says to report and stop until the user gives the go-ahead, which can come after context compaction or in a new conversation. Shell variables don't persist between tool calls, and the scratchpad path contains the session id. The only record inside the snapshot,
revisions.json, is in the directory being looked for, and neither the PR body nor the report carries the path.Failure scenario: the merge is approved in a new session. Step 11 either stops at
${SNAP:?}, or points at the new session's scratchpad and removes nothing, so the 5.7 GB snapshot stays behind: the leak #174 set out to fix.Fix: tell the refresh to put the snapshot's absolute path and size in the PR body and the report ("Snapshot: , 5.7 GB, remove after merge"), and have step 11 take the path from there.