freshness-check

Your PoE training knowledge has a **model-specific cutoff** and the game changes every league, so the biggest risk is an *unknown unknown*: confidently asserting a mechanic that changed or didn't exist yet. 1. Read [`reference_data/freshness_index.md`](../../../reference_data/freshness_index.md) and follow its "How to use it" procedure: - Identify the running model (`mcp__pob__get_context_usage` reports the model ID). - Look up that model's training cutoff in the index's model table. - Treat anything in the index **newer than the running model's cutoff as must-verify** — use the entry's "Where / verify via" pointer (a cached file, a memory, or a fresh `fetch_wiki_page` / live PoB call). 2. If the mechanic/item isn't in the index but is plausibly recent (current or last few leagues), **verify it anyway** and add a row to the index so the next session is covered. 3. **Scope filter (compartmentalization).** Also consult the mechanic-keyed companion [`reference_data/mechanics_index.md`](../../../reference_data/mechanics_index.md) for each mechanic's current **scope** (`core` / `challenge-league` / `event-only` / `removed` / `disabled-this-league` / `nerfed`). When the task concerns a **specific character**, first establish its context (league/realm, and whether it's an event character — see `playbooks/README.md` §2c), then **only apply mechanics whose scope includes that context**. A Mirage-only or event-only mechanic must not be recommended fo...