Post-Review Loop

Emulate Pi's post-review-loop as an explicit Codex workflow. Codex cannot own hidden extension state or inject follow-up prompts, so persist loop state in the conversation for one-shot work and in a visible ledger for multi-turn or resumed loops.

Modes

Interpret the user's requested mode from natural language:

• oneshot or no mode: review the implementation once, optionally apply safe fixes, validate, and report.
• review-only: review once without editing files.
• start: create a persistent loop ledger and run the first phase.
• continue or resume: read the ledger and run the next phase.
• status: report current lifecycle, phase, unresolved buckets, validation, and next action without changing files.
• report or stop: render the final/current report. Stop after the current phase if already working.
• cancel: stop immediately and leave a short cancellation note if a ledger exists.

Default scope is uncommitted changes. If the user names a branch, commit range, feature, file list, or implementation target, use that scope instead.

Ledger