corezoid-process-optimizer

# Corezoid Process Optimizer ## Mode and scope detection Determine **mode** and **scope** from the user's phrasing before doing anything else. ### Mode | User intent | Mode | |-------------|------| | "optimize", "apply", "fix", "improve" — action verb | **AUTO** — analyze, plan, execute | | "show", "what can", "suggest", "check" — analysis verb | **PLAN** — analyze, report, wait | In PLAN mode, after presenting the report ask: > "Apply all? Apply by group? (1 — tacts, 2 — data, 3 — naming, 4 — resilience)" ### Scope The user may request a specific optimization group. Detect from keywords: | Keyword(s) in request | Scope — run only | |-----------------------|------------------| | "tacts", "tact", "state changes", "nodes", "merge" | Group 1 | | "data", "payload", "cleanup", "garbage", "fields" | Group 2 | | "names", "naming", "titles", "readability", "descriptions" | Group 3 | | "resilience", "semaphors", "timeouts", "stability" | Group 4 | | No group keyword — general request | All groups | If scope is a single group — run Phase 1 analysis only for that group. Skip all others entirely. Still run `lint-process` first (its findings feed Group 1 regardless). Examples: - "optimize by tacts" → AUTO + Group 1 only - "show tact optimizations" → PLAN + Group 1 only - "add missing semaphors" → AUTO + Group 4 only - "optimize" → AUTO + all groups --- ## Step 0 — Resolve process Resolve `PROCESS_PATH` before calling any tools: 1. Check if the user provided a path, name, or I...