test(qa): report which presets each editor sets as the page does

[DemchaAV]

Why

The DOCX fidelity baselines hold each preset where it stands, however far that is from the page. Nothing says which presets are already set as the page sets them and which are not, or what keeps the rest short. That is the list the remaining DOCX work is taken from.

What changed

• FidelityAcceptance reports where each preset stands. It does not gate; the baselines gate. A preset passes when the editor:
  • sets it on the page's number of pages;
  • finds at least 95% of the page's lines;
  • sets them a median of 1pt or less from the page;
  • sets no more than 10% of them past 2pt.
• DocxFidelityCorpusTest writes the report beside each measurement as target/docx-fidelity/measured-<editor>-acceptance.md. It gives the number passing, then each preset short of it, with what keeps it short, the furthest first.
• ci.yml: the DOCX Fidelity job appends LibreOffice's report to the job summary, and uploads it with the measurements.
• Docs. CONTRIBUTING.md (testing expectations); CHANGELOG.md under Tests.

Verification

• DocxFidelityGateTest (20 tests, +2).
  • A preset at every limit passes.
  • One past each limit is held short on all four, by name.
  • The report counts those passing and lists only those short.
• The corpus, run locally:
  • Word 16.0 (16.0.20430): 41 of 62 presets pass. The furthest short are CobaltRota (median 2.48pt), OrangeOps (2 pages), SlateOrange, MidnightNavy, Editorial and MonogramSidebar.
  • LibreOffice on Windows: 37 of 62 pass.
  • Both baselines still hold.
• CI guards (CiGate*, CiGuardListGuardTest, CodeQlScopeGuardTest) pass.
• Full reactor gate: ./mvnw -B -ntp clean verify -pl :graph-compose-core,:graph-compose-render-pdf,:graph-compose-render-docx,:graph-compose-render-pptx,:graph-compose-templates,:graph-compose-testing,:graph-compose-qa,:graph-compose-coverage -am gives BUILD SUCCESS (qa 1813).
  • After install, examples run 93 green.
  • The knowledge checks pass.

Known limits

• "Lines found" stands in for "no text lost". A line the editor breaks at another word counts as not found, though its text is there.

Lane: test (qa) and CI.