Fix M5.7 compaction and failure recovery

This commit is contained in:
dingo
2026-09-26 19:40:16 -04:00
parent 56f533c738
commit a2a12fdc69
6 changed files with 187 additions and 29 deletions
+4 -1
View File
@@ -82,6 +82,9 @@ and [the manifest schema](../../schemas/local-world-manifest.md). Two alternatin
manifest slots select immutable M5.6 snapshot/journal payloads. Recovery validates
the selected snapshot and optional journal into a detached store. The manifest
replacement is the local commit point; this provides no multi-host durability,
production lease, authentication or disaster recovery guarantee.
production lease, authentication or disaster recovery guarantee. Compaction while a
journal is active accepts only its byte-identical replay result, and poisoned handles
must reopen before recovery. Partial-write and post-replacement sync failures have
deterministic test injection.
M5.6 does not write files, fsync, delete journals, clear dirty state or recover a live
server process. M7 supplies the production durability/ownership path.