blocky-writer: boundary declared — viewer/editor stays yours, placement stays ours #61

Where blocky-writer is

Rust/WASM core green on main at e1b6225; the AffineScript frontend is a
prototype with no build pipeline in this checkout. We have just published our
suite boundary statement (docs/ecosystem/ECOSYSTEM.adoc, linked from our
README) as part of hyperpolymath/docmatrix#71's acceptance criteria, and seeded
a project wiki in BerryWiki format.

The boundary, as we have written it

blocky-writer owns fixed-layout PDF and application-form placement. It is
not a document viewer or editor — that is Formatrix Docs.

So: viewing and editing one logical document across your format tabs is yours,
and we will not reach for it. Placement into a form that already exists is ours.

What you might use from here

One concrete seam, and it is a small one. Our detect_blocks returns, per
widget annotation:

{ "label": "Name", "x": 50.0, "y": 700.0, "width": 200.0, "height": 24.0 }

label comes from the AcroForm field's /T, falling back to the parent field's
/T, falling back to field_<page>_<index>. Coordinates are PDF user space.

If your graph or relationship views ever want to show where in a document a
value lands, that is the shape we emit. We are not proposing an integration —
just noting the seam exists so neither of us invents it twice.

What we would need from you

Nothing blocking. If you render AsciiDoc, docs/ecosystem/ECOSYSTEM.adoc and
our wiki/ pages are the two files most likely to be useful as test material —
they are ordinary AsciiDoc and Markdown with no exotic constructs.

A note on A2ML

Your README lists A2ML as one of the tabbed representations. blocky-writer's
machine-readable state lives in .machine_readable/ as .a2ml files
(STATE.a2ml, ECOSYSTEM.a2ml, CLADE.a2ml, and the contractiles). If your
A2ML support is a parser rather than a passthrough, those are a real-world
corpus — small, but structurally varied.

Ref: hyperpolymath/blocky-writer#73