@quillmark/wasm 0.104.0 → 0.106.0

package/CHANGELOG.md

@@ -1,5 +1,249 @@
 # Changelog
 
+## v0.106.0 - 2026-08-16
+
+- feat(typst,pdfform): a schema address may step one property into a declared
+  container, so `form-field(field: "classification.poc")` and
+  `field-region("address.city")` name a cell rather than the container holding
+  it. Two generated address tables gate the step the way `array_fields` gates
+  the index step, and a typed dictionary and a variant container reach both
+  alike: `classification.value` addresses the discriminant, `classification.poc`
+  a variant cell in any world. The pdfform binder descends a variant container
+  to match, so one address binds on either backend where `address.city` bound
+  only on pdfform and asserted on Typst. **Region addresses shift** for a plate
+  that reads a container property directly: `#data.classification.poc` regions
+  as `classification.poc` where it regioned as `classification`, and `fieldAt`
+  answers the same. A container read whole is unchanged, as is a read of a key
+  the container does not declare.
+- feat(core,wasm)!: an `enum` may declare `variants:`, a per-member field set
+  that exists only in the world where the discriminant holds that member. This
+  is the DSL's first cross-field shape, and it replaces the `cui_`-prefix
+  convention with one the engine checks: `must_fill` inside a variant keeps its
+  ordinary `default:`-presence derivation, so it reads *required in this world* —
+  a `poc` obliged on a CUI memo and silent on every other one, the thing
+  `must_fill` alone could not say. **Breaking**: declaring `variants:` changes
+  the field's resting shape at every projection, from a bare string to a
+  container, `{value: <member>, …that member's fields}`; the bare scalar
+  (`classification: CUI`) is still accepted as the spelling of a world carrying
+  no answers, and coercion normalizes both. The wire carries exactly the live
+  world, so a plate reads a variant field inside the `values ∪ blank` branch it
+  already owes the enum, and inside that branch every declared field is present
+  and needs no guard. A value stranded by a discriminant flip is kept and warned
+  (`validation::out_of_variant`), never dropped at coercion or gated at render.
+  The ceiling is enforced at load, not discovered at render: a variant carries
+  plain data only, sits at card level only, and cannot declare `value`. The
+  transform schema projects the container with every world's fields flattened
+  under `properties`, since a binding built once against a schema must address a
+  field today's document has not selected; member scoping stays on the
+  declaration view, where `schema()` emits `variants:` keyed by member.
+  `FieldSchema` gains `variants` and `variant_field` (the cell a name declares
+  under any world); `VariantFields` and `VARIANT_DISCRIMINANT_KEY` are new.
+- feat(fixtures)!: `usaf_memo`'s four `cui_*` fields move under
+  `classification`'s `CUI` variant as `controlled_by`, `poc`, `category`, and
+  `limited_dissemination`. `controlled_by` and `poc` drop their `default: ""`
+  and are therefore obliged — on a CUI memo only, which is what DoDM 5200.48
+  actually requires and what the flat spelling could state only in
+  `description:` prose. A document writes `classification: {value: CUI, …}` and
+  a plate reads `data.classification.value`.
+- feat(typst): `field-region(field, body)` claims the ink `body` draws for a
+  schema field, so a plate can tie content it *composes* — a banner keyed on a
+  field, a package-built block, a computed table — to `session.regions()` and
+  `session.fieldAt(..)`. Layout-neutral: `body` is returned untouched between two
+  invisible `metadata` markers. It is a **fallback** claim, never an override:
+  ink already tracked to a field keeps that field, so wrapping is purely
+  additive and cannot retarget. Each *call* claims independently, so a wrapper
+  invoked once per card yields one region per card — the way a card's scalar
+  fields get regions at all, reading as they do from a loop variable that carries
+  no per-instance identity. The marker stack persists across pages so a claim can
+  span a page break, which leaves a claim whose closing marker never reaches a
+  frame bounded by nothing: it would take every unattributed piece of ink to the
+  end of the document. Those are found before the scan and suppressed in both the
+  region and point queries — an unbounded claim yields nothing rather than
+  everything — and reported as a `typst::unclosed_field_region` warning naming
+  the field, since only the plate author can act on it. Typst does not separate
+  the two markers on its own — they are siblings in content flow — but a plate
+  emitting the call's return value in parts can.
+- feat(typst,pdf): `form-field` takes `font`, `size`, and `align`, so an
+  injected widget's value can be set to match the type around it. A widget was
+  fixed at Helvetica, auto-size, left: auto-size makes the rendered size a
+  function of both box height and how much the user has typed, and left
+  justification cannot be overcome by geometry, because a fillable box is sized
+  for the longest plausible value rather than the value in it. A right-aligned
+  fill-in — a USAF memo's date, say — was unreachable. `font` is one of
+  `"helvetica"`/`"times"`/`"courier"`, a widget being unable to carry a font
+  program; `size` is an absolute length or `auto` for the old behavior; `align`
+  is `"left"`/`"center"`/`"right"` and lands in `/Q`. All three are rejected on
+  `"checkbox"` and `"signature"`, which carry no variable text. `FieldSpec`
+  gains `font`, `font_size`, and `align` (`FormFont` and `TextAlign` are new).
+  A field that sets none of them stamps byte-identically to before, and
+  `pdfform` is untouched: `form.json` still carries no styling, so the flatten
+  path and canvas preview are unchanged.
+- fix(fixtures): the `usaf_memo` indorsement date widget is set in the memo's
+  own 12pt Times and ends on the right margin, where the date it stands in for
+  would have ended. It was auto-sized Helvetica starting at the fill-in rule's
+  left end. Sizing it exposed that the rule-width box clips a real date — "28
+  September 2026" sets 93pt at 12pt Times against a 72pt box, and a fixed size
+  clips where auto-size had silently shrunk — so the widget is now 10em wide
+  and hangs off the rule's right edge, overrunning leftwards into the
+  whitespace a printed date grows into. Sized in ems of its own face rather
+  than inches because `font_size` is a document field with no ceiling: an inch
+  width would stay put while the text inside it grew. 10em clears both
+  orderings at any body size (DAF's "September 28, 2026" is the widest at
+  8.03em; USAF's "28 September 2026" is 7.78em). `date-placeholder-line` seats
+  it with a measured `dx` rather than `place(bottom + right)`, Typst clamping
+  an overflowing alignment back to zero, which leaves `right` indistinguishable
+  from `left`. That helper draws no rule now and is named `date-placeholder`
+  rather than `date-placeholder-line`: the widget carries the date, and a rule
+  under a widget wider than it underlines only the fraction of the value narrow
+  enough to sit over it. It is package-internal, not exported from `lib.typ`.
+- fix(core): a name two variants declare *differently* is a load error,
+  `quill::variant_field_collision`. The name is one cell of the container
+  whichever world brings it into play — neither the coercion lookup nor the
+  transform schema consults the discriminant to fill it — so two readings of it
+  coerced a live value under the other world's type: a document selecting a
+  world whose `note` is `integer` had its `42` coerced to `"42"` by a sibling
+  world's `string` and then failed `validation::type_mismatch`, undraftable and
+  blamed for a string it never wrote. Identical declarations, which is what
+  repeating a shared field set or sharing a YAML anchor produces, collapse to
+  that one cell without loss and stay legal.
+- fix(core,wasm,python)!: `EditError::UnknownField` carries the in-field path
+  `FieldDecode` and `FieldNotContent` carry. A property an `object` field does
+  not declare — `get_content_at("address", [Key("zip")])` against an `address`
+  with no `zip` — reported `field 'zip' is not declared in the schema`, which
+  reads as a claim about a top-level field and collides outright when a real
+  top-level field shares the name. It now reports
+  `field 'address.zip' is not declared in the schema` and anchors the
+  diagnostic at `main.address.zip`, so the caller can tell an undeclared
+  property from an undeclared field. **Breaking**: the variant is a struct
+  variant, `UnknownField { field, at }`, matching the two siblings; `field`
+  stays a bare field name, and the `edit::unknown_field` code, its `field` arg
+  and the whole-field message are unchanged.
+- fix(python): declaring `license-files` ships the `LICENSE` the sdist metadata
+  names, which PyPI rejected the sdist for lacking. v0.104.0 and v0.105.0 are
+  wheels only.
+
+<!-- seed: commits since v0.105.0, confirm the entries above cover them, then delete this comment
+- chore(repo): union-merge CHANGELOG.md
+- feat: migrate usaf_memo to enum variants, document the axis
+- feat(core): enum variants — fields that exist only for one enum value
+- fix(fixtures): drop the rule under the indorsement date
+- fix(fixtures): size the indorsement date widget in ems, not inches
+- fix(fixtures): set the memo's indorsement date widget like a date
+- feat(typst,pdf): font, size, and align on injected form fields
+- Make the usaf_memo indorsement's blank date a bound fill-in widget
+- Compress the field-region prose
+- Add `field-region` so plates can tie composed content to a field
+- fix(python): declare license-files so the sdist ships its LICENSE
+- Anchor an undeclared property at the property, not at a bare name
+-->
+
+
+## v0.105.0 - 2026-08-14
+
+- feat(core,wasm,python)!: a `Content` nested inside a composite field is
+  readable at its own codec. `TypedReader::get_content_at(name, path)` (and the
+  `CardReader` twin, `reader.getContentAt(addr, path)` in JS,
+  `reader.get_content_at(name, path)` in Python) walks a `PathSegment` path
+  through the field schema — `items` for an index, `properties` for a key — to
+  the leaf whose declared type names the codec, then decodes through the same
+  dispatch the whole-field read uses. So an `array<richtext>` element, an
+  `object`'s content property and a leaf under both each read back the same
+  `Content` whatever their resting form, where before every one of them
+  answered `FieldNotContent` and the consumer had to decide for itself what the
+  stored bytes meant (#1243). The empty path *is* `get_content`. A path naming
+  nothing in the stored value reads absent rather than throwing: an editor's
+  row index goes stale between derive and read, and that is the axis a repeater
+  mutates. `Addr` deliberately gains no element axis — the path is the read's
+  own argument, since `storeField` / `isFill` / `applyChange` could not answer
+  one. **Breaking**: `EditError::FieldDecode` and `EditError::FieldNotContent`
+  each gain an `at: Vec<PathSegment>` field carrying the in-field path, so the
+  diagnostic anchors at `main.paragraphs[1]` and parses back to those segments;
+  `field` stays a bare field name and `args` is unchanged. `FieldNotContent`
+  now names the type *reached*, so a `string[]` element reports `string` rather
+  than the field's `array`.
+- feat(core,wasm)!: `must_fill:` on a field declares the **obligation** axis.
+  `default:` carried the fill value and the obligation signal on one bit, so
+  only that 2x2's diagonal was reachable; a safe value that still wants a
+  human's confirmation (`default: UNCLASSIFIED` with `must_fill: true`) and a
+  genuinely optional field with nothing to suggest (`must_fill: false`) now
+  each have a spelling. Left unset it derives `default.is_none()`, so no
+  existing quill's blueprint marker set changes. `Quill::validate` gains a
+  second trigger under the one `validation::must_fill` code, named by a
+  `trigger` arg: `marker` for a `!must_fill` tag the document carries, and
+  `unauthored` where the schema obliges a cell the document leaves absent or
+  present-null. The second closes a hole — `validate_fills` walked only the
+  payload, so a hand-written or programmatically built document drew no
+  completeness signal whatever `Quill.yaml` declared. **Breaking**: a merely
+  incomplete document no longer validates clean. Absence is still never
+  *malformed* and still never gates render, but a consumer reading "any
+  diagnostic ⇒ not done" now sees a warning per unauthored obliged cell on
+  documents that were silent. The obligation keys on cell presence rather than
+  the resolved source rung, so a must-fill leaf inside a container someone
+  touched still warns; a typed dict is never itself a cell and recurses to its
+  leaves, while an array is one cell, `[]` being a real answer. Authoring the
+  field's blank discharges it and `field: null` does not: null ≡ absent stays
+  unqualified on the value ladder, but obligation asks whether a human made a
+  call. Seeding stamps the marker on example-seeded obliged cells, so a fresh
+  seed and an empty document report the same cells, and the transform schema
+  carries `quillmark:must_fill` (#1255).
+- fix(core,wasm,pdfform)!: a field's **blank** — its spelling of "explicitly
+  nothing" — is a property of the field rather than a member of its type's
+  domain, and an `enum`'s is `""`. The render floor for a defaultless enum
+  returned `values.first()`: a choice nobody made, indistinguishable at the
+  plate from a deliberate one and reachable from a cosmetic `values:` reorder.
+  An unanswered enum now renders `""`, so a reorder is render-safe for every
+  document and only removing or renaming a member breaks
+  ([VERSIONING.md](prose/canon/VERSIONING.md)). **The accepted domain widens to
+  `values ∪ blank` for *every* enum**, defaulted ones included: `format: ""`
+  was a fatal `EnumViolation` and now coerces, validates and reaches the plate.
+  **A plate must therefore branch exhaustively over `values ∪ blank`** — an
+  `else` fallback re-opens exactly the fabrication the blank closes, and a
+  downstream package that asserts membership fails the compile outright. Note
+  `data.at(key, default: X)` is not a guard here: blank-filled render makes
+  every declared key present, so its `default:` is dead code and the blank
+  flows through. **Breaking**: `zero_value` → `blank`, `FieldSource::Zero` →
+  `Blank` and its wire token `"zero"` → `"blank"`; `""` declared in `values:`
+  is a load error (`quill::enum_blank_member`), the engine supplying the blank
+  instead; and `date: ""` renders blank rather than falling back to a
+  `default:`, settling a three-way disagreement between coercion, validation
+  and the floor. `default: ""` stays valid and keeps its meaning — `values:`
+  enumerates choices, `default:` is a value, and the blank is a legal value
+  that is never a choice. Additive: `ui.blank_title` labels an enum's blank and
+  rides the transform schema as `quillmark:blank_title`; that schema's `enum:`
+  leads with the blank, so a standard JSON-Schema validator accepts what the
+  engine accepts, and pdfform Choice widgets lead their options with it too. A
+  consumer's picker must keep the blank selectable and re-selectable — returning
+  to it is how an author clears a cell back to unset.
+  `integer`, `number` and `boolean` keep `0` / `false` as their blank,
+  indistinguishable from an authored zero — a permanent seam, since a wire
+  `none` would cost the totality the floor exists to buy. Full guide:
+  [0.104 → 0.105](docs/migrations/0.104-to-0.105.md) (#1254).
+- fix(fixtures,docs): the three fixture plates that dispatch on `$kind` read it
+  with a bare `card.at("$kind")`, which panics on a kindless card, and guarded
+  declared fields against an absence blank-filled render makes impossible.
+  Plate authors copy the fixtures rather than `PLATE_DATA.md`, so the fixtures
+  were teaching both the unsafe metadata read and a dead presence check.
+  `classic_resume` carried the live consequence: `url` is declared with no
+  `default:`, so the floor delivers `""`, `default: none` never fires, and the
+  package's `url != none` test always passes — an empty Courier element where
+  the block should have been skipped. Its `subheading-*` guard cost an empty
+  grid row the same way. Declared fields now guard their *value*, and
+  `docs/quills/typst-backend.md` states the rule as a table over the three key
+  kinds. `fixture_quills_render_test` renders every fixture quill's seed
+  document — the net that was missing, since `classic_resume`'s plate had no
+  test reaching it (#1256, #1257).
+- test(typst): `plaintext` reaches regions and navigation by inheritance — the
+  render floor coerces its resting literal to a content object, the backend
+  classifies that object by `contentMediaType` alone, and the shared lowering
+  emits it with a segment map — and every step was load-bearing and untested,
+  with the classification predicates named for richtext so the sharing read as
+  a coincidence. Pinned at engine altitude, because a test driving the backend
+  directly hand-builds the content object, bypassing the floor's coercion, and
+  would stay green through a regression that silently empties `regions()`. The
+  predicates are `is_content_field` / `is_content_array_field` /
+  `is_inline_content_field`, and `PREVIEW.md` names plaintext beside richtext
+  in its producer list (#1247, #1250).
+
 ## v0.104.0 - 2026-08-13
 
 - feat(core,wasm): a quill declares, per body, the block constructs its plate
@@ -93,33 +337,6 @@
   fixture suite reached neither path. A fourth carries a `!must_fill` tag on two
   example-seeded cells through seed → store → load → conform. Refs #1234
 
-<!-- seed: commits since v0.103.0, confirm the entries above cover them, then delete this comment
-- Carry the thematic-break and unsupported-construct work into the guide
-- Dense-prose pass over the new comments and docs
-- Let a quill declare the constructs its plate does not typeset
-- Drain the memo's heading buffer instead of dropping it
-- Canonicalize a thematic break to `***`
-- Close the 0.104 release gaps: the migration guide, and four changelog entries
-- Retire the enum: modifier; project a field's domain by capability
-- Pin the render floor's two type-domain edges and the seeded fill tag
-- Raise the Node floor to 24
-- dense-prose pass over the added prose
-- docs: dense-prose pass on the text-type sections
-- docs: give the text-type choice a decision procedure
-- docs: state the backend seam's scope and reserve its namespaces
-- docs: drop the private intra-doc link from pathFor
-- fix(core): state the unspellable-tail conditions instead of linking a private fn
-- chore(wasm): density pass, and gate a core-build dead function
-- docs: dense-prose pass over the geometry-address translation
-- docs: dense-prose pass over the pathFor / cardPath prose
-- test(wasm): execute the static-export exemption instead of listing it
-- feat(wasm): mint a DocPath from an Addr (#1225)
-- fix(core)!: parse geometry addresses segment-wise (#1223)
-- docs: carry the 0.103 CLI break, and the init gate into the quickstart (#1222)
-- SCHEMAS.md: a declared type change rewrites stored values (#1221)
--->
-
-
 ## v0.103.0 - 2026-08-09
 
 - docs: `docs/integration/operations.md`, carrying what the other integration