Checkpoints mark how each step is known
gstack 1.91.17.0 flags guessed checkpoint steps and keeps every paid image
Saved checkpoints in gstack now say how the saving session knows each remaining step. Each item ends by saying whether that path was run, with its outcome, read, or only assumed.
Restore verifies guesses first
/context-restore checks a guessed step before it acts on it
Next steps
(path run) exit 0Steps the saving session ran
Verify first
(path assumed)“continue” checks these read-only
A resumed session could act on a guess and hit the wrong system. /context-restore now puts guessed steps under verify first and checks them read-only. Older, unmarked checkpoints land there too.
Paid images are kept
Paid design images are never overwritten
variant-A.png+variant-A-2.pngRunning variants twice into one folder replaced the first round. Now a taken name gets a numbered suffix, every retry is kept, and a failed save leaves a private recovery copy.
Boards show this round
Design skills show the round you just paid for
variant-A/B/CFixed names mixed rounds on one board
approved_pathA later session opens the image you approved
Design skills built boards from fixed file names, so old and new rounds mixed. Boards now show only this round's images, and the approval records the exact path. Older letter-only approvals still work.
Three smaller fixes
Image commands report failures, and two more fixes
CHANGELOG.mdScripting the design binary in 1.91.17.0Image commands print JSON even when they fail. Design sessions now work on Windows. And setup deploy reports a failing status command as a failure. The changelog explains scripting against the new output.
