githubnext/evergreen/evergreen-repair

Evergreen Repair

Repair only the pull request, head SHA, and failing gate selected by the controller and evergreen-diagnose.

Core Procedure

1. Read deterministic-repair.md.
2. Reproduce the exact failing command with the narrowest repository-native

invocation allowed by policy.

1. Select only the specialist reference matching the diagnosed gate.
2. Apply the smallest coherent patch that can clear the gate.
3. Rerun the same command until it passes, only non-mechanical blockers remain,

or a stop condition applies.

1. Report changed files, commands, verification evidence, and the next action.

Do not run git merge or git rebase, write to the base branch, mutate the controller-owned ready label, expose secrets, or describe an unverified side effect as complete.

Specialist Routing

• API, schema, protocol, or compatibility failures: read

api-contract-gate-repair.md.

• Migration, persistence, fixture, cache, or data failures: read

data-migration-gate-repair.md.

• Package, lockfile, license, or supply-chain failures: read

dependency-gate-repair.md.

• Documentation, release-note, generated-doc, or publishing failures: read

docs-release-gate-repair.md.

• UI, accessibility, visual, or browser failures: read

frontend-e2e-repair.md.

• GitHub Actions, runner, permission, environment, or deployment failures: read

infra-ci-repair.md.

• Lint configuration or policy conflicts: read

lint-policy-review.md.

• Benchmark, runtime, memory, or performance failures: read

performance-gate-repair.md.

• Playground or Playwright failures needing deeper browser evidence: read

playground-e2e-diagnoser.md.

• Security, secret scanning, dependency alert, or security-gate failures: read

security-gate-repair.md.

• Moving automation-authored or unusually large PRs: read

autoloop-coordinator.md.

Stop Conditions

Stop and return a precise blocker when evidence is stale or incomplete, the PR head changed, trust policy denies execution, a credential or approval is required, the repair needs a protected edit, the same failure signature repeats without progress, or the patch would exceed confirmed scope.