month-startlisted

# Month-Ahead Scan (global, MCP-only) **Replaces the old project-local `/month-start`** (now archived at `Journals/.claude/skills-legacy/month-start/`). Same reasoning as `week-start/SKILL.md`'s header. `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook. **If anything this session suggests a rule should change**, per CLAUDE.md §20.14: add it to CLAUDE.md §21.3, do not act on it. **This still sets context only — same constraint as `week-start`.** No verdict, thesis, or hypothetical here; those only originate from `/sod`. **Persists nothing to `journal_rollups` either** — checked the old system first: `month-start` never wrote a file there (unlike `week-start`'s `week_ahead_scan.md`), so there's no `monthAheadScanMd`-equivalent field to write to. This session exists to inform the pilot, not to leave a record of itself. **It does, as of 2026-08-25, produce a real monthly technical score and fundamental digest** for the heatmap (`write_technical_score`/`write_fundamental_digest`, timeframe `1M`) — that's scoring, not a trading decision. **As of 2026-08-30, it also writes validated levels** (`write_level`, timeframe `1M`) for any zone from Step 4.2 that clears §3.3's validation bar. ## Step 0 — confirm the MCP server is reachable, then resolve the active set Call `get_account_state` first. If it fails, stop and explain `just run` needs to be running. Then call **`get_active_instruments`** — do not assume a fixed instrument set for S