Changelog

A focused row of a trace waterfall draws the kit's 2 px focus ring outside it, whole on both forms, where it drew a stroke on the row's background and removed the outline; the row background is inset and the stacked form's bars start clear of the ring.

A row with attributes is a button: focusing or hovering it shows them in a panel below its bar, and pressing or tapping it keeps them until the next press or Escape; the panel grows with its contents where it was clipped at 100 px, and the row tint and panel surface take tokens (designed with reference to WCAG 2.2 criteria 2.1.1 and 1.4.13).

A trace waterfall's label column and the width below which its labels stack are measured in captions, 240 px and 560 px at the regular size class, so at helm the column widens with its text and the labels stack in a wider box, as the kit's em breakpoints do.

A trace waterfall's title, row labels, axis times, durations and attributes are set in the caption role, 12 px and larger at helm, where they were fixed at 8 to 10 px; a bar holds its duration when the text fits it, and a stacked label's line grows with the text.

A trend chart's axis, threshold and time labels read 9 px on the screen whatever the chart's width, and grow at helm; drawn in the chart's own units they shrank to about 6 px in a phone's column and grew to about 17 px in a wide one. The margins that hold them follow.

A sparkline's reference line labels are two thirds of the caption role, read where the drawing is drawn, so they are 8 px at the default size class and grow at helm, their placement with them.

A chess board sizes its pieces from its own squares, so a board in a narrow column draws smaller pieces and a wide one larger, whatever the window's width; its coordinates take three quarters of a caption and grow at helm.

The logo's mark, name, tagline and version are sized in em of the body role, so at helm the whole logo grows with the text around it; at the default size class each is the size it was, to the pixel.

An entity list's record count takes the caption role's size, 12 px growing to 14 px at helm, where it was 11 px at every size.

The notice shown when the live connection to Bosun is lost sets its message in the body role, Plex Sans at 14 px growing to 18 px at helm, where it was 11 px mono at every size; its corner takes the large radius token.

A moved chess piece slides as a browser animation of its transform, on the compositor, so it stays smooth while the vessel's computer is busy; its slide was rewritten from script each frame.

A component's rise or scale entrance and exit run as browser animations of opacity and transform, on the compositor, so they stay smooth while the vessel's computer is busy; the movement was rewritten from script each frame and could stall while the fade went on.

A field refused because it changed elsewhere says "Couldn't save: this was changed elsewhere while you were editing and is now Nederlands…", opening as the list's other save errors do, where it opened with the passive "Not saved:", and the German, French and Dutch texts lose a missing object and two repeated words.

After a field's save is refused because it changed elsewhere, the list loads again and the open record holds the new value, so the record opened again shows it and the next save goes through, where it showed the old value and was refused again until the page was reloaded.

A vessel profile drawn narrower than its width, in a phone's column, keeps its proportions, where it kept its height and left empty bands above and below the hull.

Change… sends each record's value as read, as a form's save does, so bosund refuses a record that changed elsewhere since the list loaded; the dialog says "Couldn't change Jonas Berg: it was edited elsewhere since the list loaded…", and Undo puts back only the records that changed, where a refused change could be reported as done and offered for Undo.

The vessel page example draws her profile across the page with her lengths, draft, beam, air draft and displacement on it, and sets her identity and her stores in two cards that share the width under it, where the figures stood apart in one narrow list beside empty space.

A tide curve takes its column's width and widens with it, where in a column sized to its content (the design site's hero, a centered stage) it kept the narrowest width it had once drawn.

A tide curve too narrow to give each hour 24 px shows fewer hours, at least six, a quarter of them before now and the rest ahead, where it squeezed the whole period into a phone's width; the list of high and low waters keeps every one.

A tide curve's room for its axis labels grows with the caption role they take, so at helm the larger height and time labels are not cut off at the chart's edges; at the default size class nothing moves.

A rating of ten steps wraps onto a second line in a narrow column, each step a whole touch target, where it ran 480 px wide past its column.

A nav list's and a navigation bar's labels wrap onto more lines, hyphenated in the crew's language, where they were cut short with an ellipsis: each is the only copy of its page's name on the screen.

The popover's header, title, close button and body rules were declared twice, identically; the second copy is gone and nothing draws differently.

A skeleton with no height of its own is the reading body's text size tall, 16 px at the default size class and larger in a helm scope, where it stayed 16 px and fell short of a helm line.

