Export recoverable Bluesky data with a release-disabled Cyd Bluesky archive v2 writer

[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

Desktop can build a self-contained Cyd Bluesky archive v2 snapshot for one local account while user-visible export remains disabled until compatible readers ship.

Acceptance criteria

• Export captures a consistent interchange database/media snapshot for exactly one account.
• The ZIP contains version/identity metadata, unique digest-addressed media, and normalized path/size/SHA-256 manifest entries.
• Records, context, deletion state, expected assets, profile, and portable settings are included.
• Credentials, schedules, jobs, logs, diagnostics, errors, caches, temporary data, paths, and UI state are excluded.
• Incomplete backups export recoverable data and retain honest missing-asset state.
• The UI warns that Cyd Bluesky archive v2 content is plaintext.
• Preflight and resumable staging support large exports.
• Canonical semantic tests read every category, full video, incompleteness, exclusions, and integrity.
• Desktop offers no v1 writer, and the Bluesky v2 writer stays release-disabled.

Blocked by

• Define the normative Cyd Bluesky archive v2 contract and fixtures #675
• Save and browse public Bluesky records offline #676
• Save and browse Bluesky conversations offline #677
• Preview and merge Cyd Bluesky archive v2 by Bluesky identity #681

(This was written by an LLM.)