[DemchaAV]

Why

The v2.5.0 entry grew one bullet per DOCX change, all of them under ### Public API: 256
bullets, about 4,800 lines, of which 9 add or change public API. A reader had no summary of
what the DOCX export became in 2.5, and nothing told a 2.4 user what changes in the file they
get or in the code they write. Older bullets still stated as current behaviour that later
changes in the same cycle replaced — line heights written exact on every paragraph, a timeline
rail drawn as a bar, shapes anchored to the page. And the acceptance figures a Tests bullet quotes,
41 of 62 presets in Word and 37 in LibreOffice, came from the corpus's first run.

What changed

• ### Highlights at the top of the entry: what the DOCX export is in 2.5 — written from
  the compiled layout, Word charts with an embedded workbook, DocxExportReport, bytes identical
  on one platform with deterministic(true), buildDocx / writeDocx / toDocxBytes, and the
  corpus it is held to, with the acceptance measured today. One line for the PDF text layer of an
  inline icon.
• ### Migrating the DOCX export from 2.4: code keeps compiling (the Stable
  session.export(new DocxSemanticBackend()) path, kept constructors); what a reader of the file
  should expect instead (Word numbering, Normal-style runs, chart parts, anchored drawings,
  fixed-layout tables, one-line bands, spacers, a page zone as the page lays it out and on the
  pages its predicate picks — 2.4 wrote it as one line on every page — and the text headers,
  footers and page backgrounds 2.4 ignored); which log warnings went and came, and that the
  report names every node; the layout pass the export now costs; embedded fonts;
  where an editable rule comes from; byte comparisons through a deterministic backend passed to
  export(...); graph-compose-render-docx no longer needing render-pdf declared by hand; the
  two record-pattern source breaks (SemanticExportContext, ShapeNode). Each point is taken
  from the 2.4.1 recipe against the current recipe, matrix and code.
• ### Fixed: the 247 bullets that change what the export writes and add no public API move
  out of ### Public API, in their order. The 9 that add public API stay (the members come from
  the knowledge-pack diff v2.4.1..HEAD). No line is dropped or reworded by the move.
• Superseded claims: 62 sentences that a later change in this cycle replaced get a pointer
  in the form the entry already uses — (since …: see "<newer entry>") — rather than being cut;
  each names a newer entry. The deterministic-bytes entry also says the bytes match on one
  platform.
• Stale numbers: the acceptance bullet now reads 77 of 84 in Word 16 and 48 of 84 in
  LibreOffice 24.2 on CI's Linux, keeping 41 and 37 as the first run's; the corpus bullet counts
  64 presets and 20 built documents rather than 62.

No version, date or release metadata changes; the entry stays "Planned".

Verification

• Acceptance measured on this tree's base: scripts/docx-visual/word-fidelity.ps1 (Word
  16.0.20527) — 77 of 84 pass, all 64 presets, gate green against word-windows.tsv; CI run
  42135867817 on 2.5-dev at 5f42b51, measured-libreoffice-acceptance.md — 48 of 84, 40 presets.
• The move step, before any addition, is checked by script: the non-blank lines before and
  after it are the same multiset, plus the one ### Fixed heading. Every new pointer's quoted
  title is checked to be an existing bullet lead.
• ./mvnw -B -ntp test -pl :graph-compose-core -Dtest='com.demcha.documentation.**' — 172 tests,
  0 failures (VersionConsistencyGuardTest, which reads the CHANGELOG headings, included).
• ./mvnw -B -ntp test -f qa/pom.xml -Dtest='com.demcha.documentation.**' — 28 tests, 0 failures.
• scripts/release-notes.mjs on the extracted 2.5 section: 520,452 characters, condensed to its
  322 entry leads (31,111 characters) for the GitHub Release, Highlights and Migration first;
  node --test scripts/release-notes.test.mjs passes.
• Full reactor gate on the final tree (clean verify as CI runs it, the four knowledge checks,
  core javadoc, install and the examples tests): passed — core 841, render-pdf 339,
  render-docx 2539, testing 5, render-pptx 142, templates 128, qa 1910, examples 93; 0 failures,
  0 javadoc warnings.

Lane: documentation only — no code, test or generated file changes.