docs-diagramslisted

# Docs diagrams — Mermaid SSOT, diagram-design SVGs Headline diagrams on the docs site are hand-crafted SVGs in the [diagram-design](https://github.com/cathrynlavery/diagram-design) editorial system, generated from Mermaid sources. The split: - **`docs/diagrams/*.mmd`** — the source of truth. Diffable, reviewed in PRs, outside `docs_dir` so MkDocs never publishes it. - **`docs/diagrams/manifest.yml`** — the mapping: each source, its SVG pair, the pages embedding it, and the source's sha256 at generation time. `python3 docs/diagrams/verify.py` checks it (CI runs it in the `Documentation (strict)` job, so a drifted `.mmd` fails the PR); `--update` refreshes the hash after a regeneration. - **`docs/manual/assets/diagrams/<name>-light.svg` + `<name>-dark.svg`** — generated build products. Never hand-edit beyond regeneration. - The embedding page inlines both via `pymdownx.snippets` inside `dd-diagram dd-light` / `dd-dark` divs; `assets/extra.css` switches them on Material's `data-md-color-scheme` and loads the fonts (inline SVG inherits page fonts — `<img>` embedding would silently lose them). **Scope: headline diagrams only** — currently `concepts/lifecycle.md`'s flowchart. Workaday diagrams (sequence diagrams, guides) stay plain ```` ```mermaid ```` blocks. A diagram earns the treatment when it carries a page's thesis, not because it exists. ## The rule **Any PR that changes a `docs/diagrams/*.mmd` regenerates its SVG pair in the same PR** — the docs-in-s