codemux-openflowlisted

# Codemux OpenFlow Runtime Standards Patterns and rules for working on the OpenFlow orchestration engine. This file covers the BACKEND runtime, not the UI (use `/codemux-ui` for visual work on OpenFlow components). For current OpenFlow state, read `docs/features/openflow.md`. For active work priorities, read `docs/plans/openflow.md`. For project architecture, read `docs/reference/ARCHITECTURE.md`. ## Ground Rules 1. **Read the current docs first.** OpenFlow changes fast. Always read `docs/features/openflow.md` and `docs/plans/openflow.md` before making changes — they reflect what actually works today. 2. **The backend drives orchestration.** A tokio background task runs the orchestration cycle. The frontend observes via events. Never move orchestration logic to the frontend. 3. **Comm log is the protocol.** Agents communicate through the shared comm log. All phase decisions are based on parsing the comm log. There is no side-channel. 4. **Test with real agents.** OpenFlow logic cannot be verified by unit tests alone. After changes, test with real agent runs using at least 2-3 agents. 5. **Run verification.** `cargo test --manifest-path src-tauri/Cargo.toml` for backend, `npm run verify` for full pass. --- ## Architecture Boundary OpenFlow is integrated into Codemux but maintains a separate runtime boundary: - Runtime logic lives under `src-tauri/src/openflow/` - Orchestration state lives in `OpenFlowRuntimeStore` and `AgentSessionStore` - OpenFlow workspaces are r