d78e1e1277
The two-record assertion in CompensationRunCancelledMidReplay pins a bug whose root cause is in Bpmn.Semantics, not in this host, so the tracker that will actually move is valence-works/bpmn#13. #7959 stays named as provenance -- it carries the decompiled evidence and the routing rationale -- but is closed as routed upstream, so it is no longer the thing to watch. Also records what the current comment did not: both counts become 1 when the fix lands, and the flip may not be mechanical. Upstream is choosing between tearing down only the compensation handler it re-starts and tearing down every abandoned token, and the second also cancels transaction branches still in flight, which can move other scenarios in this suite. Comment-only. The assertions and the applier are deliberately unchanged. Co-authored-by: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| component | ||
| integration | ||
| performance | ||
| TlsSmoke | ||
| unit | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||