diff --git a/api/test/nowplaying-data.test.js b/api/test/nowplaying-data.test.js
index beba3eb6..c0654160 100644
--- a/api/test/nowplaying-data.test.js
+++ b/api/test/nowplaying-data.test.js
@@ -26,7 +26,7 @@ test('plex names the player from the device title', async () => {
               title: 'Arrival',
               duration: 6000,
               viewOffset: 3000,
-              Player: { state: 'playing', title: 'Living Room TV', product: 'Plex for Apple TV' },
+              Player: { state: 'playing', title: 'Living Room TV', product: 'Plex for TV' },
             },
           ],
         },
@@ -62,14 +62,14 @@ test('jellyfin prefers DeviceName over Client', async () => {
   const r = await dataFn(
     ctxFor({ provider: 'jellyfin', jellyfinUrl: 'https://jf.example.com', jellyfinKey: 'k' }, [
       {
-        DeviceName: 'Bedroom iPad',
+        DeviceName: 'Bedroom Tablet',
         Client: 'Jellyfin Web',
         NowPlayingItem: { Type: 'Movie', Name: 'Dune', RunTimeTicks: 100 },
         PlayState: { PositionTicks: 25, IsPaused: true },
       },
     ]),
   );
-  assert.equal(r.sessions[0].player, 'Bedroom iPad');
+  assert.equal(r.sessions[0].player, 'Bedroom Tablet');
   assert.equal(r.sessions[0].state, 'paused');
   assert.equal(r.sessions[0].progress, 0.25);
 });
diff --git a/docs/design-system.md b/docs/design-system.md
index 673cf08b..2a87ce48 100644
--- a/docs/design-system.md
+++ b/docs/design-system.md
@@ -2,7 +2,7 @@
 
 The visual system both pages share. It lives in `ui/css/tokens.css`.
 
-Values come from Apple's iOS, iPadOS and macOS design kits. Both the dashboard and the settings page follow iOS on a phone and iPadOS on a tablet or desktop.
+Values are measured from a reference design kit, not chosen.
 
 Dark values only. No stylesheet declares a `prefers-color-scheme` rule.
 
@@ -10,13 +10,13 @@ Dark values only. No stylesheet declares a `prefers-color-scheme` rule.
 
 Pick from the lowest layer that answers the question.
 
-**Palette.** The system colours named by hue: `--sy-teal`, `--sy-red`, `--sy-gray4`. Twelve hues and six greys. Each has a `-hi` partner holding an increased-contrast value, and the `prefers-contrast: more` block swaps the whole palette to the `-hi` set.
+**Palette.** Twelve hues and six greys, named by hue: `--sy-teal`, `--sy-red`, `--sy-gray4`. Each has a `-hi` partner holding an increased-contrast value. The `prefers-contrast: more` block swaps the palette to the `-hi` set.
 
-A rule should not name a palette entry directly. The palette exists so the layers above it have something to point at.
+Do not name a palette entry in a rule. The layers above point at it.
 
-**Roles.** What a colour is for: `--accent`, `--danger`, `--warning`, `--success`. Each points at a hue. Changing the accent is one line.
+**Roles.** What a colour is for: `--accent`, `--danger`, `--warning`, `--success`. Each points at a hue.
 
-**Semantic.** What a colour is applied to, in the kit's own sets.
+**Semantic.** What a colour is applied to.
 
 | Set | Tokens | Use |
 | --- | --- | --- |
@@ -24,15 +24,15 @@ A rule should not name a palette entry directly. The palette exists so the layer
 | Fills | `--fill-primary` through `--fill-quaternary` | The tint behind a small control |
 | Separators | `--separator`, `--separator-opaque` | Dividing content |
 | Backgrounds | `--bg-primary`, `--bg-secondary`, `--bg-tertiary` | The three layered surfaces |
-| Backgrounds, elevated | `--bg-elevated-primary`, `--bg-elevated-secondary`, `--bg-elevated-tertiary` | The same three, for content over a sheet |
+| Backgrounds, elevated | `--bg-elevated-primary`, `--bg-elevated-secondary`, `--bg-elevated-tertiary` | The same three, over a sheet |
 
-Two singletons sit beside them. `--bg-primary-light` is the opt-in light widget card, the one surface that renders in the light theme. `--control-knob` is the white of a knob on a slider or a switch, which is drawn at full white in both themes.
+Two singletons sit beside them. `--bg-primary-light` is the opt-in light widget card. `--control-knob` is the white of a slider or switch knob, full white in both themes.
 
 ## Two limits on the semantic layer
 
-**Label levels below primary do not clear WCAG on this project's cards.** The ramp assumes the surfaces it was drawn against. Use `--sy-a11y-dim` for text that has to be read on a card; use a label level for hierarchy. `ui/test/contrast.test.mjs` computes the ratios and fails on a regression, so this is enforced rather than remembered.
+**Label levels below primary do not clear WCAG on this project's cards.** Use `--sy-a11y-dim` for text that has to be read on a card. Use a label level for hierarchy. `ui/test/contrast.test.mjs` fails on a regression.
 
-**The dashboard's glass is not built from Fills.** Its overlays are pure white at low alpha over a wallpaper. The kit's fills are grey-tinted and assume an opaque surface beneath. Substituting one for the other changes the look.
+**The dashboard's glass is not built from Fills.** The glass is white at low alpha over a wallpaper. Fills are grey-tinted and assume an opaque surface. Substituting one for the other changes the look.
 
 ## The face
 
@@ -42,15 +42,15 @@ One stack, everywhere:
 -apple-system, BlinkMacSystemFont, system-ui, sans-serif
 ```
 
-`--font-ui` holds it for the two pages. `ui/test/font-stack.test.mjs` fails on any other spelling, including in the widget guide and the widget template.
+`--font-ui` holds it. `ui/test/font-stack.test.mjs` fails on any other spelling, including in the widget guide and the widget template.
 
-Do not name `SF Pro Display` or `SF Pro Text`. `-apple-system` resolves to the system face and picks the optical cut for the size it is used at, Text below 20 and Display at 20 and above. Naming a cut pins it. The dashboard used to ask for Display and the admin page for Text, and most widgets asked for Display at 11px, which is the cut meant for large sizes.
+Do not name an optical cut. The stack resolves to the system face and picks the cut for the size it is drawn at: Text below 20, Display at 20 and above. Naming a cut pins it.
 
-`monospace` is the exception, for the code spans in the admin hints.
+`monospace` is the exception, for code spans in the admin hints.
 
 ## Type
 
-Eleven text styles, at the default Dynamic Type step. Three tokens each: `--fs-<style>`, `--lh-<style>`, `--tr-<style>`.
+Eleven styles at the default step. Three tokens each: `--fs-<style>`, `--lh-<style>`, `--tr-<style>`.
 
 | Style | Size | Leading | Tracking |
 | --- | --- | --- | --- |
@@ -68,7 +68,7 @@ Eleven text styles, at the default Dynamic Type step. Three tokens each: `--fs-<
 
 Headline is Body at semibold. `--fw-headline` carries the weight.
 
-Set all three tokens together. A size without its leading and tracking is a third of a style, and `ui/test/type-scale.test.mjs` fails on it.
+Set all three tokens together. `ui/test/type-scale.test.mjs` fails on a size without its leading and tracking.
 
 ```css
 .rl {
@@ -78,7 +78,7 @@ Set all three tokens together. A size without its leading and tracking is a thir
 }
 ```
 
-Line height is stored unitless and tracking in `em`, not as the published pixel values. The dashboard multiplies its sizes by `var(--sc)` and a reader can zoom; a ratio and an em follow the size they are used with, where a pixel leading would hold still and the style would come apart at every size but the default. The test multiplies each ratio back out and checks it still lands on the published pair.
+Leading is stored unitless and tracking in `em`, never as pixels. Sizes are multiplied by `var(--sc)` and a reader can zoom, so both have to follow the size they are used with.
 
 On the admin page:
 
@@ -90,13 +90,13 @@ On the admin page:
 | Segmented options, dialog body text, small glyph buttons | `footnote` |
 | The version line and the mobile tab bar | `caption-2` |
 
-A grouped list's header and footer are `footnote`, not a caption. Caption 1 sits below the size either is drawn at.
+A grouped list's header and footer are `footnote`. Caption 1 sits below the size either is drawn at.
 
 ### Steps
 
-The table above is the default Dynamic Type step. A page can run the whole scale at a smaller step, which is how a denser screen is handled: the same eleven styles at smaller sizes, never a size chosen outside the scale.
+A page can run the whole scale at a smaller step. The same eleven styles at smaller sizes, never a size chosen outside the scale.
 
-A document opts in with a class on `<html>`, and the step applies only where the layout is not a phone. The admin page carries `type-small`, so its desktop panel runs at the Small step and a settings row is 15. On a phone it falls back to the default step and a settings row is 17, matching the phone settings design.
+A document opts in with a class on `<html>`. The step applies only where the layout is not a phone. The admin page carries `type-small`, so its desktop panel runs at the Small step and a settings row is 15. On a phone a settings row is 17.
 
 | Style | Default | Small |
 | --- | --- | --- |
@@ -107,32 +107,32 @@ A document opts in with a class on `<html>`, and the step applies only where the
 | `footnote` | 13/18 | 12/16 |
 | `caption-1` | 12/16 | 11/13 |
 
