Recovery and safe disclosure checklists
These are reader checklists, not automatic session tests. Checking a box records your own work; it does not mean a website inspected OMP, your files, or a provider.
Recovery checklist
When selection or transition behavior is uncertain:
- [ ] Stop adding work. Do not prompt the possibly wrong conversation.
- [ ] Identify the operation. Resume, continue, fork, fresh, clear, and new have different expected effects.
- [ ] Check the active session file. Do not rely on title or a success toast.
- [ ] Check persistent identity separately from provider identity. Use the saved session header for durable identity.
- [ ] Check directories. Inspect the active working directory and additional roots; distinguish them from an old header cwd.
- [ ] Account for queues and jobs. Fresh/fork can retain ordinary queues; clear/new discard them. Cancellation does not reverse completed file effects.
- [ ] Inspect the relevant journal. A reset boundary explains why old entries remain while current context is empty.
- [ ] Treat failure phase as evidence. A settings preflight failure, hook veto, guarded rollback, and post-commit reconciliation error are different outcomes.
- [ ] Use an explicit known target for recovery. Do not repeatedly try continue and hope recency chooses correctly.
- [ ] Preserve useful evidence privately. Do not clear or drop merely to make the screen look simpler.
If a persistence error leaves live messages ahead of disk, do not assume restart will recover those messages. If you need a diagnostic copy, treat any dump and sidecar as sensitive and review them locally. Do not publish a raw dump as a shortcut.
If cwd re-scoping fails, do not let tools operate while scope is uncertain. The parent terminal shell’s directory alone does not prove the OMP process and manager agree.
Safe disclosure checklist
Before forwarding any real packet outside its current trusted boundary:
- [ ] Name the recipient and purpose. Include only what that review requires.
- [ ] Identify the snapshot source. Live dump, file export, live export, default share, or custom HTML are not interchangeable.
- [ ] Inspect older history. Include pre-clear entries and alternative branches in the review scope.
- [ ] Inspect all nested content actually embedded. Do not stop at the parent’s task summary.
- [ ] Inspect header and metadata paths. Cwd, additional roots, titles, parent references, and other identifiers can disclose project or user information.
- [ ] Inspect system/tool data without republishing it blindly. Current prompts, tool descriptions, schemas, file mentions, and opaque metadata require deliberate handling.
- [ ] Inspect images and linked content. Text redaction does not inspect every pixel or authorize loading every external resource.
- [ ] Separate visibility from removal. Filters, collapsed sections, and blank viewers do not scrub embedded bytes.
- [ ] Inventory sidecars and clipboard copies. They may outlive the command and the session.
- [ ] Check effective sharing configuration and custom-handler presence. Review fallback destinations as well as the preferred destination.
- [ ] Treat redaction as assistance, not approval. Unknown strings can survive; no obfuscator can mean no typed redaction pass.
- [ ] Account for truncation. A smaller packet may omit crucial evidence without removing sensitive surviving content.
- [ ] Protect complete share links. The fragment key is access-bearing.
- [ ] Do not interpret cancellation as revocation. A started operation may finish after the UI returns.
- [ ] Hold the packet if inspection is incomplete. An authorized, manually written summary may be safer than forwarding an unreviewed full artifact.
No live sharing is part of completing this workbook.
Finish the three desks
You have reached the intended outcome when you can explain these decisions without relying on a status label:
| Situation | Sound conclusion |
|---|---|
| Maya knows yesterday’s full identity. | Resume that known target and check file plus project scope. |
| Continue returns an empty conversation. | Investigate breadcrumb/fresh-boundary/history availability; do not assume deletion. |
| Eli wants a second conversational direction. | Fork, while recognizing that workspace files remain shared. |
| Eli wants to retain the conversation but reset local provider state. | Fresh; do not claim a remote incident was repaired. |
| Eli wants an empty live conversation under the same persistent ID. | Clear; retained journal history still needs export review. |
| Noor needs the earlier Harbor Notes discussion. | Inspect saved/full history, not only post-clear live messages. |
| Noor’s blocked-CDN HTML shows only controls. | Use raw or decoded data inspection; the viewer is not self-contained offline. |
| A sharing loader says cancelled. | Treat upload/handler completion as unresolved, not revoked. |
Clean up only owned exercise material
LAB identifies the newly created temporary lab. RECEIPT identifies a separate temporary JSON receipt.
When finished, remove only the exact exercise paths you own and no longer need. The generated Review Packet HTML belongs to your disposable downloaded examples copy.
No automated cleanup command is supplied that could be mistaken for a real-session deletion instruction. Do not use /drop as workbook cleanup, and do not describe ordinary file removal as secure erasure.
Sessions, resets, and reviewable history · Source chapter: continuity/recovery-and-safe-disclosure-checklists. Original evidence remains scoped to its recorded snapshot.