chore(memory): remove flynn-related notes

memory/2026-03-05.md

@@ -37,18 +37,6 @@
 - Updated SKILL.md with experimental findings, recommended defaults by use case, cost profiles.
 - New TODOs added: unify debate/parallel flows, test 2-round sufficiency, test mixed model tiers.
 
-## Flynn council pipeline — fix plan written
-- Reviewed Flynn codebase (`~/flynn/src/councils/`): orchestrator, types, scaffold, preflight, tool all exist. Unit tests pass (mocked). Never run against real models.
-- Pipeline architecture: dual D/P groups (freethinker + arbiter + optional grounder each), bridge exchange between groups, meta arbiter merge, full trace/conversation logging.
-- Created `memory/plans/flynn-council-fix.md` — 5-phase plan:
-  1. Config & agent setup (define 5 required agents in config)
-  2. Structured output compatibility (JSON schema support varies by provider)
-  3. Bridge & cap validation (defaults may be too tight for real output)
-  4. End-to-end run with real models
-  5. Integration with zap (CLI command or ACP agent)
-- Will wants to keep zap's "light" council skill AND have Flynn's deterministic pipeline available for delegation.
-- Work to happen on feature branch `fix/council-pipeline`.
-- Estimated effort: 1-2 focused sessions.
 - 2026-03-05T21:36Z: Ran `openclaw security audit --deep` on request to clear stale-audit warning.
   - Result: 1 critical, 2 warn, 1 info.
   - Critical: plugin `acpx.bak` code-safety issue (dangerous exec pattern).