Skip to content

Diagnose repeated repair failures before retrying on Low - #6

Merged
onoderakosen89 merged 1 commit into
mainfrom
low-repair-diagnosis
Nov 19, 2026
Merged

onoderakosen89 merged 1 commit into
mainfrom
low-repair-diagnosis

Conversation

@onoderakosen89

Copy link
Copy Markdown
Owner

What changes

  • Add an optional diagnosis step to the repair loop. After two failed Low repairs by default, a read-only High diagnosis receives the check evidence, previous attempts, and latest diff.
  • Permit one more Low repair when the diagnosis identifies an evidenced fix within the current requirements. Rerun the original independent check. For an unknown cause, a human decision, or a failed final check, return a consultation.
  • Keep the existing flow for callers without a diagnosis callback. The integration supplies the model effort and the read-only environment.
  • Add a scripted demo, CI coverage, and instructions in English, Japanese, and Simplified Chinese.

This covers the diagnosis and repair handoff in #5. Its whole-workflow acceptance example and comparative measurements remain open.

Verification

  • npm test, npm run test:pytest, and npm run test:integration passed locally.
  • Both the existing stop demo and the new diagnosis demo passed. The new demo uses scripted responses and a real independent check.
  • git diff --check passed.

@onoderakosen89
onoderakosen89 merged commit 93314bd into main Nov 19, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant