v0.8.0

No changes to the core in this release. Agent access (feature-005): the new package
@silverpoint/mcp is a Model Context Protocol server that describes silverpoint to agents — the
library's catalog, a chart recommender, code generation for React, Vue, Angular and Reflex, prop
validation and canonical SVG renders — over stdio or a stateless Streamable HTTP endpoint. It
reads the agent catalog generated from the published types, which also feeds the silverpoint skill
and the Claude plugin. See packages/mcp/CHANGELOG.md.

v0.7.0

Minor Changes

• 8ff16f9: Palettes, composed components, overlays and the timeline, close-out (feature-004, step 8h):
  0.7.0. The 21 new components —twelve composed, seven overlays on the platform's <dialog>
  and Popover API, the toast and its toaster— the palettes and the optional Knight Lab timeline
  are verified end to end on the composed, palettes and timeline pages of the four example apps and
  documented on the site. Grounds: timeline.css gives TimelineJS's eras a strip of their own below
  the axis labels —with an era, the axis grows to 57px and the era is laid in its lowest 18px, its
  title on a plate of the substrate— so an era's title no longer falls on the major ticks' row and
  its hatching no longer crosses the labels. Angular: a server-rendered SpToaster no longer reaches for
  document when it is torn down —it unlistens F8 only where it listened, on the client— so a server
  render that holds a toaster resolves instead of hanging on a ReferenceError. The seven packages
  move together to 0.7.0; the rendered output of every existing chart is unchanged.

• 62258b7: Fixes found by the end-to-end pass over the composed page (T-223). A disabled SpCollapseItem's
  summary now carries tabindex="-1", so Tab skips it as it skips every disabled control (REQ-522);
  this changes the normalised markup of a disabled item. SpTooltip hides on Escape wherever focus is,
  not only on its trigger, so a tooltip shown by hover can be dismissed without moving the pointer
  (WCAG 1.4.13, REQ-496).

• 449ce95: uiOverlaySync(element, kind, open) on @silverpoint/core/ui (T-215): opens or closes a native
  overlay as its state says —showModal(), show() or close() for a <dialog>, showPopover() or
  hidePopover() for a popover— only when the element is in the other state, so no second close or
  toggle event fires. Without the Popover API a popover stays in the page's flow.

• d4d569d: Palettes, the composed components' and overlays' core, and the timeline's (feature-004,
  T-200..T-208). On the new subpath @silverpoint/core/palettes: resolvePalette, paletteStyle, PALETTE_PROPERTIES,
  contrastRatio, checkPalette, PALETTE_PAIRS and six verified presets (silverpoint,
  sanguine, sepia, ironGall, verdigris, indigo); the Palette type on the main entry.
  A palette value is accepted only if it is a CSS colour (an allowlist). On @silverpoint/core/ui:
  uiSortRows, uiPageWindow, uiPagination, uiNumberValue (now also reporting the range as
  drawn), uiNumberStep, uiInitials, uiListKey, uiTypeahead, uiPlace, uiAnchor; ten new
  glyphs in UI_GLYPHS; and the view trees of SpSurface, SpGlyph, SpTable, SpPagination,
  SpBreadcrumb, SpAvatar, SpAvatarGroup, SpStatistic, SpDescriptions, SpTimelineList,
  SpCollapse, SpCollapseItem, SpEmpty, SpResult, SpTextarea and SpInputNumber, and of
  the overlays SpModal, SpDrawer, SpPopover, SpTooltip, SpSelect, SpDropdownMenu,
  SpToast and SpToaster (native <dialog> and Popover API), with uiTriggerView,
  uiTriggerAria, uiSelectItems, uiMenuItems and uiToastDuration. On the new
  subpath @silverpoint/core/timeline: timelineView, timelineInk, TIMELINE_FRAMES,
  TIMELINE_TONES and the SpTimelineProps / TimelineData types. UI_COMPONENTS gains 21 rows
  with a family field (ui, composed, overlay), three groups and batches A1, A2, B;
  UI_DEMOS gains their 35 states, and @silverpoint/core/ui-demos exports TIMELINE_DEMO. New
  diagnostics SP023, SP024 and SP025.

  A link's href (SpButton, SpBreadcrumb) now keeps only relative URLs and the http, https,
  mailto and tel schemes, and a headingLevel outside 2..6 draws h3; both warn SP017.

  UiTokens gains the optional backdrop and rowTone levels; resolveUiTokens holds them to 1..4
  and gives a ground that declares none 2 and 1 (T-209).
  A table cell's text stands on a .sp-ui-plate, so a toned row keeps its contrast.

  palette on CommonChartProps, CommonUiProps, DashboardProps and ProviderConfig (T-212):
  resolveUi resolves it provider → dashboard cell → prop and every UI root writes it first in its
  style; dashboardView takes the section's declarations and hands the palette to its cells, where
  inCell merges it under the chart's own; svgString writes it on the <svg>. nestProvider on
  @silverpoint/core/palettes: a nested provider's set fields win and the palettes merge field by field.

