eust-w a56882bedc ✨ Verify legacy SHA256-only archives and backfill their MD5 server-side
Archived heads from protocol v1 carry only a SHA-256 receipt, so every sync
that still holds those files ends partial and they can never be cleaned.

Add an administrator-approved digest backfill job run by the coordinator.
It reads each legacy object with conditional (If-Match) ranged GETs, hashes
MD5 and SHA-256 in one pass, cross-checks every surviving receipt (retired
head sha256, drosync object metadata, BOS stored digests), and records the
MD5 on the head with a compare-and-set write, a bound attestation and an
audit event. It never writes to BOS and never accepts a client digest.

The cleanup proof now accepts an object without drosync-md5sum metadata
only through an attestation bound to its live ETag, version and size. The
next ordinary sync plans those files unchanged, completes, and they become
cleanable; closed partial sessions are left untouched.

Includes the design doc comparing remediation options, store/coordinator/
API unit tests and an end-to-end recovery test on MemoryStore and fake
object storage. Nothing is deployed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 15:44:14 +08:00
..