Run `mgf-fed onboard-prompt` and follow the printed prompt EXACTLY.

It prints the federation's **onboard** procedure — bring an **existing, non-MGF**
project INTO the federation as a new member: understand the federation → decide
the join shape (sibling `mgf-<name>` library, or consumer app) + add `mgf-common`
→ conform the existing code via the sync engine (it starts with many ⏳; that's
expected) → declare your level + ask to be registered. Resolved live from the
`mgf-standard` version this project pins, so it never drifts.

Use this in an **existing outside project you're bringing IN** — not an empty repo
(use `/new-project`), not an already-member (use `/sync`), not a project staying
outside (use `/adopt`). Do not work from memory; run the command and do what it says.

If `mgf-fed onboard-prompt` reports that the corpus is not installed, run:

    pip install -U 'mgf-common[standards]'

then re-run it. (The standards corpus is an optional Codeberg-only extra; a plain
`mgf-common` install does not carry it.)
Unsure which case you're in? `/start` (or `mgf-fed start`) auto-routes.
