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

### PAPER — auto-retrigger a pipeline that reds on the `clone` step alone (PAPER-109(b))

- **Severity:** 🟡 Sharp edge
- **Filed by:** mgf-standard (PAPER-109 investigation) on 2026-07-10
- **What hurts:** the fleet's known clone credential-injection flake
  (mgf-standard PAPER-109) reds pipelines through no fault of the change, and
  the standing mitigation is a **manual** restart (e.g. mgf-fed pipeline #154
  "re-trigger pipeline (clone step flaked)"). In-step retry is proven
  insufficient — plugin-git already defaults to `attempts: 5` / `backoff: 5s`
  and the flake survives it (the netrc is absent for the step's whole
  lifetime; only a fresh pipeline start re-injects it).
- **Why it matters:** every occurrence costs a human a manual re-trigger and
  erodes trust in red (PAPER-109's "people learn to shrug off reds").
- **Suggested shape:** wherever mgf-fed already polls/drives Woodpecker
  pipelines, detect the signature — failed pipeline whose ONLY failed step is
  `clone`, log matching `could not read Username` — and restart it **once**
  (bounded; a second identical failure stays red for a human). Poll Woodpecker
  (self-hosted, unmetered), never Codeberg commit-status (PAPER-110's rate
  budget).
- **Status:** OPEN
