<!-- BEGIN mgf-common auto-generated — managed by `mgf-fed catch-up`.
This block is managed by `mgf-fed catch-up` — edit outside the markers. -->

## The Magogi federation — start here

This project belongs to the **Magogi Foundation** federation.

> **Run `mgf-fed agents` and do what it prints.** That is the single
> federation-wide briefing: the shape, the standards, the primitives to reuse
> instead of reinventing, and where to file feedback.

**Deep context for THIS project:** `docs/claude/CLAUDE.md` (DOC-07). This root
file is the pointer Claude Code auto-loads; that file is the detail.

**Before you write "blocked", "missing", or "unreachable"** about any credential
or capability, ask the registry — the filesystem is a cache, the registry is the
truth (AG-20):

| Question | Ask this, not `find`/`grep` |
|---|---|
| What credentials exist? | `mgf-secrets list` · `doctor` · `mgf-standard/SECRETS.toml` |
| How do I *use* one? | the entry's `consumers` field · `mgf-secrets exec --with <id> -- <cmd>` |
| What libraries/repos exist? | `MGF_LIBRARIES.json` in `mgf-standard` |
| What is the fleet's state? | `mgf-fed status` |
| What infrastructure exists? | `mgf-standard/MGF_INFRA.md` (§2 = access & recovery) |

**CI, two facts you cannot derive from this bench:** the fleet runs its **own**
Woodpecker server (MGF_INFRA §1), not Codeberg's — no access request, no browser
login. And on a `pull_request` the workspace's default-branch ref is
**counterfeit** (the runner checks the PR head out under the default branch's
name), so a gate that asks "what is on main?" *by name* is answered with the
branch under review — trust only a fetched `refs/remotes/origin/*` ref.
<!-- END mgf-common auto-generated. Project-specific content below
this marker is preserved across `mgf-fed catch-up --apply` runs. -->
