Mechanically index the codebase into .popper/, then (on a second call with interpretation) persist Claude's semantic architecture/conventions/invariants.

Turn a raw problem statement into a locked problem contract. First call returns a drafting prompt + relevant files; second call (with contract) validates and locks it.

Report the current .popper/ knowledgebase summary, phase, and contract stats.

Draft (call 1) then persist (call 2 with hypothesis) a split public/private hypothesis for the locked contract.

Return a firewalled fan-out plan (call 1); log verdicts + decide survive/refine/exhaust (call 2 with verdicts).

Emit a one-shot implementation prompt for the surviving hypothesis and persist a solution record.

Report the current phase and which popper_* tool to call next (model-free conductor).

Record TDD-execution outcomes for the active contract so UltraPopper's KB learns from what actually held up under test. kind: 'held' (a refutation finding confirmed by a failing test), 'false_alarm' (a finding that did NOT reproduce), or 'missed' (a defect the tests found that refutation did not — the sharpest signal). Folded into the KB on the next popper_refute; held/missed need evidenceAnchors to ground.