context-save

To save your working state into a repo-native handoff, append a dev-log entry under .project-manager/features/<ID>/dev-log.md and create a checkpoint under .context/sessions/. This enforces a hard guard to never modify source code during saves.

A checkpoint session is a lightweight save file created under .context/sessions/ that captures your current working state. It pairs with a dev-log entry to enable pause-and-resume workflows by allowing past states to be reconstructed without touching source code.

To create a context checkpoint, invoke the save operation with an active feature ID like F46. The process appends an entry to the feature's dev-log.md and generates a new checkpoint under the .context/sessions/ directory.

No, context-save enforces a hard gate that refuses to alter feature-spec, tdd-spec, or test-scenarios files. The operation only touches the dev-log and the checkpoint, ensuring source code and specifications remain unchanged.

Yes, the dev-log checkpoint reconstructs past states by pairing the saved checkpoint under .context/sessions/ with the context-restore workflow. This allows you to pause and resume work by loading the exact artifact paths documented during the save.

You should not use a repo-native handoff checkpoint if your workflow requires modifying source code or altering feature-spec and tdd-spec files. This checkpoint mechanism is strictly append-only for dev-logs and sessions, enforcing a hard guard against code alterations.