<!--
Thanks for sending this.

A PR with a title and no description usually gets closed — not out of
strictness, but because nobody can tell whether it is safe to merge.
-->

## What this changes

<!-- One or two sentences. What is different afterwards? -->

## Why

<!-- The problem it solves. Link an issue if there is one. -->

## Type

- [ ] 🐛 Fix
- [ ] ✨ New capability
- [ ] 📝 Docs
- [ ] 🎨 Skill content (`skills/`)
- [ ] ♻️ Refactor — no behaviour change
- [ ] 🔧 Build, CI or tooling

## Which builds this touches

- [ ] `portable/` — the USB build
- [ ] `install/` — one-line install
- [ ] `bootable/` — Linux USB
- [ ] Shared (`lib/`, `skills/`, tests)

## How you tested it

<!--
Not decoration. Say what you actually ran.

  node --test          # NOT `node --test tests/` — that runs nothing

And for anything touching a launcher or an installer, say which platform you
ran it on. A change to a .bat verified only on a Mac is worth saying so about —
that has been the main source of breakage here.
-->

- [ ] `node --test` passes
- [ ] Ran it on: <!-- macOS / Windows / Linux -->

## Checklist

- [ ] No `node_modules/`, `app/`, `data/`, `*.dmg`, `*.exe` in the diff
- [ ] No API keys, tokens or passwords in any file
- [ ] User-facing text is in `lib/messages/*.json`, not hardcoded in a script
- [ ] `.bat` files stay pure ASCII with CRLF; `.command` files stay LF-only
- [ ] Unrelated files are not reformatted