---
name: release-and-registry
description: This repo sits below mgf-common (not a dep here); how it releases; the REL-13 registry-currency gate
metadata:
  type: project
---

**`mgf-common` is NOT a dependency of this repo** — `mgf-standard` is the
standards *leaf* and sits *below* `mgf-common` in the dependency order. So
`mgf-fed agents` / `doctor` may not be installed here; read the canonical
briefing from source (`mgf-common/STARTHERE.md`) when working in this repo.

**Release flow** (two-mode, via the `mgf-fed` orchestrator):
- `mgf-fed release-local mgf-standard` → build once, validate against the local
  index, publish there (the QA gate).
- `mgf-fed release-remote mgf-standard` → promote the same wheel to Codeberg:
  annotated tag (REL-01) → publish (PKG-04) → REST-verify 200 (PKG-05) →
  consistency gate (REL-13). Build-once / promote (REL-02).

**The registry** is `MGF_LIBRARIES.{json,md}` (generated). After any version
change anywhere in the federation, regenerate it from the parent dir holding all
sibling checkouts:
```sh
python scripts/gen_mgf_libraries.py           # write MGF_LIBRARIES.md
python scripts/gen_mgf_libraries.py --check    # REL-13 currency gate (CI)
```
A `[standards]` extra added to a sibling without a release nudges the registry
stale — batch the regen with the next mgf-standard touch.
