@pond-ts/react 0.44.1 → 0.46.0

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.44.1...HEAD
+[Unreleased]: https://github.com/pjm17971/pond-ts/compare/v0.46.0...HEAD
+[0.46.0]: https://github.com/pjm17971/pond-ts/compare/v0.45.0...v0.46.0
+[0.45.0]: https://github.com/pjm17971/pond-ts/compare/v0.44.1...v0.45.0
 [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
@@ -43,6 +45,146 @@ and type-level changes; patch bumps are strictly additive.
 
 ## [Unreleased]
 
+## [0.46.0] — 2026-07-14
+
+### Changed
+
+- **charts:** the boundary (second-row) axis label's **context** now pins to
+  the plot's left edge instead of riding the first tick: it shows the period
+  the *domain start* is in, and a crossing label sliding toward the edge
+  pushes it off (the sticky-header behavior). On a live sliding window the
+  old first-tick anchoring made `Jan 01` hop tick-to-tick as ticks scrolled
+  out; pinned, it stays put until the period actually changes. Crossing
+  labels (day/year turns) still ride their ticks — including a first tick
+  whose period differs from the domain start's. `TradingTimeScale` gains
+  `boundaryContext(count)`; `tickBoundaries` now labels crossings only.
+
+### Fixed
+
+- **charts:** a live (sliding-window) time axis no longer flickers between two
+  tick grains: the clock-rung choice now derives from the window's live span
+  (constant while sliding) instead of the enumerated anchor count, which
+  oscillates ±1 with the window's phase and flipped the grain for single
+  frames whenever it sat exactly at the width-derived cap.
+
+### Added
+
+- **charts:** **dual x-axes** — two tick layouts on one shared scale. A second
+  `<XAxis>` stacks by declaration order (above/below the plot, either side,
+  same side twice); the new **`transform`** prop (`{ to, from }`, exported
+  `AxisTransform`) relabels an axis into a derived unit: strike ↔ moneyness on
+  a top axis, or a nonlinear BS-delta strip under a std-moneyness chart. Ticks
+  are nice derived-unit values chosen by a pixel-aware multi-resolution fill
+  (1-2-5 steps, coarsest first, admitted where they keep room), so a span the
+  transform compresses gets coarse ticks and a stretched span picks up finer
+  ones — and a label-honesty filter drops any tick whose formatted label would
+  lie about its position. Gridlines stay on the container's primary ticks; the
+  cursor pill on a transformed axis reads in the derived unit. Stories under
+  `Charts/Axes/DualX`. Each `<XAxis>` **and `<YAxis>`** also takes a
+  per-instance **`color`** (labels, tick marks, rule, title) — the lever that
+  distinguishes stacked x strips (a blue delta strip under a grey primary) and
+  colours a y axis to match its series (the dual-axis convention).
+
+### Fixed
+
+- **charts:** annotation label chips now clip to the plot: a marker whose pole
+  pans off-plot no longer leaves its chip floating in the axis gutter, and a
+  partially visible region's chip clamps to the plot's left edge (culled only
+  when the region is entirely out of view). The lines/fills were already
+  SVG-clipped — only the DOM chips escaped.
+
+## [0.45.0] — 2026-07-14
+
+### Added
+
+- **charts:** the time axis now walks a **logical tick ladder** — clock/calendar
+  units (1s…30s, 1m…30m, 1H…12H, day / week / month / quarter / year), picking
+  the finest grain that fits the width-derived cap — and renders **two-tier labels**:
+  a first row at the tick grain (`14:00`, `Feb 02`, `Feb`, `2026`) plus a
+  **boundary row** carrying the coarser context the first row omits (the date
+  under clock ticks, the year under day/week/month ticks — never a unit the
+  first row already shows), shown once under
+  the first tick of each new period. Hour anchors are generated in **live**
+  trading time, so none lands in a collapsed gap, an early close, or a lunch
+  break. `TradingTimeScale` gains `tickBoundaries(count)`; a cramped leading
+  partial-period anchor (the `"Jun 23Jul 07"` pile-up) is dropped. Systematic
+  story matrix under `Charts/TimeAxisTicks`.
+- **financial:** the rest of the first study batch — `rollingStdev`,
+  `rollingMin`, `rollingMax`, `rollingPercentile` (linear interpolation),
+  `zScore` (rolling), `envelope` (MA ± percent, `maType` sma/ema), and
+  `percentChange` (n-bar rate of change). Same shape as the others — `column` /
+  `output` (or `prefix`) on every one, bar-count periods, length-preserving
+  warm-up — and each has a fluent method (`bars.zScore({ period: 20 })`) and a
+  **pandas oracle** case (values cross-validated bar-for-bar). This completes the
+  #449 first batch.
+- **financial:** opt-in **fluent studies** via `import '@pond-ts/financial/fluent'`
+  — mounts `sma` / `ema` / `bollinger` as chainable `TimeSeries` methods so
+  composition reads like the core operators beside it:
+  `bars.sma({ period: 20 }).ema({ period: 12 }).bollinger({ period: 20 })`.
+  Opt-in by import (the default entry leaves `TimeSeries` untouched, so a
+  non-financial series never sees `.sma()`); the methods are exactly the
+  standalone functions bound to `this`, fully typed (each appends its column to
+  the schema). Same prototype-augmentation pattern core uses for column methods.
+- **financial:** `@pond-ts/financial` gains its first **studies** — `sma`, `ema`,
+  and `bollinger` (Bollinger Bands®) — pure functions that append a column (or a
+  `${prefix}Middle/Upper/Lower` family) to a bar series. Every study takes a
+  `column` source (default `'close'`) and an `output` name, so a study runs over
+  any numeric column including another study's output; periods are **bar counts**
+  (on core's count window, gap-correct); warm-up rows are `undefined`
+  (length-preserving). Plus the `OhlcvColumns` contract + `DEFAULT_OHLCV`. (Core
+  `AppendColumn` is now exported so study return types name their appended
+  column.)
+- **core:** `smooth(col, 'ema', …)` gains the financial **`span`** rate
+  convention (`α = 2/(span+1)`, e.g. `{ span: 12 }` for a 12-period EMA) as an
+  alternative to `alpha` (exactly one required), and a length-preserving
+  **`minSamples`** warm-up that emits `undefined` for the first `N` present
+  values while **keeping the row count** — mirroring `rolling`'s `minSamples`,
+  the one warm-up convention studies use so a smoothed line aligns on its
+  source's time axis. (The existing `warmup` option is unchanged — it still
+  *drops* the head rows; `minSamples` is the length-preserving counterpart.)
+- **core:** `TimeSeries.rolling` accepts a **count-based** window —
+  `rolling({ count: N }, mapping, opts?)` reduces the last / next / centered
+  `N` _rows_ (bars) by position instead of a time span. Unlike a duration
+  window, an N-bar window stays correct across session gaps (weekends,
+  overnight) where `N` bars do not equal `N × barSize` of time — the load-
+  bearing primitive for financial N-bar studies (SMA-20, Bollinger-20, rolling
+  stdev). Honours `alignment` and `minSamples` exactly like a duration window
+  (`minSamples: N` gives the conventional first-`N-1`-rows-`undefined` warmup);
+  per-row output only (not supported with a sequence). Same amortized-O(1)-per-
+  row sweep as the duration path.
+- **charts:** `<LineChart sessionBreaks>` breaks the line at each trading-axis
+  discontinuity (a session / day / lunch close→open) instead of connecting the
+  prior close straight to the next open across the collapsed gap. For intraday
+  data on a `discontinuities` / `calendar` axis this gives the terminal look —
+  the line ends at the close and re-starts at the open, so one session's price
+  doesn't visually flow into the next. It's a **scale** break (driven by the
+  axis's collapsed gaps), orthogonal to `gaps` (a **data** break, a NaN run) —
+  set both independently. Default `false`; a no-op on a continuous axis or a
+  provider without `boundaries`. New `Charts/TradingTimeAxis/SessionBreaks`
+  story (connected vs broken) + `sessionRuns` / `gappingTicks` helpers.
+
+### Changed
+
+- **charts:** a **plain continuous time axis** now runs the same ladder as a
+  trading-calendar axis (via an internal gap-free identity provider) instead of
+  d3's multi-scale default — so a year of daily data ticks cleanly on month
+  starts (`Jul Aug … Jun` + the year underneath) rather than mixed
+  `"Jun 23" / "Sep" / "Dec"` labels, and its tick count is now width-derived
+  like the trading axis's. Month/quarter-grain anchor labels are now bare
+  months (`Feb`, was `Feb 02`) with the year on the boundary row;
+  `coarsenCalendar`'s finest granularity is renamed `'session'` → `'day'`.
+
+### Fixed
+
+- **core:** `TimeSeries.withColumn` now appends an **optional** column
+  (`required: false`) rather than a required one. It already accepted
+  `(number | undefined)[]`, but marking the column required meant a later
+  strict-intake rebuild (`smooth`, any row reconstruction) threw on the gaps —
+  so a column with a warm-up (a rolling study fed into an EMA, e.g.
+  `ema(sma(bars, …), …)`) crashed. The appended column's type is now
+  `number | undefined`, matching `smooth`'s optional append. (`OptionalNumberColumn`
+  is exported for the widened return type.)
+
 ## [0.44.1] — 2026-07-13
 
 A `@pond-ts/charts` patch: fixes trading-time axis tick density. `pond-ts`,

package/package.json

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