New-Checkpoint reuses only a file written today (1.0.2) #13

Merged

hannah-vernon merged 1 commit from fix/checkpoint-per-day into dev

2026-09-14 15:18:42 -05:00

hannah-vernon commented

2026-09-14 15:18:33 -05:00

Owner

1.0.1 changed the rule to one file per day; the script still implemented one file per session and matched a checkpoint from two months earlier. Found while writing a real checkpoint.

hannah-vernon added 1 commit

2026-09-14 15:18:33 -05:00

New-Checkpoint reuses only a file written today (1.0.2) 287a62bbdf

1.0.1 changed the rule from one file per session to one file per day,
because agent sessions get resumed over weeks.  The documentation
changed; New-Checkpoint.ps1 did not.  It still matched on the session
identifier alone, so today it offered to append a new day's work to a
checkpoint written on 2026-07-16, two months earlier.

Reuse now requires the candidate filename to carry today's date as well
as the session identifier.  Both the filename and the reuse check take a
single clock reading, so a run that straddles midnight cannot create a
file whose name disagrees with its own comparison.

Verified: same session on a later day creates a new file; a second call
the same day reuses it.

Found while writing a real checkpoint, which is the third defect this
skill has surfaced by being used rather than tested.  AGENT-README now
records the general lesson: when a rule changes, check whether a script
still encodes the old one.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>