no-mistakes(document): Jinja change docs were already mostly current. Fixed three stale spots: the Python render line in templates-and-payloads.md, the verify --templates row in cli.md, and a Jinja pointer in spec/conformance-tests.md. Nothing unresolved.

Author: dmealing

docs/features/cli.md

@@ -53,7 +53,7 @@ vocabulary everywhere, each port implementing the modes it supports.
 |---|---|---|
 | `verify --db` | **Schema drift** — does the live database (or snapshot) match the metadata? (migrate engine, ADR-0015) | yes |
 | `verify --codegen` | **Codegen drift** — regenerate from metadata into a temp dir and fail if it differs from the committed generated output. Catches "metadata changed but `meta gen` wasn't re-run". A hand-edited generated file is NOT drift — `meta gen` three-way-merges hand edits by design, so the gate compares the *generated contribution* against the committed `.gen-state/.hashes.json` rather than the file byte-for-byte. It still LISTS every generated file carrying a hand edit (count + paths, and how to see the edit) as a notice that does not change the exit code; `--forbid-hand-edits` makes any hand edit fail the build, for teams that want generated code untouchable (Node `meta` only). | no |
-| `verify --templates` | **Template/prompt drift** — `Renderer.verify` checks each `template.*` node's `{{field}}` references against its payload VO (FR-004). | no |
+| `verify --templates` | **Template/prompt drift** — `Renderer.verify` checks each `template.*` node's `{{field}}` references against its payload VO (FR-004). A Jinja body (Python and TypeScript, ADR-0061) is checked the same way. | no |
 | `verify --docs` | **Removed in 1.1.0** (ADR-0034 Amendment 9). It prints where the check went and exits 2: documentation is written by entries in `generators`, so `verify --codegen` checks it with the rest of the declared output. | — |
 | `verify --deps` | **Dependency drift** (FR-023) — re-resolves each declared dependency's `path` and compares its installed artifact's hash against `.metaobjects/deps.lock.json`, same comparison as `meta deps check`. Needs the publisher's `path` reachable, so it is never part of the bare-`verify` default. A `drifted` or `unresolved` dependency fails with `ERR_DEPENDENCY_UPSTREAM_DRIFT`. **Node `meta` only.** See [`metadata-dependencies.md`](metadata-dependencies.md). | no |
 

docs/features/templates-and-payloads.md

@@ -427,7 +427,8 @@ string output = Renderer.Render(new RenderRequest
 
 ### Python
 
-`metaobjects.render` ships the Mustache engine + `Verify`. The Python loader
+`metaobjects.render` ships the Mustache engine, Jinja through the `jinja` extra
+([Jinja templates](#jinja-templates-python-and-typescript)), and `Verify`. The Python loader
 recognizes `template.*` + `origin.*`. The payload is the value object's own Pydantic
 `BaseModel`, emitted by the `entity` generator as `<Name>.py` (ADR-0056), so a consumer
 can render from that model or from a plain `dict` — the engine reads a model through its

spec/conformance-tests.md

@@ -280,6 +280,9 @@ Each fixture is a directory under `fixtures/verify-conformance/`:
     `partials/` directory — an empty provider resolves nothing, so a
     `{{> ...}}` reference becomes `ERR_PARTIAL_UNRESOLVED`.
 
+- **Jinja bodies.** The `verify` corpus above is Mustache. The Jinja bodies (ADR-0061)
+  have their own corpus, `fixtures/jinja-verify-conformance/`, which uses the same
+  `payload.json` and `expected-drift.json` shape with a `template.jinja` entry.
 - **`expected-drift.json`** is a JSON array of `{ "code": "ERR_*", "path": "..." }`,
   where `code` is one of the three verify codes in
   [`ERROR-CODES.json`](../fixtures/conformance/ERROR-CODES.json)