@chrtco/sdk 0.10.38 → 0.10.40

package/CHANGELOG.md

@@ -4,6 +4,140 @@ All notable changes to `@chrtco/sdk` will be documented in this file.
 
 ## [Unreleased]
 
+### Added
+- `MarineZoneRef.bbox` on `weather.marineForecast()` — `[west, south, east, north]` of the
+  forecast's zone, from the same build as the `NWS_MARINE_ZONES` tile source. A camera hint: fit
+  the map to it; draw the zone from the tiles, never the box. `west > east` crosses 180°.
+- **`RELIEF_ENCODING` / `RELIEF_TILE_SIZE`** — `CHRT_RELIEF`'s raster-dem
+  `encoding` (`"terrarium"`) and tile size (512), the values `buildSources()`
+  emits for the relief source. Exported for consumers that describe that
+  source themselves, such as the tile-worker's TileJSON.
+
+## [0.10.40]
+
+The first publish since 0.10.39 (2026-09-11, from `ada7e73e`). The publish
+workflow's typecheck failed on every merge to `main` from 2026-09-11 to
+2026-09-26 — the SDK's decode parity suite compiles the app's reference
+decoder, which had begun importing `@chrtco/sdk` by name, and inside the
+package that name resolved to a `dist/` not yet built — so everything below
+reached `main` without reaching npm. No function signature is removed or
+narrowed; the **Changed** entries are behaviour and type-shape changes to read
+before upgrading.
+
+### Added
+- **`weather.conditions({ hours })` — a station's recent history.** Adds
+  `series` to `MarineConditionsResponse`: the chosen station's readings over
+  the last `hours` hours (1–1080), oldest first, each in the top-level shape
+  (`MarineConditionsObservation`). Never interpolated or gap-filled;
+  `series.cadenceMinutes` gives the station's normal spacing. Without `hours`
+  the response is unchanged. New types: `MarineConditionsSeries`,
+  `MarineConditionsObservation`.
+- **`StyleUrlOptions.units`** — `"metric"` (default) or `"imperial"`, sent by
+  `styleUrl()` / `fetchStyle()` as `?units=imperial` to
+  `GET /v1/styles/{region}/style.json`. The served style then prints
+  soundings, depth-contour labels, dredged-channel notes and bridge notes in
+  feet. Send the reader's setting here rather than converting soundings
+  client-side: a bridge note is composed text a client cannot rewrite, and
+  soundings in feet beside a clearance in metres is the disagreement this
+  prevents. Metric spells nothing, so existing style URLs and their cache
+  keys are unchanged; any other value is a typed 400 `invalid_units`.
+- **`SIGSEQ` light rhythms.** `parseSigseqTerms(sigseq, sigper)` reads a
+  light's charted on/off sequence (`"00.4+(03.6)"` — 0.4 s lit, 3.6 s dark),
+  checked against `SIGPER`, and returns the phases or a typed refusal
+  (`SigseqRefusal`: `"malformed" | "nonPositiveDuration" | "sigperMismatch"`,
+  or `"absent"` when the light charts no sequence) — never an invented rhythm. `rhythmProperties()`, `lampRhythmOpacity()` and
+  `lampRhythmColour()` turn a parsed rhythm into feature properties and paint
+  expressions so a map can flash every light on the GPU from one paint update
+  per tick. Also `SIGSEQ_MAX_TERMS`, `SIGPER_TOLERANCE_SECONDS`,
+  `LAMP_TICK_MS`, `ParsedSigseqTerms`, `SigseqTerm`. The first-party app now
+  reads SIGSEQ through this parser: one grammar.
+- **Night lamps.** `buildLampLayers(sourceId, ct)` returns two circle layers
+  on `LIGHTS` (`LAMP_GLOW_LAYER_ID` / `LAMP_CORE_LAYER_ID`, `LAMP_LAYER_IDS`)
+  that draw lighted aids as points of light: coloured by the same LIGHTS05
+  reading as the flare, sized by nominal range (`VALNMR`), viewport-aligned so
+  they neither grow nor lie flat under pitch. They carry only lights that are
+  steady from every bearing (no `SECTR1`, no `SIGSEQ`). Every generated style
+  now includes them **hidden** (`visibility: "none"`); show them with
+  `setLayoutProperty`.
+- **The app-embeddable CHRT_BASE bundle.** `applyBaseBundle(style, { tiles })`
+  points a style's `CHRT_BASE` source at a local copy of the z0–6 world
+  basemap bundle and drops every base layer the bundle cannot feed. With
+  `BASE_BUNDLE_ID`, `BASE_BUNDLE_SCHEMA` (`chrt.basemap-bundle/1`),
+  `BASE_BUNDLE_MAXZOOM` (6), `BASE_BUNDLE_SOURCE_LAYERS`,
+  `BASE_BUNDLE_ATTRIBUTION` (`"© CHRT · Made with Natural Earth"`) and
+  `BASE_CLIENT_RASTER_BEFORE_ID`. The online `CHRT_BASE` source now declares
+  its credit (`BASE_ATTRIBUTION`, which also names OpenStreetMap for the
+  z9–11 inland-water tier) through the new optional
+  `PmtilesVectorSource.attribution`.
+- **Terrain ordering helpers** — `drapedFirst()`, `drapeHalves()`,
+  `isDrapeable()`, `terrainStackCount()`, `DRAPEABLE_LAYER_TYPES`. See
+  *Generated styles are ordered draped-first* below.
+- **Band aliases** — `BAND_CODE_ALIASES`, `cellBandCharacters()`,
+  `cellBandMatch()`. See the USACE fix below.
+
+### Changed
+- **Generated styles are ordered draped-first.** The generator's last pass is
+  now a stable partition: every background, fill, line, raster and hillshade
+  layer in its existing order, then every symbol and circle layer in theirs.
+  With MapLibre terrain on, the interleaved order cut a z12+ chart into ~130
+  render stacks, each re-rendered every frame (24.6 fps → 52.6 fps measured at
+  pitch 45, MapLibre 5.24); draped-first is one stack. It applies to the flat
+  chart too — it is the S-52 display order (areas, lines, then point symbols
+  and text) — and the only pixels that move are where a symbol used to sit
+  under a later line or fill (0.1–2.8 % of pixels across six measured views).
+  If you insert your own layers into a generated style by `beforeId`, re-check
+  where they land.
+- **Land mode: `LAKARE` relocates with the water family under CHRTland.**
+  Within a band the order is water → land → lake; across bands the finer
+  band's land paints after the coarser band's lake. A coarse band's
+  generalised lake no longer bleeds over CHRTland (Tisbury Great Pond at
+  z13.5).
+- **The charted water/land repaint now sits beneath the CHRT_BASE
+  inland-water pair**, not above it. Its band-4/5/6 `LNDARE` clones have no
+  holes for ponds the chart does not chart, so above the pair they painted
+  every uncharted lake inside fine-band coverage as land.
+- **`buildSectorArcsFC()` no longer draws the derived all-round arcs.**
+  `buildSectorsFromFeatures()` still emits them (`allRound: true`) — they are
+  what a reader in the uncovered arc sees, and a bearing lookup needs them —
+  but S-52 LIGHTS05 gives an all-round light its flare and no arc. This
+  reverses the drawing half of the 0.10.x entry *All-round lights co-located
+  with sector lights were not drawn*, below.
+- **Sector arcs are coloured per S-52 LIGHTS05.** `SectorInfo` gains
+  `colourCodes` (every charted `COLOUR`, in order — an alternating sector has
+  two), `arcColourToken` / `arcColourHex` (`LITRD` / `LITGN` / `LITYW` — white,
+  yellow and orange all draw yellow — `CHMGD` where the colours do not
+  resolve, `CHBRN` when obscured), `obscured` (`LITVIS` 3, 7 or 8), and
+  `sigseq` / `sigper`. `buildSectorsFromFeatures(features, ct = "DAY")` takes
+  the palette `arcColourHex` is resolved in, and each arc feature from
+  `buildSectorArcsFC()` carries `arcColourHex`, `arcColourToken` and
+  `obscured`. **These fields are required**: code that builds `SectorInfo`
+  literals by hand must now supply them.
+- **`buildFlashPattern()` uses the chart's own timing first.**
+  `DecodedNavAid` gains `sigseq`. When a light carries a valid `SIGSEQ` the
+  pattern is its charted phases and `FlashPattern.timing` is `"charted"`;
+  otherwise it is the previous animation of the character code, marked
+  `"invented"`. (Before, every pattern was invented — 400 ms flashes and
+  300 ms gaps — though 74 % of charted lights carry their real sequence.)
+  `DecodedNavAid.sigseq` and `FlashPattern.timing` are required fields.
+
+### Fixed
+- **USACE Inland ENC features were filtered out by every band-5 gate.** USACE
+  cell ids are `U37…`: the third character is `7` on every cell and means
+  nothing. The pipeline builds the product as band 5, but the style's band-5
+  gates read that character and never matched `7`, so the offline
+  `USACE_IENC` bundle rendered blank. `BAND_CODE_ALIASES = { "5": ["7"] }` is
+  folded into `bandFilterExpression()` and the orientation-label fan
+  (`cellBandMatch()`); a gate admits `7` exactly when it admits `5`. This is
+  not a seventh band — draw order and priorities are unchanged.
+
+## [0.10.0 – 0.10.39] — 2026-07-15 to 2026-09-11
+
+Published by the publish workflow's auto-bump while `package.json` stayed at
+0.10.0, so no per-version sections were cut. The entries below are the
+`[Unreleased]` section as it stood at `ada7e73e`, the commit 0.10.39 was
+published from. For what a single version contains, run
+`npm view @chrtco/sdk@<version> gitHead`.
+
 ### Fixed
 - **Sector-light arcs were drawn on the wrong side of the light.**
   `buildSectorArcGeoJSON()` / `buildSectorArcsFC()` painted each sector at the