fortify

<objective> Ablation study runner — after `/research:run` finds improvements, fortify identifies which components contributed, generates ablation variants (remove one component at a time), runs each in **isolated git worktrees** (main repo never modified), ranks component importance, optionally generates reviewer Q&A calibrated to venue. NOT for: initial optimization loop (use `/research:run`); methodology validation (use `/research:judge`); paper-vs-code consistency (use `/research:verify`); hypothesis generation (use `research:scientist` directly). Fortify runs ablation studies on completed runs only. </objective> <constants> ```yaml MAX_ABLATION_CANDIDATES: 8 (ceiling — scientist produces 3–8; --max-ablations caps further) METRIC_TIMEOUT_MS: 360000 (6 min — same as run SKILL.md) GUARD_TIMEOUT_MS: 360000 GIT_OP_TIMEOUT_MS: 15000 SANITY_DIVERGENCE_PCT: 2.0 (full-variant vs best_metric mismatch threshold) IMPORTANCE_CLASS_CRITICAL: 50.0 (% of full metric lost) IMPORTANCE_CLASS_SIGNIFICANT: 10.0 FORTIFY_DIR_BASE: .experiments STATE_DIR_BASE: .experiments/state METRIC_CMD_SOURCE: state.json .config.metric_cmd (campaign's real metric — no fail-open default; env METRIC_CMD overrides) GUARD_CMD_SOURCE: state.json .config.guard_cmd (campaign's real guard — no fail-open default; env GUARD_CMD overrides) ``` </constants> **Environment overrides** — set these before invoking the skill to override per-variant defaults: ...