codemux-featureslisted

# Codemux ADE Feature Implementation Guide Patterns and priorities for implementing features that make Codemux a complete Agentic Development Environment. This file tells you WHAT to build and HOW to approach it. For visual and CSS standards, read the `/codemux-ui` skill. For project architecture and current state, read `WORKFLOW.md` and `docs/INDEX.md` first. For OpenFlow orchestration patterns, read `docs/features/openflow.md` and `docs/plans/openflow.md`. ## Ground Rules 1. **Check before building.** Before implementing any feature, verify what already exists in the codebase. Search for related types, commands, components, and stores. Codemux has partial implementations of several features that should be extended, not duplicated. 2. **Work in branches.** Create a feature branch for any significant new feature. Name it `feature/<feature-name>`. 3. **Research before building.** Before implementing a feature that other ADEs have, research how similar tools approach it. Understand the pattern, then reimplement it for Codemux's Tauri + Rust + React + Tailwind + shadcn architecture. Do not copy code from other projects. 4. **Backend-first.** Codemux's architecture is backend-state-driven. Implement features in Rust first (state, commands, persistence), then expose via Tauri commands, then build the React UI. The frontend is a view of backend truth. 5. **Run verification.** After implementing, run `npm run verify`. For Rust changes, also run `cargo test --manifest-path sr