Session Persistence & Checkpointing #1
Description
Summary
Define a unified approach for saving, restoring, and checkpointing session state across tools.
Motivation
Long-running sessions need deterministic restores, portability, and auditability. A persistence file defines the artifact; checkpointing defines when and how to create/restore it.
Proposed Approach
- Specify a minimal persistence schema (JSON or Markdown+frontmatter).
- Include: project, role, phase, output style, tone, interaction mode, last_updated.
- Define checkpoint lifecycle: when to save, how to restore, conflict handling.
- Require explicit user confirmation for save/restore.
- Keep optional and tool-agnostic.
Acceptance Criteria
- Spec section covers both persistence format and checkpointing workflow.
- Example schema included.
- Clear rules for save/load/restore and conflict resolution.
- Templates and prompt workflows updated to reflect spec changes, with validation passing.