teleo-infrastructure/lib
m3taversal 410cf32cfe leo: handle non-JSON 200 from Forgejo merge API
Forgejo returns 200 with HTML content-type on successful merge instead
of JSON. Our API helper threw on resp.json(), causing merge to report
failure even though the PR merged. Now treats non-JSON 200 as success.

This was causing PRs #732 and #789 to show as conflict in our DB while
actually merged on Forgejo, and tripping the merge circuit breaker.

Pentagon-Agent: Leo <294C3CA1-0205-4668-82FA-B984D54F48AD>
2026-03-13 17:38:00 +00:00
..
__init__.py Initial commit: Pipeline v2 daemon + infrastructure docs 2026-03-12 14:11:18 +00:00
breaker.py ganymede: add dev infrastructure — pyproject.toml, CI, deploy script 2026-03-13 14:24:27 +00:00
config.py leo: implement retry budget — stop infinite eval loops 2026-03-13 17:14:12 +00:00
costs.py Initial commit: Pipeline v2 daemon + infrastructure docs 2026-03-12 14:11:18 +00:00
db.py leo: implement retry budget — stop infinite eval loops 2026-03-13 17:14:12 +00:00
domains.py ganymede: extract lib/domains.py — single domain→agent mapping 2026-03-13 15:33:18 +00:00
evaluate.py leo: prioritize fresh PRs over re-evals in eval queue 2026-03-13 17:32:07 +00:00
forgejo.py leo: handle non-JSON 200 from Forgejo merge API 2026-03-13 17:38:00 +00:00
health.py ganymede: add dev infrastructure — pyproject.toml, CI, deploy script 2026-03-13 14:24:27 +00:00
llm.py leo: constrain issue tags — do not invent new tags 2026-03-13 17:27:40 +00:00
log.py Initial commit: Pipeline v2 daemon + infrastructure docs 2026-03-12 14:11:18 +00:00
merge.py leo: model diversity + calibrated review prompts 2026-03-13 17:10:30 +00:00
validate.py leo: implement retry budget — stop infinite eval loops 2026-03-13 17:14:12 +00:00