helix-tdd-fixlisted

# Helix TDD fix loop Use this loop only when the defect can be reproduced deterministically. Its first production edit is forbidden until a focused regression test has proven red. ## Required launch protocol 1. Treat `$ARGUMENTS` as the exact bug and expected behavior. If empty, ask and stop. 2. Read repository rules and identify the exact repository-relative Git-visible test paths, narrow reproduction argv, and final verification argv. All are user-confirmed bounded values. Accept at most one leading `./`; after removing it, reject ignored, absolute, empty-segment, dot-segment, backslash, and `.git` paths. Each argv must begin with a PATH-resolved executable name without `/`, `\\`, or a leading dash; pass repository scripts to an interpreter. The reproduction argv must address the exact test paths the trusted operation may create or replace; directory-name or filename heuristics are never an authorization boundary. 3. Select `mode`: `original` by default, or explicit `graph`. Original uses `${CLAUDE_PLUGIN_ROOT}/workflows/helix-tdd-fix.js`; graph uses `${CLAUDE_PLUGIN_ROOT}/workflows/graph/helix-tdd-fix.js`. If a supplied mode is neither exact `original` nor exact `graph`, stop before doctor, evidence-session, or Workflow invocation. Configure `reproductionPasses` (`1..2`, default `2`), `maxPasses` (`1..5`, default `3`), and optional models for `reproducer`, `builder`, `tester`, `documenter`, `reviewer`, and `verifier`. 4. Run `node "${CLAUDE_PLUGIN_R