week-endlisted

# Weekly Review (global, MCP-only) **Replaces the old project-local `/week-end`** (formerly at `Journals/.claude/skills/week-end/`, now archived at `Journals/.claude/skills-legacy/`, deferring to `Journals/PROMPTS.md`). Same reasoning as `sod/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. Rule changes belong at quarter boundaries (§13). **Instruments — resolved live via `get_active_instruments`, same as `sod/SKILL.md`.** Call it in Step 0 alongside the connectivity check and use its full pair codes for every subsequent MCP call — do not assume EU/GU/UJ/XAU (used here for readability only) is still the active set. ## Step 0 — confirm the MCP server is reachable, then resolve the active set Call `get_account_state` first. If it fails, stop — `just run` needs to be running in `webapp/` — and do not proceed as if anything here will be recorded. Then call **`get_active_instruments`** and use its result for the rest of this session. ## Step 1 — resolve the week **`date +%G-W%V`** (zero-padded, see `week-start/SKILL.md` for why this matters — an unpadded week number sorts wrong in every cascade read that follows), unless the pilot gives one explicitly. ## Step 2 — confirm the week's daily sessions are actually complete Call **`get_session_completeness`** (enough days back to cover