docs: apply remaining FR-006 doc-review polish

- Java capability row: split the long Output-parser cell into a short
  table entry + a paragraph below the table (Payload-VO row collapsed
  the same way — both gaps share the same Java-codegen-layer gate).
- TS / C# / Python: add a "Consumer dependency" bolded callout to each
  port's FR-006 section, mirroring Kotlin's format. Kotlin had the only
  one before (the kotlinx-serialization-json gotcha); the other three
  also have an implicit dep (zod / BCL / pydantic) that's worth naming
  even when it's trivial.
- Python: add a "Note on emitted output" callout explaining that
  ruff_format is applied to the file before write, so the literal
  layout may reflow whitespace vs the snippet — function signatures
  and class definitions are stable.

Author: dmealing

docs/ports/csharp.md

@@ -208,6 +208,10 @@ Cross-port design is at [ADR-0010](../../spec/decisions/ADR-0010-template-output
 the feature reference is at
 [`features/templates-and-payloads.md`](../features/templates-and-payloads.md#output-parsing-fr-006).
 
+**Consumer dependency.** `System.Text.Json` ships in the .NET 8 BCL — no
+NuGet package to add. The generated parser uses the strict (case-sensitive)
+default options.
+
 ## Angular 18 frontend
 
 C# 12 / .NET 8 backends pair cleanly with an Angular 18 client built from

docs/ports/java.md

@@ -243,13 +243,23 @@ configuration model that has not yet been specced.
 | Source kinds (table / view / storedProc) | Yes |
 | `field.currency` / `field.enum` / `field.object` + `@storage` | Yes |
 | Templates + render (FR-004) | Yes (`metaobjects-render`) |
-| Payload-VO codegen | Not on Java itself — consumers use `Map<String,Object>` or hand-coded VOs. See [Kotlin port](kotlin.md) for `@Serializable` payload codegen. |
-| Output parser codegen (FR-006) | Not yet — gated on Java codegen layer (per the [FR-006 cross-port spec](../superpowers/specs/2026-05-25-fr6-template-output-parser-codegen.md)). Java consumers needing typed `template.output` parsing today should drive their codegen through the [Kotlin port](kotlin.md) (`KotlinOutputParserGenerator`) or hand-write a Jackson `readValue` call. |
+| Payload-VO codegen | Not on Java itself — see note below |
+| Output parser codegen (FR-006) | Not yet — gated on Java codegen layer; see note below |
 | Migrations | `mvn meta:migrate` / `mvn meta:migrate -Dflyway=true` |
 | Drift verify | `mvn meta:verify` (DB) + `Renderer.verify` (prompts) |
 | Runtime metadata | Full — OMDB ObjectManager |
 | REST controller codegen | Spring Web MVC — `metaobjects-codegen-spring` (FR-008 §2.1) |
 
+**On payload-VO + output-parser codegen.** Java consumers today use
+`Map<String,Object>` or hand-coded VOs for template payloads, and hand-write
+a Jackson `readValue(text, MyClass.class)` call for `template.output` parsing.
+Both gaps are gated on the planned Java codegen layer (per the
+[FR-006 cross-port spec](../superpowers/specs/2026-05-25-fr6-template-output-parser-codegen.md)).
+JVM consumers needing typed payload + parser codegen today can drive
+through the [Kotlin port](kotlin.md) (`KotlinPayloadGenerator` +
+`KotlinOutputParserGenerator`) — kotlinx.serialization output is
+JVM-callable from Java consumers via the underlying bytecode.
+
 ## Conformance status (as of 2026-05-27)
 
 | Corpus | Result |

docs/ports/python.md

@@ -243,6 +243,14 @@ Cross-port design is at [ADR-0010](../../spec/decisions/ADR-0010-template-output
 the feature reference is at
 [`features/templates-and-payloads.md`](../features/templates-and-payloads.md#output-parsing-fr-006).
 
+**Consumer dependency.** The emitted parser imports `pydantic` (v2). Add it via
+`pip install pydantic>=2` or `uv add pydantic` if you don't already have it.
+
+**Note on emitted output.** The generator runs `ruff_format(content)` on the
+file before writing, so the literal emitted layout may reflow whitespace
+slightly vs the snippet above. Function signatures, class definitions, and
+import lines are stable.
+
 ## Capability snapshot
 
 | Feature | Status |

docs/ports/typescript.md

@@ -204,6 +204,10 @@ time. Cross-port design is at
 the feature reference is at
 [`features/templates-and-payloads.md`](../features/templates-and-payloads.md#output-parsing-fr-006).
 
+**Consumer dependency.** The emitted parser imports `zod`. It's likely already in
+your `dependencies` (Drizzle / `@metaobjectsdev/runtime-ts` both lean on it);
+if not, `npm i zod`.
+
 ## Capability snapshot
 
 | Feature | Status |