Tighten MEV rollout verification and deploy timeouts

docs/04-configuration/MEV_CHAIN138_ALL_MAINNET_ROLLOUT_TRACKER.md

@@ -39,9 +39,11 @@ It is intentionally split into:
   - `cWUSDC/USDC` reserve imbalance `7227 bps`
   - `cWUSDT/USDT` reserve imbalance `5025 bps`
   - `cWUSDC/USDT` reserve imbalance `7956 bps`
-  - `cWUSDT/cWUSDC` token resolution incomplete (`quote` token missing)
-- Additional public pools returned reserves, but the readiness gate ended with:
-  - `5 hard failure(s), 0 warning(s)`
+- `2026-04-14` repo-side inventory fix landed for `cWUSDT/cWUSDC` quote-token resolution in
+  `scripts/verify/check-mainnet-pmm-peg-bot-readiness.sh`.
+- Re-run result after the fix:
+  - `cWUSDT/cWUSDC` now resolves and reads healthy reserves
+  - readiness gate now ends with `4 hard failure(s), 0 warning(s)`
 
 This means Mainnet public PMM operation is not yet in a fully healthy state even
 though large parts of the deployment inventory exist.
@@ -144,7 +146,6 @@ though large parts of the deployment inventory exist.
    - rebalance `cWUSDC/USDC`
    - rebalance `cWUSDT/USDT`
    - rebalance `cWUSDC/USDT`
-   - fix `cWUSDT/cWUSDC` token-resolution/inventory drift
 6. Publish the final ALL Mainnet native venue matrix before trying to wire full MEV discovery there.
 
 ## Truthful Completion Condition