Yao Amevi A. Sossou d540b102ac fix(context): record the save commit and flag work that landed after it ...

/context-save recorded the branch, a timestamp and the modified files, but not
the commit, so /context-restore could not tell that work landed after the save.
A checkpoint saved before a step was committed came back with that step still
listed as the plan.

- gstack-slug --stamp-checkpoint also writes head:, the commit the save
  describes, next to remote:/project_root:/worktree:.
- context-restore compares head: with HEAD before presenting. When commits
  landed after the save it prints how many and lists them, and moves Remaining
  Work under Verify first; a saved commit that left the branch history is
  reported the same way. Checkpoints saved before this keep their old sorting
  with a one-line note.
- test/context-restore-head.test.ts runs the real save-path, stamp and
  head-check blocks in fixture repos: unchanged, moved, diverged after a reset,
  pre-tracking, and a malformed head: that must never execute.

2026-10-24 22:51:19 +00:00

..

SKILL.md

fix(context): record the save commit and flag work that landed after it

2026-10-24 22:51:19 +00:00

SKILL.md.tmpl

fix(context): record the save commit and flag work that landed after it

2026-10-24 22:51:19 +00:00