A storage outage during startup could become an empty registry model, allowing a later mutation or flush to overwrite existing metadata, auth, PHP, Zig, analytics, or build-status snapshots after storage recovered.
Only typed S3 NoSuchKey initializes an empty snapshot. Other failures propagate, writes require hydration, and production startup awaits its durable stores. Build-status and coverage writes additionally require both loaded snapshots to be applied; either partial-load failure preserves the stored bytes. A healthy retry retains existing and newly recorded events. Existing debounce and serialized-write behavior is preserved.
Validation: normal registry CI first reproduced nine snapshot failures (708 pass / 9 fail), then the two partial build-status failures (717 pass / 2 fail). Final run 39149171809 passes 719 tests with 4834 assertions on both Bun 1.4.2 and 1.4.3, plus full workspace lint/typecheck and registry/scanner builds.
The broader Pantry CI on this isolated branch is blocked before its tasks execute by the existing manifest requesting retired Zig 0.17.0-dev. Integration is coordinated with the verified producer candidate that corrects that manifest. Main promotion and normal deployment must verify the complete combined candidate; no tool pin or security check is bypassed here.