chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@prescriptive/reativa@0.4.0

Minor Changes

• 19d5252: Add the final batch of reativa example implementations, reaching full parity
  with the Xote examples — every spec that has a Xote demo now has a matching
  Reativa preview, mirroring website/src/Examples.res.

  • components: form, resizable, search, comment
  • pages: dashboard, landing-page, pricing, settings, sign-in
  • flows: authentication, checkout, onboarding

  search filters a list live with View.for_; resizable binds a range input
  to a reactive style on both panels; form submits with View.On.submit +
  prevent_default and reveals a success message via View.show; sign-in wires
  a native checkbox through a reactive checked binding; the authentication and
  onboarding flows step through their states from a single step signal.
  Registered in Registry.mlx's example_for / example_ids. reativa now covers
  26 elements, 42 components, 13 blocks, 5 pages, and 3 flows — the same set Xote
  implements.

• 19d5252: Add the second batch of 20 more @prescriptive/reativa example implementations —
  the overlay, data, picker, and navigation components — so each spec gets a
  Reativa preview alongside the Xote one, matching the demos in
  website/src/Examples.res.

  • overlays & menus: alert-dialog, dropdown-menu, context-menu,
    popover, hover-card, sheet, drawer, toast
  • data & pickers: table, data-table, chart, carousel, combobox,
    command, calendar, date-picker
  • navigation: navbar, menubar, navigation-menu, sidebar

  These lean on Reativa.View's reactive primitives: View.show for the
  open/closed overlays (dismissed via the existing Backdrop), View.for_ for
  the live-filtered lists (combobox, command, data-table), class_reactive
  for the selected-day / active-dot state (calendar, date-picker, carousel),
  and a reactive style for the carousel track. context-menu and hover-card
  use View.On.on for the contextmenu / mouseenter / mouseleave events.
  Registered in Registry.mlx's example_for / example_ids. This brings
  reativa to 26 elements, 38 components, and 13 blocks.

• c3d692e: Render the website's playground with reativa too. Registry.mlx gains
  playground_for — a knob-driven render of a single component for each of the 30
  specs the playground covers (button, badge, avatar, alert, checkbox,
  switch, slider, progress, spinner, skeleton, separator, kbd,
  icon, icon-button, link, input, textarea, toggle, toggle-group,
  radio-group, aspect-ratio, scroll-area, input-otp, select, field,
  tooltip, tabs, accordion, collapsible, dialog) — mirroring the Xote
  render functions prop for prop, with the generated contract types keeping the
  allowed values honest.

  Two new exports join the JS surface the website consumes:
  mount_playground(specId, containerId, props), which renders a spec from the
  knob values the props panel currently holds, and playground_ids, so the site
  knows which specs reativa can drive.

Patch Changes

• Updated dependencies [e646367]
  • @prescriptive/tokens@0.2.0

@prescriptive/tokens@0.2.0

Minor Changes

• e646367: Redesign the predefined themes so the presets look like current products rather
  than tinted washes of one hue.

  The old presets pushed their hue through the whole neutral ramp — indigo
  surfaces, indigo borders, indigo text — which read as monochromatic and dated,
  and left steps 300–600 as the unrelated warm grays of the baseline. Every theme
  is now built the way modern product palettes are: the ramp stays close to
  gray, and saturation is spent on the accent, status, and chart roles. The
  theme's hue survives in surfaces and text only as a few percent of chroma.

  • Twelve themes, each with a description of what it is for: monochrome,
    graphite, indigo, azure, ocean, forest, violet, plum, coral,
    sunset, editorial, terminal. vibrant and candy are gone; graphite,
    azure, violet and plum are new.
  • Complete ramps. Each theme defines all twelve neutral steps on a shared
    OKLCH lightness ladder, so no theme mixes its own tint with baseline grays and
    every theme has the same contrast structure.
  • Categorical chart sets. Themes now set color.chart.1…6 to six
    distinguishable hues rotated off their own, instead of inheriting the
    grayscale ramp where every series looked alike.
  • Dark mode that works. The dark mode overlay puts surface a step
    above paper (so cards read as raised, as they do in light mode), re-tunes
    every status color for a dark page, and swaps the shadows for near-black ones
    — a 5%-alpha warm gray was invisible on a dark surface. Each theme's own
    dark block re-tints those surfaces to its hue and lifts its accent.
  • Tinted shadows, per-theme type and radii. Ambient shadows carry a hint of
    the theme's hue; graphite and editorial invert to a light accent fill in
    dark mode, and terminal's signal-green fill carries a dark label.
  • AA by construction. Accents, status colors, and chart series are derived
    from the contrast requirement itself, so ink/paper, muted/surface,
    label/accent-fill, status/paper and series/paper all clear WCAG AA in both
    modes. The baseline color.status.* values move with them (success and
    warning previously failed AA as text on paper).

@prescriptive/xote@0.2.1

Patch Changes

• Updated dependencies [e646367]
  • @prescriptive/tokens@0.2.0

@prescriptive/skill@0.1.1

Patch Changes

• e646367: Redesign the predefined themes so the presets look like current products rather
  than tinted washes of one hue.

  The old presets pushed their hue through the whole neutral ramp — indigo
  surfaces, indigo borders, indigo text — which read as monochromatic and dated,
  and left steps 300–600 as the unrelated warm grays of the baseline. Every theme
  is now built the way modern product palettes are: the ramp stays close to
  gray, and saturation is spent on the accent, status, and chart roles. The
  theme's hue survives in surfaces and text only as a few percent of chroma.

  • Twelve themes, each with a description of what it is for: monochrome,
    graphite, indigo, azure, ocean, forest, violet, plum, coral,
    sunset, editorial, terminal. vibrant and candy are gone; graphite,
    azure, violet and plum are new.
  • Complete ramps. Each theme defines all twelve neutral steps on a shared
    OKLCH lightness ladder, so no theme mixes its own tint with baseline grays and
    every theme has the same contrast structure.
  • Categorical chart sets. Themes now set color.chart.1…6 to six
    distinguishable hues rotated off their own, instead of inheriting the
    grayscale ramp where every series looked alike.
  • Dark mode that works. The dark mode overlay puts surface a step
    above paper (so cards read as raised, as they do in light mode), re-tunes
    every status color for a dark page, and swaps the shadows for near-black ones
    — a 5%-alpha warm gray was invisible on a dark surface. Each theme's own
    dark block re-tints those surfaces to its hue and lifts its accent.
  • Tinted shadows, per-theme type and radii. Ambient shadows carry a hint of
    the theme's hue; graphite and editorial invert to a light accent fill in
    dark mode, and terminal's signal-green fill carries a dark label.
  • AA by construction. Accents, status colors, and chart series are derived
    from the contrast requirement itself, so ink/paper, muted/surface,
    label/accent-fill, status/paper and series/paper all clear WCAG AA in both
    modes. The baseline color.status.* values move with them (success and
    warning previously failed AA as text on paper).