<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-08-12-1-plantuml-schema-diagram-rendering/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-08-12-1-plantuml-schema-diagram-rendering/</id>
  <title>ADR: Local, No-Egress PlantUML Rendering for Code-Grounded Doctrine Schema Diagrams — a New Genre Beside the Hand-Authored C4 Lane</title>
  <updated>2026-11-10T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-08-12-1-plantuml-schema-diagram-rendering/"/>
  <summary>Why doctrine schema diagrams render locally at build time from a pinned, network-isolated PlantUML — a genre distinct from C4 progressive-zoom, carving R-04 accordingly.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;The doctrine artefact model — agent profiles, mission-type/step contracts, the DRG
(&lt;code dir=&quot;auto&quot;&gt;DRGNode&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;DRGEdge&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;NodeKind&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Relation&lt;/code&gt;), and the &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; vocabulary — is
documented &lt;strong&gt;in prose&lt;/strong&gt; across &lt;code dir=&quot;auto&quot;&gt;doctrine-kinds.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission-type-resolution.md&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;doctrine-relationships.md&lt;/code&gt;. It has &lt;strong&gt;no schema diagrams&lt;/strong&gt;: a reader cannot see the shape
of a bound model at a glance, and prose alone does not make a closed field set legible.&lt;/p&gt;
&lt;p&gt;Two facts constrain any fix.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The docsite renders Mermaid but not PlantUML.&lt;/strong&gt; The DocFX pipeline runs an ordered
&lt;code dir=&quot;auto&quot;&gt;scripts/docs/&lt;/code&gt; HTML post-processing chain over &lt;code dir=&quot;auto&quot;&gt;docs/_site&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;glossary_linker.py&lt;/code&gt; is
the established pattern). Mermaid renders client-side; a &lt;code dir=&quot;auto&quot;&gt;```plantuml&lt;/code&gt;-fenced
&lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; block does not render at all. So the diagram genre best suited to typed
schema depiction — PlantUML &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; — has no rendering path today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;These diagrams must not drift from the code&lt;/strong&gt;, and they must not send doctrine
content off-machine to be drawn. A schema diagram that is hand-copied, or rendered by a
remote PlantUML server, fails one or the other: it drifts, or it egresses.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This ADR records the rendering decision (Scope B, mission &lt;code dir=&quot;auto&quot;&gt;doctrine-schema-diagrams&lt;/code&gt;,
FR-001/FR-002), the reasoning that positions these schema diagrams as a &lt;strong&gt;new genre&lt;/strong&gt;
rather than an extension of the existing C4 model, and the reconciliation with R-04 in
&lt;a href=&quot;/architecture/diagrams/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/diagrams/README.md&lt;/code&gt;&lt;/a&gt; so the two
governance surfaces do not contradict.&lt;/p&gt;
&lt;p&gt;The governing toolguide for the mechanism is the active &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;plantuml-diagramming&lt;/code&gt;&lt;/strong&gt;
toolguide (&lt;code dir=&quot;auto&quot;&gt;packs/built-in/toolguides/plantuml-diagramming.toolguide.yaml&lt;/code&gt;), activated in
the charter’s &lt;em&gt;Writing, Communication &amp;#x26; Diagramming Doctrine&lt;/em&gt; (2026-08-08) alongside
&lt;code dir=&quot;auto&quot;&gt;USE_C4_MODEL_TECHNIQUES&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;mermaid-diagramming&lt;/code&gt; toolguide. That activation is
&lt;strong&gt;charter-prose active&lt;/strong&gt; — a governing directive read from the charter document — not a
runtime-resolved artefact loaded through the doctrine chain; this ADR cites it by name as
the source of the how-to, and does not depend on runtime resolution of it.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Zero doctrine-content egress (C-001, NFR-002).&lt;/strong&gt; The content being drawn is the
project’s own doctrine model. It must be rendered on-machine, and the renderer must be
provably unable to reach the network — proven behaviourally, not by a flag.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Generated fidelity over source-view convenience (C-002).&lt;/strong&gt; A diagram that is generated
from the frozen code model and guarded against drift is worth more than one that renders
on github.com’s raw source view. We accept docsite-only rendering to get fidelity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reproducibility (NFR-003).&lt;/strong&gt; The rendering binary must be pinned by version &lt;strong&gt;and&lt;/strong&gt;
sha256, and the diagrams must be CI-generated, not committed as SVGs that can rot.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Slot into the existing chain, disturb nothing.&lt;/strong&gt; The step must run inside the
established &lt;code dir=&quot;auto&quot;&gt;scripts/docs/&lt;/code&gt; post-processing order and leave the existing Mermaid/C4
diagrams (R-04) rendering unchanged (NFR-004).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep the genre boundary honest.&lt;/strong&gt; These diagrams depict &lt;em&gt;code models&lt;/em&gt;, not
architecture zoom levels. Conflating them with the C4 lane would misdirect both authors
and the drift guard.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Render &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; doctrine schema diagrams at docs-build time, locally, with a pinned
binary inside a network-denied container, as a post-processor after &lt;code dir=&quot;auto&quot;&gt;glossary_linker&lt;/code&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Pinned binary, sandboxed engine.&lt;/strong&gt; A single &lt;code dir=&quot;auto&quot;&gt;plantuml.jar&lt;/code&gt;, pinned by &lt;strong&gt;version and
sha256&lt;/strong&gt;, is verified before use (a sha256 mismatch fails the build before any render
from an unverified binary). It is invoked with
&lt;code dir=&quot;auto&quot;&gt;-DPLANTUML_SECURITY_PROFILE=SANDBOX&lt;/code&gt;, and SANDBOX is proven behaviourally: a diagram
carrying an egress directive (&lt;code dir=&quot;auto&quot;&gt;!include&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;!includeurl&lt;/code&gt;) must fail-closed under it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rendering runs only inside a digest-pinned JRE container under
&lt;code dir=&quot;auto&quot;&gt;docker run --network=none&lt;/code&gt;.&lt;/strong&gt; The jar never runs host-native. The container image is
pinned by digest; &lt;code dir=&quot;auto&quot;&gt;--network=none&lt;/code&gt; denies the render process any network namespace, so
even a hypothetical SANDBOX bypass cannot reach the wire. This is the portable, hard
egress gate on CI-Linux (the runners have Docker); &lt;code dir=&quot;auto&quot;&gt;unshare -rn&lt;/code&gt; is not reliable on
Ubuntu-24.04 runners (&lt;code dir=&quot;auto&quot;&gt;apparmor_restrict_unprivileged_userns=1&lt;/code&gt;) and is therefore not
the primary mechanism.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Python orchestration is host-native and stdlib-only.&lt;/strong&gt; The orchestrator
(&lt;code dir=&quot;auto&quot;&gt;scripts/docs/plantuml_render.py&lt;/code&gt;) recovers &lt;code dir=&quot;auto&quot;&gt;```plantuml&lt;/code&gt;-fenced &lt;code dir=&quot;auto&quot;&gt;@start*&lt;/code&gt; blocks
from the built &lt;code dir=&quot;auto&quot;&gt;docs/_site&lt;/code&gt; HTML (HTML-unescaping the payload; asserting the emitted
&lt;code dir=&quot;auto&quot;&gt;language-plantuml&lt;/code&gt; class), shells out to the pinned container to render each block to
SVG, and injects the SVG with descriptive alt/aria text. The orchestrator itself does
no network I/O and pulls in no third-party dependency; only the isolated container does
the drawing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Positioned after &lt;code dir=&quot;auto&quot;&gt;glossary_linker&lt;/code&gt; in both docs workflows.&lt;/strong&gt; The step runs after
&lt;code dir=&quot;auto&quot;&gt;glossary_linker&lt;/code&gt; in the PR gate (&lt;code dir=&quot;auto&quot;&gt;docs-build-pr.yml&lt;/code&gt;) and in the deploy pipeline
(&lt;code dir=&quot;auto&quot;&gt;docs-pages.yml&lt;/code&gt;, including its &lt;code dir=&quot;auto&quot;&gt;paths:&lt;/code&gt; allowlist), so glossary linking has already
run over the HTML before diagrams are injected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fidelity is enforced by the drift guard, not by hand.&lt;/strong&gt; Each diagram is bound to its
source model by an explicit &lt;code dir=&quot;auto&quot;&gt;file:class&lt;/code&gt; table and checked by the FR-004 drift guard,
which introspects the live model (Pydantic &lt;code dir=&quot;auto&quot;&gt;model_fields&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;FieldInfo.alias or name&lt;/code&gt; normalization and transitive nested recursion; frozen-dataclass &lt;code dir=&quot;auto&quot;&gt;fields()&lt;/code&gt;;
StrEnum members via &lt;code dir=&quot;auto&quot;&gt;list(...)&lt;/code&gt; — never a hand-copied count) and fails on any field-set
mismatch. The guard is the control that lets us treat a generated diagram as
authoritative.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;schema-diagrams-are-a-new-genre-distinct-from-c4-progressive-zoom&quot;&gt;Schema diagrams are a new genre, distinct from C4 progressive-zoom&lt;/h3&gt;
&lt;p&gt;The charter’s &lt;code dir=&quot;auto&quot;&gt;USE_C4_MODEL_TECHNIQUES&lt;/code&gt; directive governs &lt;strong&gt;architecture&lt;/strong&gt; diagrams via
the C4 model’s progressive zoom — System Context → Container → Component → Code — where
each level serves one audience at one altitude. Those diagrams are &lt;strong&gt;hand-authored&lt;/strong&gt; and
live under &lt;a href=&quot;/architecture/diagrams/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/diagrams/&lt;/code&gt;&lt;/a&gt; as the
living C4 model (R-04).&lt;/p&gt;
&lt;p&gt;The doctrine &lt;strong&gt;schema diagrams&lt;/strong&gt; introduced here are a &lt;strong&gt;different genre&lt;/strong&gt;. They depict the
&lt;strong&gt;shape of a code model&lt;/strong&gt; — the fields, types, and enum members of a frozen artefact
schema — not an architecture zoom level. They are not a fifth C4 tier and they are not a
finer-grained “Code” level of the architecture C4 set; they answer “what does this model’s
field set look like?”, a question C4 never asks. They are &lt;strong&gt;generated&lt;/strong&gt; from the frozen
models (not hand-authored), &lt;strong&gt;drift-guarded&lt;/strong&gt; (not narrative), and &lt;strong&gt;docsite-only&lt;/strong&gt; (not
source-view). Treating them as their own genre keeps the C4 lane’s hand-authored,
GitHub-renderable convention intact while giving schema depiction its own rules.&lt;/p&gt;
&lt;h3 id=&quot;accessibility-carve-out-nfr-005&quot;&gt;Accessibility carve-out (NFR-005)&lt;/h3&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;docs-accessibility&lt;/code&gt; styleguide requires that a diagram’s facts be &lt;strong&gt;restated in
prose&lt;/strong&gt; so the page is legible without seeing the image. For these schema diagrams that
duty is &lt;strong&gt;discharged by the surrounding doctrine-kinds prose&lt;/strong&gt; — the kind descriptions and
model explanations already on the page — &lt;strong&gt;not&lt;/strong&gt; by re-listing every field beside the
diagram. Re-listing the fields would recreate exactly the hand-maintained field inventory
that &lt;strong&gt;C-005 forbids&lt;/strong&gt;: a second copy of the schema that drifts from both the code and the
generated diagram. Each injected SVG still carries descriptive, non-trivial alt/aria text
derived from the diagram’s &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; title/caption (asserted by the render pipeline), so
the &lt;em&gt;identity and purpose&lt;/em&gt; of each diagram is available to assistive technology; the
&lt;em&gt;exhaustive field facts&lt;/em&gt; live once, in the code model, surfaced through the generated
diagram and narrated by the existing prose.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Positive&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Doctrine schema shape becomes legible on the docsite, generated from the single source of
truth (the frozen models) and unable to drift past the FR-004 guard.&lt;/li&gt;
&lt;li&gt;No doctrine content leaves the machine: the render runs in a &lt;code dir=&quot;auto&quot;&gt;--network=none&lt;/code&gt; container
with a SANDBOX engine, both proven behaviourally.&lt;/li&gt;
&lt;li&gt;The rendering binary is reproducible (version + sha256; digest-pinned image), and SVGs
are CI-generated rather than committed and left to rot.&lt;/li&gt;
&lt;li&gt;The existing hand-authored C4 lane (R-04) and its Mermaid/C4 diagrams are untouched
(NFR-004); the genre boundary is explicit, so authors know which lane a new diagram
belongs to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Negative / accepted trade-offs&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Docsite-only rendering (C-002).&lt;/strong&gt; Pre-rendered SVGs appear only on the &lt;em&gt;built&lt;/em&gt; docsite,
not on github.com’s source view of the Markdown. A reader browsing the raw doctrine
pages on GitHub sees the &lt;code dir=&quot;auto&quot;&gt;```plantuml&lt;/code&gt; fence, not a picture. We accept this: the value
is generated fidelity, and the fidelity control (the drift guard) only exists on the
build path. This is the deliberate inverse of the C4 lane’s R-04 convention, which
chooses GitHub-source rendering (Mermaid, no build tooling) over generation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Build-time and Docker dependency.&lt;/strong&gt; The docs build now shells out to Docker and adds
render time (target ≤ 60s, a &lt;strong&gt;monitored budget/warning&lt;/strong&gt;, not a hard per-PR gate, per
the flakiness policy). A runner without Docker cannot render these diagrams — acceptable
because CI-Linux (which has Docker) is the hard gate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A new lane to govern.&lt;/strong&gt; There are now two diagram lanes with different conventions
(hand-authored/source-rendered C4 vs generated/docsite-only schema). The R-04 amendment
and this ADR cross-link so the boundary is stated once and identically in both places.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Reconciliation with R-04 (and #1839)&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;R-04 in &lt;a href=&quot;/architecture/diagrams/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/diagrams/README.md&lt;/code&gt;&lt;/a&gt;
records that deterministic diagram &lt;strong&gt;generation&lt;/strong&gt; (Structurizr/PlantUML) is out of scope
for the living C4 model, which stays hand-authored so it renders on GitHub. That line is
&lt;strong&gt;unchanged for hand-authored C4 architecture diagrams&lt;/strong&gt; — the C4 lane keeps its
convention. This ADR opens a &lt;strong&gt;separate, narrowly-scoped lane&lt;/strong&gt;: &lt;strong&gt;generated,
docsite-only schema diagrams of code models&lt;/strong&gt;, governed here and by the
&lt;code dir=&quot;auto&quot;&gt;plantuml-diagramming&lt;/code&gt; toolguide. The two do not contradict because they cover different
genres: R-04’s “generation out of scope” applies to the C4 architecture model; the new
lane applies only to drift-guarded schema depictions of frozen doctrine models. The R-04
entry is amended to state this carve-out and cross-link this ADR.&lt;/p&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mission spec: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/doctrine-schema-diagrams-01KZTQTH/spec.md&lt;/code&gt; — FR-001, FR-002,
NFR-002, NFR-003, NFR-005, C-001, C-002, C-004, C-005, C-006.&lt;/li&gt;
&lt;li&gt;Research: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/doctrine-schema-diagrams-01KZTQTH/research.md&lt;/code&gt; — D1 (rendering),
D2 (drift guard), D4 (ADR / R-04 reconciliation).&lt;/li&gt;
&lt;li&gt;Toolguide (charter-prose active): &lt;code dir=&quot;auto&quot;&gt;plantuml-diagramming&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;packs/built-in/toolguides/plantuml-diagramming.toolguide.yaml&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Charter: &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; § &lt;em&gt;Writing, Communication &amp;#x26; Diagramming Doctrine&lt;/em&gt;
— &lt;code dir=&quot;auto&quot;&gt;USE_C4_MODEL_TECHNIQUES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mermaid-diagramming&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;plantuml-diagramming&lt;/code&gt; toolguides,
&lt;code dir=&quot;auto&quot;&gt;docs-accessibility&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Amended R-04 entry: &lt;a href=&quot;/architecture/diagrams/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/diagrams/README.md&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Upstream generation-scope issue this carve-out refines: &lt;code dir=&quot;auto&quot;&gt;#1839&lt;/code&gt; (deduped vs &lt;code dir=&quot;auto&quot;&gt;#1812&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-11-10--the-doc-kitty-site-renders-against-a-sandboxed-plantuml-service&quot;&gt;Amendment 2026-11-10 — the doc-kitty site renders against a sandboxed PlantUML service&lt;/h2&gt;
&lt;p&gt;Issue #6936 (epic #6100), under ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/4.x/2026-10-31-1-the-docsite-is-built-with-doc-kitty.md&lt;/code&gt; D-11.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Renderer.&lt;/strong&gt; On the doc-kitty site, PlantUML renders at build time against a PlantUML server that runs as a service container of the &lt;code dir=&quot;auto&quot;&gt;docs-site&lt;/code&gt; job (&lt;code dir=&quot;auto&quot;&gt;.github/workflows/docs-site-build.yml&lt;/code&gt;): &lt;code dir=&quot;auto&quot;&gt;plantuml/plantuml-server:jetty-v1.2026.9@sha256:065c66adc6728ba6dd353a29d4ada73f8358b68549a0f710c4bf46b43c103618&lt;/code&gt;, pinned by digest, with &lt;code dir=&quot;auto&quot;&gt;PLANTUML_SECURITY_PROFILE=SANDBOX&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;make docs-site&lt;/code&gt; renders against the same image (&lt;code dir=&quot;auto&quot;&gt;make docs-site-plantuml&lt;/code&gt;); a test keeps the two digests equal. The render output is the static SVG figure doc-kitty emits; the built-site check’s &lt;code dir=&quot;auto&quot;&gt;diagrams&lt;/code&gt; surface proves every published diagram is one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;docker run --network=none&lt;/code&gt; no longer applies on this path.&lt;/strong&gt; A service container has a network, so Decision 2 cannot carry over.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The guarantee is now behavioural: the renderer refuses every remote include, proven by a canary check on every docs-site run.&lt;/strong&gt; Before the build, &lt;code dir=&quot;auto&quot;&gt;dockitty-assert-plantuml-no-remote-include --service-container &amp;#x3C;the service&gt; --canary-host &amp;#x3C;its network gateway&gt;&lt;/code&gt; proves the canary is reachable from inside the service, then that a &lt;code dir=&quot;auto&quot;&gt;!includeurl&lt;/code&gt; and an &lt;code dir=&quot;auto&quot;&gt;!include &amp;#x3C;url&gt;&lt;/code&gt; diagram both render as errors with zero canary requests, then that the running container’s security profile is exactly SANDBOX. Any failure fails the job before the build. doc-kitty’s &lt;code dir=&quot;auto&quot;&gt;plantuml-guard&lt;/code&gt; check also runs and fails if the toolkit’s PlantUML stage names &lt;code dir=&quot;auto&quot;&gt;plantuml.com&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;External includes stay off.&lt;/strong&gt; doc-kitty’s external-include opt-in (doc-kitty #268) is not used, per the operator ruling of 2026-11-01 on #6936. No current diagram uses &lt;code dir=&quot;auto&quot;&gt;!include&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The DocFX lane is unchanged.&lt;/strong&gt; The pinned jar, the digest-pinned JRE container under &lt;code dir=&quot;auto&quot;&gt;--network=none&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;scripts/docs/plantuml_render.py&lt;/code&gt; keep serving DocFX until its retirement (#6943). The two lanes run different PlantUML versions (jar 1.2025.4, server v1.2026.9), so a rendering may differ slightly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; still renders.&lt;/strong&gt; doc-kitty v0.7.0 wraps a block in &lt;code dir=&quot;auto&quot;&gt;@startuml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;@enduml&lt;/code&gt; and prepends its theme preamble; through that transform the five &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; blocks rendered error-free, byte-identical to a plain render, with the pinned 1.2025.4 jar (checked 2026-11-10); the service renders them on every docs-site run, and a render error fails the build. The preamble does not reach them, so they keep PlantUML’s default colours.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