-Tracking is republished per step rather than inherited. There is one absolute tracking per style, so the em that reproduces -0.43 at 17 does not reproduce it at 15. The test checks every step against the same published pairs.
+Tracking is republished per step. There is one absolute tracking per style, so the em that reproduces -0.43 at 17 does not reproduce it at 15.
 
-Adding a step is a block of eleven declarations and an entry in `ui/test/type-scale.test.mjs`. Moving a page between steps is one class.
+Adding a step is eleven declarations and an entry in `ui/test/type-scale.test.mjs`. Moving a page between steps is one class.
 
 ### Off the scale
 
 Six rules do not use it, on purpose.
 
-- `.rico`, `.icon-prev`, `.fp-ic`, `.ipv`, `.kv-box::after` size a single character centred in a fixed box. That is a mark, not text, and a text leading and tracking would push it off centre.
-- `.bsep` is an uppercase separator label. Uppercase needs positive tracking, and the scale's values are for sentence case. `.dlg-sec` and `.sr-section` keep their own tracking for the same reason while taking their size from the scale.
+- `.rico`, `.icon-prev`, `.fp-ic`, `.ipv`, `.kv-box::after` centre a single character in a fixed box. A text leading and tracking would push it off centre.
+- `.bsep` is an uppercase separator label. Uppercase needs positive tracking. `.dlg-sec` and `.sr-section` keep their own tracking and take their size from the scale.
 
 ## Control geometry
 
-Measured from the kit, not chosen. `ui/test/control-geometry.test.mjs` holds them.
+`ui/test/control-geometry.test.mjs` holds these.
 
 | | |
 | --- | --- |
 | Settings row | 52 tall |
 | Row carrying two lines | 68 tall |
 | Row side padding | 16 |
-| Separator | 1 tall, inset 16 at the leading edge, flush at the trailing |
+| Separator | 1 tall, inset 16 leading, flush trailing |
 | Grouped list radius | 26, as `--sy-radius-group` |
 | Switch | 64 × 28, knob 38 × 24 inset 2, travel 22 |
-| Slider | track 6, knob 20, one design for all of them |
-| Outer margin | 16 on a phone, 20 on a tablet or desktop |
-| Group header and footer | text inset 16, so it aligns with the row's label |
+| Slider | track 6, knob 20, one design for all |
+| Outer margin | 16 on a phone, 20 otherwise |
+| Group header and footer | text inset 16 |
 | Sidebar | 320 wide, items 44 tall, selection a full pill |
 | Tab bar selection | covers the whole tab, radius 16 |
 | Segmented control | 32 track, 28 segments, capsule |
@@ -142,50 +142,38 @@ Measured from the kit, not chosen. `ui/test/control-geometry.test.mjs` holds the
 | Between a group and the next heading | about 34 |
 | Small button on touch | drawn at 30, hit area extended to 44 |
 
-The switch knob is a capsule, not a circle. That is a shape change, so resizing the old circle does not get you there.
+The switch knob is a capsule, not a circle.
 
-Sliders are the deliberate departure from the kit. It draws the system slider with a 2 × 24 line handle, too small a thing to find and drag on a phone, and a colour slider as a 34 bar with a knob the height of the bar. Both are rejected: there is one slider in this project, a 6 track with a 20 round knob, and the handle is declared once for all of them because they previously carried a copy each and drifted apart.
+On touch a slider is padded out to a 44 target and the paint is clipped back to the track. Clipping to the content box shrinks each corner by the padding on that axis. The padding is vertical only, so the two radii are set separately. A single radius draws ends that taper to a point.
 
-On touch a slider is padded out to a 44 target and the paint is clipped back to the track. Clipping to the content box shrinks each corner by the padding, so the radius is raised by the same amount or the track draws with square ends.
+`--sy-radius-group` is separate from `--sy-radius-lg`. Only the grouped list is rounded to 26; the panel, the dialogs and the toast keep 14.
 
-`--sy-radius-group` is separate from `--sy-radius-lg` on purpose. The panel, the dialogs and the toast keep 14; only the grouped list is rounded to 26.
+Derive a radius that rounds something whose size varies. An app icon is drawn at 72 with a label and 78 without, and a widget tile scales with the dashboard.
 
-A group's header and footer align with the row's label, not with the group's edge. They are separate elements sitting outside the group, so they carry the row's 16 inset themselves.
+`.btn.sm` outranks `.ic`. Name an icon button again in the touch block or it takes a text button's side padding.
 
-The tab bar's pill is not a stadium. Its label runs along the bottom edge, which is where a stadium's curve is tightest: at 6 from the bottom a 26 radius cuts about 9 in from each side and clips the ends of a long label. 16 cuts in under 4. The test checks the geometry rather than the number.
+The choice rows draw a segmented control on radio inputs. The inputs stay: the form reads them and a screen reader announces them. The input is 0 by 0, so the segment wears the focus ring.
 
