plugin-test-cycle

# Plugin Test Cycle End-to-end workflow for building, deploying, and testing the typemux-cc plugin locally. This eliminates the repetitive manual steps that are easy to forget or get wrong. ## Prerequisites - Rust toolchain installed (`cargo`) - Claude Code running - A Python project with `.venv/` available for testing (e.g., rcmr_stadium subprojects) ## Workflow ### Step 1: Build the binary Ask the user which version to build, or whether to just test the current code without bumping. **Option A — Build without version bump (quick iteration):** ```bash cargo build --release ``` The binary is at `target/release/typemux-cc`. **Option B — Build with version bump:** Use the `/publish` skill instead, then return here at Step 2. ### Step 2: Record the test state Create a resumable state note before changing Claude Code's plugin state. Record: - repository path, branch, and commit - whether the working tree is dirty - test mode (local build or GitHub release) - `target/release/typemux-cc --version` - `shasum -a 256 target/release/typemux-cc` - expected marketplace source and plugin version - each completed workflow step and its result Store the note outside the repository, for example at `/tmp/typemux-cc-plugin-test-state.md`, so it survives a restart without adding an untracked project file. Never record credentials or environment variable values. ### Step 3: Approve plugin state changes Cache deletion, marketplace registration changes, and plugin installation muta...