chore(sim): refresh deployment status, pool matrix, schemas, and scenario scripts

- deployment-status and pool-matrix snapshots aligned with validate-deployment-status.cjs.
- Micro-trade / scorecard docs and run-scenario wiring.

Made-with: Cursor

docs/04-bot-policy.md

@@ -33,6 +33,23 @@ When multiple quotes exist (USDT/USDC/DAI), the bot routes to the best edge:
 
 - If the bridge is congested or risk flags trip, bot widens bands / reduces exposure
 
+### 5. Gas-budgeted micro-support lane
+
+For selected wrapped USD rails, especially **cWUSDC** and **cWUSDT**, you can reserve a small gas budget for **micro-trades** against **USDC** / **USDT**:
+
+- Prefer matched-quote rails when they exist: `cWUSDC/USDC`, `cWUSDT/USDT`
+- Keep each trade tiny relative to `I_T^*`
+- Use inventory-aware direction first: sell cW into the pool when inventory is too low; buy cW from the pool when inventory is too high
+- If the pool is already near its inventory target, alternate tiny buys/sells only within a separate gas budget
+
+Purpose:
+
+- Give wrappers **observable turnover**
+- Tighten route discovery and quote confidence
+- Keep the support lane small enough that the PMM remains a **corridor defense tool**, not the primary venue
+
+Important: this improves **tradability and price discovery**, but it does **not** create backing or intrinsic value by itself.
+
 ## Peg bands
 
 See [../config/peg-bands.json](../config/peg-bands.json) and [05-oracles.md](05-oracles.md). Summary:

docs/12-sim-scorecard.md

@@ -29,6 +29,11 @@ Every run (hub-only, full-quote, bridge shock) should produce a scorecard with a
 | `intervention_cost_inject_total` | number | Bot inject (bridge-in) cost only |
 | `intervention_cost_withdraw_total` | number | Bot withdraw cost only |
 | `intervention_cost_by_chain` | object | Per chain: `{ inject, withdraw }` — which chains are liquidity sinks |
+| `micro_trade_count` | number | Count of gas-budgeted support trades executed |
+| `micro_trade_buy_count` | number | Support-lane buys of cW from the pool |
+| `micro_trade_sell_count` | number | Support-lane sells of cW into the pool |
+| `micro_trade_volume_total` | number | Base-token units rotated through the support lane |
+| `micro_trade_gas_cost_total` | number | Abstract gas budget consumed by support trades |
 | `scenario` | string | e.g. `hub_only_11`, `full_quote_1_56_137`, `bridge_shock_137_56` |
 | `runId` | string | Optional run identifier |
 
@@ -92,6 +97,14 @@ Compare deltas:
 
 If churn jumps >50% with full-quote → clear “don’t deploy full-quote” rule.
 
+For **gas-budgeted support scenarios**, compare:
+
+- **micro_trade_gas_cost_total** vs baseline intervention cost
+- **micro_trade_volume_total / micro_trade_count** to verify trades stay genuinely micro
+- **peak_deviation_bps_post_bot** vs the same scenario without micro-support
+
+If support gas rises faster than the deviation improvement you get back, the support lane is too aggressive.
+
 ---
 
 ## 4. Phase 0: Runnable scenarios and knob guidance