Remove the automatic bootstrap purge path that deleted persisted conversation data whenever the session file path changed. Rotation now only invalidates the stored bootstrap checkpoint and reconciles forward from the existing conversation state, preserving messages, summaries, lineage, and context items.

Update the rotation regression tests to assert that existing conversation state survives file changes and that only the missing tail messages are imported after rotation.

Regeneration-Prompt: |
  Lossless Claw should never delete persisted conversation history just because
  the backing session JSONL file path changes. We already traced a production
  data-loss incident to the rotation handling added in PR #366: on file-path
  mismatch, bootstrap hard-deleted messages, summaries, context items, lineage,
  and telemetry, then rebuilt from the new file. The earlier fix kept the full
  rotated transcript during reseed, but that still left an automatic destructive
  purge in the code, which violates the product contract that lossless is
  lossless unless the user explicitly invokes a destructive command.

  Remove the purge-on-rotation behavior entirely while keeping rotation
  detection/logging. Treat a rotated file as another transcript source for the
  same conversation: invalidate the old bootstrap checkpoint and reconcile from
  the persisted conversation state so only genuinely missing tail messages are
  imported. Preserve existing summaries and context items. Update regression
  tests to prove that file rotation does not wipe conversation history and does
  not reapply the first-bootstrap budget cap to an existing conversation.

* fix: replay full transcript after session rotation

Session-file rotation was purging the existing conversation and then reseeding it through the normal first-bootstrap cap. That left only a small suffix of the rotated transcript in LCM, which in turn made assembly fall back to live context while incremental compaction and manual compaction still evaluated the truncated persisted state.

Treat rotation reseeds as full transcript replacements instead of first-time bootstraps so LCM keeps coverage parity with the live session. Add a regression test that uses a tiny bootstrapMaxTokens value and verifies a rotated transcript is replayed in full.

Regeneration-Prompt: |
  User reported that a live lossless-claw session showed enormous actual context usage, but incremental compaction and /compact both believed the conversation was comfortably under target. Logs showed the session repeatedly falling back to live context while compaction decisions reported rawTokensOutsideTail=0.

  Trace the mismatch through bootstrap, assemble, and compaction. The key production clue is a session-file rotation event followed by an initial import that only reloaded a tiny suffix of a much larger rotated transcript. Preserve the intended first-bootstrap cap for genuinely new conversations, but do not reapply that cap when a known conversation is being reseeded after session-file rotation. In that case, replay the full rotated transcript so persisted LCM coverage matches the live session again. Add a focused regression test that would fail if rotation reseeds were trimmed by bootstrapMaxTokens.

* fix: stop purging history on session rotation

Remove the automatic bootstrap purge path that deleted persisted conversation data whenever the session file path changed. Rotation now only invalidates the stored bootstrap checkpoint and reconciles forward from the existing conversation state, preserving messages, summaries, lineage, and context items.

Update the rotation regression tests to assert that existing conversation state survives file changes and that only the missing tail messages are imported after rotation.

Regeneration-Prompt: |
  Lossless Claw should never delete persisted conversation history just because
  the backing session JSONL file path changes. We already traced a production
  data-loss incident to the rotation handling added in PR #366: on file-path
  mismatch, bootstrap hard-deleted messages, summaries, context items, lineage,
  and telemetry, then rebuilt from the new file. The earlier fix kept the full
  rotated transcript during reseed, but that still left an automatic destructive
  purge in the code, which violates the product contract that lossless is
  lossless unless the user explicitly invokes a destructive command.

  Remove the purge-on-rotation behavior entirely while keeping rotation
  detection/logging. Treat a rotated file as another transcript source for the
  same conversation: invalidate the old bootstrap checkpoint and reconcile from
  the persisted conversation state so only genuinely missing tail messages are
  imported. Preserve existing summaries and context items. Update regression
  tests to prove that file rotation does not wipe conversation history and does
  not reapply the first-bootstrap budget cap to an existing conversation.