9. Preserve continuity without rebuilding history

Use current artifacts, tool queries, the conversation and PRs first. Keep one replaceable recovery note only when they cannot support continuation.

A useful recovery note distinguishes prepared work from executed changes, known results from pending checks, active operations from stopped ones, and local-only work from integrated work. It identifies the next useful action and material holds.

Inspect actual state before replaying an operation whose confirmation was lost. A new session does not release another worker's files or resources. Transfer ownership or confirm the operation stopped before assigning overlapping work.

Historical material remains available through Git and archive tags. Frozen products explains recovery of retired product trees. Restoring files does not reactivate a product or its old procedures.

When removing a worktree, establish that its commits are preserved and that no unique local work or active operation will be lost. Ignored files are not protected by commit history. Keep necessary recovery material outside the active project; do not publish private session data.