refactor: update the docs

Author: 0xisk

README.md

@@ -176,7 +176,7 @@ yarn test:integration
 make env-down   # when finished
 ```
 
-**Expect this to be slow.** Each `describe` typically deploys a fresh contract and the genesis-funded wallet syncs against the local indexer (~30s per fresh deploy) before transactions can be submitted. The full suite takes **~40–45 minutes** wall-clock end-to-end.
+**Expect this to be slow.** Each `describe` typically deploys a fresh contract and the genesis-funded wallet syncs against the local indexer (~30s per fresh deploy) before transactions can be submitted. The full suite (15 spec files, ~50 tests) takes **~60–65 minutes** wall-clock end-to-end.
 
 The dominant cost is per-describe wallet sync; iterating on a single spec is much faster than running everything. Filter to one file via vitest's `--config` invocation directly if you're in `contracts/`:
 

contracts/test/integration/README.md

@@ -26,6 +26,6 @@ Working record of what we've learned about Compact's CMA / VK upgrade pathway fr
 | Q7 | `ReplaceAuthority` mixed with other `SingleUpdate` kinds in one bundle? | ✅ | Chain rejects in both orderings (`Custom error: 117`). Together with Q2, suggests the rule "any bundle containing a `ReplaceAuthority` must contain *only* that one SU." Pinned in `mixedBundle.spec.ts`. |
 | Q8 | Cross-contract signature replay (sign for A, address to B)? | ✅ | Chain rejects — `dataToSign` is address-bound. Pinned in `crossContractReplay.spec.ts`. |
 | Q9 | Empty-committee `ReplaceAuthority(committee=[], threshold=1)` accepted by chain? | ✅ | No. Chain rejects at submission (`Custom error: 117`). The "abandoned-key" workaround in `freeze.spec.ts` is therefore the only viable freeze pattern. Pinned in `emptyCommitteeFreeze.spec.ts`. |
-| Q10 | VK-only multi-update bundles on **different** ops (Insert+Insert, Remove+Remove, Insert+Remove)? | (pending run) | Tested in `multiVkBundle.spec.ts`. Pinning policy: assertions assume entire success (chain accepts the realistic upgrade path). Update this row after first green run. |
+| Q10 | VK-only multi-update bundles on **different** ops (Insert+Insert, Remove+Remove, Insert+Remove)? | ✅ | All three shapes accepted entirely (`status: 'SucceedEntirely'`). Confirms the realistic multi-circuit upgrade path. Combined with Q2 / Q4 / Q7, the bundle-shape rules now read: VK-only bundles work on different ops; same-op multi-insert atomic-reverts; any bundle containing a `ReplaceAuthority` must be solo. Pinned in `multiVkBundle.spec.ts`. |
 
 Status: ✅ Answered · ◐ Partial · ⏳ Open