[Transactions] Atomicity violation related to Silo eviction

[dan-terry-antithesis]

Using nightly packages: 10.0.0-nightly.20260531.2. Commit Hash: edeedb2

I'm an engineer at Antithesis testing Microsoft Orleans's atomicity guarantee using a simplified bank test. We found an atomicity violation in Orleans 10.1.0 that was recently addressed by Orleans maintainers with PR #10123. We retested using nightly packages containing that merged PR, and we believe we have found a different atomicity violation.

This particular atomicity violation appears to occur when a silo is evicted and commits suicide while a transaction involving the silo is in progress. Please see these logs for an example.

atomicity_violation_10.0.0-nightly.20260531.2.log

[ReubenBond]

Fixed on current main by the transaction recovery work merged in:

• fix(transactions): improve recovery liveness and diagnostics #10374: manager-owned single abort fan-out, cancellation dispatch before publishing the abort decision, bounded deactivation cleanup, adaptive/idempotent recovery pings, and deterministic silo-loss coverage at manager-wait, durable remote-prepare, and durable local-commit-before-confirmation phases.
• fix(transactions): isolate failed storage writes #10375: copy-on-write isolation for failed or ambiguous transactional storage writes.
• fix(transactions): harden Azure Table transactional state storage #10376: Azure Table transactional storage fencing and mandatory reload after failed mutation.
• fix(transactions): harden confirmation recovery handling #10382: authoritative confirmation/collection recovery ordering and single recovery per storage-work cycle.

Current-main validation passed the issue-specific recovery tests, 30 focused recovery/queue/confirmation tests, and 154 transaction-category tests. Closing as fixed.