-Every inline action keeps its drawn size on touch and has its hit area extended to 44 instead. Making 44 the drawn box turns an action into a slab and pushes it away from the text it belongs to.
-
-`.btn.sm` is two classes and outranks `.ic`, so an icon button has to be named again in the touch block or it takes a text button's side padding.
-
-A dashboard row drops its address on a phone. It truncates to a fragment at that width and crowds the name and the pills it shares the row with.
-
-The pill takes 6 above and below, and the bar gives back the same from its own padding, so adding it did not change the bar's height.
-
-A radius that rounds something whose size varies has to be derived, not written down. An app icon is drawn at two widths, 72 with a label and 78 without, and a widget tile scales with the dashboard. Literal radii were right at one size and wrong everywhere else.
-
-The choice rows are a segmented control drawn on the radio inputs that were already there. The inputs stay, because the form reads them and a screen reader announces them; only the dot goes, since the selected segment is the indicator. The input is 0 by 0, so the segment wears the focus ring.
-
-The group cannot clip its rows, because it keeps `overflow: visible` so a dropdown can escape it. The first and last visible rows carry the corner radius themselves instead, or a row's hover fill squares off the corners.
+The group keeps `overflow: visible` so a dropdown can escape it. The first and last visible rows carry the corner radius themselves, or a row's hover fill squares off the corners.
 
 ## Widgets
 
 A widget is a separate document in an iframe. It keeps its own stylesheet and does not load `tokens.css`.
 
-It cannot name a token. Most widget colours sit in canvas fills, SVG attributes and data modules, where a `var()` is not a colour. A widget carries the values instead, and two tests keep them from drifting.
+It cannot name a token. Most widget colours sit in canvas fills, SVG attributes and data modules, where a `var()` is not a colour. A widget carries the values instead.
 
-**Colour.** Every colour must be a palette value or be listed in `ui/test/widget-colours.test.mjs` with what it is. The list covers artwork and colours that are not the project's to choose: the GitHub contribution scale, the Plex, Jellyfin and Emby brand colours, the weather illustration set, and the fallback covers the books widget draws when there is no artwork. A second test removes an entry once nothing uses it, so a stale exemption cannot let the next colour through unexamined.
+**Colour.** Every colour must be a palette value or be listed in `ui/test/widget-colours.test.mjs` with what it is. The list covers artwork and colours that are not the project's to choose. A second test removes an entry once nothing uses it.
 
 **The face.** A widget must spell the font stack the same way as everything else.
 
-**Size.** Widget text is not on the type scale. The scale stops at 11 and the densest tiles go down to 6.5, so the sizes are snapped to a step where one is within a point and left alone below that.
+**Size.** Widget text is not on the type scale. The scale stops at 11 and the densest tiles go to 6.5. Sizes are snapped to a step where one is within a point.
 
 ## Page-scoped tokens
 
-A surface particular to one page is declared in that page's own `:root`, not here. `--pane` and `--cp` on the admin page, `--glass-bg` and `--dock-bg` on the dashboard. These are not part of the system.
+A surface particular to one page is declared in that page's own `:root`. `--pane` and `--cp` on the admin page, `--glass-bg` and `--dock-bg` on the dashboard. These are not part of the system.
 
 ## Rules
 
 A colour written as a literal outside `tokens.css` fails `ui/test/css-tokens.test.mjs`. The same test checks that every `var()` names a token that exists. `ui/test/palette-values.test.mjs` pins each palette entry to its reference value.
 
-`#fff` and `#000` are allowed as ink on an arbitrary coloured fill, where the colour underneath is chosen by the user and no token can describe it.
+`#fff` and `#000` are allowed as ink on an arbitrary coloured fill, where the colour underneath is user-chosen and no token can describe it.
diff --git a/docs/frontend.md b/docs/frontend.md
index 47df9283..e6821799 100644
--- a/docs/frontend.md
+++ b/docs/frontend.md
@@ -9,10 +9,14 @@ The admin writes the whole config with `POST /api/config`; the dashboard reads i
 
 ## Browser support
 
-Safari and iOS Safari 16.2 and newer, and current Chrome, Edge and Firefox. 16.2 is where `color-mix()` lands, which the admin's category chips derive their tints from.
+WebKit 16.2 and newer, and current Chrome, Edge and Firefox. 16.2 is where `color-mix()` lands, which the admin's category chips derive their tints from.
 
 There is no build step and no autoprefixer, so every vendor prefix is written by hand. The support floor, the list of prefixes that are still needed and the reason each one stays are at the top of `ui/css/tokens.css`; `ui/test/vendor-prefix-ratchet.test.mjs` fails on any prefix outside that list. Note that "an unprefixed property sits beside it" is not a reason to remove one: `-webkit-backdrop-filter` is paired everywhere and still required.
 
