month-endlisted

# Monthly Review (global, MCP-only) **Replaces the old project-local `/month-end`** (now archived at `Journals/.claude/skills-legacy/month-end/`). `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook — this is the first skill in the set to actually exercise §13's cascade rule for real: **this reads the level below (weekly rollups), not raw daily data.** If a specific number looks wrong, the §13 drill-down fallback still applies — open the underlying week's data via `get_daily_analysis`/ `get_compliance_scores` rather than guessing, but that's the exception, not the default path. **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. ## Step 0 — confirm the MCP server is reachable Call `get_account_state` first. If it fails, stop and explain `just run` needs to be running. ## Step 1 — resolve the month and find its weeks Use the current `YYYY-MM`, unless the pilot gives one explicitly. Call **`get_journal_rollups`** (`period: "weekly"`, `limit: 6` covers any calendar month with room to spare). From the returned rows, pick out the ones that belong to this month — **the convention: a week belongs to the month its Monday falls in.** State this explicitly if a week spans the boundary (e.g. starts in the prior month) rather than silently applying it; there's no single universally-correct definition for a week that spans two months, so being explicit about which c