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

### PAPER — `mtest` failures are unreadable in CI: detail goes to `.gates/` files, stdout gets only a count

- **Severity:** 🟡 Sharp edge
- **Filed by:** mgf-hrb (Court/CTO fleet sweep) on 2026-07-11
- **What hurts:** on failure `mtest` prints one line — `[mtest] FAIL: 567 passed, 5 failed,
  9 skipped (581 total)` — and writes the actual detail to
  `.gates/last-run/failures/*.txt`. In CI those files are **never uploaded** (no artifact
  step), so the pipeline log physically cannot tell you WHICH tests failed or why. The
  gate says "red" and nothing more.
- **Why it matters:** mgf-hrb's `main` has been red for weeks on 5 CI-only failures
  (`CI-01` there) and **no one can see what they are** without hand-rebuilding the
  container. A gate whose failures you cannot read cannot be acted on — it just teaches
  people to ignore red. Every consumer of the supervisor-driven gate inherits this.
- **Evidence:** mgf-hrb pipelines #156/#162/#165, `supervisor-tier-0-3` step: the entire
  failure output is the summary line. Locally the same tier is green, so the log is the
  ONLY window into the CI-specific failures — and it is opaque.
- **Suggested shape:** when `CI` is set (or always, behind `--print-failures`), echo each
  failure's captured detail to **stdout** after the summary — at minimum the nodeid +
  the assertion/traceback tail — so the pipeline log is self-sufficient. (Uploading
  `.gates/` as an artifact is the heavier alternative already tracked as mgf-common
  PAPER-63; printing is cheap and works on every forge.)
- **Status:** OPEN
