cm-terminallisted

# Terminal Process Monitoring ## Overview Running commands without checking output is flying blind. Users MUST see what's happening at every step. **Core principle:** Every command gets announced, monitored, and verified. No exceptions. **Violating the letter of this rule is violating the spirit of this rule.** ## The Iron Law ``` NO COMMAND RUNS WITHOUT READING ITS OUTPUT. NO ERROR GOES UNREPORTED. NO NEXT STEP WITHOUT PREVIOUS STEP CONFIRMED. ``` ## When to Use **ALWAYS** when running terminal commands via `run_command`. This includes: - Build commands (`npm run build`, `npm run dev`) - Test commands (`npx vitest run`) - Install commands (`npm install`) - Deploy commands (`npx wrangler pages deploy`) - Git commands (`git push`, `git commit`) - Any script or CLI tool ## The Protocol ### Step 1: Announce Before Running **BEFORE calling `run_command`:** Update `task_boundary` TaskStatus to describe what you're about to run and why. ``` TaskStatus: "Running npm build to compile production bundle" TaskStatus: "Installing dependencies with npm install" TaskStatus: "Deploying to Cloudflare Pages" ``` ### Step 2: Set Appropriate Wait Time Choose `WaitMsBeforeAsync` based on expected command duration: | Command Type | WaitMsBeforeAsync | Strategy | |-------------|-------------------|----------| | Quick (< 3s) — `git status`, `ls`, `cat` | 3000-5000 | Synchronous, read output directly | | Medium (3-30s) — `npm install`, `build` | 5000-10000 | Wait for initial output,