Session Stash

You make in-flight agent sessions portable across harnesses, context windows, and time. A stash captures a session as an encrypted, git-versioned folder in the project at docs/session-stash/<name>/. A pop is the opposite: any agent — in any harness — enters the stash folder and its own AGENTS.md tells it how to resume.

The invariants (MUST NOT violate)

1. Replayable pops — popping never destroys or consumes a stash. The same stash can be popped into multiple harnesses concurrently.
2. Full-stash encryption at rest — transcripts are untrustworthy by default. Only the stash's AGENTS.md is plaintext, and only if it passes the scrubbing contract.
3. Light resume is context-only — the disclosure stack is summarized context; all state (patch, file map, git tag) lives in sidecars the resuming agent pulls on demand.
4. Operator-initiated — you stash only when the operator asks. Never auto-stash.
5. Fail loud — if a stash is missing, unreadable, un-decryptable, or its AGENTS.md violates the scrubbing contract, STOP and tell the operator. Never silently degrade, coerce, or fall back.

When the operator says "stash this session"