@pond-ts/react 0.43.0 → 0.44.1

package/CHANGELOG.md

@@ -8,7 +8,9 @@ The `@pond-ts` packages — `pond-ts`, `@pond-ts/react`, `@pond-ts/charts`,
 tag, so this file covers them all. Pre-1.0: minor bumps may include new features
 and type-level changes; patch bumps are strictly additive.
 
-[Unreleased]: https://github.com/pjm17971/pond-ts/compare/v0.43.0...HEAD
+[Unreleased]: https://github.com/pjm17971/pond-ts/compare/v0.44.1...HEAD
+[0.44.1]: https://github.com/pjm17971/pond-ts/compare/v0.44.0...v0.44.1
+[0.44.0]: https://github.com/pjm17971/pond-ts/compare/v0.43.0...v0.44.0
 [0.43.0]: https://github.com/pjm17971/pond-ts/compare/v0.42.0...v0.43.0
 [0.42.0]: https://github.com/pjm17971/pond-ts/compare/v0.41.0...v0.42.0
 [0.41.0]: https://github.com/pjm17971/pond-ts/compare/v0.40.0...v0.41.0
@@ -41,6 +43,108 @@ and type-level changes; patch bumps are strictly additive.
 
 ## [Unreleased]
 
+## [0.44.1] — 2026-07-13
+
+A `@pond-ts/charts` patch: fixes trading-time axis tick density. `pond-ts`,
+`@pond-ts/react`, `@pond-ts/fit`, and `@pond-ts/financial` carry no code
+changes — republished in lock-step; their `^0.44.0` peer ranges already
+admit this patch.
+
+### Fixed
+
+- **charts:** trading-time axis tick density now derives from plot width
+  instead of a fixed count of 5. The trading scale's tick `count` caps how many
+  calendar buckets `coarsenCalendar` may keep, so the fixed count coarsened any
+  ≳6-month daily view to quarter or year grain — a 1-year daily chart on a
+  ~900px plot showed 2 ticks; it now lands on month grain (~12). Continuous
+  (non-trading) time and value axes keep the fixed default, unchanged. The
+  count is shared through the container frame (`xTickCount`), so axis labels,
+  x gridlines, session dividers, and the cursor-time formatter all derive from
+  the same instants — previously the label formatter anchored at the scale's
+  internal default (10) while ticks used 5, which is why sparse year-grain
+  ticks were labelled with dates (`Jun 22`) instead of years. (Tidal friction
+  report, charts 0.44.)
+
+## [0.44.0] — 2026-07-11
+
+The **value-axis charts** release: cross-sectional data (a volatility smile keyed
+by strike) becomes a first-class charting surface. `ValueSeries.fromColumns` is
+the direct columnar door; `<ScatterChart>` and `<BoxPlot>` join `<LineChart>` on
+the value axis; `<BoxPlot>` gains range-only (bid→ask) marks, `offset` pairing,
+and `capWidth`; and the region cursor works on value axes and snaps to histogram
+bins.
+
+### Added
+
+- **`<BoxPlot>` finished for the value axis + range-only marks** (`@pond-ts/charts`).
+  Four coordinated changes, driven by the volatility smile's per-strike bid/ask IV
+  segments (`docs/notes/vol-smile-followups-2026-07.md` §1):
+  - **Accepts a `ValueSeries`** (`series.byValue('strike')` /
+    `ValueSeries.fromColumns`) — boxes on a value axis, the same instanceof branch
+    as `<LineChart>` / `<ScatterChart>`. The box **width** now comes from neighbour
+    spacing for a **point** key (a `ValueSeries`, or a point-keyed `TimeSeries`) —
+    like bars/candles — instead of collapsing to the 1px floor; an interval-keyed
+    `TimeSeries` still uses its `[begin, end)`.
+  - **Optional `q1`/`median`/`q3`** — omit `q1`+`q3` for a **range-only** box: a
+    whisker-only `lower→upper` segment, no body (a bid→ask IV mark honestly named,
+    not a candlestick abuse). Omitting exactly one of `q1`/`q3` throws.
+  - **`offset` prop** (`<BoxPlot>` and `<ScatterChart>`) — a **pixel** shift for
+    pairing same-key marks (call/put at one strike) side by side, zoom-stable. On
+    the scatter it moves the draw **and** the click hit-test together; on the box
+    the readout hit-tests in un-shifted data space (keep the offset small).
+  - **`capWidth` prop** (`<BoxPlot>`) — the whisker end-cap width in **pixels**
+    (else half the box width). A small fixed cap keeps two `offset`-paired marks'
+    T-bars from overlapping when the value-axis slot is wide; clamped to the box
+    width, `'whisker'` shape only.
+  - **Readout labels** carry the series' `as` identity (`iv upper`, `iv median`)
+    when set, instead of bare column names — the `as ?? column` convention
+    Line/Scatter already use.
+- **`<ScatterChart>` accepts a `ValueSeries`** (`@pond-ts/charts`) — scatter
+  marks on the value axis, the same instanceof-branched adapter as
+  `<LineChart>` (the container infers the x kind from the data). The
+  data-driven `radius` / `color` encodings work unchanged on a value axis;
+  the per-point `label` reads through a new columnar branch (a `ValueSeries`
+  has no per-row events) — IV marks keyed by strike with open-interest
+  radius is the driving composition (vol smile). New value-axis Storybook
+  fan-out (`ValueAxis` / `ValueAxisEncoded` / `ValueAxisSmile` /
+  `ValueAxisFlag`) + Linux visual baselines.
+
+- **`ValueSeries.fromColumns({ name, schema, columns, sort? })`** (`pond-ts`) —
+  the direct columnar door into value-land, for data that is _natively_
+  value-keyed (cross-sectional): an options chain keyed by strike, a spectrum
+  keyed by frequency. Exact `TimeSeries.fromColumns` contract with the axis in
+  place of time — same polymorphic `number[]` / `Float64Array` inputs, same
+  zero-copy adoption, same stable opt-in `sort`, same gap rule — the two doors
+  share one ingest engine. Previously cross-sectional callers had to launder
+  the axis through a fake `time` column (`TimeSeries.fromColumns` +
+  `byValue`); that detour is no longer needed.
+
+- **The region cursor snaps to a histogram's bins** (`@pond-ts/charts`). On a
+  `<BarChart>` histogram, `cursor="region"` now snaps **bar by bar** with no
+  `cursorSequence`: hovering highlights the bar under the pointer, a drag extends
+  across whole bars, and `onRegionSelect` reports the selected bin range
+  `[lo, hi]` at the bar edges. The bar layer publishes its `[begin, end)` spans
+  (a new internal `binIntervals` channel) as the region cursor's snap buckets —
+  the same machinery a `cursorSequence` drives on a time axis, so it also covers a
+  time-axis histogram. Only a **vertical** bar layer on a continuous (time /
+  value) x axis publishes bins; a horizontal chart (value on x) and a categorical
+  axis stay freeform / excluded. An explicit `cursorSequence` still takes
+  precedence. New `HistogramBins` region-cursor story.
+
+### Changed
+
+- **BREAKING (`@pond-ts/charts`): the region cursor works on a value x-axis, and
+  `onRegionSelect` reports a neutral `[lo, hi]` pair.** The drag-select callback
+  fired a `TimeRange`; it now fires `readonly [number, number]` in **axis units** —
+  epoch ms on a time axis, the axis value (strike, distance, …) on a value axis —
+  mirroring the container's polymorphic `range` input (which never takes the axis
+  _kind_ from its value). A time-axis consumer that wants a `TimeRange` builds one
+  from the pair (`new TimeRange({ start: lo, end: hi })`). The cursor itself is
+  ungated from time-only to any **continuous** x-axis (time **or** value; a
+  **category** axis stays excluded — an ordinal-slot select is a different gesture).
+  Bucket **snapping** stays time-only (a `cursorSequence` bucket is a time
+  interval), so a value axis is always **freeform** (hover line + raw-span drag).
+
 ## [0.43.0] — 2026-07-11
 
 The **categorical x-axis** release: a first-class ordinal band scale (ticker /

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pond-ts/react",
-  "version": "0.43.0",
+  "version": "0.44.1",
   "description": "React hooks for pond-ts live time series",
   "license": "MIT",
   "repository": {
@@ -33,7 +33,7 @@
     "test:runtime": "vitest run"
   },
   "peerDependencies": {
-    "pond-ts": "^0.43.0",
+    "pond-ts": "^0.44.0",
     "react": "^18.0.0 || ^19.0.0"
   },
   "devDependencies": {