1b6e644ea6
Capture the plan to close the known gap: existing CAS/fencing tests run on MemoryDatastoreProvider (exact only for sequential calls), so single-winner behavior is not yet demonstrated under a true interleaved read->write window or against Cosmos _etag/If-Match. No production change expected; Cosmos provider already conditions writes with IfMatch. Documents Option B (adversarial interleaving test, no infra) and Option A (emulator-gated integration test), acceptance criteria, and downstream doc updates. |
||
|---|---|---|
| .. | ||
| cowork-service | ||
| extraction-service | ||
| mcp-server | ||
| monitoring | ||
| platform-service | ||