@meri-imperiumi/signalk-passage-briefing 0.4.0 → 0.5.0

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-10-03
+
+### Added
+- Daylight-anchored departure time (work doc #15): while the boat is moored, the whole forecast schedule anchors to a realistic departure instead of "now" — nobody casts off at 02:40 because the forecast said so. Auto mode: underway sails from now; night at the start position waits for next first light (civil dawn, −6° sun altitude at the route's first waypoint); day adds the prep delay (1.5 h, configurable 0.5–3) unless the sun would set within it, in which case the anchor is the next dawn — never an immediate departure right before dark (the recorded decision). The pure helper (`assumedDepartureTime` in sereno-physics) detects a rising sun crossing with 5-minute steps bounded at 18 h and states what it assumed (`reason`), including a polar `no_dawn` fallback. The tactical and strategic views share a departure control (Auto / Now / First light / +1 h / +2 h / custom) whose manual choice overrides auto until it is put back; the root owns the state, re-checks the anchor every 10 minutes, and re-simulates only when the anchor moved more than 10 minutes so the view doesn't flap around dawn. The tactical chip states the anchor ("First light 10-05 06:00 +13"), the strategic ETA header says "Assumed departure first light …" ("Underway — from now" when sailing), sparkline titles read wall-clock stamps while shifted, and a delayed departure appears in the timeline as a ⚓ event ("Departure at first light" / "Departure after prep"). The served payload carries the same `departure` metadata so external consumers see numbers consistent with the auto assumption. SPEC §2.1/§3.1 updated.
+- Energy forecast consumption (work doc #10): the briefing finally powers its energy views — in the predictor's own terms. signalk-energy-predictor's hourly forecast (`electrical.energy.prediction.forecast.hourly`, the whole 48 h series as one delta value) and its outlook paths (`status`, `net`, `surplus` + window, `timeToEmpty`) are subscribed like any other Signal K path; the hourly series adapts into the frozen `energyHourly` consumer contract at compile time (the contract's `solarWh` carries total ideal generation: solar + wind + hydro + alternator) and rides the briefing payload so the offline hours re-derive from the cache. The 24 h solar-yield strip and the deficit banner work for the first time; the conditions-here view gains an "Energy 24h" line (the passage strip's here-mode sibling at SOG 0). New in the timeline: the predictor's own energy events — **surplus** is forecast curtailment (battery full while yield continues; the event carries the curtailed Wh and its window, "run opportunistic loads"), **deficit** and **critical** come from the outlook status (the event carries the 24 h net and, when the trajectory names one, the depletion time) — no independent re-derivation with invented thresholds.
+- Territorial waters transitions along the route (work doc #17): the briefing now says where the route crosses the boundaries that change the practical picture on board — entering or leaving a country's internal, archipelagic or 12 NM waters (the metered-ocean data boundary, customs and discharge rules). Built on `@openwaters/maritime-zones` (MIT) over the Marine Regions Maritime Boundaries Geodatabase (VLIZ, CC-BY 4.0 — the "not for navigation, no legal value" disclaimer rides the payload and renders wherever zones do). Corridor tiles (about 8 MB for a 900 nm crossing) download during the online window into the plugin data directory and answer offline afterwards; the boundary walk resamples the route at 1 nm so short territorial hops are not missed. The route simulation timestamps each crossing against the passage schedule, the unified timeline renders enter/leave events (leave events carry the "ocean data rules beyond this point" connectivity note), and here mode reports the waters the vessel sits in right now in the conditions view. Missing tiles, older Node (the package needs ≥ 24, the plugin allows 22.5) or a failed download degrade to no zone data — never a failed briefing. — entering or leaving a country's internal, archipelagic or 12 NM waters (the metered-ocean data boundary, customs and discharge rules). Built on `@openwaters/maritime-zones` (MIT) over the Marine Regions Maritime Boundaries Geodatabase (VLIZ, CC-BY 4.0 — the "not for navigation, no legal value" disclaimer rides the payload and renders wherever zones do). Corridor tiles (about 8 MB for a 900 nm crossing) download during the online window into the plugin data directory and answer offline afterwards; the boundary walk resamples the route at 1 nm so short territorial hops are not missed. The route simulation timestamps each crossing against the passage schedule, the unified timeline renders enter/leave events (leave events carry the "ocean data rules beyond this point" connectivity note), and here mode reports the waters the vessel sits in right now in the conditions view. Missing tiles, older Node (the package needs ≥ 24, the plugin allows 22.5) or a failed download degrade to no zone data — never a failed briefing.
+- GDACS hazard events also surface in the conditions-here view: earthquakes, cyclones and floods near the vessel are critical while stationary, so the here view lists them (Red events highlighted) alongside the passage timeline.
+- GDACS hazard event feed (work doc #22): earthquakes, tropical cyclones, floods and volcanic activity from the EU JRC's `gdacs.org/xml/rss.xml`, fetched during the online window and cached in `weather/hazards.json` with id-based dedup (repolls update in place). Events filter route-relative — alert level at or above the configured minimum (default Orange), within 500 nm of the route corridor or 1000 nm of the vessel, and no older than 72 h — and ride the briefing payload as `hazardEvents`, render in the unified timeline as `hazard` events with the alert level setting the severity, and publish as georeferenced `resources/notes` chart notes (category `hazard-event`, provenance `GDACS`) with scoped expiry that leaves the METAREA notes and other clients' notes untouched. Zero XML dependencies: a targeted extractor reads the stable RSS shape; malformed items skip without costing the feed.
+- Slatting & roll-dampening penalty in the Sereno comfort index (work doc #14): a residual swell (combined Hs ≥ 0.6 m) with too little wind to keep the sails loaded — below 7 kn upwind, below 12 kn downwind — now scores as the wash machine it is: the vertical acceleration carries a 2.5× discomfort multiplier before banding and the hour is forced to at least Rough. The hourly rows tag `slatting: true`, and the tactical dashboard's sparkline renders those Rough blocks with a diagonal hatch (alternating `--comfort-rough` over the card background) so the skipper sees the discomfort is light-air slatting, not heavy weather. SPEC §5.2 amended.
+- Real-world bulletin fixtures (work doc #4 follow-up): ten received-as-is High Seas texts — NHC Atlantic T1/T2, OPC East Pacific EP1, NHC EP2, Honolulu North and South Pacific (NP/SP), Fiji NAVAREA XIV, MetService NZ Subtropic, Australian BoM Western X and an NHC hurricane advisory — live under `tests/fixtures/bulletins/` with a per-family regression suite asserting issue metadata, issuer and geography extraction.
+- The bulletin engine now parses the NHC/OPC/PHFO High Seas families: compact coordinate pairs (`13N67W`, no separator) normalize into the spaced form; a hemisphere-less second number that is not the dateline shorthand is rejected as prose ("07N TO 31N" is two latitudes, not 7N 31E); issue lines from NHC (`0430 UTC SAT OCT 3 2026`), PHFO (`1130 UTC TUE FEB 17 2026`), Fiji (`OCT 022000 UTC`, mixed case `Oct` from the WMO bulletin sets), MetService New Zealand (`Wellington issued at 021856UTC`) and the Australian BoM (`commencing 2300 UTC 2 October 2026`) all parse to real timestamps; `.FORECASTER <NAME>.` lines identify the issuer when no `ISSUED BY` exists, and a leading article is trimmed ("Issued by the Australian Government Bureau of Meteorology").
+- NWS's renamed Gulf is normalized back to the crew's name: "GULF OF AMERICA" reads "GULF OF MEXICO" everywhere the cleaned bulletin text is shown or matched.
+- Lines of interest (work doc #1): the briefing detects where the planned passage crosses the traditional ceremonial lines — the equator (Shellback ceremony), the tropics, the polar circles (Blue Nose / Red Nose), the prime meridian and the antimeridian (Domain of the Golden Dragon, with the calendar skip/repeat note) — reading the simulated track, so each crossing's position, distance from start and ETA come from the boat's own schedule rather than the forecast window. The crossings ride the unified passage timeline as `line` events (⌀ glyph, the general form the timeline was built for) instead of a separate strategic block; `passageSummary.linesOfInterest` carries the data, `lines_of_interest_enabled` (default on) turns the feature off.
+- Celestial ephemeris engine (work doc #3 Phase 2): the sky is computed, not fetched. A new `plugin/celestial-ephemeris.js` module built on `astronomy-engine` (MIT, zero transitive dependencies — the dependency decision is made) derives planetary conjunctions and oppositions during nautical night, and meteor shower peaks (static annual calendar) gated to dark, clear, visible nights: moon set or a crescent, radiant able to clear 20° from the vessel's latitude, forecast cloud cover under 30 %. Bright station passes (ISS, Tiangong) are propagated locally from CelesTrak two-line elements with `satellite.js` (MIT — the SGP4 propagator call resolved) in `plugin/satellite-source.js`, reported when the pass peaks over 15° in nautical night under a clear enough sky. Every event passes the full tactical visibility gate the work document specifies — nautical night, altitude over 15° to clear the marine boundary-layer haze, cloud cover, moonlight — and the Phase-1 aurora alert is upgraded onto the same gate (nautical night replaces the sunset-based check; moonlit or overcast nights no longer raise aurora banners). Briefing payloads gain `celestialNights` — per-night twilight times (civil, nautical, astronomical) and moon phase/illumination — and `TimeStepForecast` gains `surface.cloudCover` (Open-Meteo `cloud_cover`; the Weather API provider publishes none and maps null, which leaves the cloud gate open).
+- The timeline's night stamps show the actual moon phase instead of a fixed crescent: `mergeTimeline` picks one of the eight moon glyphs (🌑🌒🌓🌔🌕🌖🌗🌘) for each night-flagged event from the payload's `celestialNights`, falling back to ☾ for payloads that predate the field. The strategic ETA table's night-arrival markers (P10/P50/P90) get the same treatment.
+- **METAREA notes now carry provenance: who published, when.** Every note the bulletin pipeline serves in `resources/notes` is stamped in its `properties` with `publishedBy` — the issuing authority parsed from the bulletin header ("ISSUED BY FIJI METEOROLOGICAL SERVICE …" → `FIJI METEOROLOGICAL SERVICE`), falling back to `signalk-passage-briefing` when the bulletin names no service (structured UKHO warnings, some NWS products) — and `publishedAt`, the bulletin's issue time. Chart plotters can show the line "Published on 10-03 12:00Z by FIJI METEOROLOGICAL SERVICE" straight from the resource; the DR webapp's note detail surface does.
+
 ## [0.4.0] - 2026-10-03
 
 ### Added

package/README.md

@@ -1,121 +1,58 @@
 # signalk-passage-briefing
 
-Offshore passage daily briefing webapp for Signal K: a plugin that plans
-and reviews passages for a cruising sailing vessel.
+Offshore passage daily briefing webapp for Signal K: a plugin that plans and reviews passages for a cruising sailing vessel.
 
 The plugin fetches weather along the planned route — from the server's Weather API when a provider answers, Open-Meteo otherwise; fetched online, or via a GRIB/text spool when offline offshore. It runs a step-forward isochrone simulation with a monohull comfort model, learns the crew's sail preferences from the electronic logbook, and serves a two-screen webapp: a 24-hour tactical dashboard and a strategic passage summary. See [SPEC.md](SPEC.md) for the full design.
 
-Part of the Lille Ø offshore suite, alongside
-[@meri-imperiumi/signalk-energy-predictor](https://github.com/meri-imperiumi/signalk-energy-predictator)
-and [@meri-imperiumi/signalk-logbook](https://github.com/meri-imperiumi/signalk-logbook).
+Part of the Lille Ø offshore suite, alongside [@meri-imperiumi/signalk-energy-predictor](https://github.com/meri-imperiumi/signalk-energy-predictator) and [@meri-imperiumi/signalk-logbook](https://github.com/meri-imperiumi/signalk-logbook).
 
 ## Data sources
 
 ### Signal K
 
-- `navigation.course.activeRoute` — the route being sailed; wins over
-  the last briefed route when the cron/oneshot fetch window opens
-- `navigation.position` — vessel position for the conditions-here
-  empty state and position-only bulletin filtering
-- `network.internet.state` — connectivity gating (weather, bulletins
-  and backfill only fetch while `online` or `metered`)
-- `navigation.state`, `electrical.batteries.house.capacity.stateOfCharge`
-  — state machine inputs (moored/anchored/sailing, publication windows)
-- `polars.activePolar`, `polars.performanceFactor` — the canonical
-  polar resource consumed for boat speed (falls back to a bundled
-  default table)
+- `navigation.course.activeRoute` — the route being sailed; wins over the last briefed route when the cron/oneshot fetch window opens
+- `navigation.position` — vessel position for the conditions-here empty state and position-only bulletin filtering
+- `network.internet.state` — connectivity gating (weather, bulletins and backfill only fetch while `online` or `metered`)
+- `navigation.state`, `electrical.batteries.house.capacity.stateOfCharge` — state machine inputs (moored/anchored/sailing, publication windows)
+- `polars.activePolar`, `polars.performanceFactor` — the canonical polar resource consumed for boat speed (falls back to a bundled default table)
 - Resources API — route geometries and polar tables
-- History API (on board) — wind/attempt snapshots for the sail-event
-  backfill
-- Published tile paths — `navigation.briefing.generatedAt` / `.route` /
-  `.hasNew` / `.comfort` drive the plotter-extension tile
-  (`.acknowledgedAt` is writable to clear the NEW badge)
-- [signalk-logbook](https://github.com/meri-imperiumi/signalk-logbook)
-  store — crewed sail events (reefs, sail changes) that train the
-  preference matrix
-- [signalk-ships-time](https://github.com/meri-imperiumi/signalk-ships-time)
-  — `environment.time.timezoneOffset` / `.timezoneRegion`, the
-  vessel's published timezone: briefing stamps render in ship's time
-  when available (the offset rides on every stamp), falling back to
-  UTC `Z` when nothing is published
-- [signalk-watch-schedule](https://github.com/hoeken/signalk-watch-schedule)
-  — `watch.state.onWatch`, `watch.state.startedAt`, `watch.system` and
-  `watch.schedule`: the running watch rotation. While a watch is
-  running, planned sail changes anchor to the previous watch handover
-  (both teams awake) instead of sunrise/sunset; boundaries are
-  extrapolated across the forecast horizon from the rotation cycle
-- [@signalk/sailsconfiguration](https://www.npmjs.com/package/@signalk/sailsconfiguration)
-  — sail inventory used to filter free-text noise out of log entries
-- Weather API (`app.weatherApi`) — waypoint forecasts from the
-  registered provider, the preferred source (`weather_source: auto`)
-  whenever one answers; [signalk-weather-router-plus](https://github.com/motamman/signalk-weather-router-plus)
-  serves it from its decoded ECMWF run, so briefing numbers match what
-  the router planned with. That source carries combined sea only:
-  swell/wind-sea partitions and the upper-air fields behind the
-  convective warnings degrade to absent rather than being invented
+- History API (on board) — wind/attempt snapshots for the sail-event backfill
+- Published tile paths — `navigation.briefing.generatedAt` / `.route` / `.hasNew` / `.comfort` drive the plotter-extension tile (`.acknowledgedAt` is writable to clear the NEW badge)
+- [signalk-logbook](https://github.com/meri-imperiumi/signalk-logbook) store — crewed sail events (reefs, sail changes) that train the preference matrix
+- [signalk-ships-time](https://github.com/meri-imperiumi/signalk-ships-time) — `environment.time.timezoneOffset` / `.timezoneRegion`, the vessel's published timezone: briefing stamps render in ship's time when available (the offset rides on every stamp), falling back to UTC `Z` when nothing is published
+- [signalk-watch-schedule](https://github.com/hoeken/signalk-watch-schedule) — `watch.state.onWatch`, `watch.state.startedAt`, `watch.system` and `watch.schedule`: the running watch rotation. While a watch is running, planned sail changes anchor to the previous watch handover (both teams awake) instead of sunrise/sunset; boundaries are extrapolated across the forecast horizon from the rotation cycle
+- [@signalk/sailsconfiguration](https://www.npmjs.com/package/@signalk/sailsconfiguration) — sail inventory used to filter free-text noise out of log entries
+- Weather API (`app.weatherApi`) — waypoint forecasts from the registered provider, the preferred source (`weather_source: auto`) whenever one answers; [signalk-weather-router-plus](https://github.com/motamman/signalk-weather-router-plus) serves it from its decoded ECMWF run, so briefing numbers match what the router planned with. That source carries combined sea only: swell/wind-sea partitions and the upper-air fields behind the convective warnings degrade to absent rather than being invented
 
 ### External
 
-The Open-Meteo entries below are the fallback weather source: used
-when no Weather API provider answers (or `weather_source` is
-`open-meteo`), and the only source of the partition and upper-air
-fields the Weather API providers don't publish.
-
-- [Open-Meteo Forecast API](https://open-meteo.com/en/docs) — surface
-  wind, gusts, MSL pressure, CAPE and the pressure-layer fields behind
-  the K-index (best-match model)
-- [NOAA SWPC planetary K-index forecast](https://services.swpc.noaa.gov/products/noaa-planetary-k-index-forecast.json)
-  — geomagnetic activity behind the aurora advisories
-- [JPL SBDB query API](https://ssd-api.jpl.nasa.gov/doc/sbdb_query.html)
-  — comet brightness parameters (M1/K1) behind the Sky Notes comets
-- [NOAA TGFTP radiofax tree](https://tgftp.nws.noaa.gov/fax/) and the
-  [BoM difacs charts](http://www.bom.gov.au/difacs/) — synoptic
-  surface-analysis charts per METAREA zone (work doc #11), per the
-  schedule in
-  [otherfax.txt](https://tgftp.nws.noaa.gov/fax/otherfax.txt)
-- [Open-Meteo Marine API](https://open-meteo.com/en/docs) —
-  NOAA GFS-Wave 0.25° combined sea/wind sea/swell partitions, and
-  Météo-France SMOC surface currents
-- NOAA TGFTP (`tgftp.nws.noaa.gov`) — raw METAREA bulletin text for
-  the resolved GMDSS zone's station (e.g. `FQPS01 NFFN` for XIV)
-- WMO GMDSS portal (`weather.gmdss.org`) — per-zone bulletin pages,
-  fallback when the TGFTP station is not configured
-- api.weather.gov product API — US High Seas Forecast texts (default
-  `bulletin_urls`: HSF NP/EP1/EP2); extra sources can be added via the
-  `bulletin_urls` configuration (plain text or api.weather.gov
-  product URLs; UKHO MSI JSON works too)
-
-All external fetches are online-gated and cached to the plugin data
-directory, so the last payloads survive the offline hours.
+The Open-Meteo entries below are the fallback weather source: used when no Weather API provider answers (or `weather_source` is `open-meteo`), and the only source of the partition and upper-air fields the Weather API providers don't publish.
+
+- [Open-Meteo Forecast API](https://open-meteo.com/en/docs) — surface wind, gusts, MSL pressure, CAPE and the pressure-layer fields behind the K-index (best-match model)
+- [NOAA SWPC planetary K-index forecast](https://services.swpc.noaa.gov/products/noaa-planetary-k-index-forecast.json) — geomagnetic activity behind the aurora advisories
+- [JPL SBDB query API](https://ssd-api.jpl.nasa.gov/doc/sbdb_query.html) — comet brightness parameters (M1/K1) behind the Sky Notes comets
+- [CelesTrak](https://celestrak.org/NORAD/elements/gp.php?GROUP=stations&FORMAT=tle) — two-line elements for the crewed stations (ISS, Tiangong); bright satellite passes are propagated locally from the fetched TLEs with SGP4, gated to nautical night, clear sky and a 15° haze line
+- [NOAA TGFTP radiofax tree](https://tgftp.nws.noaa.gov/fax/) and the [BoM difacs charts](http://www.bom.gov.au/difacs/) — synoptic surface-analysis charts per METAREA zone (work doc #11), per the schedule in [otherfax.txt](https://tgftp.nws.noaa.gov/fax/otherfax.txt)
+- [UKHO Admiralty MSI API](https://msi.admiralty.co.uk/) — structured NAVAREA navigational warnings for the resolved zone; the third rung of the GMDSS bulletin fetch ladder (TGFTP raw text, WMO GMDSS portal, then UKHO MSI JSON) and also accepted verbatim as a `bulletin_urls` source
+- [GDACS RSS](https://www.gdacs.org/xml/rss.xml) — EU JRC global disaster alerts (earthquakes, tropical cyclones, floods, volcanic activity), filtered route-relative by alert level and corridor distance: they ride the unified passage timeline and publish as georeferenced chart notes (work doc #22)
+- [Open-Meteo Marine API](https://open-meteo.com/en/docs) — NOAA GFS-Wave 0.25° combined sea/wind sea/swell partitions, and Météo-France SMOC surface currents
+- NOAA TGFTP (`tgftp.nws.noaa.gov`) — raw METAREA bulletin text for the resolved GMDSS zone's station (e.g. `FQPS01 NFFN` for XIV)
+- WMO GMDSS portal (`weather.gmdss.org`) — per-zone bulletin pages, fallback when the TGFTP station is not configured
+- api.weather.gov product API — US High Seas Forecast texts (default `bulletin_urls`: HSF NP/EP1/EP2); extra sources can be added via the `bulletin_urls` configuration (plain text or api.weather.gov product URLs; UKHO MSI JSON works too)
+
+All external fetches are online-gated and cached to the plugin data directory, so the last payloads survive the offline hours.
 
 ## Pairing with Weather Router Plus
 
-[signalk-weather-router-plus](https://github.com/motamman/signalk-weather-router-plus)
-plans the passage: isochrone routing against the vessel's polar on the ECMWF open-data run it keeps decoded on disk, with map overlays, tides and currents. Activate the route it publishes to the Resources API, and this plugin briefs it — `navigation.course.activeRoute` wins over the last briefed route at the next fetch window, and with `weather_source: auto` (the default) the briefing reads its forecasts from the router's Weather API provider. One forecast on board, planner and briefing in agreement: the router for planning and visualization, the briefing for the underway daily routine (comfort, sail changes, bulletins, energy).
+[signalk-weather-router-plus](https://github.com/motamman/signalk-weather-router-plus) plans the passage: isochrone routing against the vessel's polar on the ECMWF open-data run it keeps decoded on disk, with map overlays, tides and currents. Activate the route it publishes to the Resources API, and this plugin briefs it — `navigation.course.activeRoute` wins over the last briefed route at the next fetch window, and with `weather_source: auto` (the default) the briefing reads its forecasts from the router's Weather API provider. One forecast on board, planner and briefing in agreement: the router for planning and visualization, the briefing for the underway daily routine (comfort, sail changes, bulletins, energy).
 
 ## Pairing with Watch Schedule
 
-[signalk-watch-schedule](https://github.com/hoeken/signalk-watch-schedule)
-runs the crew's watch rotation and publishes it under `watch.*`. When a
-watch is running, this plugin reads the schedule at app load and moves
-planned sail changes (reefs, canvas work) to the *previous* watch
-handover — the moment both teams are awake on deck — rather than
-sunrise/sunset; tacks and gybes stay at their tactical times, since
-course work can't wait for a handover. The watch boundary wins over
-sunlight. Without a running watch, canvas work anchors to the next
-sunrise/sunset. Webapp-side only: no configuration, and the briefing
-works unchanged when the plugin is absent.
+[signalk-watch-schedule](https://github.com/hoeken/signalk-watch-schedule) runs the crew's watch rotation and publishes it under `watch.*`. When a watch is running, this plugin reads the schedule at app load and moves planned sail changes (reefs, canvas work) to the *previous* watch handover — the moment both teams are awake on deck — rather than sunrise/sunset; tacks and gybes stay at their tactical times, since course work can't wait for a handover. The watch boundary wins over sunlight. Without a running watch, canvas work anchors to the next sunrise/sunset. Webapp-side only: no configuration, and the briefing works unchanged when the plugin is absent.
 
 ## Acknowledgments
 
-The comfort model and the whole idea of "what will each departure
-actually feel like" come from SV Sabado's
-[passage-weather](https://github.com/sailing12388/passage-weather)
-ensemble departure planner by Ray Hendricks. The Sereno comfort scale
-(Champagne, Easy, Coffee, Rough, Sick), the encounter-period motion
-math, and the ISO 2631-1 comfort bands are adapted from it for a
-monohull (heel and waterline-pitch resonance instead of catamaran
-beam-roll and bridgedeck slam).
+The comfort model and the whole idea of "what will each departure actually feel like" come from SV Sabado's [passage-weather](https://github.com/sailing12388/passage-weather) ensemble departure planner by Ray Hendricks. The Sereno comfort scale (Champagne, Easy, Coffee, Rough, Sick), the encounter-period motion math, and the ISO 2631-1 comfort bands are adapted from it for a monohull (heel and waterline-pitch resonance instead of catamaran beam-roll and bridgedeck slam).
 
 ## License
 

package/SPEC.md

@@ -77,6 +77,52 @@ signalk-passage-outlook/
       "type": "number",
       "title": "Pitching Acceleration Multiplier Constant",
       "default": 0.40
+    },
+    "lines_of_interest_enabled": {
+      "type": "boolean",
+      "title": "Lines of Interest (ceremonial crossings)",
+      "default": true
+    },
+    "hazard_events_enabled": {
+      "type": "boolean",
+      "title": "GDACS Hazard Events",
+      "default": true
+    },
+    "hazard_min_alert_level": {
+      "type": "string",
+      "enum": ["green", "orange", "red"],
+      "title": "Minimum GDACS Alert Level",
+      "default": "orange"
+    },
+    "hazard_radius_offroute_nm": {
+      "type": "number",
+      "title": "Hazard Off-route Radius (nm)",
+      "default": 500
+    },
+    "hazard_radius_ahead_nm": {
+      "type": "number",
+      "title": "Hazard Vessel Radius (nm)",
+      "default": 1000
+    },
+    "hazard_max_age_hours": {
+      "type": "number",
+      "title": "Hazard Event Aging (hours)",
+      "default": 72
+    },
+    "departure_daylight_auto": {
+      "type": "boolean",
+      "title": "Anchor Departure to Daylight (auto)",
+      "default": true
+    },
+    "departure_prep_hours": {
+      "type": "number",
+      "title": "Departure Prep Delay (hours)",
+      "default": 1.5
+    },
+    "departure_dawn_altitude_deg": {
+      "type": "number",
+      "title": "First Light Sun Altitude (degrees)",
+      "default": -6
     }
   }
 }
@@ -144,6 +190,63 @@ interface UnifiedWeatherPayload {
     issuedAt: string;
     bulletinText: string;
   };
+  spaceEvents?: {
+    kind: string;               // 'aurora' | 'comet' | 'conjunction' | 'opposition' | 'meteor'
+    timestamp: string;          // ISO timestamp
+    tactical: boolean;          // 24h dashboard banner vs strategic sky note
+    description: string;
+  }[];
+  celestialNights?: {
+    timestamp: string;          // ISO timestamp (night anchor)
+    moonPhaseDeg: number;       // 0 = new, 90 = first quarter, 180 = full, 270 = third quarter
+    moonIllumination: number;   // fraction 0-1
+    civilDusk: string | null;   // ISO timestamps, null beyond polar day/night
+    nauticalDusk: string | null;
+    astronomicalDusk: string | null;
+    astronomicalDawn: string | null;
+    nauticalDawn: string | null;
+    civilDawn: string | null;
+  }[];
+  hazardEvents?: {
+    id: string;                 // GDACS event id
+    type: string;               // 'EQ' | 'TC' | 'FL' | 'VO' | 'DR' | 'WF'
+    alertLevel: string;         // 'green' | 'orange' | 'red'
+    title: string;
+    description: string;
+    timestamp: string;          // ISO, newer of pubDate/datemodified
+    lat: number;
+    lon: number;
+    distanceNm: number;         // from the admitting reference (vessel or route)
+    bearingDeg: number;         // degrees true from the same reference
+    link: string | null;        // GDACS event page
+  }[];
+  zoneTransitions?: {
+    kind: 'enter' | 'leave';    // boundary crossing direction
+    territory: { name: string; iso_ter: string };
+    lat: number;                // crossing position
+    lon: number;
+    distanceFromStartNm: number;
+    connectivity?: 'ocean';     // leave events: metered-ocean rules beyond
+  }[];
+  zonesHere?: {                 // here mode: waters the vessel sits in
+    layer: string;              // 'internal' | 'archipelagic' | '12nm'
+    name: string;
+    iso_ter: string;
+    territory: string;
+  }[];
+  zoneDisclaimer?: string;      // Marine Regions attribution + no-navigation notice
+  energyHourly?: {
+    timestamp: string;          // ISO hour stamp
+    solarWh: number;            // total ideal generation (solar+wind+hydro+alternator)
+    loadWh: number;             // house consumption
+    netWh: number;              // solarWh - loadWh
+    soc: number | null;         // ideal SoC 0-1 at hour end
+  }[];                          // signalk-energy-predictor forecast, 48 h
+  departure?: {
+    assumed: boolean;           // auto daylight anchor vs crew override
+    time: string;               // ISO — the schedule's anchor instant
+    reason: string;             // 'underway' | 'next_dawn' | 'daylight_prep' | 'no_dawn' | 'manual'
+  };
 }
 
 interface TimeStepForecast {
@@ -152,6 +255,7 @@ interface TimeStepForecast {
     tws: number;                // knots
     twd: number;                // degrees true
     mslp: number;               // hPa
+    cloudCover: number | null;  // percent (0-100); null when the source carries none
   };
   marine: {
     hsCombined: number;         // meters
@@ -351,6 +455,19 @@ $$a_z = a_{z,\text{base}} \cdot \mu_{\text{heel}} \cdot \mu_{\text{pitch}}$$
 * $0.630 \le a_z < 1.250\text{ m/s}^2 \implies \mathbf{Rough}$
 * $a_z \ge 1.250\text{ m/s}^2 \implies \mathbf{Sick}$
 
+#### Slatting & Roll-Dampening Penalty (work doc #14)
+
+On a monohull, aerodynamic pressure in the sails dampens roll. When
+that pressure is lost but a residual swell remains, the snap-roll and
+boom shock-loading can be worse than a gale — yet raw $a_z$ scores it
+calm, because the sea state itself is modest. After the base rating:
+
+1. **Glassy-calm gate:** if $H_{s,\text{combined}} < 0.6\text{ m}$ there is not enough wave energy to roll the hull — the penalty is skipped entirely.
+2. **Dampening-loss thresholds:** otherwise the sails have lost their dampening pressure when
+   * upwind / reaching ($|TWA| < 90°$): $TWS < 7.0\text{ kt}$
+   * downwind / running ($|TWA| \ge 90°$): $TWS < 12.0\text{ kt}$ — the boat sails away from its wind, dropping apparent wind below flow-attachment.
+3. **Washing-machine penalty:** when the regime is detected, the vertical acceleration is multiplied by $\mu_{\text{slat}} = 2.5$ before ISO banding, and the hour's tier is forced to at least **Rough**. The hourly row carries a `slatting` tag; the tactical dashboard renders slatting-triggered Rough blocks with a diagonal hatch (alternating `--comfort-rough` over the card background) so the skipper sees the discomfort is light-air slatting, not heavy weather — alter course for a better wave angle, drop the main and motor, or lock the boom down.
+
 
 
 ### 5.3 Hazard Proximity Ray-Casting Algorithm

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meri-imperiumi/signalk-passage-briefing",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Offshore passage daily briefing webapp for Signal K",
   "main": "plugin/index.js",
   "scripts": {
@@ -44,6 +44,9 @@
     "node": ">=22.5.0"
   },
   "dependencies": {
+    "@openwaters/maritime-zones": "^0.2.1",
+    "astronomy-engine": "^2.1.19",
+    "satellite.js": "^7.1.0",
     "yaml": "^2.9.0"
   },
   "devDependencies": {

package/plugin/bulletin-engine.js

@@ -54,6 +54,10 @@ const SECTION_ANCHORS =
  * lines. The NAVTEX message id line (`ZCZC GA05 011200Z AUG 26`) is
  * kept — the subject filter reads it first.
  *
+ * NWS's renamed geography is normalized back to the name the crew
+ * uses: "GULF OF AMERICA" reads "GULF OF MEXICO" everywhere the
+ * cleaned text is shown or matched.
+ *
  * @param {string} text - Raw bulletin text
  * @returns {string} Cleaned text
  */
@@ -71,6 +75,7 @@ function stripBoilerplate(text) {
       return true;
     })
     .join("\n")
+    .replace(/\bGULF OF AMERICA\b/gi, "GULF OF MEXICO")
     .replace(/\n{3,}/g, "\n\n")
     .trim();
 }
@@ -175,14 +180,24 @@ function hemisphereDegrees(value, hemisphere) {
  * are missing are prose numbers ("280600 UTC", "20 TO 30 KNOTS")
  * and rejected.
  *
+ * Also accepts the compact NHC Atlantic form (`13N67W`, no separator
+ * between the latitude and longitude parts) by normalizing it to the
+ * spaced form first — the loose pattern cannot match it because
+ * there is no separator to consume.
+ *
  * @param {string} text
  * @returns {number[][]} [[lon, lat], …] (possibly empty)
  */
 function parseCoordinatePoints(text) {
+  // Compact NHC pairs: digits + NS + digits + EW glued together
+  const compact = text.replace(
+    /\b(\d{1,3})([NS])(\d{1,3})([EW])\b/g,
+    "$1$2 $3$4",
+  );
   const pair = /(\d+(?:\.\d+)?|EQT)\s*([NS])?[,\s]+(\d+(?:\.\d+)?)\s*([EW])?/gi;
   const points = [];
   let match;
-  while ((match = pair.exec(text)) !== null) {
+  while ((match = pair.exec(compact)) !== null) {
     const equator = match[1].toUpperCase() === "EQT";
     const latHemi = match[2]?.toUpperCase();
     const lonHemi = match[4]?.toUpperCase();
@@ -192,10 +207,17 @@ function parseCoordinatePoints(text) {
       pair.lastIndex = match.index + 1;
       continue;
     }
+    const lonValue = hemisphereDegrees(match[3], lonHemi ?? "E");
+    if (!equator && !lonHemi && lonValue !== 180) {
+      // A hemisphere-less longitude that is not the dateline
+      // shorthand is prose's second number ("07N TO 31N" is two
+      // latitudes, not 7N 31E) — reject it the same way
+      pair.lastIndex = match.index + 1;
+      continue;
+    }
     const lat = equator ? 0 : hemisphereDegrees(match[1], latHemi ?? "N");
-    const lon = hemisphereDegrees(match[3], lonHemi ?? "E");
-    if (Number.isFinite(lat) && Number.isFinite(lon)) {
-      points.push([lon, lat]);
+    if (Number.isFinite(lat) && Number.isFinite(lonValue)) {
+      points.push([lonValue, lat]);
     }
   }
   return points;
@@ -737,6 +759,38 @@ function intersectsTrack(geometry, track) {
   return true;
 }
 
+/**
+ * Extracts the issuing authority from a bulletin's text (work doc #12
+ * provenance): GMDSS bulletins name their service in the header block,
+ * e.g. "ISSUED BY FIJI METEOROLOGICAL SERVICE SEP 270800 UTC." The
+ * name is captured verbatim, minus the trailing issue-time fragment
+ * and punctuation. Null when the bulletin does not name an issuer
+ * (structured UKHO warnings, some NWS products) — consumers then fall
+ * back to the publishing plugin.
+ *
+ * @param {string} text - Raw or cleaned bulletin text
+ * @returns {string|null} Issuer name, e.g. "FIJI METEOROLOGICAL SERVICE"
+ */
+function extractIssuer(text) {
+  const match = text.match(/ISSUED\s+BY\s+(.+)/i);
+  if (!match) {
+    // NHC High Seas style: ".FORECASTER DELGADO. NATIONAL HURRICANE
+    // CENTER." — the forecaster's surname stands in for the issuer
+    const forecaster = text.match(/\bFORECASTER\s+([A-Z][A-Z .'-]+)/i);
+    return forecaster ? forecaster[1].replace(/[.\s]+$/, "") : null;
+  }
+  // Strip the trailing issue-time fragment in its observed shapes
+  // ("SEP 270800 UTC", "270800 UTC", "270800Z"), then any trailing
+  // punctuation or padding the station style leaves behind. The
+  // leading \s+ anchors the fragment to a word start, so a name that
+  // merely ends in 3–4 letters can't be mistaken for the month token.
+  const name = match[1]
+    .replace(/\s+(?:[A-Z]{3,4}\.?\s+)?\d{4,10}Z?(?:\s+UTC)?\.?\s*$/i, "")
+    .replace(/^[Tt][Hh][Ee]\s+/, "")
+    .replace(/[.\s]+$/, "");
+  return name || null;
+}
+
 /**
  * Runs the full pipeline over one raw bulletin (work doc #4 §2–4):
  * boilerplate stripping, NAVTEX subject filter, GMDSS segmentation,
@@ -751,9 +805,9 @@ function intersectsTrack(geometry, track) {
  *   keep (default {@link RETAINED_SUBJECTS})
  * @param {string} [params.issuedAt] - Issue time override (spool
  *   file parsing result); extracted from the text otherwise
- * @returns {object|null} `{header, issuedAt, bulletinText, source,
- *   blocks: [{text, subject, geometryType, source}]}` — null when
- *   the whole message is discarded by the subject filter
+ * @returns {object|null} `{header, issuedAt, issuer, bulletinText,
+ *   source, blocks: [{text, subject, geometryType, source}]}` — null
+ *   when the whole message is discarded by the subject filter
  */
 function filterBulletin({
   rawText,
@@ -792,6 +846,7 @@ function filterBulletin({
       issuedAt ??
       spoolWatcher.extractIssuedAt(cleaned) ??
       new Date(0).toISOString(),
+    issuer: extractIssuer(cleaned),
     bulletinText: rawText,
     source,
     blocks,
@@ -979,6 +1034,7 @@ module.exports = {
   polygonIntersectsTrack,
   bboxIntersectsTrack,
   intersectsTrack,
+  extractIssuer,
   filterBulletin,
   fetchRemoteBulletin,
   resolveBulletinSource,