Session Continuity Ops

Workflow

1. Read session-start.md to understand the hydration contract — what fields must be present in the saved context file for the Start hook to inject them.
2. Simulate a PreCompact event: trigger the hook manually with a test session context and verify the output JSON contains all required fields (org alias, active task, evidence paths, scratchpad summary).
3. Validate the Stop hook: confirm it writes last-session.json with a complete artifact inventory before the session terminates.
4. Check transcript backup controls (see transcript-backup.md): confirm the backup file exists at the expected path and was written within the current session window.
5. Test recovery: start a new session, confirm the UserPromptSubmit hook detects the prior state file and injects the context summary.
6. Diagnose failures: if hydration is incomplete, compare the saved context schema against the hydration contract to find missing fields.

Routing Boundaries

Use this skill for hook-level session state persistence and hydration. Defer to context-budget-guardrails-framework when the concern is throttling tool use to avoid compaction, rather than recovering after it.

References

• Session Start Hydration
• Session Stop Persistence
• Transcript Backup Controls