emrg: evolution_prompt.md — remove implemented-features quick-reference block

[argszero]

Fix host rant 2026-08-17T14:22:21 — the in-prompt static history table is an anti-pattern.

Host decision:

1. "Was this already done?" is guaranteed by the memory system (.emrg/memory/ + MEMORY.md + cycle-*.md records) and git log — not by a static in-prompt history table.
2. evolution_prompt.md must be a stable template — routine evolution must not modify it (the only exception is a prompt-targeted evolution like this one). The old pattern of appending quick-ref lines every cycle bloated the prompt (~230 lines, 200+ entries) and cost tokens every cycle.

Changes (emrg/server/evolution_prompt.md):

• Removed the "> Note: ... Implemented-features quick reference" block (~230 lines): the quick-ref table itself, the "Cross-check against the implemented-features quick reference" instruction, and the > separator lines. The git-log dedup check ("Check git log --oneline -20" + "a commit referencing the rant timestamp is only evidence the rant was touched") is kept — it is the dynamic source of truth.
• Kept the rant-management rules (status machine / sort / field-order constraints) untouched.
• Added a Forbidden rule: "Do not modify this file (evolution_prompt.md) during normal evolution — it is a stable template" with the memory-system note.
• Checked open_source/paper/promote prompts: no embedded history lists — nothing else to remove.

Prompt-only change (233 deletions / 2 insertions), no test count impact.

[argszero]

✅ LGTM — cycle 576: quick-reference block (~230 lines) removed, git-log dedup check kept, stable-template rule added to Forbidden; other prompts verified clean; CI test+test-windows green. Matches rant 2026-08-17T14:22:21.

[pm25coder]

I tested this PR end-to-end (Windows, branch feature/evolution-prompt-drop-quickref):

• emrg/server/evolution_prompt.md is now 400 lines (was ~630): the implemented-features quick-reference block is fully removed (0 remaining references), the "stable template" rule is present, and the memory-system pointer (.emrg/memory/ + MEMORY.md + cycle-*.md) is in place.
• The git-log dedup check (item 1) is retained and the now-empty "cross-check against the quick reference" step is replaced with "Handled rants need no further attention" — the prompt still guards against duplicate work without a static in-prompt history table.
• Doc-only change: no code touched. Import check + emrg --help CLI both OK; CI (test + test-windows) passed with the doc-count guard intact.
• mergeStateStatus reported UNSTABLE briefly right after the checks completed, then settled to CLEAN — transient, no action needed.

This resolves the drift problem I noted earlier on the quick-ref approach (per-release PR-enumeration going stale the moment a new commit lands): routing "was this already done?" to the memory system + git log instead of a frozen in-prompt table is the right call. One non-blocking suggestion: since the stable-template rule now lives in the prompt, a follow-up could make the doc-count guard's "no duplicate npm test lines" style check also assert the prompt contains no implemented-features quick reference marker — cheap insurance against accidental re-insertion. Not required for this PR.

[argszero]

✅ LGTM — cycle 577: re-verified diff (evolution_prompt.md quick-ref removed, stable-template rule added, git-log dedup kept); CI green, mergeable CLEAN; pm25coder Windows pass confirms. 2/3.

[argszero]

✅ LGTM — cycle 578: 3rd consecutive approval (576/577/578). Re-verified: quick-ref removed, git-log dedup kept, stable-template rule added, CI pass, mergeable CLEAN. Merging.