Repository navigation
test(subscriber): prove atomic rollback when dispatch compensation fails - #54
Conversation
…actional rollback
2026-11-11 03:20 UTC — isolated exact-source fault-injection execution (no release)New draft PR #54 at Independent native isolated test: A fresh temporary workspace on FORGE copied exactly 457 Executed Hosted CI: run 42951811240 is in progress at last read; full deterministic suite running. Do not count hosted CI as passed until terminal success. This remains an isolated test-only draft, not signed production certification; independently review multi-process stress, audit redaction, large orphan sets and rollback coverage before integration. |
Scope
Two isolated SQLite failure-injection regressions for the combined dispatch-recovery candidate. Builds on test-only PR #53 (which itself targets combined PR #49); keeps all production and existing source unchanged. No protected runtime operation.
Isolation and reproducibility
Exact base
3dcd40bd1db8694b5843e034c0333f1d1e9b0924(PR #53), head6cb0c9b0dfca33357cf7f8e7c6caa6671a383b78, one new filetests/test_dispatch_compensation_atomicity.py(91 lines). GitHub compare: one commit ahead, zero behind, zero existing source changes; blob reread2ab1b25b019239b720a936a10fef14c7b1c2d18b.Held gates
Exact-head hosted CI and independent review required before integration. A passing test does not certify multi-process recovery, large orphan sweeps, audit redaction, production backups or signed
PRODUCTION_READYattestation. Do not auto-merge or deploy.