classifyOnboardingFirmware() (firmware-compat.ts) returns kind values of
"custom" | "flashable-stock" | "newer-stock" | "unknown", but
applyClassification()'s switch (onboarding-firmware-check-view-model.ts)
checked for "flashable" / "newer" -- names borrowed from the unrelated
CheckPhase type used a few lines later via setPhase(). Since kind was
typed as plain string, nothing caught the mismatch at compile time.
Effect: any device that successfully reported a firmware version (stock,
flashable-stock, or newer-stock alike) fell through to the switch's
default case and showed "Connected, but couldn't read a firmware
version" -- the hard-block message meant for when the probe gets no
data at all. Confirmed on real hardware (glasses on 2.2.9.22): the BLE
probe read the version correctly every time, logged it correctly, and
the UI still reported it as unreadable.
Fix: match the real OnboardingFirmwareKind strings, and tighten the
parameter's type from `string` to `OnboardingFirmwareKind` so this
category of typo fails to compile instead of failing silently.
<details>
<summary>Prompts Used</summary>
Currently we receive user input events from the R1 ring mainly via the G2 glasses, which have their own connection to ring, and we also try to connect to the ring directly; but the direct connection currently winds up not workign reliably. Let's add a "Ring connection mode" to the Developer section of the Settings app, with options "Only via glasses" (new default) and "Direct". If the "Only via glasses" option is selected, we don't open a bluetooth connection to the ring at all.
> Done. Build + typecheck pass.
>
> **Changes:**
>
> - `app/ui/dashboard-settings.ts:393` — new `ringConnectionModeSetting` (`ConfigSettingEnum<RingConnectionMode>`), values `"glasses"` (default, displayed "Only via glasses") and `"direct"`, stored under `developer.ringConnectionMode`.
> - `app/ui/dashboard/settings-menus.ts:182` — added it as the first row of the Developer section.
> - `app/g2/dashboard-controller.ts:988` — `connect()` now computes `ringAddress = mode === "direct" ? addresses.ring : ""` and passes that to `FaceclawCommunicatorBridge` (and into the connect log line).
>
> The gate works by handing the Java communicator an empty ring address: `FaceclawBleCommunicator.hasRingAddress()` then returns false, so `tryConnectRing`/`shouldAttemptRingConnect`/the teardown `disconnect(ringAddress)` all short-circuit — no GATT connection to the ring is ever opened, and the retry loop never fires. Gestures still arrive over the glasses' own link to the ring, unchanged.
>
> Since the mode is read at connect time, changing it while connected takes effect on the next connection; the setting's description says so. If you'd rather it apply live (drop/raise the ring link without cycling the glasses), that needs a small new Java method on the communicator — say the word and I'll add it.
</details>