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

### PAPER (→ mgf-common) — `doctor --standards` should report graceful N/A on non-Python repos (not error)
- **Severity:** 🟢 Nice-to-have
- **Filed by:** mgf-standard (federation conformance sweep) on 2026-06-07
- **What hurts:** `mgf-common doctor --standards` requires a `pyproject.toml`
  with `[project]`; on a **non-Python** federation member it prints "cannot
  detect project shape" and exits non-zero. The 6 Zig libs (`build.zig.zon`:
  mgf-common-zig, mgf-common-identity, mgf-hrb-{model,kabi,cap,rt}) and the
  `mgf-website-template` cookiecutter hit this. It reads as a failure when the
  honest result is **"N/A — not a Python project."**
- **Why it matters:** a federation-wide `doctor --standards` sweep shows 7
  members as errors that are actually just out-of-scope for a Python audit —
  noisy + misleading, exactly like the `catch-up` case PAPER-97 fixed.
- **Evidence:** `_discover_project` returns None → `doctor_standards()` prints
  the shape error + returns EXIT_OPERATION_ERROR; repros on all 7 non-Python
  members (verified 2026-06-07).
- **Suggested shape:** mirror PAPER-97 — detect a non-Python member (no
  `pyproject [project]`, presence of `build.zig.zon` / `cookiecutter.json`) and
  emit a single "N/A — not a Python project (no Python conformance surface)"
  finding with exit 0, instead of the shape error. The DOC-15/DOC-19 root-doc
  facts (ledger, LESSON_LEARNED.md) are language-agnostic and could still be
  checked, but the Python code-level checks (AP-09/AP-13/TS-04/DP-12) are N/A.

## Relayed (closed)

## Relayed (closed)

- **2026-06-07 — `catch-up` live latest-check** → relayed as **mgf-common
  `PAPER-98`** (merged, PR #9, commit `100b52e`). Resolved *no-network*: the CLI
  stays offline and now states its registry-SNAPSHOT provenance explicitly; the
  live latest-check is performed agent-side by the sync-prompt's STEP-0
  ASSERT-LATEST. (mgf-standard FEEDBACK PAPER-05.)
- **2026-06-07 — gate `LESSON_LEARNED.md` in `doctor --standards`** → relayed as
  **mgf-common `PAPER-99`** (DEFERRED — blocked on `LESSON_LEARNED.md` becoming
  a binding required doc here, mgf-standard FEEDBACK PAPER-03; gating a
  non-binding doc would retro-fail every repo).
- **2026-06-07 — re-sync `mgf-common/.claude/commands/sync.md`** → **NOT relayed;
  no mgf-common action needed.** Verified the command is already a thin
  *delegator* (`Run mgf-common sync-prompt …`), not an inline copy, so it never
  drifts. The real defect was a stale Note in this repo's
  `federation-sync-prompt.md` recipe (it described an inline-copy model) — fixed
  here, not in mgf-common.
