First moveStop every writer, copy the complete Session directory, hash the original, and inspect only the copy. In Windows report #4855, one bad header prevented workspace initialization.

Route the exact signature.

01 / FRAMEfirst frame is not exactly one header line

Quarantine one artifact. Generic recompression changes the format.

02 / SEQUENCEseq gap in committed region

Find duplicate writers before touching durable event numbers.

03 / IDENTITYinvalid message or duplicate start

Identify the producer or reused call identity before editing a healthy frame stream.

04 / READolder history silently disappears

Capture request, response, base cursor, and durable range before believing exhaustion.

Startup wrapper, inner causeplugin tree failed to load identifies the workspace loader; first frame is not exactly one header line identifies the Session artifact. Isolate the latter before changing the launcher or deleting a profile.

Choose the least destructive outcome.

Restore the listQuarantine one Session
Preserve the recordExtract read-only history
Resume workStart a fresh Session
Repair exactlyUse a version-aware tool
Neverturn a failed page request into durable knowledge that history ended

Proof gates.

Primary evidence.

Keep the full recovery runbook.

The canonical guide includes physical framing, sequence, identity, projection, read-state boundaries, immutable evidence capture, and bounded recovery.

Read the complete guide