An auto-saved field sent the whole record as the form first loaded it, so a change made elsewhere meanwhile (a crew member's "speak Dutch" to bosun, another browser) was either overwritten or silently kept while the form showed the field as saved. A save now names, under as_read, the value each field it changes had when the form read it; bosund refuses a field that moved since with a 409 listing it and its value now, and the field says "Not saved: this changed elsewhere while you were editing and is now Nederlands. Reopen the entry to see it, then choose again." A save that goes through is answered with the stored record, and the next field's save builds on it.

A vessel overview's profile drawing keeps to 42% of the screen's height, as the device preview or a shell of fixed height draws it, where it took 42% of the window's and could fill a short screen.

A switch, a select's trigger, an outlined field and a password field's show button are sized in steps of the reading body's size, which is 1rem at the default size class, so a helm scope around part of a page enlarges them with their text; in rem they followed only the page's root.

Every icon a component draws is sized in em of the text around it, so at helm it grows as the text does: a field's calendar icon from 20 to 25 px, a button's from 16 to about 21 px. At the default size class each is the size it was, to the pixel.

The language picker's trigger sets its language code in the label role, so it follows the size class; it took the browser's own button font, 13.3 px at every size.

On a short screen, a phone on its side, a chat input's "/" menu is about two commands tall and scrolls inside itself, so the field and the page above it stay in sight; it was 16em, most of a 360 px screen.

In a shell that fills a container of fixed height, the open phone navigation ends at the shell's bottom edge and scrolls inside itself, where it measured the window and ran past the shell, as in the design site's device preview.

The button's and the due chip's motion docs say that true also scales them in as they mount anywhere, the alert list row's doc says a warning's icon stays steady, and the setting's save chip names its spinner.

The language picker's menu fades out over the fast duration as it closes, as other menus do; it vanished at once.

An autocomplete's and a combo box's suggestion list fades out over the fast duration as it closes, as the motion foundation's table promises for the combo box list; it vanished at once.

The panel an outlined field opens under itself (a calendar, a time list, a country list, a crew list) fades out over the fast duration as it closes, where it vanished at once.

A select's list fades out over the fast duration as it closes, as the motion foundation's table promises for the select list; it vanished at once.

A popover enters over the medium duration, as the motion foundation's durations say for a popover entering; it entered over the fast one. It still leaves over the fast duration.

A menu, a context menu and an action menu enter over the medium duration on the enter curve and leave over the fast one on the exit curve, as the motion foundation's durations say; they entered on the fast duration, and a menu left on the enter curve.

A component's default entrance plays when it is added with a child of a MotionPresence, not when it appears later inside a child already on the page: a reading that arrives in a card, or anything on a page under a route-level presence, appears in place.

Switching between the full and the reduced motion no longer plays every badge's, button's and reading's last change again; a change plays once, when its value changes.

A component's motion prop no longer takes attention: it ran the alert clock on a skeleton, a notice, a chart or a field and drew no flash; the badge and the alert card set their own flash for an unacknowledged alarm.

Closing a collapsible fades its content out over the fast duration before it leaves, as opening fades it in; the height still changes in one step, as only opacity and position move.

The kit carries the OpenBridge sensor, speed, heading, route, waypoint, target, collision and instrument-quantity icons, the navigational statuses AIS reports, the IEC 62923 alert icons, machinery and tank icons, communications and weather conditions, 934 icons in all; the OpenBridge icons page lists the families by group and its gallery filters by each.

On a phone the header bar's padding is the small steps and an empty alert zone adds no row, so the bar stays under 64 px with the status strip's 48 px chips; at 24em and narrower the strip's items close up and the sensors chip shows a gauge and its integrity mark without its word, which stays in its name, so the clock keeps the row at 320 px in every language.

On a phone or a tablet, or under a finger, a chat input's model picker is the touch size, as its field and send button are, and lines up with the send button; it was 44 px, 2 px off the button's line.

data-prefers-reduced-motion on the page's root element, reduce or no-preference, chooses the reduced or the full motion for every kit component whatever the device asks; with neither the device decides, as before.

The line under a date range picker is there from the start: it says to choose the first day, then the last, and then writes the range out with its days, so choosing a range no longer adds a line and moves what is below the field.

The chess board measures where the browser's symbol font draws the piece glyphs and moves the pieces by that much, so they center on their squares with Apple Symbols on a Mac as with Noto Sans Symbols 2 or DejaVu Sans; a fixed offset measured for those two drew them low on a Mac.

An outlined field's error line rises in when it appears and fades out when the value is fixed, by default, as a form field's error does and the motion foundation's table says; it stood still unless the caller asked. An error there on the first render does not move.

A moved chess piece, and a castling rook, slide to their square on the standard curve, the one for something moving within the screen; they slid on the enter curve, which is for something arriving.

A change's pop plays at most once per highlight interval on each element, as the highlight does, so a badge counting AIS targets that climb quickly pops once and then shows each new count at once.

A due chip whose label is markup, with no changeKey, fades its words in when its priority changes; it faded again on every render, since markup is a new object each time.

A collapsible's trigger takes motion: false turns its chevron at once, where only the panel's motion could be turned off. The audio control passes its own motion to the trigger of its details.

Under reduced motion a setting's Saved mark fades out after its hold, as the motion foundation keeps fades; it stayed on the screen until the setting changed again.

Under reduced motion the copy button's label fades to its result, as the motion foundation keeps fades and drops only movement; it changed at once.

With motion={false} the copy button's label changes to Copied or Could not copy at once; it went on fading over the fast duration.

The command palette takes motion, as every other dialog does: on by default, and false opens and closes it at once.

An event timeline's motion prop takes a preset or enter and exit motions, as every display component's does; it read only false, so a new entry faded whatever it was given.

With motion={false} a skeleton stands still: its fades and its shimmer are both off, where the shimmer went on looping.

With motion={false} the startup modal's progress bar takes each phase's width at once; it went on growing over the slow duration.

With motion={false} the create button's plus becomes a cross at once when the grid opens, as its doc says, where it still turned over the medium duration.

The app shell reads its em as each drag starts, so after the size class changes to helm with the page open, a splitter's edge stays under the pointer instead of running 12.5% ahead of it.

The status strip's sensor list sizes its name column to the longest name, shared by every row, so a name like echosounder no longer runs under its detail and every detail starts at one edge.

On a screen up to 68.75em the strip's chips and buttons, the Night suggestion's dismiss among them, are the touch size whatever pointer the device reports, where they grew only under a coarse pointer or at helm.

The N, S, E and W buttons take the field's icon-button size, the touch size on a phone or under a finger, whichever stylesheet a page loads first, where a page that rendered another field first drew them 36 px wide.

An AIS target's vessel name, a saved crew member's name in the crew picker and a file's name in the file list break over lines in a narrow column instead of ending in an ellipsis, since nothing else on the row shows them.

In a narrow pill the label goes onto more lines, whole, beside a value that stays on one line, where it was cut with an ellipsis into "DEP…" and the screen no longer said what the value measured.

A long network name breaks over lines on a narrow screen instead of ending in an ellipsis, so two names that differ only at the end, such as one per pontoon, read apart.

A model id such as a provider's full model path breaks onto more lines inside the panel's by-model list instead of running past the panel on a narrow window.

When the browser refuses a copy, the field that holds the text for copying by hand is never wider than its line, so a long link does not scroll a phone sideways, and on a phone, a tablet or under a finger it is the touch size tall.

Options that do not fit their column go onto another line, so four long options on a 320 px phone stay on the screen instead of scrolling it sideways.

Each digit's box is 2.5em where there is room and narrower where there is not, so an eight-digit code, or a six-digit one at helm, fits a 320 px phone instead of scrolling the page sideways.

The select's trigger takes its height as a minimum, so a long value that wraps in a narrow column or at helm stays inside its frame instead of spilling over its border.

Under a coarse pointer each hour and minute in the time picker's lists is the touch size tall, and every option takes a minimum height rather than a fixed one, so text enlarged to twice its size is not cut.

On a phone, a tablet or with a coarse pointer, the round target that opens an unlabelled line's detail is the touch size, where it was the 32 px visual size on every screen.

On a phone, a tablet or under a finger a crumb is at least the touch size wide as well as tall, its label centered, so Log or Fleet is not a 25 px target.

Opened inside a dialog, the language picker's menu stacks above it and takes the press, as the other menus do.

The alert zone's ACK, the LLM status chips and the status strip's chips take the helm touch size inside any helm scope, as every other component does, where they took it only when helm was set on the whole page.

Weather bar set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 12px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Trend chart set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its empty text 10px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Tooltip set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 11px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Telemetry strip set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 11px → the caption role (12 px, 14 px at helm); its label 9px → 0.8em of its line, so it keeps its size beside the text it sits in. The owner chose to snap each size to the nearest role (2026-10-24).

Status strip set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 11px → the caption role (12 px, 14 px at helm); its auto 11px → the caption role (12 px, 14 px at helm); its brilliance 10px → 0.9em of its line, so it keeps its size beside the text it sits in; its tz 9px → 0.8em of its line, so it keeps its size beside the text it sits in; its sensor row 11px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Startup modal set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its title clamp(34px, 6vw, 72px) → the twice the page heading role (56 px, 64 px at helm); its label clamp(10px, 1.2vw, 12px) → the caption role (12 px, 14 px at helm); its close 30px → the page heading role (28 px, 32 px at helm); its steps clamp(12px, 1.5vw, 15px) → the body role (14 px, 18 px at helm); its step marker 11px → the caption role (12 px, 14 px at helm); its status clamp(12px, 1.6vw, 16px) → the body role (14 px, 18 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Setting control set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its label 14px → the body role (14 px, 18 px at helm); its description 11px → the caption role (12 px, 14 px at helm); its pill label 12px → the caption role (12 px, 14 px at helm); its unit 11px → the caption role (12 px, 14 px at helm); its unit 14px → the body role (14 px, 18 px at helm); its saved 14px → the body role (14 px, 18 px at helm); its status 12px → the caption role (12 px, 14 px at helm); its chip 10px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Setting chips set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its entry 11px → the caption role (12 px, 14 px at helm); its chips input 11px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Section divider set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its label 10px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Reading set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its trend 11px → the caption role (12 px, 14 px at helm); its age 10px → the caption role (12 px, 14 px at helm); its reason 10px → the caption role (12 px, 14 px at helm); its last seen 10px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Page header set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its eyebrow 11px → the caption role (12 px, 14 px at helm); its title clamp(22px, 3.5cqi, 32px) → the page heading role (28 px, 32 px at helm); its subtitle clamp(14px, 1.8cqi, 18px) → the reading body role (16 px, 20 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Instrument pill set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 12px → the caption role (12 px, 14 px at helm); its trend 10px → 0.85em of its line, so it keeps its size beside the text it sits in. The owner chose to snap each size to the nearest role (2026-10-24).

Entity list set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its empty title 16px → the component heading role (16 px, 20 px at helm); its empty subtitle 12px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Due chip set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 10px → the caption role (12 px, 14 px at helm); its shape 9px → 0.9em of its line, so it keeps its size beside the text it sits in. The owner chose to snap each size to the nearest role (2026-10-24).

Data table set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its th 10px → the caption role (12 px, 14 px at helm); its cell 13px → the body role (14 px, 18 px at helm); its sort order 9px → 0.8em of its line, so it keeps its size beside the text it sits in; its empty cell 13px → the body role (14 px, 18 px at helm); its range 11px → the caption role (12 px, 14 px at helm); its hit 13px → the body role (14 px, 18 px at helm); its columns toggle 11px → the caption role (12 px, 14 px at helm); its columns item 13px → the body role (14 px, 18 px at helm); its filter control 13px → the body role (14 px, 18 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Collapsible set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 11px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

Chat input set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its field 14px → the body role (14 px, 18 px at helm); its field 13px → 1em of its line, so it keeps its size beside the text it sits in. The owner chose to snap each size to the nearest role (2026-10-24).

Alert zone set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its active 11px → the caption role (12 px, 14 px at helm); its shape 9px → 0.8em of its line, so it keeps its size beside the text it sits in; its ack 10px → 0.9em of its line, so it keeps its size beside the text it sits in. The owner chose to snap each size to the nearest role (2026-10-24).

Alert card set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its head 9px → 0.75em of its line, so it keeps its size beside the text it sits in; its icon 12px → the caption role (12 px, 14 px at helm); its name clamp(15px, 2vw, 18px) → the component heading role (16 px, 20 px at helm); its time 11px → the caption role (12 px, 14 px at helm); its msg clamp(13px, 1.5vw, 15px) → the body role (14 px, 18 px at helm); its delivery 10px → the caption role (12 px, 14 px at helm); its advisory toggle 11px → the caption role (12 px, 14 px at helm); its step 13px → the body role (14 px, 18 px at helm); its step num 11px → the caption role (12 px, 14 px at helm); its stat value clamp(16px, 2vw, 22px) → the section heading role (20 px, 24 px at helm); its stat label 8px → the caption role (12 px, 14 px at helm); a coarse-pointer 12px on its advisory toggle, removed: a coarse pointer changes a target's size, never its text. The owner chose to snap each size to the nearest role (2026-10-24).

Badge set its text in px, which stays the same size at the helm size class while the type roles around it grow (the typography foundation: a font size in pixels ignores the size class). Its sizes now come from the roles: its text 10px → the caption role (12 px, 14 px at helm). The owner chose to snap each size to the nearest role (2026-10-24).

The craft floor's type check names IBM Plex Mono for readings, units, codes and the small capital labels beside a value, and Plex Sans for prose and control labels, as the typography foundation and the label role set them.

The rules a screen follows were spread over the foundation pages, the maritime pages and the kit's notes, with nothing saying which one holds when two disagree or what every change is checked against before it ships. The page names the order (the bridge-display rules, then the foundations, then the kit's conventions, then design judgment), the three modes and the surfaces each covers, the checks of the craft floor, and the habits the kit refuses, with the kit's own forms where a common rule would conflict: the page header's eyebrow, the alert card's priority edge, Plex Mono for readings, real series in charts. It is adapted from impeccable's design guidance (Apache-2.0), which the designing-interfaces skill carries for agents.

On a phone, a tablet or under a finger, the compact info button keeps its small look and takes a press 48 px wide across its own line, and no taller than the line, so a press between two lines of a dense column never opens the other line's explanation.

Every transition and animation in the kit takes its duration and its curve from the motion tokens; hover, press, focus and selection feedback may change color, background, border and shadow over the fast duration on the standard curve, as the motion page now says, and the saved chip fades over the slow duration after its hold.

Folding the navigation to its rail or shutting the side panel changes the shell's columns at once; it moved them over 200 ms, which laid the whole app out again on every frame.

A red badge marked unacknowledged flashes its dot until the alarm is acknowledged even with motion={false} or a preset, as the alert card and the alert zone do; motion chooses only how the badge enters, leaves and changes, and no other badge flashes whatever it asks.

While an alarm is unacknowledged the faint cause icon behind the card is lighter in the shared clock's on phase and fainter in its off phase, with the frame's ring; it ran its own two-second swell, which drifted against the 800 ms alarm flash.

The data table's sort buttons, checkboxes, column choices and filters, the duration presets, the event timeline's filters and the Wi-Fi network rows take --target-touch-size, so they grow to 54 px at helm with every other target.

--target-touch-size is 54 px at helm, 18/16 of the default 48 px, as the text is, so every control that takes the touch size grows with the label it carries.

Under prefers-reduced-motion dialogs, popovers, menus, select lists, collapsible panels and toasts fade in and out as the motion page says, and nothing moves; the token reset had turned every animation and transition off, so they appeared and vanished at once.

Under prefers-reduced-motion a tooltip only fades in and out, over the same durations, so it still shows that it arrived; it moves nothing, where it appeared and disappeared at once.

An AIS target's name and its ▲ Dangerous word are drawn at the caption role's size on the screen however wide the chart is, where a phone's narrow chart shrank them with the drawing to about 5 px.

Inline takes wrap, which lets its children go onto more lines where the row is too narrow; the chart range's five large buttons use it, so on a phone every one stays on the screen instead of off its edge or clipped by the chart panel.

A degraded reading's reason and an invalid reading's last-seen line wrap inside the reading even in a row that keeps its items on one line, as the situation line does, so a caption never runs over the reading beside it or off the screen.

On a phone, a tablet or under a finger, a lane is tall enough that each entry, and each of the entries that share hours, is 48 px tall, and a movable entry's edges take a press 24 px wide.

The round close button on the startup screen is 48 px, the touch target, where it was 44 px on every screen.

Under a finger the status strip's Auto (follow device) in the brightness menu is 48 px tall, as the strip's chips are.

The unit button keeps its small chip and takes a press anywhere in a 48 px square around its middle, so changing kn to m/s on a phone is a full touch target.

On a phone, a tablet or under a finger, the alert's name, which opens the situation board, is one line as tall as the 48 px target beside ACK.

On a phone, a tablet or under a finger, a row that opens a record is at least 48 px tall, as a selectable row is, and the Columns toggle is the touch size.

The pencil, Save and Cancel stand far enough from the title, the field and each other that each 48 px press area ends where its neighbor's begins, so a press at Save's edge saves and a press at the end of the field places the caret.

Under a coarse pointer the calendar's days are 48 px tall and the panel widens to seven 48 px columns where the window has room, as on a 375 px phone; a 320 px phone takes the widest days its window allows.

On a touch screen the calendar's previous and next month buttons are 48 px targets, as the field's own buttons are; they had shrunk to their 20 px arrows.

A toast is inert from the moment it starts leaving, so an Undo pressed during its exit cannot run after its close has made a deletion final.

The trend chart page and the maxGap description name a point's value and time, the fields TrendPoint has, where they still said v and t.

TrendChart and a chart series take maxGap, and ChartRange takes minSpan, in the short form the kit's other limits take (maxBytes, maxAddresses, minQueryLength).

Skeleton takes testId, which becomes data-testid on the placeholder, as every kit component's does; a skeleton without one carries no test id.

EntityList, SchemaEntityList and SchemaForm take the crew's own currency and the day's rates as moneySources, the name of the MoneySources type it holds, so the prop is not read as an amount of money.

Chips takes items, the ChipEntry list it draws, so the prop is not read as the values a setting field edits, which SettingChips takes as values.

Heading exports HeadingLevel (h1 to h6) and NestedHeadingLevel (h2 to h6), and the card, section heading, chart panel, audio control, empty state, event timeline, navigation list and ship data take their headingLevel or level as NestedHeadingLevel; their props tables name the one type.

The alert card's values beside its actions are figures, each an AlertFigure, and the audio control's capture measurements are captureFigures (CaptureFigures): the props name what they hold, a figure with its label, in the words the pages already use for them.

Types named for their component's parts left the component out (Tab, SectionVariant, TimelineEvent, FileItem, UploadResult, OtherChange, InputLevelScale) or read backwards (IpVersionAccepted, HourMeterText for a parse result); they are TabsOption, SectionDividerVariant, EventTimelineEvent and its kin, FileInputItem, FileUploadResult, InlineEditIncoming, AudioInputLevelScale, AcceptedIpVersion and TypedHourMeter.

The line above the title was label, the name every other kit component gives its accessible name; it is eyebrow, as the report blocks call it.

The reading detail took its age as written text under the name age, where a reading's age is ageSeconds, a number, and its integrity reason as integrityReason, where a reading's is reason; they are ageText and reason.

The tide curve took its dark hours as night, a list of spans, where the situation line's night is a flag; the curve's prop is nightSpans.

The flag that lays the sea under the waterline was water, a noun for a switch; it is showWater, off by default as before.

The flag for the popover's close button was closeButton, which named the part rather than whether it shows; it is showCloseButton, on by default, as the kit's other optional parts are show…

The mark on the most recent value was showDot, though on a bar plot it draws the latest bar at full strength rather than a dot; it is showLatest, beside showLow and showHigh.

A sample, an extreme and a point on the curve gave their moment as t; they give it as time, beside heightM.

A point was { t, v }, the marker markerT and the tick count yTicks; a point is { time, value }, and the props are markerTime and yTickCount.

The do-not-disturb state was dnd, an abbreviation, of type StatusStripDnd, and the Night Watch suggestion was suggestNight, a verb for a flag; they are doNotDisturb (StatusStripDoNotDisturb) and nightSuggested.

The number of characters typed before a suggestion request was minChars, an abbreviation; it is minQueryLength on the async combobox and autocomplete.

When the longest-waiting alert first fired was an ISO time where an alert's raisedAt and a status strip's lastEventAt are epoch milliseconds; oldestUnacknowledgedAt is epoch milliseconds too, and the wait reads the same.

A fixed now, for examples and tests, was a number in the countdown, event timeline, tide curve and schedule, an ISO string in the date and time input and the hour meter input, an HH:MM string in the time picker and a Date in the schema form's default sources; all take epoch milliseconds, and the time picker reads it on its zone's clock.

The nautical chart's symbols were in a chart-symbols folder and page, among the analytical chart family's chart-legend, chart-tooltip and chart-panel; the entry and the page are nautical-chart-symbols, beside the chart they draw on.

The grid lays out alert cards and section dividers and gives them the list motion only they read, so its name and its page say so: CardGrid is AlertCardGrid at @bosunkit/components/alert-card-grid, drawn in .alert-card-grid, on the Alert card grid page, first in Layout.

The zone's alert took firstFiredAt, an ISO time, where an alert list item takes raisedAt in epoch milliseconds; the zone takes raisedAt in epoch milliseconds too, and its age reads the same.

The logo's hideTagline and hideVersion and the pill group's labelHidden were on to hide a part, where the kit's flags for an optional part are show… (showValue, showGrid); they are showTagline, showVersion and showLabel, on by default, and false hides the part as before.

The kit wrote most abbreviations as words (AisTargetRow, IpAddressInput, QrCode, YamlEditor) and a few in capitals (MMSIInput, VHFChannelInput, NMEAOfflineNotice, staticSVG); those are MmsiInput, VhfChannelInput, NmeaOfflineNotice and staticSvg, with their types and helpers (formatMmsi, isValidMmsi, readVhfChannel). Page titles and text keep MMSI, VHF and NMEA in capitals.

The board took neither the testId every kit component puts on its root nor a ref; it takes both, on the grid element.

The three named themselves with ariaLabel where every other chart and component takes label; they take label, and the accessible name they build from it is unchanged.

The command palette and search suggestions called back through onChoose, the nav list's account menu through onAction, and the action menu and command palette closed on closeOnChoose, where the action menu, context menu, create button and crew picker report through onSelect; all of them say onSelect and closeOnSelect.

Ten pages linked a Modal page that no longer exists, and pages called the command palette, navigation bar, radio cards and segmented radio group Command menu, Tab bar, Choice cards and Segmented control; the links go to the task dialog and the pages use the components' names.

The slot that holds a NavigationBar along the foot of a phone screen was tabBar, the component's old name, with data-tab-bar and shell__tab-bar beside it; it is navigationBar, with data-navigation-bar and shell__navigation-bar.

The context menu's entry types were ContextMenuItemEntry, SeparatorEntry, SubmenuEntry and GroupEntry where the action menu's are ActionMenuCommand, Separator, Submenu and Group; the context menu's are ContextMenuCommand, ContextMenuSeparator, ContextMenuSubmenu and ContextMenuGroup.

The pill's status mixed alert levels (warn, critical) with data integrity (stale) under one name, in words of its own, and its trend said up, down and stable where a reading says rising, falling and steady; it takes priority (warning or alarm), stale, and a ReadingTrend, and draws its state from data attributes.

What pressing a suggestion does, fill or send, was suggestionAction, a name the kit keeps for a prop that takes an Action the component waits on; it is suggestionBehavior, of type ChatSuggestionBehavior.

The vessel's language, marked "Vessel default" in the list, was defaultLanguage beside defaultValue, the language an uncontrolled picker starts on; it is vesselLanguage.

The deprecated instrumentRange alias of maxDepth is gone, and the examples that used it pass maxDepth; the page names the scale's default as the range ladder's first rung, 25 meters, where it said 10.

Calling Select directly was a deprecated adapter that turned a cleared choice into an empty string, and every select example used it; the adapter is gone, the examples and the chat input's model picker use Select.Root, and their handlers take the null Base UI reports for no choice.

The panes parts took the resizable-panels library's props types with no kit name, and Panel shared its name with the popover's internal panel; each part's props are exported as PanesGroupProps through PanesGridlineProps, and the popover's internal panel is PopoverPanel.

The summary line's sea state, text the caller formats, was seaState beside sea, the sea state object the detail draws; the text is seaStateText.

The schema form exported its field's shape as FormField, the name of the form field component a page wraps an input in; the type is SchemaField.

The QR code's network name and passphrase were a WifiNetwork, the name the Wi-Fi network list gives a scanned network with its signal and security; the QR code's type is WifiCredentials.

The number of alerts waiting for an acknowledgement was unacknowledged, the name a badge gives the boolean that starts its alarm flash; it is unacknowledgedCount.

The radio group, checkbox, checkbox group, slider, scale picker and radio cards took the line under a field as description, where the outlined inputs and the YAML editor take it as hint and the schema form had to translate one into the other; they take hint. An option's own detail line keeps its name.

Pagination took page, defaultPage and onPageChange where the kit's controlled state is value, defaultValue and onValueChange, as steps, tabs and every input take it; it takes those.

The prop that draws an alert-colored edge was tone, with values of its own ("neutral" where the kit's priorities say "none"); it is priority, of the kit's Priority type, and the tooltip's state attribute is data-priority.

The pending prop's description said the button waits until "the Action resolves", but onNext returns nothing and the caller sets pending; the description says the caller sets and clears it around its own work.

The form waits on what its save callback returns and shows a rejection, as an Action, but the callback was named onSubmit like an event handler; it is submitAction, as the kit names a prop that takes an Action (saveAction, acknowledgeAction).

A sensor's seconds since its last reading was age, where a reading, the ship data trust panel and a situation reading call the same thing ageSeconds; the sensor summary takes ageSeconds too.

The limit was maxSize, in bytes by its doc comment only; it is maxBytes, so a caller cannot read it as megabytes.

A length of time in milliseconds named its unit only in its doc comment, beside props that name theirs (ageSeconds, vectorMinutes); the props are resultDurationMs, peakHoldMs, cautionWithinMs, warningWithinMs and relativeWithinMs, and an audio capture's chunkMilliseconds is chunkMs, as its latencyMs neighbor writes it.

The date picker's DateZone, the date and time input's DateTimeZone and the time picker's inline union were three names for "utc" or "local"; all three take ClockZone, and LLM status takes zone="local" where it took utc={false}.

The flag was the kit's only one named with…; it is showExtension, as the kit names an optional part it draws (showValue, showGrid).

A picked-up piece was put back only by pressing its square again; Escape now puts it back too, and with no piece picked up it closes a dialog around the board.

A tide curve moved along with the arrow keys had no way back to the present but to step there; Escape now returns its readout to now, as a sparkline's Escape clears its point, and at now it closes a dialog around the curve.

The first Escape asks to leave the editor so that Tab stops indenting; read-only or saving, Tab already leaves it, and that Escape now closes a dialog around it at once.

The Escape that drops an Alt-and-arrow move also closed a dialog around the schedule, where the Escape that drops a new slot did not; both now stop at the schedule, and the next Escape closes the dialog.

N and / are the list's page shortcuts, and they also acted for a key pressed in an unrelated dialog over the page, opening a new record behind it; a key from a dialog the list is not in is now the dialog's.

While an input method composed text, its Escape closed the suggestion list and its Enter could choose a suggestion; both fields now leave those keys to the composition.

The field kept every Escape to itself, even with its suggestions closed and nothing typed, so a dialog around it could not be closed from it; the Escape that closes the suggestions stops there, the next one closes the dialog, and neither clears the query.

Escape on an interactive sparkline cleared the point being read and, on the same press, closed the dialog around it; it now stops at the readout, and a second Escape, with no point read, closes the dialog.

The checkbox cell stopped every key so its Space and Enter would not also press the row, Escape included, so a dialog could not be closed from a row's checkbox; the cell now keeps only Space and Enter.

A setting row changing a saved secret showed Save and Cancel but ignored Escape, which closed the dialog around it with the change form still open; Escape now cancels the change as Cancel does, puts the focus back on Change password, and leaves the dialog open.

A setting saves itself when the crew leave it, and Escape left the edit in place, so the next Tab wrote it to the vessel; Escape now puts the saved value back in a setting field or row and drops an entry not yet added to setting chips, and with nothing to take back it closes the dialog around them.

Escape, Cancel or the close button on the "Change N entries" dialog dropped the choices made in it without a word; it now asks "Close without saving?" as the create and edit dialogs do, and keeps the choices on Keep editing.

A schema form's long choice list erased the crew's typed search when Escape closed its list, as the async combobox did until the fix of 23 October; every combobox now keeps it, and one holding a choice shows that choice again.

With its list closed, an Escape emptied the field and its choice, and in a form with nothing chosen went on to close the dialog in the same press; it now leaves the text and the choice, and closes the dialog, and one that cancels an input method's composition does nothing else.

The marina office's number in the extension example was one no United Kingdom range has, so the example doubted it once the field was left; it is now a London number from Ofcom's range for drama, which the field names as a landline.

The line doubting a number hid whenever the number took focus and came back when it lost it, so the field grew and shrank by a line each time the crew tabbed through it or moved to the extension; it now hides only while the crew change the number, and shows again when they leave it.

A text field marked with the tel-extension autofill token, in the group of a phone field, is now drawn as that phone input's extension and saved in its own field, so a marina office's number and extension are entered, pasted and filled together.

A number with more digits than E.164 allows showed its error but was reported and submitted as it stood, a number bosund refuses; the field now reports none until the number fits, as the other inputs do for text they do not take.

Escape with the suggestions open closed them and also emptied the field, so the crew lost the query they were typing; the first Escape now closes the list only, and a second, with the list closed, clears the field, as the WAI-ARIA combobox pattern has it.

On the night the clocks go forward, 02:30 on the device's clock does not exist, and the field reported 03:30 while it still showed 02:30; it now reports nothing and says the time does not exist on that date, so the crew enter one before or after the change.

"2026-10-23T23:30:00-05:00" pasted into a UTC date picker gave 23 October, though that moment is 24 October in UTC; the date and range pickers now read an instant with its offset on their own clock, and a date of birth keeps the date as written.

The three popups said they were modal (aria-modal="true") while Tab walked out of them: after the last button focus landed on the page body, then on the page behind, with the calendar still open. They now trap the focus, as the date picker dialog pattern does, and each has a Close button at the end of its last row, a way out for a touch screen reader, which has no Escape key. While a popup is open the page behind it is out of the accessibility tree, as a modal dialog's page is.

The pad took ink from a pointer only, and the schema form offered nothing beside it, so a required signature blocked a crew member signing on the keyboard alone, with a switch or a screen reader. The box's keyboard button, "Type the name instead", puts an input for the name in the pad's place; the value is the name as SVG text marked data-signature="typed", so whoever reads the record tells a typed signature from a drawn one. The pen button draws again, a signature is one or the other, and a required one left empty asks for the name.

A secret copied with a space before or after it, as a key selected from a web page often is, was saved with the space, hidden behind the dots, and failed; a secret is now pasted trimmed, and a password of any other purpose keeps its spaces.

A minus before an amount was always refused, so a refund or a correction could not be entered; with allowNegative, which a schema form sets for a field whose least value is below zero, "-12,50" is −12.50, and every other money field refuses a minus as before.

"€ 1.250,00", "1.250,00 €" and "EUR 12.50" copied from a receipt or an invoice were refused in a euro field; the field's own currency, by its code or its symbol, is now read at either end of the amount, and another currency's is still refused.

"12.5 kn" pasted into a knots field was refused for its unit; a value followed by the unit the field shows is now read as its figure, and one in another unit is still refused rather than converted.

Text the field could not read, or an amount with more decimals than its currency has, typed over a held €151,20 showed the problem but left €151,20 reported; the field now reports no amount until its text is one it takes.

Minutes past 59 or text the field could not read, typed over a held reading, showed the error but left the held reading reported; the field now reports no reading until its text is one it takes.

Text the field could not read, or a value outside its bounds, typed over a held quantity showed the error but left the held quantity reported; the field now reports no value until its text is one it takes.

A bearing past 359, text it could not read or one from the other north typed over a held 090 showed the error but left 090 reported; the field now reports no bearing until its text is one it takes, as the date, time and duration fields do.

"045º", written with the ordinal mark those keyboards give the degree key, was refused, though the position field reads it; it now reads as 045°.

"VHF 16", "Ch. 72.", "Ch:16", "CH-16" and "channel 16 (156.800)" were refused as no marine channel; the field now reads the VHF word, a mark after Ch, a closing full stop and a frequency in brackets.

Every paste into a list of addresses was set apart with spaces, so pasting 1.1 after a typed 192.168. gave "192.168. 1.1" and refused both; one piece pasted after part of an address now joins it, and a list, or an address after a whole one, is still set apart.

Pasting "900 123" after a typed 07700 read the paste as a whole number and replaced the 7700; digits alone pasted into a number being typed now go in at the caret, as typed digits do.

Every paste had to hold a whole MMSI, so pasting 456 after a typed 244 123, or over a selected group, changed nothing; a few digits alone now go in at the caret or over the selection, as typed digits do, while the whole stays within nine.

An MMSI copied from a French or Swiss document, its groups split by a narrow no-break space or a thin space, was refused; those spaces now group digits as a space does.

The browser's length limit cut a paste at the field's limit without a word, so "Engine oil changed at 1234 h, filter too" was saved as "Engine oil changed a"; the text now stays whole, the count goes past the limit and the field says how long it may be.

A position copied from a word processor or a web page, with U+2212 for its minus ("39.4690, −0.3763") or opening quotes for its minutes and seconds (39°28‘08“N), was refused; those marks are now read as the minus and the minute and second marks.

Text the field could not read, pasted with Ctrl+V or a long press, left every segment empty with no word, where the paste button says why; the status line now names what the clipboard held, as the paste button does.

Typing 4 between the digits of 39° gave 34° and moved on to the minutes, and a 0 inside 12.345′ gave 10.345′ with the caret at the end; a full field now takes no digit typed inside it, keeps its own and the caret, and moves on only while the crew type at its end.

A time copied from the log with its clock after it ("14:05 UTC", "14:05Z") or as an ISO instant was refused as unreadable; the field now reads its own clock's marks and turns an instant with an offset into its clock's time, and a time marked on the other clock is refused with a line that says which clock the field takes.

The arrows choose a star as they move to it, and Space on it then cleared the rating, since the browser sends Space as a click and a click on the chosen star clears it; only a press with the pointer clears it now, and the keyboard clears with 0, Backspace or Delete.

Two numbers with a colon were always hours and minutes, so "1:30" typed into a timer or an alarm delay held in seconds was 90 minutes; in a seconds field they are now minutes and seconds, as a timer shows them, and 90 seconds.

Text the field could not read, or a duration past its limits, typed over a held 4 hr showed the error but left 4 hr reported; the field now reports no duration until its text is one it takes, as the date and time pickers do.

With 1 hr held, typing "5 h" and pressing ArrowUp gave 1 hr 5 min, stepping from the held value and throwing the typing away; the arrows now step from a typed duration that reads as one, so it gives 5 hr 5 min.

Home and End were taken as the spinbutton's jumps to the limits even with no limits set, and the arrows with no step, so the caret could not reach the start or end of the text; each key now goes to the text when the field has nothing for it to move to.

With a long saved crew, the arrows moved the active row below the panel's edge without scrolling it, so the crew member Enter would choose could not be seen; the panel now scrolls to keep the row in view.

The arrows moved the active country past the bottom of the list without scrolling it, so after a few presses the country Enter would choose could not be seen; the list now scrolls to keep it in view.

Shift+Tab never left the editor: the Shift press undid the Escape before it, and on a line with nothing to outdent the key was swallowed; Escape then Shift+Tab now moves focus back, Shift+Tab does on an unindented line, and a line under the editor says "To leave the editor, press Escape, then Tab."

Enter saved with Shift held too, so an inline edit whose field is a text area could not hold a second line; Shift+Enter is now left to the field.

After Enter or Escape the focus went to the page itself, so a keyboard user had to Tab from the top again; it now returns to the pencil, as the inline edit pattern says it does.

The Enter that commits a word in a Japanese, Chinese or Korean keyboard added the unfinished word to a list field as a chip; keys the input method is composing with are now left to it.

The Enter that commits a word in a Japanese, Chinese or Korean keyboard inserted a new line and its indentation in the middle of the composition; keys the input method is composing with are now left to it.

The Enter that commits a word in a Japanese, Chinese or Korean keyboard, or a phone's accented-letter picker, saved the rename with the word unfinished; keys the input method is composing with are now left to it.

With a Japanese, Chinese or Korean keyboard, or a phone's accented-letter picker, the Enter that commits a word sent the message with the word unfinished, and an arrow among the candidates stepped through the history; keys the input method is composing with are now left to it.

Clearing the date of a held instant showed "Enter the date too." but left the instant reported, so a form saved a time nobody could see; the field now reports nothing until both parts make an instant within its bounds.

Text the field could not read, or a time outside its bounds, typed or pasted over a held 08:00 showed the error but left 08:00 reported; the field now reports no time until its text is one it takes.

A last day typed before the first, or a new first day chosen in the calendar and then left with Escape, kept the range held before reported while the field showed other days; leaving the field with days that are not a whole range it takes now reports no range.

Typing "35/10/2026" or a date past the latest over a held date showed the error but left the held date reported, so a form saved a date the field no longer showed; the field now reports no date until its text is one it takes.

A number that reaches a switchboard, such as a marina office, an agent or a yard, can have an extension, and the field had nowhere to put one: a pasted "ext 1" was dropped and a typed one joined the number's digits. withExtension adds an input for it after the number, marked with the crew's word for it (ext., Dw., poste, int., tst.), reported apart from the E.164 number through onExtensionChange and sent with a form under extensionName. A letter typed after the number moves the focus to it, and a paste of "07234 515226 ext 1", "x1", "Durchwahl 1" or a tel link's ;ext=1 fills both inputs. Without withExtension the field takes the number and its status line says the extension is not saved.

The field kept only the digits of what was typed, so "07234515226 ex 1" was saved as +4472345152261, a different number; letters now stop the reading, the number stays as it was, and the field says letters and what follows them are not saved.

The field took the first run of digits in pasted text, so "MMSI 244123456, phone +31 6 12345678" gave +44244123456 and "23/10/2026 call 07700 900123" +4423102026; it now skips dates, times and numbers labelled MMSI or IMO, prefers a number in international form, and keeps to one line.

With the caret before a group space, Delete removed the digit before the caret, as Backspace does, so "7700 900123" became "7709 00123"; it now removes the digit after the space, "7700 00123".

A paste of “mara@example.org” in typographic quotes, in guillemets or brackets, or at the end of "Write to mara@example.org!" kept those marks and was saved with them; the field now takes only the characters an address is written with.

Escape, the first step of leaving the editor with Escape then Tab, also closed the dialog the editor sat in, as when a schema form edits a record in one, losing the edit; the first Escape is now the editor's alone, and a second is the dialog's.

With the saved crew open, Escape closed the list and also the dialog the field sat in, losing the crew member being added; it now closes only the list, and the next Escape is the dialog's.

With the suggested addresses open, Escape closed them and also the dialog the field sat in, losing the edit; it now closes only the list, and the next Escape is the dialog's.

A carriage return inside a flow collection, as in a job definition saved with Windows line endings ("a: [b,\r\n c]"), sent the editor's scanner into a loop that froze the page; inside brackets it is now whitespace, as a newline is.

A field holding one file emptied itself before it checked the new one, so a refused paste, drop or pick removed a file already stored; the new file is now checked first, replaces the held one only when the field takes it, and is otherwise listed as refused beside it.

A pasted "05/04/2026" was read day first as 5 April, where the date picker refuses it because the day and the month could be either way round, and "23 Oct 2026" was refused; each end now reads a paste as the date picker does and says when a date's order is unclear.

"ETA set to 23 October 2026" was read as 23 September, since "set" starts the Italian settembre, and "14:05, 23 October 2026" as 14 October; a month's name now counts only with the day beside it and the year beside that, so both read as 23 October.

A lone separator before three digits counted as thousands even after 0 or after four digits, so "0,125" was read as €125 and "1234,567" as 1,234,567; thousands are grouped only after a first group of one to three digits other than 0, and the field otherwise says the currency's decimals.

In German "1.234" hours was read as 1,2 and in English "1,234" as 1.2, with no error unless a last reading made it look backwards; the field now refuses the mark its language does not write before decimals when exactly three digits follow it, and asks for the reading as the meter shows it.

In German "1.250" liters was read as 1.25 and rewritten "1,25" without a word, and in English "1,234" as 1.23; the field now refuses the mark its language does not write before decimals when exactly three digits follow it, where it may group thousands, and asks for the figures again.

A float field pasted "1,5" was shown and saved as 15; the form's number fields now read a paste as the number input does, so "1,5" is 1.5 and an ambiguous "1,234" leaves the field as it was.

The browser's number field dropped the characters it could not hold, so a pasted "4,2" became 42 and "1,234" or "12.5 kn" a number nobody pasted; a decimal comma is now read as the point, and a paste with grouping, a unit or a separator before exactly three digits leaves the field as it was.

A true-north field took "045° M" as 045° T, dropping the variation without a word; it now refuses a bearing whose T or M names the other north and says to correct it for variation, in both a true and a magnetic field.

The field held its hidden caret after the last digit, so a wrong third digit could only be fixed by deleting the three after it, and Shift+Tab left the field where some expected it to step back a box. Left and Right now move the marked box, Home and End go to the first box and to the one after the last digit, and a tap on a box moves to it; a digit typed on a filled box takes its place and moves on to the next. Tab and Shift+Tab leave the field and come back in one press, as they do from every other field.

With 12 typed, pasting "482 913" from the message added the code after them and cut it at six digits, as 124829; a paste that holds the whole code now takes the place of what was typed, so the field holds 482913.

An SMS code is usually six digits and usually drawn as six boxes, and the field drew one long input. With length={6} it draws six boxes over its one input: each box shows a digit, the box the next digit goes in is marked with a caret and carries the focus ring, and the field takes no more than six digits. A paste of "482 913", the phone's offer from the message and a password manager's fill still go into the one input, which is also what a screen reader reads; an input per box would break all of them. Without length the field takes a code of any length, and in the outlined appearance length only caps the digits.

A draft or an air draft typed as 33 ft was saved as 10.06 m and then written back rounded up a second time, as 33.01 ft, a figure that would itself save as 10.07 m; the field now keeps the figure typed when it reads back as the value saved, and writes a saved value as the nearest figure that does, so 10.06 m reads 33.00 ft.

A separator reached with the keyboard only turned its 2 px line accent, which is also how it looks under the pointer; it now draws the focus ring around its whole touch target, as every focused control does.

The gap between a particular's label and its value was 0.15em, off the spacing scale; it is now the scale's smallest step, --space-xs.

The check moved each source's reading and verdict under its name on a screen up to 30em, a width the kit's breakpoints do not have; it now does so on a phone, up to 40em, where the other components take their phone forms.

The line that says an acknowledgement failed was written at 11 px whatever the size class; it is now 0.6875em, the same 11 px at the default size and larger at the helm.

A duration wrote its amounts with the language's thousands separator, "1,000 hr" or "1.000 Std.", and the duration field reads its own text back when the crew edit it, so adding "30 min" to a 1,000-hour service interval saved 1 hour 30 minutes; amounts are now written ungrouped, "1000 hr", as the formatting rules ask, and read back as written in all six languages.

The file input rounded a size to a thousandth of its unit before flooring it to a tenth, so a limit of 10 MB less one byte read "10 MB" and a file of 630.59997 MB read "630.6 MB", more than it is; it now floors the tenths directly and they read "9.9 MB" and "630.5 MB".

The tide curve and the situation line rounded a depth or a height to the millimeter before flooring it, so a value less than half a millimeter under a tenth read as that tenth, 2.9996 m as 3.0 m, more water than there is; they now floor the value itself, as bosund's DepthNum does, and 2.9996 m reads 2.9 m.

The list loaded its schema and option lists once, so a caller that translates their text as it arrives, as ui/web does, kept showing the old language after the crew switched; the list now asks again in the new language, keeping the open record and what was typed.

A reload that failed, such as the one after a field saved on its own, replaced the whole list and the record being edited with one error line; the list now keeps the records it had and says why above them, and shows the error alone only when it has no records and no record open.

The card's, the zone's and the list row's buttons stopped waiting when bosund answered, before the board showed the acknowledgement, so a quick second press sent it again or, in the zone, acknowledged the alert that took its place; they now wait for the board, for at most 10 seconds after bosund's answer, and then say the board has not shown it and offer the button again.

A refused or unanswered acknowledgement used to bring the button back with no word of why the alert was still there; the card now says "Couldn’t acknowledge this alert. It is still unacknowledged; try again." under its buttons, as the alert list row does, and the zone says so in its live region.

ui/web's Situation and Conning pages have no way to acknowledge every alert at once any more, so the page's Open callout keeps only the alert rate and the reason for overwhelmed.

Reset set brightness back to 50% and also switched the theme to the device's choice, so at night it left Night for whatever the device gave; it now resets the brightness alone and is named "Reset brightness", through the brilliance menu's new resetPalette prop.

detail draws what the page has about the open record above its form, such as a crew member's documents, which the list's own schema does not hold; a record being created shows none.

Where the zone was narrow, as on a phone or a wide window's crowded header, the age broke between its number and its unit, so "3 min" read as a 3 above a word; the number and its unit now stay together.

The quantity, bearing, VHF channel and hour meter inputs kept a 12em minimum width even in a column narrower than that, so four of them in a row of a schema form, such as a vessel's LOA, beam, draft and mast height, ran over each other and covered each other's units; each now shrinks to its column.

A bearing's north and sense, a quantity's rounding, a VHF channel's purpose, an hour meter and an observation scale come from bosund's reference, sense, rounding, purpose, component and scale tags, not from field names, so a log entry's sea state is the Douglas scale picker, a current's set reads "Towards east" and a draft typed in feet rounds up.

An engine's hours in a log entry, an engine log or the fleet record were decimal number fields, so 1234:30 off a clock-faced meter was typed 1234.30; they are the hour meter input, which reads hours and minutes as well and saves the tenth, while a duration in hours stays a number.

Engine and generator hours (log/types.go:250, 467; fleet/types.go:554) were decimal number fields, so a meter that shows hours and minutes was typed 1234.30 for half past, and a reading below the last one or a slip of a digit was saved without a word. HourMeterInput reads decimal hours or hours and minutes, holds the tenth a meter shows, writes the hours run since the reading before it, and questions a reading that runs backwards or gains more hours than have passed, keeping it, since a new meter starts from zero.

The asterisk after a required group's name stood 0.2em from it, a length outside the spacing scale that the spacing foundation refuses; it stands the scale's smallest step from it.

Every position bosund's schemas hold, a log entry's, a distress position, a man overboard mark, a waypoint, was two decimal-degree number fields; a latitude field and the longitude in its group are one position input, in degrees and minutes with its hemispheres and the vessel's position a press away, saving decimal degrees in each field.

A contact's and a harbour office's VHF channel were free text, which took 70 or 99 as readily as 72; the field named vhf_channel is the VHF channel input, which writes the channel's frequencies, refuses a channel that carries no voice and saves the designator.

A number field in m, L or kts, a vessel's draft and air draft, a tank, a wind limit, was a number input with its unit after it, so a draft typed in feet was saved as meters; it is the quantity input, whose unit button takes feet, gallons, km/h or m/s and saves the value in the schema's unit, and a field in another unit, NM among them, stays a number.

A datetime field was the browser's datetime-local field, which showed no zone and on an English system a 12-hour clock, while the form read the typed time as UTC; it is the date and time input, read in UTC with UTC printed beside the time, saving the instant, and the field table lists the bearing input as well.

The line under the group appeared only once the time was taken, which happens as the crew leave the time field, so a press on Save straight after typing the time moved the button from under the pointer at mousedown and was lost; the line keeps its height, empty or not.

A number field in degrees bounded 0 to 360, as the log bounds its courses and wind direction, was a number input with ° after it; it is the bearing input, °M for a field named for its magnetic reference, so the crew can type a point of the compass and step round the circle, and a field in degrees with other bounds or none stays a number.

bosund's schemas hold lengths in meters, volumes in liters and speeds in knots (fleet/types.go:133-201, ops/types.go:711, 876, 943), and their fields were number inputs with the unit as text, so a US skipper who typed a draft of 6.5, meaning feet, saved 6.5 m. QuantityInput takes the value in feet, gallons, km/h or m/s through a unit button after it, holds it in the base unit by the exact factors, says under the field what a value in another unit is saved as, and rounds it the way rounding says: down for a depth, up for a draft. A value the field wrote is never read back through its rounding again, so switching units or leaving the field twice does not move it.

An instant, the time of a log entry, a departure or a flight home, could be entered only through the browser's datetime-local field, which shows no zone and on an English system a 12-hour clock, while the form read the typed time as UTC. DateTimeInput groups the date picker and the time picker under one name, reads both in one zone that it prints beside the time, UTC by default or the device's own with its offset, and reports the instant in UTC once both parts are set and within its bounds, which are instants: max at the current time keeps an entry from recording the future. The date picker gains writeDate, so a group that writes the date out with its time does not write it twice.

A contact's and a marina's VHF channel were free text of up to ten characters (ops/types.go:426, 972), which takes 70, a DSC-only channel, or 99, which does not exist, as readily as 72. VHFChannelInput reads a channel number, a four-digit simplex designator or its US letter form, and the UK marina channels, writes the designator and the channel's frequencies under it, says what the Radio Regulations set a channel aside for, refuses the channels that carry no voice and questions 16 as a working channel. The arrow keys step through the voice channels.

The log's sea state was a select of eight words and its cloud cover free text (log/types.go:192, 201), and a wind force was a bare number, so nothing showed what a level stands for or checked it against the instruments. ScalePicker draws a scale's levels as a radio group, each with its code, its name in the crew's language and, for wind and sea, the range it stands for, from the same bounds bosund uses to turn a measured wind or wave height into a level. Arrow keys and a code's digits choose a level. With measured, the level the measurement stands for is marked, and a choice more than one away from it is questioned in an attention message without being refused.

The log's wind, swell and current directions, a course and a bearing to a mark were number fields, which store 360 beside 000 for north, stop at 359 where the circle turns on to 000, write 045 as 45 and say nothing of which north. BearingInput reads degrees or a point of the compass, in the crew's language and in English, writes the bearing in three digits with °T or °M after it, steps round the circle with the arrow keys, writes the nearest point under the field in words (from or towards it with sense) and draws the bearing on a small rose, so a bearing with its digits swapped points visibly the wrong way.

A log export, a charter, a crew rotation and a yard period each take a range of days, which the kit could hold only as two date pickers that knew nothing of each other. DateRangePicker holds the first and the last day in one field, typed or chosen from the date picker's calendar in two presses, and reports the range only when it is whole and within its limits: min and max for the dates either end can fall on, and minDays and maxDays for the days it holds, both ends counted. The calendar disables every last day that would break a limit once the first is chosen, and a typed range that breaks one names the day that would fix it. The date picker's month grid moved into a module the two share, and draws a range.

Under a Reading, the age badge, the degraded reason and the last-seen line ended at the readout's outer edge, 2 to 8 px past the end of its source and rule. A caption wider than the readout widened the whole reading, so a heading that turned degraded moved its value sideways and pushed the readings beside it. The captions also sat 5 px higher than the age badge in the same row. The status line now ends where the rule ends, at every size and direction. A caption wraps inside the readout's column, with a no-break space keeping an age's number with its unit and without the tracking set for capitals, and takes the badge's line box.

The degraded and last-seen captions were set in capitals, which wrote a lost reading's age as "8 MIN" beside a stale badge's "1 min", and a capital M is the symbol for mega; they are in sentence case, their first letter a capital and the rest as written.

The page's hero and its flash specimen drew site mock rows flashed by keyframes on the page, beside a note not to copy them; they are the kit's AlertListRow, flashing on the shared blink clock, with their times in UTC.

A movable entry showed the grab cursor before and during a drag, though the cursors page asks for grab, then grabbing during the drag; it shows grabbing while it is moved, and a foundation test holds the pair for every stylesheet.

In English the status strip wrote a stale sensor's age and the time the stream has been down as "3m", "42s" and "2h", and "3m" beside a depth reads as three meters; it writes "3 min", "42 s" and "2 h", as the other five languages and the Reading badge do.

The section cards left out Voice and tone, and the wind example wrote "14G22", a form neither the kit nor bosund writes; the cards list the page, the wind reads "14 kn, gusts 22 kn" as weather.bar.wind_gusts writes it, and the index and feature discovery say vessel where they said boat.

The page gave every error message a fix and a dismiss action, though a banner or a section message takes none, and said an error never uses red; it now gives actions to a toast only, shows the NMEA offline notice as its four parts in the kit, and states the data integrity red that notice takes.

The page asked for a way back and a pending message without naming what the kit gives for them, and wrote times with no reference; it now names the toast's Undo countdown, the deletion made final in onClose, and track() for a task that is still running, with every time in UTC.

The page said an info message never pops up over the page, though info is a toast's default kind, wrote "2 h 05 min" and bare times; it now allows an info toast about something the crew just did, writes "2 hr 5 min" and every time with UTC, and says vessel.

The content guide drew a site mock with three states, Empty, Blank and Unavailable, and showed a receiver that stopped reporting as an empty state; it now renders the kit's EmptyState with its kinds, empty, no-results, unavailable and done, says that a stopped source is an alert, that an empty state wears no message color, and writes ranges in NM.

The page told writers to keep the standard alarm label but drew the alarm as "Person overboard", which no catalog writes, and showed times with no reference; the alarm reads "Man overboard", as alert.mob.title does in every language, and its times carry UTC.

The page showed bare times, ages such as "95 s old", abbreviated months, a relative time hidden behind hover and spoken times in UTC; it now prints every time with its reference, ages in one floored SN.1/Circ.243 unit, durations in the language's short units, the written date with months in full, the relative time beside the time, and the voice in the vessel's local time, and it settles the log's UTC and the site's locale clock.

The conning display and the night watch display stay on one view, but the shell drew them as an application screen, with a navigation column and a menu button that lead away from it. mode="console" draws the header and its alert zone, the page and the side panel, and no navigation, menu button or tab bar. splitPresets names the ways the screen divides between the page and the side panel; a segmented control at the header's end offers them, sets the panel's width as its splitter would, and checks the split in use.

A schema form laid out as a wizard kept a new record's typed values but opened again on the first step; it now keeps the step the crew were on and the steps they had reached, and shows the kept-draft notice with Start over, which goes back to the first step.

A new record's draft, and the values a form keeps for the next record, wrote every field to the browser's storage, a password field's included, as plain text; they now leave out every field drawn as a password, which a restored draft opens empty.

The vessel mark existed only as markup: drawn by hand on the logos page and as a stylesheet rule in the web UI's sidebar. The kit now has it as VesselMark, in four sizes in em of the text around it, decorative beside the vessel's name and an image named by its label on its own. The logos page draws its specimens with it.

The rest rule counted the periods of rest only in the 24 hours from the start of each rest, so a split that showed in a window ending at a rest went unflagged; it now also checks every 24 hours that ends where a rest ends, without cutting a rest at the window's edge.

Red means alarm, so the plotter's red-cored echo palette and looks are for comparing with a chart plotter and never offered on a screen that shows alerts; the page states the rule in place of its open question.

Given automaticModel, the model bosund's routing would send the next message to, the picker reads "Automatic · Qwen3.5 4B", so the crew know before they send which model answers and whether the message stays on board.

The tooltip's closing fade ran on the standard curve, where the motion foundation gives everything that leaves the exit curve; it now accelerates away like the popover, the menus and the dialog.

A long press opened the context menu on a touch screen, but nothing showed that it would. Under a coarse pointer the area now shows a ⋯ button at its end, named by the menu's label, that opens the same commands anchored to it; under a fine pointer the button is not drawn.

The page now says a live list holds its order while the crew are in the table, and its Open callout keeps only grouping and column resizing, which are not built yet.

A live list re-sorted on every update, so a row could move from under the eye or the finger; while focus is in the table or the pointer over it, an update now leaves the rows where they are, a new row comes in at the end, and the order applies when the crew leave, while a sort or filter they set applies at once.

Up and Down moved through the tiles in reading order and Left and Right did nothing; now Left and Right move along a row and Up and Down a column, by the number of tiles the grid draws on a row, skipping a disabled tile.

When the browser refused the copy, the button said "Could not copy" and left the crew with nothing to do. It now also shows the text beside it in a read-only field, selected and focused, with the keys that copy it (⌘C on Apple's platforms, Ctrl+C elsewhere), in the crew's language; the field stays until it loses focus.

The panel's readouts carried no integrity, so a heading from a compass that had stopped looked as current as a live one. A value the caller gives its trust (integrity, age, reason, source) is now drawn as a reading, with its age, its integrity treatment and its reading detail, and a position the caller marks stale, degraded or lost says so under it. A value without trust keeps the plain readout, and a missing one its dash.

A reading's source, trend and trust were a native title on the reading, which a coarse pointer cannot open, so a gloved hand at the helm saw the value and the state badge but never the source. A reading with a source now wraps its value in the kit's reading detail: a resting mouse, a press or a tap opens a panel named by the source, with the state below it. The trend and the state stay on the reading and in its accessible name, and no title remains on it or its trend arrow. The reading detail's age is now optional.

The owner decided on 18 October 2026 that warnings do not flash, and the kit's alert rows and icons already drew them steady; the vendored alert frame, which readouts and tanks draw around a value, still flashed an unacknowledged warning on the slow tempo and a rectified one on the very slow tempo. It now draws a warning steady in every mode, a house deviation from OpenBridge.

Faint gradient tints mark identity surfaces (the vessel mark, the vessel overview, a report's header) and nothing else; the conning screen opens on the rose and the chart; the watch settings sit beside the AIS table and on Settings; the site takes the app's tokens and icons with a larger display scale and entrance motion; the reports render the kit's icons and the site copies their SVGs; and bosund is to gain an output mute that keeps the level.

A metric card's corner was 24px and a chart panel's 16px, both outside the radius scale, and the radius page kept them as an open question; by the owner's decision both take --radius-xl, 12px, as dialogs and alert cards do, and their two corner tokens are gone.

In Day and Bright the house yellow sat 29 and 28 ΔEuv from the amber, so a caution badge's dot read as a second amber. It moves toward olive, #938400 in Day and #857f00 in Bright, 67 and 73 ΔEuv from the amber; the badge's label keeps its text step, which already reads at 4.5:1. The owner chose to separate them now rather than wait for the OpenBridge 2.0.0 palette. Dusk's pair measures 38 ΔE*uv and is unchanged.

Night's dim and faint text sits at 3.9:1 on black, and the pages listed it as open; it is now the one role held under 4.5:1, by the owner's decision, to keep the crew's dark adaptation, and it carries labels, never values.

Tabs takes value, onValueChange and activateOnFocus (no active, onChange, activation or TabPanel; a panel is Tabs.Panel), the collapsible's region is CollapsiblePanel, the command palette returns focus through finalFocus, a setting toggle reports through onCheckedChange, and a splitter its last size through onValueCommitted.

The flat exports (SelectContent, SelectTrigger, SelectValue, SelectGroup, SelectLabel, SelectItem, SelectSeparator) and an item's textValue are gone: a list is Select.Portal, Select.Positioner, Select.Popup and Select.List, a group heading is Select.GroupLabel, and an item's typeahead text is its label. The chat input's model picker and the select page's examples are written that way.

ComboBox, which chose between free text and a held id with a freeText flag, and its page are gone: free text takes AsyncAutocomplete, a record takes AsyncCombobox with the record as its value, and the pages that linked the combo box link the one they mean.

The Modal adapter (onClose(reason), initialFocusRef, returnFocusRef) and its second page are gone; the dialog's stylesheet, its tests and its examples sit under task-dialog, and a caller reads Base UI's reason from onOpenChange.

The TabBar, ChoiceCards, SegmentedControl and CommandMenu aliases, which the package no longer exported, and their second pages are gone; each component's stylesheet, tests and examples sit under its own name.

The chart folder held a Chart alias the package no longer exported, the chart's stylesheet and tests, and a second page for the same component; the stylesheet, tests and examples now sit under nautical-chart, and the alias and the old page are gone.

The OpenBridge alert colors are fills, and as text they fall under 4.5:1: in Day the warning is 2.0:1 and the caution 1.2:1 on the page, in Bright 2.2:1 and 1.4:1, and the alarm 3.9:1 in Dusk. The palette's amber and yellow are under it in Day too. Each now has a text step, --red-text, --amber-text, --orange-text, --yellow-text, and --bk-alert-alarm-text, -warning-text and -caution-text for an alert's word or number, and PRIORITY_SPECS gives every priority a textToken. A badge's label, an alert card's step numbers and figures, the alert list row's priority word, the due chip, the countdown, the alert zone's count, the event timeline's priority word, the status strip's chips and risk, a reading's age and reason, and the telemetry and instrument pill values take them; shapes, borders, fills and icons keep the colors. Dusk keeps its own colors, which already read; Night's warning and caution are brighter as text. This is the owner's decision of 18 October 2026.

Four pages kept open what the kit already does: the banner, section and inline messages are built; a popover or list opened from a dialog or a toast opens above it; an error message's mark is neutral; and the documentation is a Fumadocs site, not mdBook. The pages now say so.

The content guide had a warning message kind drawn in the alert warning color, which the kit does not have: a message's kinds are error, attention, info, success and discovery, and none wears an alert color. The page is now Attention messages, every specimen takes the kit's marks and colors (error and attention neutral, info and discovery in the accent, success green), its forecast example (an alert bosund raises) gives way to a route-timing one, and its confirmation quotes the entity list's own words.

The page offered compatibility imports (Chart, TabBar, CommandMenu, Modal, ChoiceCards, SegmentedControl, ComboBox) and a migration list, but the package exports none of those paths; the names table now lists the canonical names alone, a section gives the conventions every component follows (display text, Action props, ref, testId, data-* state, className, motion), and an Open callout asks whether the unexported adapter folders and the deprecated props are deleted.

The overview had a card for every foundation in the sidebar but the component API; it now has all eighteen.

The page said the logo's name is near-black or near-white, while it is the accent in every theme and only the tagline takes the text color, and gave the sidebar's vessel mark as 24px where the web UI draws 26px; it now says both as drawn, links the vessel overview, and asks in an Open callout whether the mark stays the one gradient now that the vessel overview and a report's header carry a tint.

The size specimens gave the vessel application's fixed pixel sizes; they now show the kit's em sizes (1.375em in a navigation row, 1.8em in the tab bar) and the 48 px icon-only button, the pages name the pinned 2.0.0-next.128 package, the AIS tile shows the -iec target the page tells readers to use, and the Open icon-gap item gives the steps the kit uses.

The page called uppercase "a deliberate choice for particular content"; it now gives the rule the foundation test holds, capitals only for small mono labels and never for a sentence, a name, an alert's title or a heading, and says text takes a role or em so it follows the size class.

The page said a portaled menu applies the touch size to every choice whatever screen its trigger is on; a list in the page body is outside every screen container, so its choices take the touch size under a coarse pointer, and the page now says so, gives the 68.75em condition for buttons, tabs, switches, chips and fields, and names the metric card's inset role.

The hero, the five layouts and the region table gave the vessel application's sidebar (a 52px rail, a 216px panel, a 900px window switch); the page now draws the kit shell (a 14em panel dragged between 11em and 24em or folded to a 4.5em rail, a 20em side panel, a tab bar or menu on a phone), adds the wider-than-phone condition and the bounds rule to the breakpoint table, says where the phone menu opens, and adds a section on height queries.

The raised row drew an inset hairline no kit selection has, and the hero's menu typed its own shadow; the row now takes --bk-selected-background with the accent on its icon, the menu --shadow-floating, and the layer table adds the header on the alert layer, the brightness menu above it and the lists that open over a dialog or a toast, with a note that Night's floating shadow is a 1px line.

The alarm outline is --alert-alarm-outline-color, a darker red than the alarm color in Day and Bright, drawn as a 2px ring that flashes until the alarm is acknowledged; the page now names it, adds the selection border --bk-selected-indicator, and says an invalid field's border is dashed in the text color.

The table put buttons, inputs and the alarm row at 8px and badges fully round, which the kit drew before every corner took a scale step; it now gives buttons, inputs and the alert zone's row 6px, badges, chips and the ACK 4px, dialogs and alert cards 12px, and full rounding to switches, setting chips, progress bars, radios, dots and avatars, and marks the metric card's and chart panel's corners open.

The interaction states page now says when targets are touch-sized and that a pending control the crew will press again stays focusable, busy and inert to more presses, as the alert zone's ACK does; the cursors table adds the crosshair the charts and the signature pad use and the cell cursor of a schedule lane that takes entries.

The source table named six of the seventeen sheets index.css imports; it now lists all of them with what each owns, including the flash tempos, the stacking order, the breakpoints and the size classes, and says charts.css also holds the analytical series palette.

The themes page named six overlays as carrying their scope into the portal, where every kit overlay does, and called the indent role "inset"; the control styles page said the house control roles follow a red Night palette, where Night's accent, focus ring and selection are amber, and left out the selection and invalid-field tokens.

The contrast list left out the accent in Day and Bright and the alarm in Dusk and Day, and the page said every target is 48 px whatever the screen; it now names every role under 4.5:1 and the readable accent step, says targets are touch-sized on a screen up to 68.75em or under a coarse pointer, and adds a section on flashing: only an alarm or an emergency flashes, 400 ms on and 400 ms off.

The page called every theme's text neutral grey, said red and yellow belong to alerts alone while its own swatches gave them to stale and invalid readings, gave Night's dim text as 3.2:1 where the amber palette measures 3.9:1, and named a categorical palette it never showed; it now says Night is amber on black, gives the integrity roles their place beside the alert colors, shows the invalid reading's background, and draws the nine operational series colors.

The page said an alarm flashes on a 2-second cycle and a warning flashes on its own clock, and named flash tokens that do not exist; it now gives the fast tempo (400 ms on, 400 ms off) for an alarm or an emergency, steady warnings and cautions, the real --bk-flash-fast-* tokens, a durations table that matches the kit's exits, toasts and layout moves, the components with motion defaults, and an Open list with the unbuilt emergency takeover.

The alarm row the foundation pages draw is the site's own specimen, and it drew an alarm as a filled circle, a warning as a triangle and a caution as a small circle, so the alarm and the caution were both circles and neither matched the kit. Its shapes now come from PRIORITY_SPECS: ▲ alarm, ● warning, ■ caution. The ACK chip carried an "A" key no kit component or screen has; it is gone from the row and from the border and accessibility pages, and the radius page shows its key cap with /. The ACK is now 48 px tall, as the kit row's is, and a caution, which needs no acknowledging, shows none. On the accessibility page the warning and the caution take a wind and a battery icon for their cause in place of the anchor.

The home page gains UI composition and lists the WiFi portal and investor communications among the consumers, and the overview adds cards for instruments, UI composition, the WiFi portal, report types and investor communications, says the components render from the kit, drops the mdBook docs, the claim of no cards or shadows and an acknowledge key the kit does not have, and keeps open only what the foundation and consumer pages still mark open.

The outline's draft runs to the outboards' lower units, but the examples drew boats at the hull draft their builders print, so the motors were squeezed into the hull's depth; they now draw a Robalo R200, a Pursuit S 328 and a Boston Whaler 360 Outrage, whose catalog drafts are taken with the motors down.

The motor yacht outline was drawn by eye. It is now traced from Beneteau's side view of the Gran Turismo 50: the hull with its raked bow and swim platform, the hardtop over the deckhouse with its curved glass, three hull-window panels, and the pod drives that set the draft. No builder publishes a full side view of a flybridge yacht that could be traced, so the outline is a planing yacht under a hardtop, and flybridge yachts draw from it too. At the waterline the hull measures 13.94 m and the freeboard at the bow 1.86 m.

The cruising trimaran outline was drawn by eye. It is now traced from YACHT magazine's side elevation of the Neel 52: the hulls with the stepped stern and the plumb bow, the deckhouse with its saloon windows and windscreen, the hardtop over the open cockpit on its post, the hull window, and below the boot stripe the canoe body, the fin keel, the saildrive and the spade rudder. The waterline falls at the top of the antifouling; there it measures 15.22 m and the freeboard at the bow 2.10 m.

The outboard boat outline was drawn by eye. It is now traced from Grady-White's line drawing of the Canyon 336: the hull with its raked bow, the console under the T-top with the windscreen's two panes as its windows, and the twin outboards on the transom, whose lower units set the draft. The drawing has no waterline, so it is set at the builder's hull draft above the bottom; there the waterline measures 8.69 m and the freeboard at the bow 1.51 m.

While the label slid in, its motion made it the arrow's containing block, and once the motion ended Base UI's positioner was, so the arrow jumped by the border's width, a pixel along the edge and two across it; the label is now always the arrow's containing block, and the arrow stays where it opened.

The arrow ended at the label's outer edge, so the label's border ran straight across its base and the arrow read as a separate shape stuck on; it now reaches a pixel into the label, over the border, and its two edges meet the border's line, on every side.

Trawlers and expedition yachts drew as a planing motor yacht. The trawler outline is traced from Nordhavn's own drawing of the N41: the high bow and the sheer sweeping down aft, the pilothouse, the saloon with its windows and portholes, the boat deck over the open cockpit on its post, and under the water the full keel running aft to the rudder and the propeller in its aperture. Scaled to the N41's 12.5 m, its waterline measures 12.25 m against the catalog's 12.19 m and its keel 1.55 m against 1.37 m.

The traced outlines carried every dark mark of their drawings (stripes, fittings, frames, logos) as glass or lines, which drew the hull full of gaps; each now keeps its outline and only the windows: dark shapes large, solid and compact enough to be glass.

The sailing catamaran outline was drawn by eye. It is now traced from YACHT magazine's side elevation of the Fountaine Pajot Elba 45: the hull with its windows and boot stripe, the saloon's glazing, the flybridge's hardtop over the open cockpit on its post, the swim steps, the canoe body, the low keel, the rudder and the drive. Scaled to the Elba's 13.41 m, the drawing's waterline measures 13.39 m against the catalog's 13.25 m and its keel 1.40 m against 1.25 m, which the outline's notes record.

The cruising monohull outline was drawn by eye. It is now traced from YACHT magazine's side elevation of the Jeanneau Sun Odyssey 440: the hull with its raked transom and bow roller, three hull windows, the coachroof and its window band, the boot stripe, the canoe body, the fin keel with its bulb, the spade rudder, and the shaft with its strut and propeller. Scaled to the 440's 13.39 m, the drawing's waterline measures 12.39 m against the catalog's 12.00 m and its keel 2.13 m against 2.30 m, which the outline's notes record; each vessel's own particulars set hers through the stretch.

The Hanse outline was drawn by eye. It is now traced from the hull plan Hanse publishes for the 460: the silhouette from the plan's outline, the canoe body below the antifouling line with a straight line across each appendage's root, the keel, rudder and saildrive as drawn, the dark windows and coachroof band as glass, and the boot and sheer stripes as lines on the hull. The rails, the anchor and the shallow-keel option are left out. The reverse transom, the bow roller and the L-shaped keel are now the boat's own.

The pressure by the hour was one solid line whether its hours were measured or forecast, so a coming fall read as one already measured beside the 3-hour change; the record up to now and the new pressureForecastHpa are drawn apart, the forecast hours as the sparkline draws a forecast.

A missing value leaves a gap, as the page asks, but a zero drew no bar either, so the two looked the same; a zero in a grouped chart now draws a 2 px bar on the baseline. A stack keeps exact heights.

A reading's age and an alert's age were written 45s, 3m, 2h and 1h 25m, so beside a depth "stale, 3m old" read as a length; they now take SN.1/Circ.243's symbols, 45 s, 3 min, 2 h and 1 h 25 min, the same in every language.

The alert list row flashed an unacknowledged warning's icon on the slow clock, while the priority mapping, the alert card and the alert zone held it steady; by the owner's decision only an unacknowledged alarm or emergency flashes, and the alert icon takes steady for the rest.

A pill whose reading had stopped kept its value in the full text color and changed only its small dot, so it looked and read like a current one; its value is now dimmed and carries "stale" for a screen reader. ACK in the alert zone is dimmed and busy until the acknowledgement is answered, and a second press sends nothing more.

The open navigation was a row in the page's flow between the header and the page, so with the page scrolled down the menu button opened it out of sight; it now stands under the header, over the page, and scrolls inside itself.

The strip was a status region, so a screen reader read the whole strip out each time a reading changed and buried the alert zone's announcements behind it; it is now a plain row, read when the crew reach it.

Without formatTime the axis wrote the browser's local time in the browser's locale with no reference, so "14:20" could be any zone; it now writes the time in UTC, in the crew's language, followed by "UTC".

With a caller's formatValue and no fractionDigits, a forecast of 3.6 m between 3.2 and 4.0 m was read out as "± 0", an interval read as certain; the spread now takes the digits the value is written with and rounds up, so it reads "± 0.4".

On a screen up to 68.75em or under a coarse pointer, the LLM status chip in the status strip was 32 px high and a chip's remove button about 13 px square; both are now at least 48 px, as the strip's other controls and every touch-sized control are.

Commissioning had no way to show what the box receives: the WiFi portal's progress screen ran on timers. The instrument check is the setup step that does: a row for each source bosun reads, with where it comes from, its live value, and a verdict (receiving, stopped for how long, not received, listening, or not fitted). While a source is not receiving, its row says what to check; a count heads the list, of the sources receiving out of those fitted.

Heading, course and the wind's and current's directions were whole numbers with "deg", so 359.6° read 360 deg and 5° read 5 deg; they now read 000° and 005°, as the bridge writes a bearing.

The text area's own glyphs are transparent over a painted copy that did not scroll, and the line numbers ran on past the field, so a document longer than the field showed lines 1 to 12 while the caret edited line 18; both layers now follow the text area's scroll, and the numbers stop at the field's last line.

Dialogs offset themselves by --app-header-height, which only ui/web's layout set, so in the kit's shell a full-screen dialog or the command palette drew its title and close button under the header; the shell now writes its sticky header's height there too.

With stickyHeader={false} the header lost its place on the alert layer, so an open dialog's scrim covered the alert zone and a press on ACK closed the dialog instead; the header now keeps the alert layer whether or not it sticks.

A closest point of approach of 0.96 NM was rounded to 1.0 NM and a TCPA of 4.6 minutes to 5 min, a target passing closer and sooner than written; both are now floored, as a depth is, while speed and course keep core/i18n's rounding.

A Reading takes a value that is not one number as text, shown as written, with the same stale, degraded and invalid treatment as a number, and empty text counted as lost; a position is a reading like any other.

With neither a heading nor a course over ground the hull was drawn unturned, bow-up, which on a north-up chart states a heading of north; the position now takes IEC 62288's own-ship mark, two concentric circles, which states none.

The chart joined every sample, so three hours without data were drawn as a measured fall; a sample can now be missing (v: null) and maximumGap stops the line across a longer time between samples, each run drawing its own line and area.

The situation board wrote the vessel's position, depth, speed over ground and activity in a line of its own, with the depth rounded to a tenth, which can say there is more water than there is, and no value marked stale or invalid. The situation line sets them as the board's second element, under the vessel overview: the position in chart notation, the depth floored, the speed over ground to a tenth, each with its trust state, then what she is doing and for how long, and night. The position is a reading too, written as text, so it is marked as every value is.

The zone holds the worst unacknowledged alert but drew an alarm or an emergency as a steady red tint; its ring now flashes on the shared alarm clock until the alert is acknowledged, also under reduced motion, as the alert card's frame does.

The compass took a missing heading or course over ground as 0°, so a vessel whose heading sensor had dropped out was drawn bow-north with her HDG and COG arrows at 000° beside readouts showing a dash; an unset or non-finite heading now draws no vessel and no heading arrow, and an unset course no course arrow.

The name's button kept the browser's smaller font, so the name and chevron were drawn at 13.33 px a size and the lines under them started a few pixels off; the button now takes the overview's font, the model and summary lines are indented once at that size, and the button holds her MMSI and call sign, so its hover and its target cover the whole line.

When neither the side asked for nor its opposite had the room, Base UI moved the label to the cross axis, so the flip example's label, asked for above, opened to the left of its button; the label now stays on its axis at the side with more room, and the example gives it room to open below.

The notice now opens with OpenBridge's signal-failure mark and a heading, No instrument data, in the body type. Its first sentence says how long nothing has arrived when the page passes quietSeconds (the youngest of bosund's instrument_age_seconds), floored so it never says longer than it has been. The second says whether the readings below are the last ones received or will appear when data returns, and the third what to check, instruments first. The notice sets no margin of its own, and its style moved from inline values to a stylesheet on tokens.

The outline drawn from the Hanse 460 was named "Hanse, 2016 on", credited to Judel/Vrolijk and said to draw the 315 to the 675; the 460 is Berret-Racoupeau's first Hanse (2021), so the outline is now HANSE_2021, "Hanse, 2021 on", drawing the 360, 410, 460, 510 and 590, and its range example draws the 360 where it drew the Judel/Vrolijk 315.

Without its stylesheet the overview ran each label into its value ("MMSI244123456Call signPDAX") and showed the closed summary under the open profile; the spaces are now text in the markup, and the summary is rendered only while the profile is closed.

The situation board drew the vessel profile between its alerts, unlabeled, at a fixed size. The vessel overview is its first element: her name in display type is the heading and the button that opens and closes her profile, her MMSI and call sign on its line, and her model with its designer and years under it. Open, her profile is drawn in the water from her outline at her own particulars, dimensioned, with her length overall, beam, draft, air draft and displacement listed beside it on a wide board and under it on a narrow one. Closed, a line keeps her length overall, draft and air draft. Its open state is the overview's own or the board's, through open and onOpenChange.

Given water, the profile fills the frame under the waterline with a tint of the waterline's color fading toward its foot, behind the hull, so she sits in water; off by default, and the vessel overview turns it on.

An outline can draw hull lines, such as a chine or a cove stripe, cut to the topsides; its strake is optional; and the frame's top clears the topsides too, so an outline traced whole, its superstructure part of its topsides, is never cut off.

The dimension labels were hard to read at the size the profile is drawn on a board: they are now 12 units, the freeboard's 10, with the rows under the keel spaced to suit. The particulars a side view without its rig cannot show are set in a strip under the length overall, as a drawing's title block sets them: a hairline rule, then each one with its label in small capitals over its value, aft to forward. The air draft joins the beam and the displacement there, since it is what the crew check against a bridge, and joins the drawing's accessible name.

A label written as plain text in Menu.Item fell into the items' 1.25em mark column and broke after each word, with a Menu.CheckboxItemIndicator written after it laid over the text; every item now holds the mark column, so the label takes the label column, and both indicators sit in the mark column wherever they are written.

A list of more than ten currencies now opens with a shortcut group: the crew's own currency (localCurrency) first, then the most traded ones the list holds, and after a separator the others in the list's order. Each currency appears once, so keyboard type-ahead and the selected mark find one option. A list of ten or fewer stays whole.

Each outline has a page under the vessel profile's, showing the outline as drawn, dimensioned from its marked points, and three catalog vessels drawn from it to one scale; Hanse's range example moves to the Hanse page.

Every vessel drew as a Hanse, whatever she was: a catamaran or a center console came out as a monohull with a fin keel. The profile now has an outline for each hull shape the vessel catalog carries, each drawn once with the same marked points, so any vessel stretches to her own particulars: a cruising monohull (CRUISING_MONOHULL); a sailing catamaran, one hull with the saloon on the bridgedeck above it (SAILING_CATAMARAN); an outboard boat with a console under a T-top, whose outboard's lower unit sets the draft (OUTBOARD_BOAT); a flybridge motor yacht, whose propeller sets the draft (MOTOR_YACHT); and a cruising trimaran with its near float in front of the main hull (CRUISING_TRIMARAN). A vessel steered by her outboard draws no rudder, and the frame's top now clears the highest structure drawn, a hardtop or a saloon roof, not only the rails. Where the hull reaches down beside the draft's line, as an outboard boat's does, the draft's label goes under the keel's foot so that it never sits on the hull.

The paste reader took the first nine-digit run, so a Spanish phone number before the MMSI filled the field, and read a ten-digit phone number in groups ending in 0 as the NMEA 2000 form; a number labeled MMSI now wins, and the ten-digit form counts only written whole.

A GGA with no fix or a simulated one, an RMC whose mode says it is not valid, a sentence whose checksum does not match, or a latitude marked W was read as a position; the field now refuses each, as bosund's decoders do, and the paste example carries its right checksum.

The field took off a leading 0 everywhere but four countries, so a Benin number lost its 0 and was saved wrong, while a North American 1 or a Russian 8 stayed; it now reads each country's trunk prefix from libphonenumber, and keeps a prefix that is part of the number.

The lists scrolled only the focused hour into view, so a chosen 20:00 showed its hour on the third row and its minute, the first in its list, on the first. Both lists now hold their chosen option in the middle whenever the lists open or the focus moves, and half a list of padding above and below lets the first and the last option reach the middle.

The entity list's expense examples drew the amount as a number with a € prefix; they now declare it as bosund's expense schema does, a money field with its currency, so the form draws the money input, and the schema form's prefix example shows Ch before a VHF channel instead of a currency sign.

The profile was one picture, so a 9.7 m and a 17.6 m vessel drew the same hull. It is now drawn from an outline: one builder's range drawn once, hull and deck without the rig, with the points a naval architect dimensions marked on it (transom, the waterline's ends, stem, bow fitting, deck at the bow, canoe body, keel's foot). Given proportions, the vessel's particulars in meters, the outline grows to her length overall, her waterline length moves the waterline's ends, her freeboard the deck at the bow and her draft the keel's foot, while the deck structures and rails keep the range's proportions. A shorter waterline goes to the stern in the outline's own share: Hanse's is all of it, so the plumb stem stays upright and the stern lifts. frameLength draws several vessels to one scale. Hanse's range from 2016 on is the first outline (HANSE_2016, listed in VESSEL_OUTLINES for the vessel catalog to name); the mast and stays are gone from the drawing.

An empty field with a prefix, such as a currency sign, set its name at rest over the prefix, so "€" and "Amount" overlapped; a field with a prefix now keeps its name on the outline, as a list does.

Focused from the keyboard, a list inside an outlined field drew its own ring, offset inside the field's thickened outline, so the field showed two boxes; the field's outline is now the only ring, as it is for a text input.

The DNS picker's custom servers were a free-text field split on commas and spaces, checked only when the crew left it. The IP address input holds one address, or with multiple several as chips, adds each as a space, a comma or Enter ends it, and refuses by cause: not an address, the version the field refuses, one it holds, or more than maxAddresses. IPv6 addresses are reported as Go's net/netip writes them, the form bosund stores. The DNS picker's custom servers use it, and isIpAddress and the address splitting move from the DNS picker to it. Its reading is fuzzed against the platform's address parser and the field under the interaction fuzzer.

The choose button reads Select File (Select Files for several) as written, not in capitals, the outline stays solid while the field takes files, and the examples take files up to 100 MB.

The drop area set its prompt beside the button on one line ("Drag files here, or CHOOSE FILES") inside a solid outline, and listed the files inside the outline too, each with a bare ✕. The area now stacks a file mark, the prompt as a heading, the limits and the button, centered, inside the field's outline; the files sit under the outline, each with a framed trash button (✕ stays for stopping an upload), and a refused or failed file is framed in red as an invalid field is. OutlinedField gains after, content under its outline before its error or hint.

A whole number now names its kind and the country it belongs to under the field: Mobile, United Kingdom; Landline, Guernsey for a +44 number in Guernsey's ranges. Once the crew leave the field, a number no country with its calling code has is doubted by its cause: too few digits, too many, a length no number has, or no number starting this way. The doubt is a quiet line, never an error: libphonenumber's patterns age, and a vessel that has not updated for months must still be able to save a number from a range opened since. The patterns are 28 KB gzipped and load in a chunk of their own once a field holds a number.

A trailing icon (the time picker's clock, the date picker's calendar, the paste and reveal buttons) stood about 7 px from the field's right edge while the text stood 12 px from the left, and the browser's own time field, now drawing the same clock, left it 15 px. The end slot's right padding is --space-sm in place of --space-xs; with the button's 2 px around its icon and the icon's own margin, the last icon's ink stands 12 px in. The controls reserve the wider slot by measuring it, as before.

The time input, the time picker's native mode and the schema form's date and time field are the browser's own fields, and Chromium drew its own small, bright clock or calendar in them, unlike the time and date pickers' 20 px Lucide icons in the dim text color. The browser's picker button keeps its job, opening the browser's picker, and now draws the kit's clock (or, in a date, date and time, month or week field, the calendar) at the same size and color. Safari and Firefox draw no such button on a desktop, so nothing changes there.

The three-digit groups matched no country's convention, so a crew member checking a number against the one on a card or a phone had to read it digit by digit. The field now groups the national digits by the formats of Google's libphonenumber for the country's calling code: 7345 615225 for a UK mobile, 20 7946 0958 for London, 6 39 98 12 34 in France, 202-555-0123 in the United States. Five territories libphonenumber has no format for (Ascension, the Falklands, Kiribati, Saint Helena, Tokelau) show the digits as typed rather than an invented grouping.

The clock button's 48 px target reached 20 px past the field's right edge when a reference stood before it, which widened the column the field sat in; it now reaches left over the reference, and the hero's fields narrow to 160 px.

A time field was the browser's own, whose popup on a desktop could not be driven by the keys. The time picker is an outlined field that reads a time as the crew type it (14:30, 1430, 14h30, 2:30 pm) and opens hour and minute lists under a clock button, with min, max, minuteStep, Now on the UTC or the device's clock, and timeReference printed beside the time. With a finger it is the browser's own time field, whose wheels suit a touch screen; picker chooses one everywhere. The schema form's time fields use it, with the field's unit as the reference.

The country button centered GB and +44 apart, so the smaller code's baseline sat about a tenth of its size above the calling code's; the two now share a baseline.

Typing uk listed Ukraine, whose name holds it, before the United Kingdom, so Enter chose Ukraine; a country whose ISO code, or a code ISO 3166-1 reserves for it such as UK, matches the search now leads the list.

A countdown's chip and a due chip had the same purpose, a time that has come or is coming in a list row or a card, but separate styles, so they looked like different things. appearance="chip" now renders a DueChip with the countdown's timer as its label, and the countdown's own chip styles are gone. DueChip gains a none treatment, its neutral colors with no shape, for a moment not yet near; its label takes markup, so the countdown keeps its timer role and <time> element; and changeKey sets what its fade follows, which a countdown sets to its treatment.

Only the setup portal could list WiFi networks, with its own list. The WiFi network list shows the networks in range with their signal, band and security, merges the access points that share a name, and opens a chosen network's details, its password field, its DNS and what can be done with it: connect, disconnect, forget, or let the vessel join it by itself. A network that does not broadcast its name is joined by typing it.

The setup portal chose the vessel's upstream DNS with its own controls. The DNS picker offers the same four choices for any network, each with its addresses, and checks custom servers as IPv4 or IPv6 addresses before it reports them.

The setup portal drew a WiFi network's strength with its own bars in the success green, and nothing else in the kit drew a signal. The signal strength takes NetworkManager's 0 to 100 or an RSSI in dBm, lights one bar for each quarter of the range so the bars and the word agree, and can write the word and the value beside them.

A diagram was a picture: a reader who wanted to know what a box or an arrow stood for had to look for it in the prose. Given details, keyed by a node's id or a line's ends, each part gets a clear target that opens a tooltip on hover or focus, a popover beside it on a press, or a dialog for longer text, through the kit's own overlays. The targets sit beside the drawing rather than inside it, so the diagram keeps its image role and its description, and they follow the drawing when it is expanded or the page is resized. Mermaid's own click handlers stay off under its strict security level.

Every message was a bubble with a colored bar down its left side, the crew's tinted and Bosun's grey, each a log region of its own, so a screen reader met a stack of logs. As a chat assistant does it, the crew's message now sits in a bubble at the end of the column, Bosun's answer is plain text across it at a readable line length, and a system notice is centered in the caption type. Under a message a line carries its time and an answer's actions (the caller's icon buttons), shown on focus or hover, on a touch screen and on the latest answer. An answer still arriving shows a caret that does not blink. Each message is an article named by its author; the conversation around it is the log.

The readout page opened on a crowded panel. The heading, speed and depth readouts now stand in three equal columns with their feet on one line, so their sources read across; the horizontal rows start on one edge under a rule; the low-integrity wind row is framed once; and the note floors the depth to tenths, as depth is always written. In the instrument, a horizontal readout's label with no unit takes the unit's place at the foot of its column, so "Standby Radar" reads on one line where the label stood raised above the value.

The sidebar's lists of components and instruments were text with a few icons among them, so a page was found only by reading. Every page now names an icon in its frontmatter, and the navigation's icon registry grows from 36 to 198 names: 166 Lucide icons for controls, layout, charts and forms, and 32 OpenBridge icons for alerts, AIS targets, the nautical chart, the radar, tide, depth, wind, current, swell, buoys, beacons, the harbour and the vessel.

The chosen segment carried a 2 px line along its foot, an inset shadow that the segment's rounded corners bent up at each end, and its fill barely differs from the track. The mark is now a 2 px ring inside the whole segment, sliding between options with motion and drawn on the chosen option without it.

Reading a tidal gate meant subtracting the time now from a window's start. With relative the curve says whether the gate is open and when it closes or next opens, and how long until or since each high and low water, written as the countdown writes it.

A log read hours later asked the crew to work out how long ago each entry was, and an entry offered nothing to do with it. Each entry can now say how long ago it was beside its time, show its actions (two as icon buttons, the rest in a menu) under the pointer or with focus, write its moment in full in its time's tooltip, and draw its source and tags as chips; a row of filter chips shows the entries that match any pressed chip.

The choice groups' rule reset the track's padding and border to 0 when its stylesheet loaded after the segmented control's, so the chosen segment touched the track's edges; the track's own rule now outranks it in any load order.

A vessel's page showed her particulars in a table beside a profile that carried none of them. Given dimensions, the profile draws them as a naval architect's drawing does: length overall from the transom to the stem and length at the waterline under the keel, the draft beside the keel from the waterline to its foot, the freeboard ahead of the bow, and the beam and displacement on a line underneath. The drawing does not change; the frame grows downward to hold the lines, the dimensions join the accessible name, and the labels are in all six languages.

The profile is the picture at the head of a vessel's page, and it looked like a placeholder. It is now drawn on the lines of a yard's side elevation: a straight sheer rising to a plumb stem, a near-vertical transom with the rubbing strake and a twin boot stripe, three hull windows led in by fine lines, a low coachroof with its window band, the cockpit coaming, stanchions with two lifelines between pushpit and pulpit, a bow roller, and the mast and stays leaving the frame. Below the water an L-shaped fin keel with its bulb aft, a saildrive and a raked spade rudder share one shading that darkens toward their foot, drawn under the canoe body so their roots disappear into it. Each drawing gets its own gradient ids.

A row of two short lists, such as Hull and Propulsion, gave its spare columns to the second, a third beside two thirds, so its edges missed those of the rows above; a short row whose fields all widen now splits evenly when the row divides without narrowing one.

The thumb of a switch that was on stopped 4 px from the track's end while an off thumb sits 2 px from its start, so the two looked set differently; both now leave 2 px.

The log, the alert history and the watch handovers had no shared way to show what happened over time. The event timeline sorts and groups entries by day, shows who recorded each and where it came from, and shows each correction against the entry it corrects with the value first recorded struck through, so a corrected record never reads as if it had always said the new value.

Nothing in the web UI could attach a file, though bosund stores documents, photos and manuals. The file input takes them by button, drop, paste or a phone's camera, checks each one's type, size, count and first bytes before it is taken, and with the caller's upload action sends it with progress, a way to stop it and a retry. Thumbnails are read into data: URLs, which the web UI's Content-Security-Policy allows.

The tides page drew its prediction with a generic trend chart that knew neither the datum nor high and low water. The tide curve marks and lists them, reads the height now and whether it rises, adds the tide to a charted depth, shades night, and for a bar or a gate shades and lists the windows when the tide is above the height it needs.

The passage plan's decision points each computed their own countdown on a page-wide timer. The countdown keeps its own clock, waking only when its text changes and sleeping while the page is hidden; it floors so it never promises more time than there is, takes the caution or warning treatment as the moment nears, and can count up once it has passed.

On passage the ship's clock is advanced or retarded at a set time, and a schedule printed every time with one reference. Given clockChanges, each change draws a dashed line down the lanes with its words on the axis, and every time is printed with the reference in force when it falls: an entry, a refusal, a new slot and the now line. An entry across the change gives each end its own reference ("12:00 UTC+1–17:00 UTC+2"), and since times are instants the watch keeps its true length of four hours.

Watch lengths, alarm delays and service intervals were plain numbers in a unit the crew had to know. The duration input takes "4h30", "4:30", "1,5 h" or "2 Std 15 Min", writes the value back in its fields, steps it by keys or buttons, and offers presets; in a schema form a number field tagged component=duration with a unit of time draws it.

Six pages wrote their own "No … yet" line, each in its own style, and a search that matched nothing said so to sighted crew only. The empty state is one block: a mark for why there is nothing (nothing recorded, nothing matched, the data cannot be shown here, nothing left to do), the line saying what is empty, why, and the next step as a button.

The schedule could warn about one short gap (minRest) but not about the rest counted over a day or a week, which is what the rules on hours of rest measure. Given restRule, each lane is checked over every 24 hours and 7 days that overlap the range: the least rest in each, how many periods the day's rest is split into and the longest of them, and the longest work between two rests. A lane that meets the rule says so under its name; one that breaks it lists each limit with the caller's durations, such as "7 hr rest in 24 hours, under 10 hr". The arithmetic lives in rest-hours.ts, tested on its own.

Creating an entry needed a pointer: a drag or a click on an empty part of a lane. Given onCreate, New entry in the head places a slot one step long from the quarter hour of now in the first lane that takes entries and focuses it. The arrow keys move it, Shift with them changes its end, Up and Down change its lane, and each step is read out. Enter hands it to onCreate, Escape drops it, and focus goes back to New entry. Its words are in all six languages.

A swipe that starts on an entry scrolls the rota instead of moving the watch; a finger held still on the entry for 0.4 s picks it up, ringed, and its next moves drag it.

Two entries in one lane on the same hours were drawn on top of each other, so one hid the other, and nothing stopped a move that gave a crew member two watches at once or left them an hour's rest. Overlapping entries now take a band of the row each, with a layers mark, and are named as overlapping each other. A move onto hours another entry in the new lane holds is refused before changeAction is asked, with the reason in the crew's language; allowOverlap lets it through where work can run side by side. Given minRest, a gap shorter than it is drawn solid with an hourglass, and the entry after it is named as having a short rest before it.

A new watch or job could only be added outside the schedule, with its hours typed in. Given onCreate, dragging across an empty part of a lane marks every quarter hour (moveStep) the drag touched, with a ghost showing the hours, and a click marks one step from the quarter hour clicked in. The schedule hands the lane and hours to the caller, which opens its own form to name the entry. A lane with a note, such as a crew member off sick, takes no new entries.

A schedule could only be read: a watch that had to move to another crew member, or end later, was changed somewhere else. Given changeAction, an entry dragged along its lane moves its hours, dragged onto another lane goes to that crew member, and its edges change its start and end, each snapped to moveStep. The same moves work with Alt and the arrow keys, announced step by step. While the save is pending a ghost shows the new hours; a refusal puts the entry back and shows the reason. An entry marked locked, such as a watch already stood, does not move.

A schedule showed one day at one scale: an hour of a crowded watch could not be read more closely, and the crew could not move to tomorrow's rota from the schedule itself. Zoom in and Zoom out widen and narrow the hours in two steps, keeping the same time in the middle of the view. Given onNavigate, Previous day, Today and Next day ask the caller for another day, which works out the new range in the vessel's day. The controls are named in all six languages.

A new toast appeared farthest from the edge the stack is anchored to, on top of a stack at the bottom, so the newest message was the one the eye reached last, and a toast closing at the edge moved the whole stack. Only three showed by default, and a fourth waited out of sight to appear seconds later. The newest toast now stands nearest the edge, at the bottom for a stack at the bottom and at the top for one at the top, and the older ones glide away from the edge to make room. Every toast shows by default, a stack taller than the screen scrolling; limit still sets how many show, with the toasts that wait for the crew always among them.

A leaving toast's place stayed empty while it slid out, and the others moved in only once it was gone, two motions with a gap between; they now glide into its place as it slides out, in one 200 ms motion, and stay there when it is removed.

bosund's component=money (with currency_field), rating and signature draw those inputs in a schema form, the expense amount and its currency as one money input and a place's or contact's rating as stars; a list shows a money column as the amount with its currency and a rating column as its stars, and passes the crew's own currency and the day's rates to its forms.

A place's holding or a marina had no rating control, and an average no picture. The rating is a row of steps on Base UI's radio group: the pointer previews, a press or a typed digit chooses, a press on the chosen step clears, and the arrow keys move through the steps. Read-only, it is one image named by its value, so an average such as 3.7 fills part of a step.

The kit had no way to show a rota: who stands which watch, which jobs fall when, who is off. Schedule lays out one day, one lane per crew member or piece of equipment, each entry where its hours fall with its title and hours. The hours run across the top with their reference; now is a line down every lane; the time between two entries in a lane, such as rest between watches, is written on a dotted line; a lane can carry a note in place of its entries, and a summary sums the day up. An entry is named in full and, given renderDetail, opens its detail in a popover. On a narrow screen the hours scroll sideways while the lanes' names stay put.

A watch handover, a delivery or a guest's waiver had no way to be signed on the screen. The signature input is a pad in an outlined box with a line to sign on: each stroke is smoothed and kept as SVG path data, so the value is a standalone SVG of a few kilobytes in the page's ink color. Undo, redo and clear sit at the box's end, with Ctrl+Z and Ctrl+Shift+Z on the pad; pointerTypes can limit drawing to a stylus.

An expense or a fuel fill was a plain number beside a separate currency, so "151,20" on a German keyboard was refused and a receipt in lira said nothing of its cost in the vessel's own currency. The money input puts the currency at the start of the field, takes the amount with either separator, writes it back the crew's way, and, given the ECB rates bosund holds, shows the amount in the crew's own currency under the field with the day of the rates.

Three brief toasts shown after one that stays until dismissed pushed it out of sight until they left, since the limit took the newest whatever their kind; a toast that waits for the crew (persistent, an error or attention message, a running task) now always shows, and the brief ones take the places left, newest first, with the older ones waiting.

The pencil sits to the right of the title, centered on it, and the pencil, save and cancel are drawn small, each with its 48 px touch target kept around it, so the controls no longer outweigh the title or push the content below down a row.

"93" typed on the year is 1993 and "20" is 2020, or 1920 when minAge makes 2020 too recent: the latest year ending in the two digits that the bounds allow, with four digits still making any year; in the open year list, two digits jump to that year.

A toast took a swipe down (up at the top) as well as to the right, but on a touch screen the browser kept vertical drags for scrolling, so only a mouse could swipe down; it now takes a swipe to the right only, the same under a finger and a mouse, and a stack taller than the screen still scrolls.

In the open month list, "3" or "03" jumps to March and "12" to December, as the names did; on the month's segment, letters type its name in the crew's language, "ma" for March and then "y" for May.

A toast's actions were always 48 pixels tall, heavier than the kit's own buttons on a desktop and taller than a one-line toast needed; they now take the kit's small size under a mouse, the split button and its menu button included, and the touch target under a finger.

Under the calendar's month, Today and Yesterday choose those days in one press, in the picker's zone, each disabled when min or max excludes it.

A toast's actions took a column beside its text, between the text and the dismiss button, which squeezed the text into a narrow column, and the title sat higher than the controls beside it. The actions now stand on a row of their own under the text, starting at the title's edge, so the text keeps the toast's width. The dismiss button is centered on the title's line: the toast's top padding grows to half the difference between the touch target and the title's line height when that is more than the padding, and the button is drawn up exactly that far, so it never covers the toast's border. At the end it reaches the padding's edge, so its icon sits about as far from the edge as the kind's mark does. A countdown with no action keeps its seconds on the title's line.

The day's digits start at its segment's edge, with the label's text, and its focus ring began a step inside them, cutting the first digit; the day's ring starts a step before its edge.

The calendar, the date of birth's lists, the countries, the email suggestions and the saved crew opened behind a dialog the field sat in, such as the entity list's edit modal; each panel's positioner carries the overlay scope, so inside a dialog it takes the layer above it.

A toast beyond the provider's limit was drawn though it could not be pressed, and its time ran, so an Undo could run out before it was ever usable; it now waits out of sight with its timer held and gets its whole time, countdown included, once a toast in front of it leaves.

With the day, month or year list open, the crew type to jump to a choice: "1" then "4" to the 14th, "ma" to March, "1979" to the year, matched without accents in the crew's language; a pause of a second starts a new search, and Enter chooses as before.

A long task, such as an export, had no toast of its own: the caller showed one when it started and another when it ended, and the first stayed or left on a timer that knew nothing of the task. toast.track(task, { running, done, failed }) shows the running toast with a spinner as its mark and no timer, then replaces it in place with the result, whose timer starts then. Cancel is an action on the running toast; when an action closes it, the result is not shown, while a running toast the crew dismissed comes back with the result. A toast replaced in place now also takes the provider's default timeout when its new options name none, instead of keeping the old toast's.

A row with a checkbox is as tall as the checkbox's 48 px target, and its text sat at the top with the space below it; a one-line row's text now sits in the middle of that height with the checkbox level with it, and a wrapped row still reads from the top.

A schema form's suggestion field (a port, an agent) drew the kit input's own border and focus ring inside the outlined box, because .input:focus outweighed the outlined field's reset; a compound reset now removes the input's frame, focus ring, invalid border and touch height whatever order the stylesheets load in.

A toast about a record gave no way to reach the record: the crew had to find the saved route or the restored entry themselves. href makes the title a link to it, underlined in the title's color, through the provider's link component for a path inside the application, and following it closes the toast.

A toast had no place to say where its message came from or since when, so that went into the description, mixed with what happened and what to do. footer adds one line under a rule at the toast's foot, in the small dim type of a card's footer, lined up with the title and the description past the kind's mark: the source and the time, such as "Shore link, down since 13:12 UTC".

A record's modal showed its values with nothing about how they came to be, so a changed watch, phone number or amount could not be traced to a person or a time. The schema's history (bosund's ops audit trail, for crew, guests, contacts, expenses and places) gives the modal a line above the form, "Changed by Maya Lindqvist, 14:02 UTC", and Show previous values lists each field the last change set with its value before and after, written as the list writes values. The list asks for the history when the modal opens and again after a save.

A toast left with a 120 ms fade and a four-pixel drift, too short to see, and the toasts that stayed jumped into its place when it was removed. A toast at the end of the screen now slides out past the screen's edge while it fades over the medium duration on the exit curve, and one in the middle shrinks a little as it fades. The toasts that stay glide from where they were to their new places over the medium duration on the standard curve, measured on the screen so a stack anchored at the bottom glides too. The region at the end of the screen reaches the screen's edge, its toasts held off it by its padding, so a leaving toast is cut off only at the edge, and it no longer shows a horizontal scrollbar while one slides. Under reduced motion a toast only fades and nothing glides.

Every new record started empty, so an expense was dated by hand, a man-overboard mark typed from the plotter and the skipper's name retyped on every voyage. bosund's default tag gives a field its starting value: a literal of the field's type, now (the UTC date, time or date and time), position.lat and position.lon, skipper, or last, the value saved with the last record. The form fills them on a new record from defaultSources and lastValuesKey and counts them as unchanged, so an untouched form neither asks before it closes nor keeps a draft. The entity list finds the skipper in the fixed vessel's crew and takes the position from the page.

A toast's action sat centered against its text while the dismiss button stayed at the top, so a toast with a description showed them at two heights; every control now starts at the dismiss button's top and is as tall as it.

N opens a new record and / moves to the list's search while no modal is open and nobody is typing, Ctrl+S (Command+S) saves a schema form as Enter does, and the Add button, the search and Save name their keys in aria-keyshortcuts; DataTable takes searchRef and searchKeyShortcuts for the search field.

A list could act on one record at a time, a record like another had to be typed again, and a modal closed by Escape or outside it lost what the crew had typed. The table's rows take a checkbox when the schema allows delete or edit; the ticked rows show how many are selected, with Delete, which removes them together behind one Undo, and Change…, a form of the schema's choice fields that sets the same value on each with a PUT, undone the same way. Duplicate opens a new record filled from the one being edited, without its id. Closing a form that holds changes asks "Close without saving?" with Keep editing and Discard. A new record's form keeps its draft per entity and fixed values and offers Save and add another. useUndoToast (with onUndoable) holds a delete until its toast leaves without Undo, so the request never goes while Undo is still on the screen.

A message that repeated while on the screen showed its count as "×3" in dim code on a line of its own between the title and the description, easy to miss and gone from the title's row, and nothing marked the moment it came again. The count is now a badge after the title, on its row, that grows and fades in once on each repeat. The toast stacks one edge under itself for its second showing and two from its third, so a message that keeps coming reads as a small pile without a copy being stacked, and it keeps room below for its edges.

defaults fills a new record's form, as a duplicated record's values without its id, while the form still creates: no field saves on its own, Save and add another is offered, the values count as unchanged, and no draft is kept.

A toast took one action, as a label with no icon on a short text button, so a message with two useful follow-ups had to drop one, and Undo did not look like Undo. actions now lists what the crew can do, each with a label and an icon drawn before it. The first is the toast's button; the others open from the menu of a split button around it, named by the provider's moreActionsLabel, so a toast keeps one row of controls. The menu opens over the toast stack (the overlay scope marks it data-over-toast, which lifts the dropdown and tooltip layers above the toast's), a press on it no longer starts the toast's swipe, and the toast holds its timer while the menu is open. Every action is a touch target as tall as the dismiss button. The split button gains icon, adornment (the countdown's seconds), size and textCase, and the action menu's positioner carries the scope's stacking attributes, which lift a menu opened in a dialog above it as well. actionLabel and onAction are gone; the entity list's delete toast passes actions.

A new record's form closed half-filled lost what the crew had typed, a dialog could not tell whether its form held changes, and adding several records meant reopening the form for each. Given draftKey, a new record's values are kept in the browser until saved and the form opens again from them, saying so, with Start over; onDirtyChange reports when the values start or stop differing from those the form opened with; and addAnother offers Save and add another, which saves with { another: true } and empties the form for the next record.

A wrong call sign or an overlong name was reported only at Save, after the crew had moved on, and a long form gave no sign of which tabs still needed something. A field is now checked as the crew leave it, once they have typed in it, and checked again as they type while it shows a message, so the message goes as soon as the value is right; an empty field they move past says nothing until Save, and the kit's own inputs keep their own messages. A text field with a max_length counts its characters in its hint line. A tab or wizard step whose required fields are filled, with nothing to fix, is marked done.

A toast that offered Undo after a deletion gave no sign of how long Undo would stay, and the caller had no point at which to make the deletion final. countdown now shows the time left: the seconds after the action's label, in figures of fixed width, and a bar along the toast's foot that shortens each second. Both stop while the pointer or focus is on the stack or the window is in the background, as the toast's timer does. onClose runs once when the toast leaves without its action pressed, by its timer, its dismiss button or a swipe, which is where the deletion is made final.

A toast shown again with its key while on the screen kept its first timer unless the repeat named a timeout, so a message repeated on the provider's default timeout left as early as its first showing would have; every repeat now starts the timer again.

A read-only field the schema marks copyable (bosund's copy tag) shows its value with a copy button inside its box, which copies the value as stored, such as an MMSI's nine digits.

A delete asked once and then removed the record for good, and a list showed only what it had loaded, so a crew member added from another phone appeared only after a reload. Given onDeleted, useEntityList now deletes without asking: the record leaves the list at once, the request waits out six seconds, and Undo sends nothing (or, once the request went, creates the record again); useDeleteToast shows Deleted {label}. with Undo. Given subscribe, the list applies bosund's change reports: a record saved joins or replaces its old self when it belongs to the page's fixed values, a record deleted leaves. The records live in a store read through useSyncExternalStore.

A page that listed records wrote the list's URLs, its columns and its save and delete requests by hand, and the columns drifted from the fields bosund serves. useEntityList(entity, { request, fixed }) now builds the list's props from bosund's schema: the records from its collection (placeholders filled from fixed, the other fixed values as the query), a create with POST, an update with PUT and a delete with DELETE to its item, then the records again, and the form's choices, conditions, suggestions and record names from bosund's form endpoints. SchemaEntityList draws it, with a placeholder while the schema loads. Requests go through the page's request, so the kit itself makes none, and a request that never reached bosund says so.

The schema could not ask for most of the kit's inputs, and the form ignored much of what the schema said: a date's bounds, a slider's marks, a list of choices, the text under a group. The schema and the form are now extended both ways. A field's component asks for a slider (with its step, marks and a soft_max limit), a checkbox, two to five segments, cards with a sentence per choice, chips for a list of words (up to max_items), a password input, the YAML editor or the date of birth input (also chosen by autofill=bday); a list field with choices is a checkbox group; a date takes min_date and max_date; a text area grows to max_rows; a group's description shows under its heading, its tab and its wizard step. Each takes the width it needs. The entity list takes a column's column_width, wrap and column_hidden, offers a column picker when the schema asks, and passes the phone's country and the layout to its forms. bosund serves all of these from its form tags.

The form drew its maritime inputs (MMSI, phone, email, date) outlined, with the name on the box's edge, and every other field plain, with its name on a line above the box, so one form mixed two looks and each plain field spent a line on its name. Every field now draws outlined: the name on the box's top edge, the description and help as the box's hint, the error in its place, and a prefix and unit inside the box, read after the value. Lists, combo boxes, text areas and times sit in the outlined box as its control; the outlined field gains the text area's reset. A switch has no box and stands with its name beside it. The outlined field and input pages say when each is used: a form's fields outlined, a single field outside a form plain.

A list's columns were written by hand for every page, the list could not be searched or opened sorted, every list offered Add, edit and Delete whatever bosund allowed, and Delete deleted at the first press. The schema now carries the list: the fields marked as columns, sortable, filterable and searchable, the record's label and title field, the sort the list opens with, and the actions the crew may take. With no columns, the entity list builds its table from that metadata and shows each value as the crew read it: a choice by its label, a number with its prefix, unit and decimal places, a time in UTC. Delete asks once, naming the record. The schema form also passes a field's autofill to the browser, so it can offer a name, an email address or a phone number.

A form of eight groups ran several screens tall, the crew scrolling past contact and medical details to reach the field they came to change. The schema's layout, or the form's layout prop, now arranges the groups. A form of four or more groups and sixteen or more fields draws each group under a tab; on a form 48em wide or more with five or more groups, the tabs stand in a column beside the fields. wizard walks the crew through a record they are creating, a step per group, each checked before the next, with Back keeping what was typed and Save on the last step; a record being edited opens in tabs instead. A refused save opens the tab or step of the first field to fix, and a tab or step with fields to fix says how many.

A field's help sat behind a "Help" disclosure unless its schema set help_visible; it is now always shown under the field with its description, since help the crew have to open is help they do not read.

A change a reader does not need to compare or weigh, such as a wording fix or a spacing adjustment, may now be an entry of its title, the pages it touches and one sentence, without rules or pictures.

The form drew its lists as the browser's native select, its numbers as bare number fields with the unit beside them, and its times as plain inputs, so it looked unlike every other kit form. A list is now the kit's select, with "—" to clear it unless the field is required; a list of more than ten choices is a combo box that narrows to what the crew type, with a line saying so when nothing matches. A number is the kit's number input with its unit inside the field, and a time the kit's time input.

Lists, menus and popovers portal into the page body and stack on the dropdown layer, which is below the modal layer. One opened from a field inside a dialog, such as a select in the entity list's edit dialog, opened behind the dialog, and a press on an option landed on the field under it. A dialog now marks its content, an overlay opened from there carries data-over-modal, and the layer tokens lift that overlay's dropdown layer one step above the modal's.

Every field took the full width of the form unless its tag said half or a third, so a two-digit number, a switch and a date each filled a row, and a form of thirty fields ran several screens tall. A field now takes the share of twelve columns its value needs: a quarter for a switch, a number or a time, a third for a date or a short list, half for a name or a contact, the row for long text. A row of several fields that ends short widens its last text field to end square. A required field is always drawn, whatever its priority, and a group with no primary field draws its secondary ones instead of a heading over "More fields". The form measures its own width, so in a dialog it stacks as it would on a phone. Group labels, which bosund writes in lower case from the group's id, start with a capital.

Each look drew its sweep at one fixed strength: the Ice beam could be too faint on a bright desk and the Tactical wedge too strong over the echoes. A Beam slider under each radar example now sets the sweep from 0 to 200 % of the look's own, in steps of 10 %, for the tail, wedge, beam or comb of whichever look is chosen. At 0 % the sweep is not drawn at all; the light of a sweep is its opacity, so above 100 % it gives more light, up to full, in the same color. A look without a sweep shows the slider disabled and says why.

A ring's range was a bare number, and the unit was written only in the settings in a corner or on the bezel. A "Units on rings" switch under each radar example now writes NM after every ring's range, in type smaller than the number so the figures still lead. Until the switch is used, the look decides: the Chart look, which labels its north arm alone, writes the unit, as it did; the others leave it to the settings.

The radar page runs six simulated radars, and each made 819 spokes a second whether it was on screen or not. On the development server that held the page to about 8 frames a second, and the sweeps moved in jumps. A plotter screen now tells its controls whether it is in view, and an example holds its radar while it is not, as its pause button does; scrolled back, it carries on from where it stopped. With one or two radars running, the page draws at the display's frame rate.

The radar examples simulate a radar in the page, and filling a spoke took about 83 µs: six radars on the page at 24 rpm took most of the main thread. Each nearby vessel's beam weight, glint, sidelobe and course were worked out again for each of a spoke's 512 samples, and every sample measured its distance to both breakwaters and to the rain shower. They are now worked out once a spoke, and a sample measures a breakwater or the shower only in the stretch of range where the spoke can pass near it. A spoke takes about 60 µs.

bosund sends a radar frame every 40 ms, and at 24 rpm the antenna turns 5.8° in that time. The scope looks drew the sweep at each frame's last spoke, so the beam jumped 5.8° at a time, 25 times a second. The sweep now turns at the display's own frame rate: it keeps the rate the frames report, turns toward where the latest frame says it is, a little faster when behind and slower when ahead, and stops when the frames stop. The sweep layer is turned by its style alone, without rendering the page again.

The Ice look drew its scope in perspective, leaning back and turned to one side as a display seen from a seat. That squeezed the picture into an ellipse, so the range rings stopped being circles and a mile on the north arm was shorter than a mile on the east. The scope now faces the viewer, round, in the same gunmetal bezel. Round, the bezel is taller than the ellipse was, so the scope is drawn smaller to keep its bearings on the screen, and the display keys stand in a column down the left edge, as the zoom keys do on the right, clear of the bezel.

Compared side by side with their reference pictures, the two looks lacked what the references draw outside and over the picture. Ice now sits in a gunmetal bezel, tilted back and turned to one side as a display seen from a seat. A dark band carries the cardinal points and the screen's settings in Rajdhani. A scale is ticked inward from the glowing rim. The beam blooms toward the rim and flares where it meets the glass, and a reflection crosses the glass. Targets are small symbols by AIS class, and only the four nearest carry their particulars, each where it covers no other label or target. The buttons are console keys. Tactical's wedge now fades from its bright leading edge and lights the echoes under it. Its land is drawn dim under a faint grid, and its targets are boxed glowing dots. Its panels lean and set pale titles over green values, and the echo profile has a scale. Its controls are a slim bar of tabs under the scope.

A picker on each example switches the look: the plotter's own, or Tactical, Ice, Chart, Phosphor, Sonar, Target, Red glow or Amber, each built after a reference picture and drawing its own echo colors, ink, face, bezel, crosshair or grid, sweep, glow, target symbol and panels. The sweep follows the bearing of the latest spoke. The AIS targets from the simulated scanner are drawn at their reported positions in the look's symbol, with labels; the Tactical and Chart looks add panels with the range, resolution, own ship's position, the target list and the echo profile. Buttons pause the scan, show the targets and their labels, and filter rain and clutter; Tactical offers them as Scan, Track and Filter. The HUD looks letter in Rajdhani (SIL Open Font License), which the site serves from public/fonts. The Scope looks example shows the chosen look's reference picture beneath it: stock previews, kept on the page for comparison only.

The examples' scene now has a container ship on the offshore route, three ships at anchor east of the fairway, a tug towing a barge, a fast RIB without AIS, yachts racing off the island (one without AIS), and a racon on the west cardinal mark that answers Morse K for 20 s in every 40. Vessels run along their courses and back, so the scene never runs ashore, and own ship turns at the top of the approach. The scanner reports AIS for the vessels that carry it at the intervals ITU-R M.1371 sets, from the position at each report, so a report lags the echo between reports as it does on a real screen.

halftone draws the echoes through a grid of round dots, as a stylized display shows land and targets; it is a look and a bridge screen keeps it off. The picture's water and rim read --radar-ppi-background and --radar-ppi-border before the theme's --bg2 and --border-bright, so a screen around it can give the picture its own surroundings.

Each example is a plotter's radar page with a zoom in and a zoom out button, stepping the range scale through 1/8, 1/4, 1/2, 3/4, 1, 1.5, 2, 3, 4, 6 and 8 NM, and a selector for the range rings: off, the plotter's choice for the scale (three on a scale of three times a power of two, four otherwise, two on 1/8 NM), or two, four or six. The simulated scanner switches scale in place, so the scene carries on and the next frame is swept on the new scale; its terrain now reaches past 8 NM. The bearing scale sits outside the picture: a tick every degree, longer every 5° and 10°, and every 5° numbered in small three-digit figures, upright however the scale turns heading-up, with own ship's heading marked on the rim.

The picture's water is transparent in every palette, so it lies on the component's own background, the theme's, rather than on black. With no palette the echoes follow the theme around the picture: RADAR_PALETTE_GREEN on a dark theme, the new RADAR_PALETTE_DAY (a pale blue fringe round a dark green core) on a light one, and RADAR_PALETTE_NIGHT on Night, checked four times a second so a theme change reaches the picture at once. Both renderers draw from RGBA palette tables; between water and a color only the alpha ramps, so an echo's edge fades into the background. The example screen and marks take the theme's background, green and text colors.

The examples run a simulated Navico scanner that writes bosund's radar WebSocket frames: 2,048 spokes a revolution at 24 rpm, 512 samples in sixteen levels, north-referenced angles. decodeRadarFrame reads them, refusing a frame whose length, angle, heading or range is wrong, and the picture takes the spokes it returns. The scene has a coast with radar shadow behind its hills, an island, five ships under way with wakes, buoys, breakwaters, a drifting rain shower, sea clutter, the main bang and now and then another radar's interference, with own ship steaming north at 7 kn. The picture is drawn on WebGL2 by default, with the CPU renderer where the browser has none; the sweep line is gone, since the plotters draw none. The intensity buffer has 2,048 bearings, one per spoke. The palettes are banded, so the weak levels fringe each echo, and a plotter palette with the Zeus3S's red cores is offered for a display that shows no alerts. The example marks draw the plotter's graticule and the page is a plotter screen with its settings at the top left, larger than before.

trails takes off, relative or true. Relative trails are the plotter's own aged echo and show how a target moves relative to own ship. True trails are radar_pi's: a grid over the picture, fixed to the ground and moved with own ship (ownShip), in which each cell remembers how long ago it held an echo; a trail is drawn only where the echo has gone, in its own colors (trailPalette, blue by default), so a fixed mark leaves none however own ship moves. trailSeconds gives how long a trail lasts, the way the plotters offer it, and replaces the per-second fraction. The WebGL2 renderer runs the true trail as a third pass with the age in 16 bits, so a ten-minute trail still ages in whole steps; the blanking uniform is declared for the eight sectors it carries.

The threshold was applied to the latest echo at each bearing, so when the sweep repainted a bin with anything weaker than the threshold, such as the noise floor every bin carries, the trail behind a target vanished. The texels now carry the firmware's four channels: the latest echo, the shown intensity, the original intensity that set it, and the fraction of an 8-bit step the aging has not yet taken. The threshold applies to the original, so a trail lasts until it has aged out.

With trails off the picture showed only the spokes of the latest frame: bosund's WebSocket sends the spokes swept since the previous frame, about a sixtieth of a revolution, so the picture was a thin wedge behind the sweep. Each frame now says which bearings it covered, and a bearing it did not cover keeps the echo it had, on both renderers.

The picture kept its echoes and trails when rangeNm changed, so for the rest of a trail every echo from the old scale was drawn at the wrong distance: an echo received at 2 NM on the 3 NM scale showed at 4 NM on the 6 NM one. A range change now clears the echo buffer and both renderers' trail buffers, and the next frame starts an empty picture.

The spoke's angle was read as bow-relative and the whole picture was turned by the current heading for north-up. bosund's radar WebSocket sends north-referenced angles, because its spoke ring adds the heading when the spoke arrives, so the picture was turned twice; and every echo still on screen swung with each yaw, wherever the vessel was heading when it was received. The spoke field is now angle, north-referenced: the picture stores each echo at its true bearing, north-up draws it as stored, heading-up turns it by the heading, and blanking sectors are measured from the bow.

The picture held each spoke until the next one in its frame, but it found the next one by sorting the frame's spokes by bearing. When the sweep crossed north inside a frame, sorting put the last spoke before the gap across the wrap, and that spoke was painted up to 64 bins, about 22°, past where the radar sent it. The spokes now hold in the order the radar swept them, with the step measured round the circle.

NauticalChart, NavigationBar, CommandPalette, RadioCards, SegmentedRadioGroup and TaskDialog describe their roles explicitly. Menu, Dialog, Field, Select, Tabs, Autocomplete and Combobox offer named parts. Input exposes string change events, field recipes share labeling and validation, selections accept custom children, and callbacks use value, checked and open conventions. Existing imports remain compatibility adapters. Documentation examples use canonical APIs, and props tables read exported contracts for compound parts.

The error-breakdown example uses item inspection with a token-colored active segment outline. Its tooltip displays only the hovered failure category, exact count and percentage. ChartTooltip exposes Recharts' shared inspection option while retaining the chart root's default when unset and omitting the shared cursor for item inspection. Item tooltips can extend below a compact plot so they do not cover its selected mark. The complete breakdown remains visible in the ranked rows and source table.

Checkbox and CheckboxGroup cover independent choices and select-all; RadioGroup covers one choice from a visible set. Groups include descriptions, errors, native field names and wrapping horizontal layouts. Interactive examples demonstrate mixed selection, validation, disabled values, submission and reset.

ActionMenu offers commands, descriptions, shortcut hints, groups, submenus, checkboxes and radio choices. SplitButton pairs a primary command with a separately named alternatives menu. The navigation account control uses the shared menu. Examples keep confirmation and result handling in the caller.

Line-chart examples show daily P50, P95 and P99. Custom Recharts compositions through ChartContainer show a latency distribution with a P95 marker, exclusive failure shares, and model cost versus response time. The analytical series palette and ChartPanel appearance reproduce the reference's blue family and quiet dark framing. Card's metric appearance uses a large supplied value and an anchored comparison footer. Sparkline accepts a thin bar width, muted context color and an explicitly selected interval; a missing selected observation remains missing. Numeric bar axes also support controlled histogram windows.

Breadcrumbs disclose long paths, Pagination supports local state and real URLs, Steps exposes explicit progress, and CommandMenu supports grouped search, loading, empty states and drill-down. NavUser shows identity and account actions in a panel or rail; the app shell provides a persistent navigation footer. Navigation groups use a larger gap than individual rows, and secondary destinations can include descriptions. Interactive examples cover browser history, form validation, account actions and a responsive three-region workspace. The overview explains how the patterns combine, while existing tab and wizard guides link their responsibilities.

Modal offers five sizes, top placement, body or whole-dialog scrolling, supporting footer content and an optional named close button. Dismissal requests identify their source; callers can configure Escape and backdrop behavior and block dismissal during a pending action. Focus targets support entry and return. Interactive examples cover layout choices, protected drafts, validation, saving, retry and long content.

The page review expands foundation decisions, component usage and instrument integration guidance. Numeric, time and chip pages include additional live specimens. Alert guidance uses shared list and lifecycle components and distinguishes their attention behavior. Consumer pages explain report structure, exports and adoption; typography, spacing, priority ordering and depth-reference descriptions follow the implemented contracts.

ScatterChart plots independent pairs, PolarChart preserves numeric angular spacing, and StateTimeline clips explicit intervals with unknown periods. ChartRange provides controlled pan, zoom and follow-live requests. Line and area plots share synchronized inspection, bounded continuity and drag range requests. A line can draw the shortest circular increments while retaining original inspection values. Charts accept a persistent, caller-formatted summary bubble with a selectable corner. The history guide documents protected transport, source discovery, processing provenance, directional aggregation, state validity and consumer loading.

The foundation names the CSS source and generated output, documents reading and diagram typography, and distinguishes template measure from the site layout. Live specimens and a four-theme matrix show diagram roles and independent scopes. Guidance covers editorial color, SVG styles, Markdown and email exports, and role changes. Mermaid's navigation and guide describe its general purpose; report examples remain available.

The report flowchart renderer adds rounded boxes, neutral groups, service styling, open arrowheads and left-aligned group headings. Optional connection classes compile with the current theme without introducing CSS-variable syntax that Mermaid cannot parse. Authored connection styles retain precedence. Multiline HTML labels are parsed as HTML, avoiding partial SVGs caused by XML line-break errors. Optional complete geometry preserves the reference's arrangement with editable Mermaid content; ordinary diagrams keep automatic layout. Missing placements fail visibly rather than dropping a node. Label typography is isolated from the kit's generic label class. Component examples fit the documentation column and keep “On this page” visible. Desktop preview provides the larger canvas. The before image records the preceding renderer; the after includes the architecture example.

Report metadata groups category identity, an optional issue reference, status and distribution badges, audience, publication details, tags and expandable source evidence. The reports library maps category icons and accents from its validated frontmatter. Decision records show rationale and ownership; milestone timelines distinguish achieved, current and planned checkpoints; action lists keep owners, deadlines and source task links together. Wide documentation pages show a desktop report canvas with metadata across the header and planning blocks side by side. Both sites share the components and preserve their static data in search and Markdown exports. The metadata before picture is captured from the preceding production build; the after includes the expanded example.

AreaChart supports overlapping and stacked amounts; PieChart supports pie and donut compositions. Missing parts suppress a pie and incomplete stacks retain gaps. LineChart and overlapping AreaChart accept typed intervals whose bounds appear in inspection and source tables. Context emphasis makes a raw comparison trace subordinate to the filter output, while preserving its observations. The history guide records stream selection, forecast quantile mapping and the proposed asynchronous-window integration; no transport or filter runs inside the kit.

Bosunkit owns report metadata, facts, metric strips, panels, notes, processes, commit rows, figures and Mermaid. Editorial accents, icon-led metric cards and process stages add visual variety. Highlight and quote blocks give conclusions and sourced observations a clear place in a report, using theme-aware foundation colors. Live component pages include usage guidance, source examples and generated props. Both sites register the same MDX components and Mermaid fence transform. Lazy diagram rendering preserves source, handles errors and serializes scoped themes so adjacent diagrams cannot exchange palettes. The reports library retains its content and routing.

Line and bar charts use a typed numeric series registry for labels, palette slots, patterns and value formatters. Grouped, stacked and horizontal bars keep zero visible; line charts retain missing-data gaps and numeric time spacing. A responsive container supports direct Recharts composition through a private theme adapter, and a drawing-agnostic panel holds controls, legend and source information. Public examples use illustrative data.

Eight forms cover daily commits, weekly progress, features, technical deep dives, audits, benchmarks, plans and investor updates. Each has a live outline, evidence guidance and an MDX download. Classification labels describe distribution intent; access control belongs to the report host. Agent notes identify the canonical sources and keep private investor content out of public starter files.

Live examples cover a multi-metric summary, a table of comparable trends, daily bars with a switchable trailing mean, and stacked composition bars. Guidance explains chart selection, zero baselines, derived metrics and source evidence. Example values are clearly marked as illustrative.

Previous and Next follow the sidebar order and sit beneath the article, with directional arrows and full link targets. The table of contents uses Fumadocs anchor tracking on desktop and mobile. Its own scroll container reveals the current entry without scrolling the page or adding motion.

Four templates cover quarterly reports, shareholder emails, fundraising briefs and personal outreach. Each has HTML and plain-text downloads; the live gallery previews the actual generated file. The quarterly versions share an editorial source with a founder's note, metrics, explanation, product and team updates, risks and requests. Email uses inline styles and fallback fonts; reports embed IBM Plex. Placeholder facts prevent a starter from presenting invented performance or accounting claims. Email-client delivery testing remains pending.

The presentation consumer page defines eight layouts, their content, safe margins, themes and chart/source guidance. The gallery offers a layout picker, Day and Dusk, safe-area guides and speaker notes. An editable HTML starter embeds its fonts and screenshot and provides keyboard navigation and one slide per printed page. Native PowerPoint export remains pending. The MDX page uses a relative component import so the development server resolves it correctly.

The language example's scope wrapper shrank to the header's intrinsic width, squeezing its traffic rows. The width now belongs to the outer example frame. Sidebar section labels become keyboard-operable disclosures, with the active page's section open and an Overview link for each folder. Foundations groups color and surfaces, layout, type and identity, and interaction in both the sidebar and overview. The home intro uses the shared logo.

Buttons, input and select borders, navigation choices and menu focus share semantic roles. Primary action text uses a darker teal in Day and Bright to remain readable on tinted button backgrounds. Input and select invalid borders use a neutral dashed cue with a separate focus ring. Switches expose keyboard focus and a disabled treatment while retaining their checked state. The Night interface stays red, and raised-pressed palettes retain their existing treatment. Browser checks cover actual primary-button contrast and combined control states.

The document reset overrode component styles because its top-level CSS layer came after every kit sublayer. Buttons inherited larger body text and lost their label weight, foreground and border. Document styles now occupy kit sublayers between reset and components, so the existing label role and presentation size apply. A browser check verifies the actual document cascade in all four themes at default and helm sizes.

The three portals inherited the page root, so a locally themed control could open an overlay in another palette. They now use the same scope attributes as the shared popover. The Themes page demonstrates the list, dialog and tooltip in a local Day region, and browser tests cover all four themes with a scoped size and language.