kata-checkpoint-save

Validate the .checkpoint file against an exact markdown schema with required headings to ensure session state integrity. This validation enforces structural correctness before the workspace state is persisted, checking for forbidden sections like Activity or Steps that belong in active plans.

Yes, you can use .gitignore to exclude the checkpoint file from version control. The saving process explicitly verifies .gitignore coverage for the .checkpoint file at the workspace root, ensuring your session state is not committed to the repository.

The best way to persist session focus and open threads on demand is to write them into a canonical .checkpoint file. This captures session context in one place for later recovery, applying atomic tmp-to-final writing to safely store the workspace state without duplicating thread content.

You need to save a session checkpoint at the workspace root during on-demand or end-of-session persistence workflows. This ensures your current session context, including active plans and notes, is safely persisted via a UTF-8, LF-formatted .checkpoint file for later recovery.