# Cutover / consumer notification — mgf-common 0.46.x

> **REL-09 consumer-notification artifact** for the 0.46.x line. Copy-pasteable
> for consumers; no breaking changes — 0.46.x is additive within the `<0.47`
> cohort window (no pin-walk required).

## TL;DR for consumers

Nothing you MUST do. 0.46.x is backward-compatible within `mgf-common>=0.46,<0.47`.
New, opt-in surface you MAY adopt:

| Version | What landed | Consumer action |
|---|---|---|
| 0.46.0 | New `mgf-fed federation` + `design` CLI; loud-degrade when `[standards]` extra is absent; `doctor --standards` partial-sync ledger gate | none required; install `mgf-common[standards]` to use the standards CLI |
| 0.46.1–0.46.3 | `doctor --standards` shape detection: dist-name≠package, deep PEP-420 namespaces, flat/multi-package layouts | none |
| 0.46.4 | `catch-up` states its federation-registry **snapshot provenance** (FEEDBACK PAPER-98) | none |
| 0.46.5 | `doctor --standards` gates `LESSON_LEARNED.md` presence (DOC-19 / PAPER-99) — corpus-aware, inert below corpus 0.1.20 | add a root `LESSON_LEARNED.md` once you bump `mgf-standard ≥ 0.1.20` |
| 0.46.6 | **Behavior fix (CF-02):** `.env` now correctly outranks the on-disk `[tool.mgf]` pyproject config (was inverted). README/precedence corrected. | if you set the **same** setting in BOTH `.env` and `[tool.mgf]`, `.env` now wins (per CF-02) — verify intent |

## The one behavior change to note (0.46.6)

`MgfSettings` config precedence is now CLI → env → **`.env` → `[tool.mgf]`** →
defaults (CF-02 order). Previously `[tool.mgf]` incorrectly outranked `.env`.
Only affects you if you set the *same field* in both places expecting the
pyproject value to win — rare. No migration code needed.
