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

### PAPER — `feedback --relay` crashes on a target with no `FEEDBACK.md` (and half-applies the batch)

- **Severity:** 🟡 Sharp edge
- **Filed by:** mgf-standard (supervisor relay run) on 2026-07-10
- **What hurts:** relaying to a target repo that has no `FEEDBACK.md` yet
  raises `FileNotFoundError` from `_relay_one` (`_feedback.py:130` reads the
  target file unconditionally) and aborts the whole `--relay` run mid-batch —
  papers earlier in the plan may already be written/moved while later ones are
  not (non-atomic). Hit live on 2026-07-10 relaying mgf-standard's outbox to
  `mgf-cloud-provision` (a real member with no feedback file yet).
- **Why it matters:** the first relay to any newly-onboarded member fails, and
  a half-applied batch leaves the queues inconsistent — the exact silent-loss
  FB-05 exists to prevent.
- **Evidence:** traceback `mgf/fed/_feedback.py:130 → FileNotFoundError:
  …/mgf-cloud-provision/FEEDBACK.md`; `--dry-run` showed a valid 5-paper plan.
- **Suggested shape:** in `_relay_one`, seed a minimal canonical `FEEDBACK.md`
  header (the feedback-md-template shape) when the target file is absent — or
  skip-with-a-loud-warning; and catch per-paper errors and continue, reporting
  failures at the end (per-paper write+move stays atomic).
- **Status:** OPEN