• 61e98a2: SpTimeline on @silverpoint/react/timeline, @silverpoint/vue/timeline and
  @silverpoint/angular/timeline (T-221): a Knight Lab TimelineJS timeline inside the ground's surface,
  with @knight-lab/timelinejs ^3.9.13 an optional peer. The server renders the surface, its probes
  and an empty mount; the client imports TimelineJS after render, builds it there without the font
  and theme options, and forwards its seven events (change, loaded, navNext, navPrevious,
  zoomIn, zoomOut, backToStart) as each framework's props, emits or outputs. If TimelineJS cannot
  be loaded, the mount shows the fallback (React's prop, Vue's slot, Angular's
  <ng-template spFallback>), SP025 is warned in development, and nothing throws. Import the subpath
  only with the peer installed. The core's @silverpoint/core/timeline gains timelineMount,
  timelineOptions and TIMELINE_EVENTS, which the three adapters share, and UiSlot gains
  fallback.

Patch Changes

• 3625f7e: Documentation for the 0.7.0 additions (T-224). Each adapter's README lists the 38 UI components and
  shows the palettes and the timeline, with TimelineJS as an optional peer; the grounds README names
  ui.css and timeline.css, and the core README its ui, palettes and timeline entries.
  SpTimelineProps.data gains its documentation comment.
• dec07a4: Fixes found by the pixel gate of the new components (T-219): uiAnchor re-places an overlay when
  its trigger or the overlay changes size, as when a web font replaces its fallback; the AvatarGroup's
  overlap and the dividers between CollapseItems also hold through the display: contents wrappers an
  Angular host keeps around each child; a Vue SpDropdownMenu mounted open focuses its active item, as
  React's and Angular's do.
• 194c0b4: timelineMount (@silverpoint/core/timeline, T-222) builds TimelineJS in a <div> of its own inside
  the mount, so TimelineJS's className rewrite leaves the mount's sp-kl-mount class alone, and hands
  it a copy of data (structuredClone): TimelineJS writes each slide's unique_id into its data,
  which threw on a frozen object such as TIMELINE_DEMO and left the timeline loading forever. An
  error thrown while TimelineJS is built is now handled as a failed load: its container is removed,
  SP025 is warned and the fallback is shown.

v0.6.0

Minor Changes

