moai-meta-harness

# moai-meta-harness (DEPRECATED — redirect to v4) > **DEPRECATION NOTICE** — This legacy 7-Phase meta-harness is > **superseded by the v4 harness Builder** (`/moai:harness <natural-language > request>`). The v4 design replaces the static 7-Phase workflow with: > > - An **orchestrator-direct 4-phase Builder** (ANALYZE -> PLAN -> GENERATE -> > ACTIVATE) that holds the plan in Claude's session context and can call > AskUserQuestion at the PLAN->GENERATE approval gate (first-class boundary). > - A **manifest-driven dynamic-workflow Runner** (`hns-<name>-run.js`) that > reads `manifest.json` and dispatches specialists per their declared > `primitive` (sub-agent / dynamic-workflow / worktree / /goal / > adversarial-fan-out) — no heuristic re-derivation. > - **Conditional sub-agent-granular worktree isolation** (no mandatory > top-level worktree; worktree only for conflict-prone parallel generation). > - **Signal-driven phase synthesis** (not a fixed pipeline); the evaluator is > conditional (skipped for tasks within the model's solo reliable range). > > **To create a new harness**: issue `/moai:harness <natural-language request>` > (e.g., `/moai:harness build a harness for my-project's API development`). The > orchestrator runs Context-First Discovery on the request, derives a harness > `<name>`, and enters the Builder. Do NOT use the 7-Phase workflow below for > new harness creation. > > **What is preserved here**: the 7-Phase body below is retained as the > **redir...