* fix(voice): a selection steps a docked assistant panel down so Context shows; the panel keeps the last reply
A voice or chat action that selects an entity (select_nearest_aircraft,
track_entity) now minimizes a voice or chat panel docked in the right rail's
lane, so the rail and its Context panel show as after a click. The voice
card inside the panel no longer hides 14 s after its last update: the reply
stays until the next turn, Stop or a dismissal. The floating card keeps its
idle deadline.
* fix(voice): a voice or chat selection opens its card in the Context panel
A successful select_nearest_aircraft or track_entity now selects the entity
in the Context panel's entity card store the same way a click does, so the
panel opens on its details; the docked assistant panel then steps down so it
shows. track_entity reports the id it tracked. Nothing opens in Cockpit,
where Context is hidden.
* fix(voice): a slow selection never replaces a card picked since; Cockpit is read from its own state
The entity card store counts selections and clears. A voice or chat
selection notes that count when it is asked and opens its card only if no
other card was picked or cleared before it finished. Whether Cockpit is
running is read from the style manager's Cockpit state when it has one.
* Add the changelog entry
* fix(voice): the app hands voice its Context card opener
The voice package no longer imports the entity card store. The app builds
the opener (createContextCardOpener) and passes it to the voice commands as
contextCard, which keeps the voice package inside its own boundary.
* fix(voice): voice Cockpit entry no longer turns Contacts on
Voice entry now changes no Context mode or detection setting, as the COCKPIT
button does not. An entry that names a layer or class searches that layer's
own aircraft, nearest first from the followed aircraft or the ground under
the camera, and follows the nearest match before entering; the followed
aircraft counts when it matches. A military request while Military Flights
is off switches that layer on as a plain layer. The class filter is shared
with Contacts navigation.
* fix(voice): a military Cockpit entry waits for the layer's first data and leaves no layer behind
A military entry that switched Military Flights on waits for that layer to
report its first data before searching it, bounded by that update, the
layer failing or going off, and the request's cancellation. If entry then
fails, the layer is switched off again; a layer that was already on stays
on. The search covers only the aircraft the person's filters show.
* Add the changelog entry
* Show JTWC warnings in Cyclone advisories
Cyclone advisories now also read the Joint Typhoon Warning Center (keyless,
public domain) for the western North Pacific, North Indian Ocean and Southern
Hemisphere, beside NHC and CPHC.
- server/providers/jtwc.js reads JTWC's warnings feed, each storm's JMV 3.0
warning (.tcw) and its overlay (.kmz). /api/cyclones merges them with NHC's:
one storm per id, NHC's advisory where NHC lists the storm. A failed JTWC
read keeps its last storms, marked stale, and never hides NHC's.
- Storms carry an agency. A JTWC warning has no cone; its 34-knot wind danger
area is drawn as its own dashed area and named for the selected storm.
- A JTWC storm's card notes that the regional centre's warning is official
and that JTWC winds are 1-minute averages. Source and coverage wording names
both agencies.
- Each storm is served while its own advisory is usable (12 hours for NHC,
13 for JTWC).
* Keep one JTWC failure from affecting other storms or NHC
- A storm whose JTWC warning cannot be read or parsed is left out and the
others are shown; the read fails only when every listed storm's does.
- JTWC is read under its own 8-second deadline. A failed or slow JTWC read
keeps JTWC's last good storms and never delays, fails or stales the NHC
answer.
- Danger-swath longitudes past ±180 (a ring crossing the antimeridian) are
wrapped into -180..180 instead of dropping the ring.
* Add the changelog entry for JTWC cyclones
_clearTracking cleared the focus rectangle, then told the camera to stop
following before marking the satellite released. A follow listener that read
the tracked position in between (the Cockpit entry button does) published the
rectangle again, and nothing cleared it: every icon inside a centred screen
rectangle stayed at 25% opacity once the camera was farther than the old
follow distance.
The satellite is now marked released before the camera hears of it.
It timed a 0.2 s camera flight against real timers with a few milliseconds of slack, so slow runners failed it at random. The resumed-hold tests next to it still cover resuming a run partway through a scene.
The desktop search layout had moved the round globe actions down to the
HUD's top rows, where the loading line (top: 74px) was drawn over them.
They now sit on the title row again (top: 32px), level with the title,
and the loading line stays under them. Narrower than 1180px, where the
centred row would reach the title, the actions keep their lower place and
the loading line moves 42px under them.
setMarkerStandIn takes an optional focusRangeM(record): when a click on a fire the stand-in draws moves the camera there, it stands off that many metres instead of the usual fire framing. A world focus request may carry its own rangeM; past the framed radius it replaces the kind's range.
The fire layer takes a stand-in for its markers (setMarkerStandIn({ hitTest })): its glows, heatmap and ambient cards are hidden, and a click the stand-in answers selects and focuses the fire exactly as a marker click does.
The fire layer module exports filterFires and DEFAULT_FIRE_FILTER, the filter its markers use, so an application drawing the same detections another way hides the same fires.