• fa8dc13: Second catalog, wave 1 in every adapter (feature-003, T-177, T-178). The 14 charts of wave 1 —
  HistogramChart, EcdfChart, BoxPlotChart, ViolinChart, RidgelineChart, BeeswarmChart,
  LollipopChart, DumbbellChart, SlopeChart, BumpChart, ErrorBarChart, IntervalChart,
  DivergingBarChart and ConnectedScatterChart — each at its own subpath of every adapter
  (@silverpoint/react/histogram-chart, @silverpoint/react/server/histogram-chart,
  @silverpoint/vue/histogram-chart with SpHistogramChart, @silverpoint/angular/histogram-chart
  with <sp-histogram-chart>) and in each barrel. Their recipes are on a new core subpath,
  @silverpoint/core/catalog, so the core's main entry keeps its budget; every one-chart build of the
  first 33 stays within 0.1 KB of its 0.3.0 size.

  RidgelineChart requires groupKey and DivergingBarChart requires levels in every adapter
  (input.required in Angular); the demo ignores both. levels and axis describe how the data's
  columns are read, so like the …Key props they are ignored without data.

  The keyboard model of a hierarchy now reaches stepActive as each hit area's moves, computed with
  the layout, so no chart without one carries its code. No existing output changes.

  Each package README lists the 47 charts, and the core's names @silverpoint/core/catalog; the
  documentation site states, for every chart of the second catalog, how each derived value is
  computed.

• da77adb: Second catalog, comparisons (feature-003, T-172..T-176). The core recipes of LollipopChart,
  DumbbellChart (dot or arrow end), SlopeChart, BumpChart (ranks computed in the core),
  ErrorBarChart, IntervalChart (numbers or ISO dates in UTC), DivergingBarChart and
  ConnectedScatterChart, each with a derived table and one heightened mark. They reach the adapters
  with wave 1; no existing output changes.

• c1d0ebd: Second catalog, distributions (feature-003, T-168..T-171). The core recipes of HistogramChart,
  EcdfChart, BoxPlotChart, ViolinChart, RidgelineChart and BeeswarmChart: statistics derived
  in the core (Freedman–Diaconis bins, type-7 quartiles, Tukey whiskers, Epanechnikov densities), a
  derived tabular alternative, one heightened mark each, and a deterministic beeswarm packing. They
  reach the adapters with wave 1; no existing output changes.

• a83ca34: Second catalog, foundations (feature-003, step 7a). The props types of the 27 charts of
  0.6.0 (API Spec §7.3) and NetworkNode; the diagnostics SP020 (invalid hierarchy),
  SP021 (invalid statistic parameter) and SP022 (group too small for its statistic); HitArea.node,
  through which stepActive follows the WAI-ARIA tree pattern when every item is a node. No chart
  is added yet and no existing output changes: every canonical render is identical.

• 2171e7d: Second catalog, wave 2 in every adapter (feature-003, T-187..T-189). The 8 charts of wave 2 —
  WaffleChart, MarimekkoChart, SquarifiedTreemap, SunburstChart, TreeChart,
  ParallelCoordinatesChart, PolarLineChart and PolarScatterChart — each at its own subpath of
  every adapter (@silverpoint/react/sunburst-chart, @silverpoint/react/server/sunburst-chart,
  @silverpoint/vue/sunburst-chart with SpSunburstChart, @silverpoint/angular/sunburst-chart with
  <sp-sunburst-chart>) and in each barrel; their recipes join @silverpoint/core/catalog.

  SquarifiedTreemap and SunburstChart drill down under the consumer's control: rootId in, and
  onRootChange (React), @root-change (Vue) or (rootChange) (Angular) out, emitted with the
  activated node's id — its parent's for the drawn root, null for the top. The components keep no
  root of their own, so a server render with rootId is the client's. rootChangeOf, on
  @silverpoint/core/catalog, is what the three adapters share.

  ParallelCoordinatesChart requires dimensions in every adapter (input.required in Angular); the
  demo ignores it. dimensions and period describe how the data's columns are read, so like the
  …Key props they are ignored without data.

  Each package README lists the 55 charts; the documentation site states how each wave-2 chart
  computes what it derives.

