docs: Define fresh-Tails handoff

[BenWestgate]

What

Replace the full-Persistent-Storage clone instructions with a short fresh-Tails handoff procedure. The recipient owns their Tails installation and Persistent Storage, while any optional data copy is an explicit choice.

Why

A whole Persistent Storage clone can transfer wallet ciphertext, configuration, logs, and identifying state. A handoff should transfer only authenticated CipherStick software plus data the person performing the handoff deliberately selects.

Closes #213

Testing

• git diff --check
• verified the added local documentation links resolve

[BenWestgate]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: def702c112

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[BenWestgate]

Reworked this onto the concise documentation stack. The PR now has one focused commit: fresh Tails, recipient-owned Persistent Storage, authenticated CipherStick software, and only explicitly selected optional data. Full Persistent Storage cloning is no longer recommended. git diff --check passes.

[BenWestgate]

AI-generated review (Claude), posted at the maintainer's request.

Not ACKing dde05c3: one factual error.

• "Bitcoin Core validates the copied data when it starts" is wrong. At startup Core only re-verifies the last few blocks (-checkblocks, default 6), so a chainstate/ copied from a compromised node is used as-is. The removed sentence ("If you don't trust this node is not compromised, do NOT do this") was the accurate one; restore it. HANDOFF.md:15 needs the same caveat.
• The fresh-Tails handoff and dropping the Tails Cloner backup look right otherwise. Needs the #226 rebase too.

[BenWestgate]

AI-generated review, posted at the maintainer's request.

ACK aca6ad5. The copied-chainstate trust warning is restored in both the FAQ and handoff guide; Lint CI is green. Ready for human review after its parent #227.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aca6ad50cd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[BenWestgate]

AI-generated review, posted at the maintainer's request.

ACK b8b38fe. The copied-chainstate trust caveat is restored in both guides and the fixup history is squashed cleanly. This head has the same tree that passed Lint CI before the squash. Ready for human review after #227.

[BenWestgate]

Codex current-head review at 52bcf84: no findings. The handoff docs explicitly avoid whole-Persistent-Storage cloning, require authenticated software before execution, scope optional data copies path-by-path, and call out the current signed-release prerequisite.

[BenWestgate]

AI-assisted current-head review, posted at the maintainer's request.

ACK 453567f. The outstanding handoff comments are addressed: recipient storage is created by normal setup, and node-data copying requires both source and destination Core shut down. Lint is green.