goalforge-hardenlisted

# SDD Harden Advances a WP through two transitions: 1. `spec → hardened` (automated, driven by `goalforge-interview`, which wraps the `interview` plugin engine) 2. `hardened → ready` (human-gated by default; auto-advances only under the signal-scoped rule — Step 2) ## Unattended mode (`SDD_AUTONOMY=unattended`) When the environment variable `SDD_AUTONOMY=unattended` is set (the `autopilot` driver sets it), there is no human to answer. Wherever this skill would call `AskUserQuestion` — the Step 0 dependency-frontier halt, and the `hardened → ready` sign-off — **do not block. PARK instead:** write the blocker / verbatim gate prompt to the WP `findings.md` and stop (exit cleanly so the run resumes later). This does **not** bypass the human gate — a WP outside the signal-scoped auto-advance class (Step 2.3) is still not advanced autonomously; the run simply stops and hands off so a human approves later. A WP *inside* that class advances with `--mode auto` in either autonomy mode — the rule, not the autonomy setting, decides. Classify per `~/.claude/skills/autopilot/references/autonomy-policy.md`. Unset (`interactive`) behaviour is unchanged. ## Preconditions - WP `overview.md` exists with `status: spec`. - `goalforge-validate.sh` passes for this WP (no schema errors). ## Step 0 — Dependency-frontier gate (the harden frontier) A WP may not be hardened until its dependencies are **`verified` or `archived`** — the *harden frontier*. This is the first gate, run before a