code-test

# code-test > **Stage-session entry (`standard+` dispatch, spec/stage-dispatch SD-2)**: Run in-session or as an isolated dispatch-depth-2 stage worker dispatched by the `autopilot-code` conductor. Read the verification section in `plan.md` and marks in `checklist.md` from disk; never depend on prior-stage conversation. Source is read-only in this stage. The write class is `test_logs/` and `_internal/test_reviews/`. The stage runs as the `qa/test` unit (the node's unit); it dispatches no units itself. > **Plan resolution**: Treat [arguments-and-decisions.md#plan-resolution](../autopilot-code/references/arguments-and-decisions.md) as the single authority for resolving `$ARG`. If no plan matches, interpret the argument as the file or directory test target instead of returning a plan-resolution error. > **Language rule**: Follow the audience and artifact language contract in [arguments-and-decisions.md#language-rule](../autopilot-code/references/arguments-and-decisions.md). Preserve commands, paths, test names, identifiers, and raw output. ## Run Graduated Tests Run the `qa/test` unit. Select one prompt form: - Plan path: ```text Run graduated tests for plan: {$ARG} Read the plan verification sections and checklist.md in the task root to identify targets. Execute Level 1 → 2 → 3 → 4 → 5 in order, stopping on the first failure. ``` - File or directory path: ```text Run graduated tests on: {$ARG} Execute Level 1 → 2 → 3 → 4 → 5 in order, stopping on the fir...