Record launch readiness blockers

SESSION.md

@@ -89,6 +89,12 @@ Continue the trading-module mainline in autonomous mode until `Real-time Assiste
 - Final remote smoke passed:
   - `/trading/live-readiness`
   - workbench `Live Readiness` panel visible
+- Completed launch-readiness hardening pass:
+  - `/trading/launch-readiness`
+  - `scripts/run_launch_readiness.py`
+  - workbench `Launch Readiness` panel
+  - explicit split between `assisted_trading_ready` and `real_live_ready`
+  - stable `news_state` via provider chain + cached snapshot fallback
 
 ## Current Working State
 
@@ -129,5 +135,7 @@ npm run visual:snapshots
 - If `192.168.3.73:10808` is unavailable, market truth will degrade.
 - If OKX read-only credentials are changed or revoked, broker state will degrade.
 - Current remote account has `0` recent fills, so live reconciliation is verified as a clean no-op; the import path itself is covered by focused tests and the runtime/manual reconcile flow.
-- `news_provider` can still go stale because the public feed returns `429`; this is now surfaced correctly but not yet hardened with a more reliable source.
-- `ready_for_real_live` is still intentionally `false` because the OKX order adapter remains placeholder-only. That is the correct current boundary, not a hidden failure.
+- Launch readiness now reports the remaining assisted-trading blockers explicitly:
+  - `trust_model_available`
+  - `real_trade_sample_verified`
+- `real_live_ready` remains intentionally `false` because the OKX order adapter is still placeholder-only. That is the correct current boundary, not a hidden failure.

TASKS.md

@@ -20,7 +20,8 @@
 
 ## Blocked
 
-- [ ] No active blocker
+- [ ] `trust_model_available`
+- [ ] `real_trade_sample_verified`
 
 ## Done