kitchenloop-regress

KitchenLoop: Regress

Phase 4 -- Run full regression, evaluate stop conditions, update loop state.

Triggers

• kitchenloop regress
• loop regress
• regression test

---

Overview

The Regress phase is the loop's quality gate. It runs the full test suite, evaluates whether the codebase is healthy enough to continue looping, and consolidates patterns learned during the iteration. If stop conditions are triggered, the loop pauses until a human intervenes.

---

Procedure

Step 1: Pre-Flight Checks

1. Load kitchenloop.yaml -- read verification, paths, and repo.
2. Verify all verification.preflight_env_vars are set. If any are missing, record them and STOP -- regression results would be misleading.
3. Ensure you are on the correct branch (repo.base_branch) with latest changes:

   git checkout {repo.base_branch}
   git pull origin {repo.base_branch}
   

4. Read loop state at paths.loop_state for:
   • Current iteration number
   • Previous pass rate and test count
   • Consecutive failure count

Step 2: Run Lint

Run the lint command from verification.oracle.lint_command:

{lint_command}

Record: PASS or FAIL with details.

If lint fails, attempt auto-fix (if the lint command supports it). Record whether auto-fix succeeded.

Step 3: Run Full Regression

Run the full test command from verification.oracle.full_command:

{full_command} 2>&1 | tee {paths.logs}/regress-iter-{N}.log

Parse the output to extract:

• Total tests: number of tests executed
• Passed: number passing
• Failed: number failing (with names and error summaries)
• Skipped: number skipped
• Duration: wall-clock time

Calculate:

• Pass rate = passed / (passed + failed)
• Skip rate = skipped / total