docs(operations): make the recovery cleanup safe to run after the snapshot volume

[Fl0p]

The What a recovery leaves behind section of the DuckDB recovery page predates the timed Parquet snapshots. That feature added a fourth cotel* volume on the host which is not a recovery leftover and is the only restore point there, but the page's cleanup table never mentions it. An operator following this page to delete leftovers therefore meets the backup with no guidance, and docker volume prune looks like a reasonable shortcut.

What changed:

• cotel-snapshots is now a row in the table, marked never-delete.
• Spells out what docker volume prune actually destroys in each direction: with the deploy up it takes the irreplaceable forensic original, with the deploy down it also takes the snapshots.
• The page no longer implies the step-2 ...-backup-... copy is already deleted. That deletion is one write on a host whose read-write access may belong to someone else, so it can sit undone. The page now tells you to classify a listed leftover by hash instead of inferring anything from its name.

Verified: npm run build in docs/ passes (VitePress fails the build on dead links). The documented classification loop was run read-only against the four live cotel* volumes: the two damaged twins return the same hash, the snapshots volume returns no database file, production's hash is unique. Production's /data mount was confirmed with docker inspect rather than assumed from the volume name.

🤖 Generated with Claude Code

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4ed22e0b-a10c-4d2c-9bca-3ce642e24e5e

---

📥 Commits

Reviewing files that changed from the base of the PR and between c0c36c5 and 06a0dcc.

---

📒 Files selected for processing (1)

• docs/operations/duckdb-recovery.md

---

 ______________________________________________________________________
< I see you chose the 'dynamic typing' difficulty setting. On purpose. >
 ----------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}