Write the handoff note for the NEXT session, in this project. Write it BEFORE context runs out, not when you notice it is running out -- the note is the only thing that survives, and a session that dies mid-thought leaves nothing. project_path is REQUIRED and a missing one is the usual reason a write fails silently. Record what is UNFINISHED and what was learned the hard way; a note that only lists accomplishments is the one that gets a future session to redo work or act on a wrong assumption.

Read continuation note from handoff location and delete it (deprecated - use continuation_read_with_staleness)

Read continuation note with staleness detection (does not delete until new note written)

Delete an old continuation note. READ IT FIRST -- this is destructive and the note is the only copy. Normally you do not need this at all: continuation_write replaces the note, and continuation_read_and_cleanup does the read-then-delete in the right order.

Check if a continuation note exists at handoff location with staleness info

List the continuation notes that exist for one project. Use it when you are not sure a note exists -- a note that is ABSENT and a note that is STALE look the same from the outside, and acting on a stale one has repeatedly caused work to be planned around bugs that were already fixed.

Read one continuation note without deleting it. CHECK ITS DATE AGAINST THE ACTUAL REPO before trusting it: a note is a claim ABOUT the code, not the code. Notes here have been hours to days out of date and described files that no longer existed. Prefer continuation_read_with_staleness, which tells you how old it is.