Resume Cyd Bluesky archive imports without partial account mutation

[micahflee]

Note

In this issue, “version 2” and “v2 archive” mean version 2 of the Cyd Bluesky archive contract. Cyd archive formats and version histories are platform-specific; this issue does not define version 2 for X, Facebook, Mastodon, or any other platform.

Parent

• Add full Bluesky platform support with mobile-compatible archives #672

What to build

Large Cyd Bluesky archive v2 imports can resume safely while maintaining an all-or-nothing boundary around the live local account.

Acceptance criteria

• Extraction, validation, hashing, copying, and merge preparation resume after interruption.
• Staged data is invisible until final commit.
• Cancellation, corruption, resource abuse, or disk exhaustion leaves the live account unchanged.
• Preflight and streaming checks report expansion, capacity, and uncertainty; large legitimate Cyd Bluesky archives proceed after confirmation.
• Staging size is visible and cleanup cannot touch live or other-account data.
• Real-ZIP restart and failure tests prove recovery and absence of duplicate merge effects.

Blocked by

• Securely read and import a complete Cyd Bluesky archive v2 #680
• Preview and merge Cyd Bluesky archive v2 by Bluesky identity #681

(This was written by an LLM.)