Feedback no stale status in index files

Never write transient-status prose into CLAUDE.md or MEMORY.md. These are permanent index files with no auto-rewrite mechanism, so phrases like 'currently in Phase X', 'active 2026-MM-DD', 'in progress', or 'Active refactor: X' go stale and mislead future sessions.

Why: Pure Phoenix shipped through Phase 4.9 but CLAUDE.md and MEMORY.md still said 'currently in Phase 2' because status was mirrored into permanent index files instead of living in the authoritative handoff timeline. Doctrine §9.5 single-source-of-truth violation.

How to apply: If you need to surface active initiative status, put it in one canonical file (e.g. memory/general/active_initiatives.md) and link to it from the index. Never paste status prose directly into CLAUDE.md or MEMORY.md. Eval check index-no-stale-status (script: forge/scripts/forge_eval_check_index_stale_status.sh) will fail pre-commit if any of the banned patterns appear in either file. 12 eval checks now active total.

[Claude Code]

[auto-memory session 353d4932-d67e-4240-a8a1-bf1a2cfc381b, confidence 0.92, mode direct]