Upgrade from 0.10 to 0.11

0.11 completes the readable composition direction. The structured visual changes are in MIGRATIONS.json. JavaScript exports, classes, and tokens remain available. If you are coming from 0.9, apply the 0.10 migration first, including the retired adapters/modal.

Review reusable layouts

Figures use their own inline-size container to stack a right-hand key below 44rem. Decision grids and action lists stack their rows below 32rem of their own width, including inside an otherwise wide report. Keep the documented ui-report__decision-grid and ui-report__actions wrappers. Two-up comparisons need no wrapper: they keep at most two columns, with a 16rem reading floor.

Test a 280px and 320px parent inside a 1440px browser. Check that charts have useful drawing width, text columns remain readable, long labels wrap and all sources are reachable. Zero page overflow alone does not prove those things. Keep authored SVG labels and annotations inside the drawing's viewBox, or provide a narrow fallback with the same information. Bronto does not own chart geometry. Named size containment is disabled in print; review your PDF too.

Review typography overrides by role

Figure captions, legends, generated labels and command groups use sans and sentence case. Technical log bodies and identifiers keep mono. Inline citation markers have a 12px floor at a default 16px root. Do not globally replace Doto: keep intentional hero/display and readout roles.

1. Find explicit font-family: var(--display) and var(--dot-font) declarations in your loaded consumer styles, plus old root-size and control-height rules.
2. Classify each use: display identity, numeric readout, heading, instruction, control label or metadata. Check grouped selectors individually.
3. Remove overrides that recreate old generic styles. Use var(--sans) for local explanatory headings and labels; keep intentional display roles.
4. Inspect complete tasks, not just the homepage. Include setup, result, filtering, error/retry, source details and an empty state where applicable.
5. Compare long names and translated text at narrow, laptop, and desktop widths, in both themes, with keyboard and touch input.

Consumer CSS outside a layer takes precedence over the package's bronto layer. Updating the package alone cannot change those explicit overrides. A prepared patch from an older application revision must be reintegrated and checked against current source before it can count as migration evidence.

Verify the package and consumer together

Install the packed candidate into an isolated consumer checkout before changing production pins. Record the exact package version, consumer revision and screens checked. Update the dependency and registry lock file together after publication; do not commit a task-local tarball path into a production lock file.

Use the composition guide for the service's local state scenarios, container boundaries and report reading/print checks. Existing package checks remain necessary; real consumer tasks provide additional evidence.

Optional discussion UI

Import @ponchia/ui/css/discussion.css for thread lists, quotations, messages, and composers. The new ui-discussion vocabulary is additive. It carries no posting behavior, storage, or editor dependency; see Discussions.