docs: reconcile plans/ status against actual code state

Audited all 10 active plan docs against the codebase (not just commit
titles). 5 were fully shipped and stale-tagged "Planned"/"In Progress" —
moved to done/ with verification notes. The other 4 got corrected
Planned→In Progress status plus concrete remaining-gap notes so the next
pass doesn't re-derive what's already done.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

plans/2026-07-10-general-gated-execution.md

@@ -1,6 +1,13 @@
 # 2026-07-10 — General gated execution: from fixed actions to unlimited-but-gated
 
-**Status:** Planned
+**Status:** In Progress — audited 2026-07-11. Done: `ClassifyCommand` risk
+classifier, general `run` MCP tool, chat-assent approval (no button
+required), blast radius on approval cards, session digest, global activity
+feed (`Ops.svelte` "Executions" tab, risk-badged), Learning view
+(success-rate trend). Still open: retire the fixed `request_execution`
+action enum (`restart, systemctl, pct_exec, apt_upgrade, pct_create` still
+hard-coded alongside `run`), and revive auto-act — `internal/actuator/actuator.go:125`
+is still a literal `{"success": true, "message": "stub execution"}` stub.
 
 ## Goal