test(docx): fail Word's restyle scenario when text is left without room for it

[DemchaAV]

Why

The restyle scenario passed documents whose text Word visibly breaks after the restyle. restyle-body-through-normal in scripts/docx-visual/edit-protocol-corpus.ps1 checked one thing: that the body's letters grew with Normal by 2pt. It passed every corpus document.

An exported DOCX sets almost every paragraph on an exact line (w:lineRule="exact"), and an exact line keeps its height when the letters grow. After Normal +2pt, Word sets cv-editorial_blue's profile in 11.5pt letters on the 10.3pt lines its 9.5pt letters had. The lines overlap, and on screen Word also cuts the letters' tops. Word's PDF export does not show the cut, so the fidelity gate cannot catch it either.

What changed

• Restyle judges the room the grown letters get, wherever the restyle reaches.

  • Get-StoryParagraphs collects every paragraph Normal reaches: the main text, each section's own headers and footers, and the text drawings hold. Each is keyed by story and place, so the reopened document gives the same keys.

  • Before the edit it records each paragraph's largest letters (Get-LargestLetters) and the drawings whose text already overflows (Get-OverflowingFrames).

  • The scenario fails when a paragraph whose letters grew:

    • stands on exact lines shorter than 1.1× them, or
    • sits in a row or frame of exact height (Get-HeldBox);

    or when a drawing's text newly overflows it.

  • The detail counts each kind and names the first of each, for example 'Platform engineer with 1' (body 8) 9.5 -> 11.5pt letters on 10.3pt exact lines.

• One threshold, the one the protocol already had. 1.1 is $EXACT_LINE_SHARE, which add-a-page uses for typed text.
• Only grown paragraphs are judged. The page sets many exact lines tighter than 1.1× their own letters before any edit: all 74 exact paragraphs of cv-editorial_blue are. That spacing is the page's leading, not a cut the edit made.
• A scenario with nothing to edit is recorded N/A with a reason from $NOT_APPLICABLE, instead of vanishing from edit-protocol-corpus.json.
  • N/A does not fail the run.
  • An edit counts as having nothing to edit only when it returns [bool] $false. PowerShell treats 0 -eq $false as true, so an edit ending on a call that returns 0 would otherwise turn into N/A.
  • drawings-follow-text is N/A when no drawing stands beside text, for example when the only drawings are page backgrounds.
• One-scenario runs write a list. Invoke-Protocol's result is wrapped in @(...), because PowerShell hands a one-element array back as its element.
• CONTRIBUTING's description of the protocol and a CHANGELOG Tests entry describe the checks.

Verification

Known-answer documents in Word 16.0 (16.0.20430), all scenarios:

Document	restyle	What it shows
Plain document Word wrote itself	PASS	Word's own line spacing passes
Word-written document: header line on exact lines (1.2× before the edit), text box its text just fills	FAIL	names header 1.1 1 (12 → 14pt on 14.4pt lines) and the overflowing drawing 1
Word-written document: footer line in a frame of exact height	FAIL	names it as grown in a frame of exact height
cv-editorial_blue	FAIL	22 paragraphs
receipt-modern	FAIL	9 paragraphs

On the exported documents the other scenarios keep the statuses an earlier run of the protocol gave them, including receipt-modern's add-a-page FAIL: text typed at its end goes into its closing table. The table, list and drawing scenarios are recorded N/A where a document has none.

Full corpus, 62 documents exported at 7c9808c7c, -Scenario restyle-body-through-normal:

• FAIL in 60.
• Of 1,989 paragraphs whose letters grew (body in all 62, footers in 2, text boxes in 3), 1,730 stand on exact lines too short for them. None is in a row or frame of exact height, and one drawing's text overflows.
• MintEditorial and MintEditorialLetter pass: none of their exact lines falls below 1.1×.
• The body follows Normal in all 62, and every document's scenarios is a list.

Documentation guards:

• ./mvnw -B -ntp test -pl :graph-compose-core -Dtest='com.demcha.documentation.**' → BUILD SUCCESS, 166 tests.
• ./mvnw -B -ntp test -f qa/pom.xml -Dtest='com.demcha.documentation.**' → BUILD SUCCESS, 28 tests.

No Java, POM or workflow file changes, so the full reactor gate was not run.

Lane: test — the local Word editing protocol (scripts/docx-visual) and its docs. No backend or public API change.