[DemchaAV]

Why

A drawing placed from its paragraph moves with that paragraph when a reader edits the text above
it. One placed from the page keeps its place on the sheet while the text it belongs to is edited
away from under it — the card walks down the page and the icon over its corner stays behind.

Four changes in a row taught the export to carry such drawings, bringing the template corpus from
465 drawings placed from the page down to 32. Nothing held what they won: no test read where a
drawing is placed from at all, so a change putting one back on the sheet would have left every
suite green.

What changed

Test code only — no engine change, so the corpus is byte-identical and no baseline moves.

DocxDrawingPlacements (new) reads every drawing of a DOCX from every XML part — the body, its
headers and footers, and the tables and text boxes nested in them — with what each is placed from
and across, whether it floats, and the wp:docPr name the export writes it under, which is what
tells a drawing a node paints (Drawing N) from a page's own fill (Page background N). A drawing
standing in another's text box is read in its own right, each anchor in its own frame.

It also reads simplePos, which the rest of this would be blind without: at simplePos="1" Word
and LibreOffice take the place from wp:simplePos and read neither positionH nor positionV, so
a drawing nailed to the sheet that way still says relativeFrom="paragraph" in the file. A truthy
value is reported as a problem; left out, the attribute means what "0" means, as the schema has
it.

An anchor the reader cannot classify — nothing to be placed down from, no name, a name that is
neither a drawing nor a page fill, an offset that is no number, a place it was not written to judge
— is reported as a problem rather than passed over.

FlowOwnerDrawingDocuments (new) holds six small documents, one for each paragraph that carries
a drawing today: a paragraph of the body, a panel's, a column of a row, an item of a list, the one
line two halves of a band share, and a table cell a drawing is all of. Between them they cover all
three writers of text that offer a paragraph to the drawings beside it — a paragraph node, a list's
item, a band's shared line — and the exception for a drawing that is all a cell holds, which offers
no paragraph at all; the first three share the paragraph node as their writer and differ in the
holder whose paragraph the walk must find. Each is small enough that a failure names what stopped
carrying the drawing. They are deliberately not in the fidelity corpus — they hold the rule, where
the corpus fixes what the export does today, and adding documents to the corpus moves its
baselines.

DocxDrawingAnchorGuardTest (new) holds both. Over the corpus, the drawings still placed from
the page must equal, document for document and drawing for drawing, a ledger that names the reason
each is there:

• 25 of a table's composed cell, where the walk from the cell whose box holds the drawing finds
  no paragraph of that cell it can be placed from and the fall back to the nearest text does not
  place it either — invoice-payments 13, invoice-workspace 8, invoice-merchant 4, each with
  92 or more paragraphs on its page, so it is not for want of one. Which step gives up is not
  pinned down, and the entry states the outcome rather than guessing at a mechanism.
• 6 whose owner's own text is written as the drawing itself — a brand lockup's four badges and
  a closing banner's two, laid over the flow and set in a text box where the page sets them — so
  that no paragraph of the blocks holding them stands on their page at all.
• 1 with four paragraphs of its own block on its page that none of them was placed from. How
  far it rises is not what refuses it: risesNoFurther is reached only from Seat.place, which a
  composed cell's drawing takes by way of placeBeside, while a drawing a node paints is placed by
  Seat.placeHeld, which never asks. Of what placeHeld does refuse on, one is measured out — the
  nearest paragraph's top is known, 52.80pt — and the rest are named in the entry, unmeasured.

The ledger names each drawing rather than counting them, so a change fixing one and breaking
another in the same document cannot pass on a tally that comes out the same. The equality holds
both ways: it is a record of work still to do, not a licence, and when the export learns to carry
those drawings the test fails until the ledger is brought down to match.

Over the six documents nothing may be placed from the page, and every drawing must be placed down
from a paragraph — not merely kept off the page, since an export that wrote these shapes into the
text instead would satisfy the weaker claim.

DocxFixtures (new) holds what this guard and DocxPageReferenceGuardTest both need to write a
DOCX by hand — the namespaces, a body, a header, a footer, a paragraph, the zip, and the check that
an export was made from its layout — which were about to exist twice. The page-reference guard now
uses it instead of its own copies.

docs/recipes/docx-export.md now says what being placed from the page costs a drawing, which the
rules around it described without naming the consequence.

Verification

Run on this branch, ./mvnw from the worktree:

• DocxDrawingAnchorGuardTest 15 tests and DocxPageReferenceGuardTest 11, 26 of 26 passing.
• test -pl :graph-compose-render-docx -am — 2363 tests, 0 failures, 1 skipped.
• test -f qa/pom.xml — 1871 tests, 0 failures, 1 skipped.

Each rule the guard holds was broken once, alone, and the guard had to go red on a reported test
failure — an exit code was not accepted as proof, after a scripting fault turned a Maven that never
started into a false "caught":

broken	guard
every drawing nailed to the sheet	red
every drawing sent to an absolute point (simplePos="1")	red
no holder ever places a drawing	red
no holding cell ever places a drawing	red
page fills no longer on the sheet	red
the reader reads no XML part	red
the reader reports every drawing as carried	red
the reader ignores simplePos	red
the reader takes a missing offset for nought	red
the reader ignores a second wp:positionV	red

Each was applied alone, to the final tree, and the set was re-run after every round of review
fixes, since both the reader and one document changed.

The corpus figures above were measured over the 71 exported documents: 760 floating drawings a node
paints, of which 728 are carried and 32 are placed from the page — the ledgered ones; 381 inline
drawings, which are placed from nothing and are not this guard's subject; and, separately, 32 page
fills, every one of them on the sheet, which is how the reader proves it can read a page-placed
drawing at all. The two 32s are different measurements that happen to agree.