• 0e724d6: Second catalog, wave 2 recipes (feature-003, T-180..T-186). The core recipes of
  SquarifiedTreemap, SunburstChart (with a controlled rootId), TreeChart, WaffleChart,
  MarimekkoChart, ParallelCoordinatesChart, PolarLineChart and PolarScatterChart, on owned
  layouts: stratify, reroot, squarify (Bruls et al.), partition and the Buchheim tidy tree, and the
  waffle's largest-remainder cells. Hierarchy charts walk as a tree by keyboard and announce each
  node's path, value and share of its parent. They reach the adapters with wave 2; no
  existing output changes.

• 68d2b7c: Second catalog, wave 3 in every adapter (feature-003, T-196..T-198). The 5 charts of wave 3 —
  DensityBinChart, ContourChart, DelaunayChart, VectorFieldChart and NetworkChart — each at
  its own subpath of every adapter (@silverpoint/react/network-chart,
  @silverpoint/react/server/network-chart, @silverpoint/vue/network-chart with SpNetworkChart,
  @silverpoint/angular/network-chart with <sp-network-chart>) and in each barrel, with the
  NetworkNode type; their recipes join @silverpoint/core/catalog.

  NetworkChart lays its nodes out by force, the same on the server and in every browser for a given
  seed, or draws them at the consumer's x and y when every node has them. Its nodes are data,
  and ContourChart's levels say how the data's values are read: like the …Key props, both are
  ignored without data. The density bins are drawn the smaller the lighter their tone, so the count
  survives precision mode; the heatmap shares that scale. The contours' grid demo is printed as its
  values, its positions implied: the same rows, a fifth of the weight.

  Each package README lists the 60 charts; the documentation site states how each wave-3 chart
  computes what it derives.

