fix(streaming): stop replaying committed recenter retirements

Root cause: pending-only live projection buckets were misclassified as landblock presentation owners during origin recentering. That manufactured a second full cleanup receipt for a generation whose first receipt was still advancing; the duplicate guard threw and the broad retry path replayed the already-committed detach 243 times.

Keep pending live projections through the spatial identity map without issuing another receipt, and fail fast when a receipt-ledger invariant occurs after detachment. Evidence: docs/research/2026-08-02-collision-throughput-handoff/p1-retirement-receipt-loop.md. Release suite, lifecycle gate, and nine-stop soak pass.
This commit is contained in:
Erik 2026-08-02 20:53:11 +02:00
parent c65559d8f8
commit 01f4791e95
9 changed files with 309 additions and 9 deletions

View file

@ -1433,6 +1433,14 @@ public sealed class StreamingController
transaction.PreparationCommitted = true;
return true;
}
catch (StreamingMutationException error) when (error.MutationCommitted)
{
// The old spatial generation is already gone. Re-entering this
// transaction would replay the detach against a new state, so a
// committed receipt/adoption invariant is terminal and must be
// surfaced to the caller.
throw;
}
catch (Exception error)
{
Console.WriteLine(