> **Relayed** to mgf-fed#PAPER-119 by the supervisor (FB-05).

### PAPER — bake the Codeberg API rate-budget into mgf-fed's client (PAPER-110, code half)

- **Severity:** 🟡 Sharp edge
- **Filed by:** mgf-standard (PAPER-110 resolution) on 2026-07-10
- **What hurts:** the rate-budget discipline lives only as recipe guidance
  (`activate-ci.md` §"Codeberg API rate-budget", mgf-standard PAPER-110) — an
  agent driving `mgf-fed` at automation speed can still hammer Codeberg into
  the hourly 429 wall, because nothing in the client enforces the budget.
- **Why it matters:** the observed failure (mgf-standard PAPER-110 evidence)
  wedged merges for ~an hour after ~9 PR opens + 20s-interval status polls;
  guidance alone doesn't survive an agent that hasn't read the recipe.
- **Suggested shape:** in mgf-fed's Codeberg HTTP layer: (a) a client-side
  steady-rate cap on state-changing calls (a few/min); (b) **exponential
  backoff + jitter on 429** with a hard stop (never retry-hammer); (c) route
  all pipeline-status polling to the Woodpecker API by construction (make the
  Codeberg commit-status call one-shot-only in the API surface); (d) prefer
  SSH git operations where a REST call is avoidable.
- **Status:** OPEN
