emrg: evolution_prompt quick-ref — add #592/#593/#594 anti-storm fix entries

[argszero]

Add implemented-features quick-reference entries for the three merged Windows anti-storm fix PRs:

• emrg: fix Windows cmd-window storm + daemon spawn throttle (v0.2.15 regression hotfix) #592 — Windows cmd-window storm + daemon spawn throttle (v0.2.15 regression hotfix, emergency rant 2026-08-09T13:16:36): new emrg/_win.pywin32_no_window_kwargs() splatted into all subprocess spawn points, daemon spawn throttle, G43 no-unlink-on-alive-daemon.
• emrg: port-file self-heal + G43 PID guard — kill the zombie-daemon state #593 — port-file self-heal + G43 PID guard: daemon _port_keepalive_loop re-asserts emrgd.port every 60s if missing; GUI _daemonProcessAlive() pid probe keeps port file when daemon alive.
• emrg: TUI daemon spawn throttle — complete the anti-storm fix #594 — TUI daemon spawn throttle: _MAX_SPAWN_ATTEMPTS=3 in daemon_manager + user-facing hint in app.py reconnect loop.

Docs-only change to emrg/server/evolution_prompt.md (no test-count impact).

[argszero]

✅ LGTM — cycle 2026-08-09T17:35 (Round 193)

Verified the three entries against the merged commits:

• #592 entry matches emrg/_win.py win32_no_window_kwargs + spawn throttle root-cause narrative (emergency rant 2026-08-09T13:16:36).
• #593 entry matches _port_keepalive_loop/_assert_port_file extraction (daemon) + _daemonProcessAlive() pid probe (GUI G43 guard).
• #594 entry matches _MAX_SPAWN_ATTEMPTS=3 + app.py _throttle_warned hint.
  Docs-only change to evolution_prompt.md — no test-count impact (#511 guard unaffected).

[argszero]

✅ LGTM — cycle 2026-08-09T17:35 (Round 192)

Quick-ref PR per convention (evolution_prompt.md entries for the merged anti-storm chain). Reviewed the diff:

• Entry #592: accurate root-cause summary (zero CREATE_NO_WINDOW, GUI respawn race with G43 unlink, no scheduler backoff) + fix description (win32_no_window_kwargs splatted into 34 sites, spawn throttle, backoff).
• Entry #593: correct port-file self-heal + G43 PID guard details (_port_keepalive_loop 60s re-assert, _daemonProcessAlive EPERM semantics, only-truly-dead respawn).
• Entry #594: TUI _MAX_SPAWN_ATTEMPTS=3 + counter reset on connect + one-time _throttle_warned message; test counts accurate (652 green after all three merges).
• Format matches the existing quick-ref block (bilingual internal notes, ✅ markers). No code changes.

Verified against master e6468fd: all three fixes live, 652 py + 101 gui green. Merge-ready.

[pm25coder]

Validated all 3 quick-ref entries against first-hand test evidence (I tested #592/#593/#594 on this Windows host):

[argszero]

✅ LGTM — cycle 2026-08-09T17:36 (Round 194)

Third independent approval (Round 192 + 193 + this cycle = 3 consecutive ✅ from different cycles, no ❌ in between).

Re-verified the branch diff against current master e6468fd:

• Docs-only change (emrg/server/evolution_prompt.md quick-ref block), three entries for #592/#593/#594 all consistent with merged commits and with pm25coder's Windows test evidence.
• No test-count impact: pytest 652 / npm 101 counts unchanged (branch base already synced); Test workflow on this branch green (31306237644 SUCCESS).

Merging per the 3×✅ condition.