challenge-resolve

Before asking, read User Questions.

Challenge and Resolve

Read, apply ../../shared/adversarial-loop.md before dispatch or edits. That shared procedure owns the algorithm; this entrypoint owns Codex artifacts, the closing gate. Read evidence-contract.md before source capture or reviewer dispatch. Also read ../../shared/native-skill-contract.md and ../../shared/specialist-orchestration.md for authority, recurrence, reviewer admission, evidence limits.

Input Schema

{
  "goal": "required review-and-fix objective",
  "scope_files": ["bounded files or diff scope"],
  "specification": "required behavior or acceptance criteria",
  "symptom": "reported failure, or explicit preventive review",
  "caller_run": "optional existing workflow run to resume",
  "done_when": "independent final review is clean and normal checks pass"
}

Use default max 3 review rounds, including initial W_0. In-scope feasible fixes are authorized by a review-and-fix request; a structural finding does not authorize scope expansion, public API changes, commits, installs, network access or publication. A caller's stricter scope or admission still applies.

Workflow

01: Establish scope and evidence ownership

Read ../../shared/helper-cli-contract.md; create a run with create_run.py --skill challenge-resolve. Record caller_run when supplied, without overwriting its artifacts. Retain baseline source and acceptance evidence. Write loop-report.md with Scope, Rounds, Findings, Recovery, and Verification sections. Identify implementation author and allowed reviewer route before dispatch.

02: Run the shared bounded procedure

Follow the shared five-step procedure: challenge and collect findings; report the old/new table once after each validated round; resolve every feasible in-scope finding; escalate unresolved security, critical or high; repeat until clean, three rounds, plateau or a non-converging score. Retain loop-ledger.json, loop-actions.json, round-<index>.diff, current snapshot current.diff and each independent report. Read adversarial_loop.py --help, validate the ledger after each round, and invoke adversarial_loop.py --ledger <run-directory>/loop-ledger.json --progress only after a newly completed challenge, before the next fix, review or stop. Show its full cumulative stderr table with Iteration | Critical | High | Medium | Low | Nits | Weighted score and literal old + new cells. Never show a placeholder progress table before a validated round or repeat the table in unrelated status updates. Keep the final canonical Results table unchanged. Structural or repeated findings alone do not stop an authorized feasible fix; scope, authority, recurrence, plateau, missing independence, stale evidence and exhausted rounds retain their shared stop rules. A fixed-pending-verification finding remains open. After resolution/escalation, bind every open finding to an action and run adversarial_loop.py --ledger <run-directory>/loop-ledger.json --actions <run-directory>/loop-actions.json before another challenge or final handoff. The helper validates recorded actions, not their truth; the parent must inspect feasibility and fix evidence.