Session save — checkpoint
Resolve this skill directory as SKILL_DIR. Read CLIENT.md beside this file for the installed client_id. Read the shared home’s GUIDE.md.
- Run
python3 "$SKILL_DIR/scripts/session_save.py" doctor --client <client_id>. Stop unlessokis true andmigration_requiredis zero. - Locate the current record with
locate --client <client_id> --session-id <id>when a real stable host ID exists, otherwiselocate --client <client_id> --slug <known-slug>. - If no record exists, run
project-listand resolve one exact approved project. Ask on ambiguity; never infer identity from tags or similar keywords. Register a genuinely new project only after explicit confirmation. Then runbegin --client <client_id> --project <project> --name <name> --status provisional --gist "Checkpoint saved; run session-tag to tag this session." --require-registered-project. Never invent a verdict or an unconfirmed project. This is the single provisional record. - Run
checkpoint-path --client <client_id> --record <record>and write one Markdown checkpoint to the returned unique path. Use### <HH:MM> — <client_id>followed by Now, Working on, Next, and Watch. Keep it approximately 100–300 words. - Run
sync --client <client_id> --record <record> --operation checkpoint-written. Do not change an existing open record back to provisional. - Print the compact checkpoint receipt with the client label and real path.
Checkpoints are immutable event files. Never append to another client’s file, create a second record for the same client session, write a close-out here, or edit _INDEX.md directly.