+### Platform identifiers
+
+Some vendor names appear in the source as identifiers, not as references. `-apple-system` and `BlinkMacSystemFont` are font-family keywords. `apple-touch-icon` and the `apple-mobile-web-app-*` meta names are web platform names read at add-to-homescreen time. `showLabels.ios` is a stored config key. User-agent patterns match device strings. None of these can be renamed. Prose describes behaviour in neutral terms instead.
+
 ## Colour
 
 `ui/css/tokens.css` holds the palette, the roles and the semantic sets. See [docs/design-system.md](design-system.md).
diff --git a/nginx/dashboard.conf b/nginx/dashboard.conf
index 7d8d0257..ee6f7820 100644
--- a/nginx/dashboard.conf
+++ b/nginx/dashboard.conf
@@ -42,8 +42,8 @@ server {
         add_header Content-Type "application/manifest+json" always;
     }
 
-    # ── iOS apple-touch-icon ──
-    # Served directly. iOS reads this path at add-to-homescreen time and does not
+    # ── apple-touch-icon ──
+    # Served directly. The platform reads this path at add-to-homescreen time and does not
     # follow a redirect.
     location = /apple-touch-icon.png {
         alias /icons/favicon.png;
diff --git a/playwright.config.js b/playwright.config.js
index feb60a1d..f9a29b20 100644
--- a/playwright.config.js
+++ b/playwright.config.js
@@ -9,8 +9,8 @@
    not covered here yet.
 
    Two browsers on purpose. WebKit is not decoration: the documented support
-   floor is Safari 16.2, and the last two layout and keyboard problems found by
-   hand were Safari-specific.
+   floor is WebKit 16.2, and the last two layout and keyboard problems found by
+   hand were WebKit-specific.
 
    BASE_URL points at a running Stackyard. The workflow starts the built image;
    nothing is started here, because the thing worth testing is the image that
diff --git a/ui/admin/index.html b/ui/admin/index.html
index 6ffa30e4..5bec2927 100644
--- a/ui/admin/index.html
+++ b/ui/admin/index.html
@@ -8,7 +8,7 @@
   <meta name="theme-color" content="#0d1117">
   <title>Stackyard Settings</title>
   <script src="/js/mobile-class.js?v=fe95da0d"></script>
-  <link rel="stylesheet" href="/css/tokens.css?v=cbcdec0a">
+  <link rel="stylesheet" href="/css/tokens.css?v=f8135c6f">
   <link rel="stylesheet" href="/css/admin.css?v=2635f968">
   <link rel="stylesheet" href="/css/widget-config-form.css?v=53b91d5f">
 </head>
@@ -288,6 +288,6 @@ <h1 class="sec-title" id="ev-title">General</h1>
   </div></div>
 </div>
 
-<script type="module" src="/js/admin.js?v=7562a9d2"></script>
+<script type="module" src="/js/admin.js?v=4a92bad6"></script>
 </body>
 </html>
diff --git a/ui/css/dashboard.css b/ui/css/dashboard.css
index de267659..90b8218c 100644
--- a/ui/css/dashboard.css
+++ b/ui/css/dashboard.css
@@ -507,7 +507,7 @@
     .sra { margin-inline-start:auto; color:rgba(255,255,255,.25); font-size:var(--fs-footnote);line-height:var(--lh-footnote);letter-spacing:var(--tr-footnote)}
 
     /* ── Mobile safe area ──
-       iOS reports an inset after the first paint and again after a rotation.
+       The platform reports an inset after the first paint and again after a rotation.
        These stay in CSS so the browser keeps them current. Nothing reads them
        into JavaScript. */
     body.is-mob {
diff --git a/ui/css/tokens.css b/ui/css/tokens.css
index 5e38c9e8..1fed3aea 100644
--- a/ui/css/tokens.css
+++ b/ui/css/tokens.css
@@ -1,5 +1,5 @@
 /* ── Browser support ─────────────────────────────────────────────────────────
-   Safari and iOS Safari 16.2 and newer, and current Chrome, Edge and Firefox.
+   WebKit 16.2 and newer, and current Chrome, Edge and Firefox.
    16.2 is where color-mix() lands, which the chip tints in admin.css derive
    from. There is no build step and no autoprefixer, so every vendor prefix in
    this project is hand-written and has to earn its place.
@@ -8,15 +8,15 @@
    set (-webkit-flex, -webkit-align-items, -webkit-justify-content and friends),
    -webkit-transform, -webkit-transition, -webkit-animation-*, all of which have
    been unprefixed everywhere for a decade, and -webkit-overflow-scrolling,
-   which iOS has ignored since version 13.
+   which mobile WebKit has ignored since version 13.
 
    These are the ones that stay, and why. Do not remove them on the grounds that
    an unprefixed property sits beside them; for the first two that is exactly
    the point.
 
-     -webkit-backdrop-filter     Safari needed the prefix well past 16.2, so the
+     -webkit-backdrop-filter     WebKit needed the prefix well past 16.2, so the
                                  glass panels flatten without it.
-     -webkit-text-size-adjust    Safari supports only the prefixed form.
+     -webkit-text-size-adjust    WebKit supports only the prefixed form.
      -webkit-line-clamp          With display:-webkit-box and -webkit-box-orient
      -webkit-box-orient          this is still the only portable way to clamp
      display:-webkit-box         text to a number of lines.
@@ -25,13 +25,13 @@
      -webkit-appearance          Required inside ::-webkit-slider-thumb.
      ::-webkit-slider-thumb      Pseudo-elements with no standard equivalent, as
      ::-moz-range-thumb          is the Firefox counterpart.
-     -webkit-user-select         Safari only dropped the prefix at 17.
+     -webkit-user-select         WebKit only dropped the prefix at 17.
 
    ui/test/vendor-prefix-ratchet.test.mjs holds this list, so adding a prefix
    outside it fails rather than accumulating quietly. */
 
 /* ── Palette ─────────────────────────────────────────────────────────────────
-   Apple's system colours, dark values. Both pages render on a dark panel or a
+   System colours from the reference kit, dark values. Both pages render on a dark panel or a
    wallpaper, and no stylesheet declares a prefers-color-scheme rule.
 
    Each hue also has a -hi entry, the increased-contrast value for the same
diff --git a/ui/index.html b/ui/index.html
index 8bba93d1..44bb7b38 100644
--- a/ui/index.html
+++ b/ui/index.html
@@ -10,21 +10,21 @@
     <link rel="manifest" href="/manifest.json">
   <meta name="theme-color" content="#0d1117">
   <meta name="apple-mobile-web-app-capable" content="yes">
-  <!-- Not black-translucent. iOS then places the web view at the top of the
+  <!-- Not black-translucent. The web view is then placed at the top of the
        screen but still sizes it to the screen minus the status bar, leaving a
        dead strip below the dock in a home-screen install. -->
   <meta name="apple-mobile-web-app-status-bar-style" content="default">
   <meta name="apple-mobile-web-app-title" content="Stackyard">
   <meta name="mobile-web-app-capable" content="yes">
 
-    <!-- No sizes attribute: iOS accepts any size and scales it -->
+    <!-- No sizes attribute: the platform accepts any size and scales it -->
   <link rel="apple-touch-icon" href="/icons/favicon.png">
   <link rel="icon" type="image/svg+xml" href="/icons/favicon.svg">
   <link rel="icon" type="image/png" href="/icons/favicon.png">
 
   <title>Stackyard</title>
-  <link rel="stylesheet" href="/css/tokens.css?v=cbcdec0a">
-  <link rel="stylesheet" href="/css/dashboard.css?v=f5117d06">
+  <link rel="stylesheet" href="/css/tokens.css?v=f8135c6f">
+  <link rel="stylesheet" href="/css/dashboard.css?v=352a7817">
 </head>
 <body>
 <h1 class="visually-hidden">Stackyard</h1>
@@ -53,5 +53,5 @@ <h1 class="visually-hidden">Stackyard</h1>
     </div>
   </div>
 </div>
-<script type="module" src="/js/dashboard.js?v=537f459e"></script>
+<script type="module" src="/js/dashboard.js?v=603a98ae"></script>
 </body></html>
diff --git a/ui/js/admin.js b/ui/js/admin.js
index 45367973..4bbb006d 100644
--- a/ui/js/admin.js
+++ b/ui/js/admin.js
@@ -399,7 +399,7 @@ function parseDragData(raw) {
   return null;
 }
 
-/* Native HTML5 drag does not fire from touch on iOS Safari. The handle needs
+/* Native HTML5 drag does not fire from touch on mobile WebKit. The handle needs
    touch-action:none (see admin.css) or starting on it scrolls the list. */
 function wireTouchDrag(row, handle, { indent, folderId }) {
   handle.addEventListener('pointerdown', e => {
diff --git a/ui/js/dashboard.js b/ui/js/dashboard.js
index 65e21f59..bbc0b302 100644
--- a/ui/js/dashboard.js
+++ b/ui/js/dashboard.js
@@ -25,7 +25,7 @@ import { html, setHtml, raw } from '/js/html.js?v=c71f8903';
 import { initI18n, t, currentLang } from '/js/i18n.js?v=d056c9c5';
 import { pwStrength, passwordMismatch } from '/js/password-strength.js?v=42f45ac7';
 import { sanitizeItemLinks } from '/js/link-url.js?v=54adb40f';
-import { initUI, mkFolder, openFolderDesktop, openFolderMobile, buildMobile } from '/js/ui.js?v=a8e01084';
+import { initUI, mkFolder, openFolderDesktop, openFolderMobile, buildMobile } from '/js/ui.js?v=7522fffa';
 import { badgeMinimum, badgeSignature, computeBadgeVisual, readBadgeUpdate } from '/js/badge-logic.js?v=e2857764';
 import {
   configChanged,
@@ -769,7 +769,7 @@ async function boot() {
     buildLayout();
   }, MOB);
 
-  /* iOS reports its safe-area insets after the first paint, and again after a
+  /* The platform reports its safe-area insets after the first paint, and again after a
      rotation. The probe is sized by them, so its box changing is the signal
      that the space the layout was measured against has moved. */
   if (typeof ResizeObserver === 'function') {
diff --git a/ui/js/mobile-metrics.js b/ui/js/mobile-metrics.js
index 6264426d..259ec99e 100644
--- a/ui/js/mobile-metrics.js
+++ b/ui/js/mobile-metrics.js
@@ -2,7 +2,7 @@
    rendering at one physical size whatever page scale the browser reports.
 
    Safe-area insets are not here. The stylesheet holds them, and the layout
-   measures the box the stylesheet produced. iOS reports an inset after the
+   measures the box the stylesheet produced. The platform reports an inset after the
    first paint, so a value read into JavaScript is stale from the moment it is
    taken. */
 
diff --git a/ui/js/ui.js b/ui/js/ui.js
index dbb243d4..3239c07b 100644
--- a/ui/js/ui.js
+++ b/ui/js/ui.js
@@ -13,7 +13,7 @@ import {
 } from '/js/utils.js?v=b81f6875';
 import { t, currentLang } from '/js/i18n.js?v=d056c9c5';
 import { trapFocus } from '/js/dialog.js?v=05935547';
-import { mobileMetrics } from '/js/mobile-metrics.js?v=4cf70285';
+import { mobileMetrics } from '/js/mobile-metrics.js?v=e48d02a8';
 
 let _state = null;
 export function initUI(state) {
@@ -569,7 +569,7 @@ export function buildMobile() {
 
   /* Every size below comes from this box, so the safe-area insets reach the
      layout as the space the stylesheet already reserved. Reading the insets
-     instead would take a value iOS has not reported yet. */
+     instead would take a value the platform has not reported yet. */
   const firstPage = mkPage();
   strip.appendChild(firstPage.page);
   const gridBox = firstPage.grid.getBoundingClientRect();
diff --git a/ui/test/folder-overlay.test.mjs b/ui/test/folder-overlay.test.mjs
index 43a4f910..21c5c5bc 100644
--- a/ui/test/folder-overlay.test.mjs
+++ b/ui/test/folder-overlay.test.mjs
@@ -16,7 +16,7 @@
 
    The second defect: the overlay trapped focus without saying what to focus,
    the trap fell back to the first focusable element, and that is the first app
-   link. iOS Safari paints its own focus ring for a script-driven focus on an
+   link. Mobile WebKit paints its own focus ring for a script-driven focus on an
    anchor, which the stylesheet only styles for :focus-visible. Opening a folder
    also should not move focus onto an item nobody asked for.
 
@@ -101,7 +101,7 @@ test('the native focus ring cannot render on a folder app link', () => {
   }
 });
 
-/* Desktop Safari showed the same ring the phone did: same trap, same missing
+/* Desktop WebKit showed the same ring the phone did: same trap, same missing
    plain-focus rule. */
 test('the desktop overlay takes focus itself too', () => {
   const desktop = ui.slice(ui.indexOf('export function openFolderDesktop('), ui.indexOf('function mFolder('));
diff --git a/ui/test/mobile-metrics.test.mjs b/ui/test/mobile-metrics.test.mjs
index a75e298a..f784fe74 100644
--- a/ui/test/mobile-metrics.test.mjs
+++ b/ui/test/mobile-metrics.test.mjs
@@ -44,7 +44,7 @@ test('every metric scales with sc', () => {
 
 /* ── The insets belong to the stylesheet ──────────────────────────────────── */
 
-/* iOS reports an inset after the first paint. A value read into JavaScript at
+/* The platform reports an inset after the first paint. A value read into JavaScript at
    build time is the zero it reported before, and nothing re-reads it. */
 test('no metric is computed from a safe-area inset', () => {
   const src = read('js/mobile-metrics.js');
@@ -56,7 +56,7 @@ test('no metric is computed from a safe-area inset', () => {
 
 test('the layout never reads an inset out of the document', () => {
   const ui = read('js/ui.js');
-  assert.doesNotMatch(ui, /safe-area-inset/, 'reading the inset back returns 0 on iOS until it is reported');
+  assert.doesNotMatch(ui, /safe-area-inset/, 'reading the inset back returns 0 until the platform reports it');
   assert.doesNotMatch(ui, /readSafeInsets/);
 });
 
diff --git a/ui/test/vendor-prefix-ratchet.test.mjs b/ui/test/vendor-prefix-ratchet.test.mjs
index ffc80b28..4dc57d1a 100644
--- a/ui/test/vendor-prefix-ratchet.test.mjs
+++ b/ui/test/vendor-prefix-ratchet.test.mjs
@@ -8,9 +8,9 @@ import { fileURLToPath } from 'node:url';
    they accumulate, and nothing said which were still doing anything.
 
    P12-1: there were 177, of which 97 were dead at the support floor written at the top
-   of tokens.css (Safari and iOS Safari 16.2+, current Chrome, Edge and
+   of tokens.css (WebKit 16.2+, current Chrome, Edge and
    Firefox). The tempting test, "does an unprefixed equivalent sit beside
-   it", is wrong and would have removed -webkit-backdrop-filter, which Safari
+   it", is wrong and would have removed -webkit-backdrop-filter, which WebKit
    needed well past 16.2 and which is paired with the unprefixed property in all
    26 places. Membership of this list is a per-property judgement, so the list is
    explicit rather than derived.
@@ -18,8 +18,8 @@ import { fileURLToPath } from 'node:url';
    Adding a prefix that is not here fails. If it genuinely belongs, add it with
    a reason in tokens.css and a line here. */
 const ALLOWED = new Set([
-  '-webkit-backdrop-filter' /* Safari needed it well past 16.2 */,
-  '-webkit-text-size-adjust' /* Safari supports only the prefixed form */,
+  '-webkit-backdrop-filter' /* WebKit needed it well past 16.2 */,
+  '-webkit-text-size-adjust' /* WebKit supports only the prefixed form */,
   '-webkit-line-clamp' /* the line-clamp idiom, with the two below */,
   '-webkit-box-orient',
   '-webkit-box' /* as a display value, not the old flexbox */,
@@ -29,7 +29,7 @@ const ALLOWED = new Set([
   '-webkit-appearance' /* required inside ::-webkit-slider-thumb */,
   '-webkit-slider-thumb' /* pseudo-element, no standard equivalent */,
   '-moz-range-thumb' /* the Firefox counterpart */,
-  '-webkit-user-select' /* Safari only dropped the prefix at 17 */,
+  '-webkit-user-select' /* WebKit only dropped the prefix at 17 */,
 ]);
 
 /* Removed by P12-1. Named so a reintroduction is reported as a regression
diff --git a/ui/widgets/backup/backup.html b/ui/widgets/backup/backup.html
index e4e263d5..3c7cd00b 100644
--- a/ui/widgets/backup/backup.html
+++ b/ui/widgets/backup/backup.html
@@ -174,7 +174,7 @@
   + 'Keep it safe.\nExpect the|unexpected.\nWorries don\'t.|Good backups|do.\nPrepare early.|Panic rarely.|Smile.')
 ).split('\n').map(line => line.split('|'))
 
-/* Safe rounded rect — avoids ctx.roundRect which has iframe bugs in Safari */
+/* Safe rounded rect — avoids ctx.roundRect which has iframe bugs in WebKit */
 function rrect(ctx, x, y, w, h, r) {
   if (w <= 0 || h <= 0) return;
   r = Math.min(r, w/2, h/2);
diff --git a/ui/widgets/github/contributions.html b/ui/widgets/github/contributions.html
index f71d56ea..8e1e57a0 100644
--- a/ui/widgets/github/contributions.html
+++ b/ui/widgets/github/contributions.html
@@ -84,7 +84,7 @@
   const old = widget.querySelector('.graph');
   if (old) old.remove();
 
-  /* Wait for layout to settle before measuring — critical inside iframes on iOS */
+  /* Wait for layout to settle before measuring — critical inside iframes on mobile WebKit */
   requestAnimationFrame(() => _renderGraph(data, weeks, widget));
 }
 
diff --git a/ui/widgets/stats/system-stats.html b/ui/widgets/stats/system-stats.html
index 51cfcb78..c92a97a7 100644
--- a/ui/widgets/stats/system-stats.html
+++ b/ui/widgets/stats/system-stats.html
@@ -109,7 +109,7 @@
   if (!cfg) cfg = { widgetType:'stats', widgetSize:'medium',
     widgetConfig:{ slots:[{type:'cpu'},{type:'ram'},{type:'disk',primary:'/'}], network:{enabled:false} }};
 
-  /* Detect narrow/iOS */
+  /* Detect a narrow viewport */
   if (document.documentElement.clientHeight >= 180) document.body.classList.add('narrow');
 
   buildShell();