A CI job hard-killed by OOM / pod eviction produces no verdict — nothing
in the diff to fix. The implementer correctly emits
outcome=ci-infra-failure, but that alone only shuffles workflow state;
CI never re-runs, so every retry reads the same dead run and the
workflow loops until the _MAX_CI_INFRA_FAILURE backstop STUCKs it
(observed live on PR #39 in run-3).
New ``implementer_retrigger_ci(owner, repo, pr_branch)`` MCP tool on the
implementer response-builder lets the agent kick a fresh CI run. Forgejo
15.x has no Actions rerun API, so it reuses the controller's existing
mechanism — ``ci_rerun.trigger_ci_rerun_via_empty_commit`` — an empty
commit that advances the PR head SHA, which is the unambiguous
fresh-state signal for CI (and a stale review).
- ci_rerun.py is loaded standalone (importlib by file path, registered
in sys.modules before exec so its @dataclass resolves) — the
response-builder MCP must not pull the heavy tools.controller.master
package.
- _retrigger_ci resolves the Forgejo base URL + token from env
(FORGEJO_URL / FORGEJO_API_BASE, FORGEJO_TOKEN / GITEA_TOKEN) and
never raises.
- Once per session: a second implementer_retrigger_ci call is refused
benignly so a looping agent cannot pile junk commits on the PR.
- The implementer prompt's ci-infra-failure block now instructs the
agent to call the tool before emitting the outcome.
10 new tests (test_mcp_builders.py, test_worker_prompts.py); full
controller suite (1192) green.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
drew
eb1d81828f