snapshotlisted

# Snapshot Follow the [shared recording policy](../context/references/recording-policy.md) first. On a durable signal, resolve project settings once; only enabled owners participate automatically. User-approval instructions below describe `explicit` mode. In `auto` and `adaptive`, use policy authorization on the same validated write path; semantic attestations must remain truthful. Disabled features still allow explicit historical reads. SNAP is mutable resume context with `authority: staging`; it is not authoritative decision or evidence history. Apart from the shared recording policy, do not read `references/`, plugin manifests, `context/*.index.md`, or plugin scripts, and never run `--help`; the commands below are complete. Use the active language for user text and English for machine fields; preserve user-authored artifact prose. 1. Resume: when the user asks to continue earlier work without restating it, run one `snapshot list`, then `snapshot load --id <id>` for the matching SNAP, and continue from its Next steps and Open items under its stated constraints. Do not ask the user to restate what the SNAP already says. 2. Save only with unfinished context and handoff intent authorized by the user or configured recording policy. `save` is create-only and fills Current context, Open items, and Next steps; state the exact next step and any constraint the user gave. 3. `update` is full replacement unless deliberate `--merge`; `load.freshness` is only a warning. `discard` tar