# DEPS — mgf-uitest-web's bidirectional dependency manifest

> **§1** — what mgf-uitest-web depends on. **§2** — who depends on it. Knowing both
> directions makes deprecation + breaking-change blast-radius tractable.
> **Per standard DOC-16** — every project ships a `DEPS.md`.

Last verified: 2026-07-16.

---

## §1 What mgf-uitest-web depends on

| Dependency | Window | Why | Tier |
|---|---|---|---|
| `playwright` | `>=1.50,<2` | drives the real Chromium (the whole point) | runtime |
| `axe-playwright-python` | `>=0.1.4` | axe-core accessibility scan | runtime |
| `pytest` | `>=8.0` | this distribution ships a `pytest11` plugin + fixtures | runtime |
| `mgf-common` | `[standards]>=0.47,<1.0` | federation standards corpus | `[standards]` |
| `mgf-standard` | `>=0.1.6,<0.2` | standards + templates | `[dev]` |
| `mgf-test-supervisor` | `>=0.1.3,<0.2` | the fleet test runner | `[dev]` |

**Deliberately NOT a dependency:** FastAPI / Jinja / uvicorn or any console's
stack. The harness drives each console as a black box over HTTP, launching the
console's *own* CLI from its *own* virtualenv (see `SCOPE.md` §1).

## §2 Who depends on mgf-uitest-web

| Consumer | How | Since |
|---|---|---|
| `mgf-fed-web` | `[dev]` — its `tests/ui/` specs | (pending spec-move, enshrine step D) |
| `mgf-test-web` | `[dev]` — its `tests/ui/` specs | (pending spec-move, enshrine step D) |
| `mgf-cloud-web` | `[dev]` — its `tests/ui/` specs | (pending spec-move, enshrine step D) |

*No published consumers yet — the console specs move into their own repos as part
of enshrine step D.*