• c6191de: Second catalog, wave 3 recipes (feature-003, T-190..T-195). The core recipes of
  DensityBinChart (hexagonal or square bins, toned by count, with a key of the count ranges),
  ContourChart (iso-lines and filled bands of a point density or a regular grid), DelaunayChart
  (the triangulation or its Voronoi cells), VectorFieldChart (an arrow per grid point) and
  NetworkChart (a force layout from the seed, or the consumer's positions), on owned engines:
  marching squares with saddle resolution, the Epanechnikov density splat, 2-D bins, Bowyer–Watson
  with exact predicates (BigInt when doubles cannot settle a sign) and a fixed-iteration
  Fruchterman–Reingold layout. They reach the adapters with wave 3; no existing output
  changes.

v0.3.0

Minor Changes

• 281dfa5: First UI components: batch B1 (feature-002, step 6c). SpButton, SpInput, SpCheckbox,
  SpSwitch, SpCard and SpDivider in React (@silverpoint/react/ui/<name>, plus
  server/ui/card and server/ui/divider for Server Components), Vue (@silverpoint/vue/ui/<name>)
  and Angular (@silverpoint/angular/ui/<name>; SpButton decorates the consumer's own <button>).
  The markup is the core's view tree (@silverpoint/core/ui: resolveUi, ui*View), identical in
  the three adapters; ui.css gains their layout and folds frame slots and tone states onto each
  ground's tokens. The Angular adapter now takes @angular/forms as a peer, for its
  ControlValueAccessors, and its tokens and environment move to @silverpoint/angular/env
  (re-exported from @silverpoint/angular). No change to the rendered output of any chart.

• 41805a0: UI components, batches B2 and B3 (feature-002, step 6c): the catalog's 17 are complete.
  SpRadioGroup, SpSegmented, SpTabs with SpTabPanel, SpSlider, SpRate, SpSteps,
  SpTag, SpBadge, SpProgress, SpAlert and SpSkeleton in React, Vue and Angular
  (ui/<name>). React also ships server/ui/steps, tag, badge, progress, alert and
  skeleton for Server Components. Each component writes the core's view tree
  (ui*View in @silverpoint/core/ui), so the markup is the same in the three adapters.

  • Keyboard. The composites follow the WAI-ARIA patterns through the core's uiRovingFocus,
    which calls uiRovingKey. Disabled items are skipped and dir="rtl" mirrors the arrows.
  • Values. Every value component is controlled or uncontrolled, and the Angular ones are
    ControlValueAccessors.
  • Heightening. Each component has at most one heightened element.
  • Styles. ui.css gains the components' layout. Slider and Progress use exact fractions on
    logical properties. An indeterminate Progress only moves when reduced motion is off.

  No change to the rendered output of any chart.

• eb2bd8e: UI components, close-out (feature-002, step 6f): 0.3.0. The 17 Sp-prefixed components are
  verified end to end on the UI page of the four example apps —keyboard patterns, native form
  submit, focus ring, target size, reduced motion, RTL, axe A/AA— and documented on the site with a
  live example per state and a props reference read from the types. Every prop of the UI types now
  carries its JSDoc. Angular: SpUiControl hands the .sp-ui root to the roving-focus helper, so a
  dir="rtl" set on the component mirrors the arrows. Grounds: ui.css removes the browser's own focus ring from
  the native, text and range controls, whose exact ring is drawn on their item, box or thumb, so a
  focused SpInput shows one ring, not two. The seven packages move together to 0.3.0;
  the rendered output of every chart is unchanged.

• 5a1b53f: UI components in the core (feature-002, step 6a). The new subpath @silverpoint/core/ui holds
  the framework-neutral half of the 17 UI components of 0.3.0: their props types (SpButtonProps …), the catalog UI_COMPONENTS, value
  geometry (uiValue, uiRateCount, uiProgressArc, uiSteps), the WAI-ARIA roving-focus
  transition uiRovingKey, the frame variant and outlines (uiFrameVariant, uiFrameOutline,
  UI_FRAME_KINDS), and the checks uiItems and uiRequireName. The reference states UI_DEMOS
  live on the new subpath @silverpoint/core/ui-demos. New diagnostic codes SP017, SP018,
  SP019. The main entry is unchanged, and so is the rendered output of every chart.

• 10cc90a: UI tokens and tone tiles in the core (feature-002, step 6b). Ground gains an optional ui
  section (Data Model §3.8: frame style and variants, control heights, radius, focus width, tone per
  state); a ground without it takes UI_TOKEN_DEFAULTS. @silverpoint/core/ui gains
  resolveUiTokens, which holds a ground's tokens to their domain, and uiToneTile, the seamless
  tile geometry the grounds build draws a control's tone from. No change to the rendered output of
  any chart.

v0.2.0

Minor Changes

• edcfb8e: A second ground: cyanotype, where tone is line weight. ground="cyanotype" prints any chart
  as a white line on Prussian blue (REQ-028). It hatches nothing. A toned shape, such as a bar, a cell
  or a band, is drawn as its own outline, and its tone is how thick that outline is. No chart code
  changed to add it.

  • New exports. cyanotype and WeightInker from @silverpoint/grounds, both registered by
    default. From @silverpoint/core: ToneSpec becomes a union, HatchToneSpec | WeightToneSpec.
  • One substrate, prussian. The ground ignores substrate, so it needs none.
  • Heightening inverts. The heightened element is the deepest blue, outlined in the white ink.
  • Rendered output. A weighted path carries data-weight="1"–"4". The stylesheet turns it
    into a stroke width with --sp-weight-1..4, so a consumer re-weights with CSS. silverpoint
    output is unchanged: no path of it carries a weight.

• 1a8c006: Reference dashboards. DASHBOARD_DEMOS holds three frozen, data-only dashboards —
  kpi-strip, ops and mixed-spans — shared by the fixtures, the example apps and the
  documentation. No change to the rendered output of any chart.

• 5f69fde: Dashboard layout types (Phase 5, first step). The core's internal surface gains the types of
  the upcoming Dashboard composition (DashboardProps, DashboardLayout, DashboardCellLayout,
  DashboardModel, …) and their defaults: DASHBOARD_DEFAULTS (1 / 2 / 4 columns at sm / md /
  lg, row unit 240 px, gap 16 px), perBreakpoint and resolveLayout. A dashboard's id and its
  title or label are required by the type. No component uses them yet; no change to the rendered
  output.

• 5191333: Linked dashboards. A dashboard with link={{ key: 'hour' }} marks, in every other chart, the items
  whose datum carries the same hour as the active item of the chart being explored, and clears them
  when it clears. The marks are hidden from assistive technology, and linked state never reaches the
  server render. The dashboard reports the linked value through onLinkChange (React),
  @link-change (Vue) or (linkChange) (Angular). A chart whose data has no such field warns SP016.
  In React the link is its own client boundary, @silverpoint/react/dashboard-link, rendered only when
  link is set.

• 81f9b59: Dashboard resolution in the core. resolveDashboard(props, childCells) matches children to
  layout cells by id, keeps the reading order, clamps spans to the breakpoint's columns (SP014),
  reports every mismatch without throwing (SP015), derives chart ids (ops--traffic), and gives
  each cell its nominal box at ssrWidth. cellChartBox sizes a chart to fill its cell with its
  own card chrome subtracted. New diagnostic codes SP014, SP015, SP016. No change to the
  rendered output of any chart.

• 5359ab8: The demo applies view props; VolvelleChart's index turns it. Without data, a chart
  renders its demo dataset (REQ-093). It now follows one written rule (REQ-098): accessor props
  (…Key, keys, names) are ignored, because they point into your rows, and every other prop
  applies exactly as it would to your data.

  • Behaviour change. <VolvelleChart indexRing={1} indexValue="Night" /> without data now
    turns the demo so Night faces the pointer, and the readout becomes Day Sat · Shift Night · Team Eridanus. Before, the demo kept its own index and a development-only SP002 said so; that
    warning is gone. An out-of-range indexRing or an absent indexValue warns SP002 and falls
    back, as it does with your rings.
  • Rendered output. The normalised SVG changes only for a VolvelleChart given indexRing or
    indexValue without data. With no index, and in every canonical fixture, it is unchanged.
  • Props reference (REQ-099). Every accessor prop's documentation ends "Ignored without
    data."; data states the rule; indexRing and indexValue name the demo's rings.

• 8ee76ad: React Dashboard. @silverpoint/react/dashboard and @silverpoint/react/server/dashboard export
  Dashboard and DashboardCell: a section labelled by its heading, a CSS-grid of article cells in
  reading order, laid out by the core from a data-only layout. Each chart inside a cell gets a derived
  id, a size that fills its cell with its own card chrome, and the dashboard's ground, substrate,
  mode and locale below its own props. Neither entry adds a client boundary.

  Server charts (@silverpoint/react/server/*) no longer require id, width and height by type:
  inside a Dashboard the cell supplies them; standing alone, a missing one warns (SP002, SP003).

  The reference dashboards moved to their own subpath, @silverpoint/core/dashboard-demos, off the
  core's main entry. No change to any chart's rendered output.

• ed5b943: Vue SpDashboard. @silverpoint/vue/dashboard exports SpDashboard and SpDashboardCell, with
  the same markup, layout and inheritance as the React Dashboard: each chart inside a cell takes its
  id, size and the dashboard's configuration from the cell, below its own props. Server-rendered with
  @vue/server-renderer, it hydrates at the nominal size and then follows its container.

v0.1.1

Patch Changes

• Package pages and the release pipeline. Every package now ships a README, so its npm page
  explains how to install it. The React, Vue and Angular READMEs give the tested quickstart and
  examples for a provider, precision mode, interaction, a custom readout, the imperative handle and
  server rendering. From this release on, the packages are published from CI on every merge into
  main, through npm Trusted Publishing and with provenance. No change to the rendered output.