Complete M7.5 durable batch outcomes and commit resolution

ADR-0063: manifest v2 (360 bytes) binds a per-tick validation trace
object and a canonical decision block by SHA-256. Publication replays the
trace from the committed predecessor's verified payload and requires
every report and the candidate bytes, derives deaths deterministically,
uploads payload and trace with verified read-back, then sends manifest
and decisions to one fenced statement. RegionBatch seals at a terminal
transition or 64 ticks and refuses ticks until durable confirmation.

Schema v5 records the checkpoint, its decisions and outbox rows
atomically; a unique index keeps one terminal outcome per actor
(EVL08), triggers make commits/decisions immutable (EVL09), an exact
retry of a committed ID returns the original receipt, changed bytes
conflict, and read-only resolve_region_commit answers committed/absent/
conflict. Outbox pending/acknowledge give idempotent at-least-once
delivery. Recovery reconciles durable deaths with restored lifecycle
(and archive deaths for the lineage profile).

Validated: Windows CTest 58/58; Linux GCC Debug/Release, clang-tidy and
ASan/UBSan CTest 58/58 each; PostgreSQL suites Release, analysis, ASan
(lost response, committed-after-timeout, terminated orphan retry,
changed bytes, repeated/partial/reordered decisions, gap, outbox
redelivery, history quarantine); five mutations each caught. No
Docker/Gitea CI, process kill, broker or deployment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-28 17:30:30 -04:00
co-authored by Claude Opus 5.5
parent a2c4543df2
commit dd7e8028b0
27 changed files with 2075 additions and 216 deletions
+15
View File
@@ -186,3 +186,18 @@ archive codec and the `environmental-lineage-v1` profile validate:
- the living set, identity high-waters and retained dead members.
Recovery restores all of these. Durable history rows (M7.5) and process-kill
recovery (M7.7/M7.9) remain before the retained-ancestry exit claim.
M7.5 (ADR-0063) executed its rows against real PostgreSQL:
- A rejected publication (repeated death, partial or reordered decision block,
gap) leaves the head, commits and decisions unchanged. Publication is a single
statement; an injected failure between insert and commit is not yet tested.
- A lost response resolves to the original receipt, and an exact retry adds no
second death.
- A client timeout while queued resolved as committed after the lock cleared,
and was adopted.
- A terminated orphan resolved as absent and was retried with the same bytes.
- Changed bytes conflict.
- Outbox redelivery is idempotent and never touches the simulation.
Recovery now reconciles durable deaths with the restored lifecycle, so the
checkpoint and durable history must agree. Kill tests at each boundary remain
M7.7.