@quillmark/wasm 0.105.0 → 0.106.0

package/CHANGELOG.md

@@ -1,5 +1,143 @@
 # 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

package/backends/pdfform/wasm.d.ts

@@ -462,6 +462,11 @@ export interface QuillFieldSchema {
     /** The closed set of allowed values. Required on `type: "enum"`, and valid
      *  nowhere else. */
     values?: string[];
+    /** Per-member field sets on a card-level `type: "enum"` field, keyed by
+     *  member: the fields that exist only where the discriminant holds that
+     *  member. Declaring it makes the field rest as a container,
+     *  `{value: <member>, …that member's fields}`, rather than a bare string. */
+    variants?: Record<string, Record<string, QuillFieldSchema>>;
     /** Whether a human must author the field. Absent, it derives from
      *  `default`: a defaulted field is unobliged, a defaultless one obliged. */
     must_fill?: boolean;

package/backends/typst/wasm.d.ts

@@ -462,6 +462,11 @@ export interface QuillFieldSchema {
     /** The closed set of allowed values. Required on `type: "enum"`, and valid
      *  nowhere else. */
     values?: string[];
+    /** Per-member field sets on a card-level `type: "enum"` field, keyed by
+     *  member: the fields that exist only where the discriminant holds that
+     *  member. Declaring it makes the field rest as a container,
+     *  `{value: <member>, …that member's fields}`, rather than a bare string. */
+    variants?: Record<string, Record<string, QuillFieldSchema>>;
     /** Whether a human must author the field. Absent, it derives from
      *  `default`: a defaulted field is unobliged, a defaultless one obliged. */
     must_fill?: boolean;

package/core/wasm.d.ts

@@ -407,6 +407,11 @@ export interface QuillFieldSchema {
     /** The closed set of allowed values. Required on `type: "enum"`, and valid
      *  nowhere else. */
     values?: string[];
+    /** Per-member field sets on a card-level `type: "enum"` field, keyed by
+     *  member: the fields that exist only where the discriminant holds that
+     *  member. Declaring it makes the field rest as a container,
+     *  `{value: <member>, …that member's fields}`, rather than a bare string. */
+    variants?: Record<string, Record<string, QuillFieldSchema>>;
     /** Whether a human must author the field. Absent, it derives from
      *  `default`: a defaulted field is unobliged, a defaultless one obliged. */
     must_fill?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quillmark/wasm",
-  "version": "0.105.0",
+  "version": "0.106.0",
   "description": "WebAssembly bindings for Quillmark, a schema-driven document engine",
   "type": "module",
   "license": "Apache-2.0",