Frame Control: Mac app, web UI, Android and Steam tooling

Package the Frame Control web UI as an installable Electron Mac app and
bring in the tooling built alongside it.

- app/: Electron wrapper that starts ui/server.py on a free loopback port,
  hardened window (sandbox, no navigation, runAsNode fuse off), login-shell
  PATH so Homebrew tools work from Finder, first-run offer to run
  connect.sh, ad-hoc signed DMG/zip via electron-builder.
- ui/: headset view (OpenVR screenshots), device status, library, Steam
  "Get games" (owned games, install, store search), Android apps as
  persistent Lepton instances with a rated F-Droid catalogue and a private
  compatibility database, Android display controls over ADB, file and
  clipboard transfer, Flatpaks, remote and power actions.
- apk-catalog/, compat-db/, frame/: catalogue build pipeline, Lakebed
  capsule for compatibility reports, Frame-side launchers.
- tests/ and CI: server guard and validation tests plus Steam helper tests,
  run on Python 3.9 with script and app syntax checks.
- Docs: README leads with the Mac app; new Android, panels, Steam games and
  field-notes docs; security notes on LAN-exposed ADB ports.

Screenshot values for the headset's IP and Wi-Fi name are placeholders.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.claude/skills/steam-frame/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: steam-frame
+description: Operate the user's Valve Steam Frame headset from the Mac through the ~/projects/steam-frame helpers and field notes. Use for Steam Frame SSH, screen streaming, clipboard, file push, APK or Flatpak installs, launching apps on the headset, arranging floating windows or panels in VR space, or debugging SteamOS/gamescope/SteamVR on the Frame.
+---
+
+# Steam Frame
+
+The repo is `~/projects/steam-frame`. SSH works through the `frame` alias
+(user `steamos`). The headset has to be awake for anything that touches its
+desktop or panels.
+
+## Start here
+
+1. Read `docs/how-the-frame-works.md`. It's the map: the layer cake (SteamVR →
+   gamescope → nested Plasma), the verified facts, and debug recipes.
+2. Open the topic doc for the task:
+
+| Task | Doc | Script |
+|---|---|---|
+| Floating windows in the room, one panel per app | `docs/panels.md` | `scripts/panel-on-frame.sh` |
+| First-time access, SSH keys | `docs/ssh.md` | `scripts/connect.sh` |
+| See the Frame from the Mac, or the Mac inside the Frame | `docs/streaming.md` | `scripts/run-on-frame.sh mac-screen` |
+| Files and clipboard | `docs/file-transfer.md` | `scripts/push.sh`, `scripts/paste-to-frame.sh` |
+| Android apps (Lepton) | `docs/apks.md` | `scripts/install-apk.sh` |
+| Install or buy Steam games, Frame ratings | `docs/steam-games.md` | `ui/frame_steam.py` |
+| Flatpaks | `docs/streaming.md` | `scripts/install-apps.sh` |
+| Launch an app inside the desktop panel | the script's header comment | `scripts/run-on-frame.sh` |
+| Mac GUI over all of this | `README.md` → Frame Control | `scripts/frame-ui.sh` |
+| What's still unverified | `docs/open-questions.md` | — |
+
+Each script's usage is in its header comment. Read the header rather than
+running `--help`: `paste-to-frame.sh`, `serve-bootstrap.sh` and
+`bootstrap-on-frame.sh` act on any argument.
+
+## Ground rules
+
+- Label every claim **verified** (seen on the device, with the date and
+  SteamOS build) or **inferred**. The docs use this convention. Keep it, and
+  move items out of `docs/open-questions.md` once they're checked.
+- When you learn something new about the Frame, record it in
+  `docs/how-the-frame-works.md` (or the topic doc) in the same change.
+- The Frame's rootfs is read-only and SteamOS updates replace it. Put changes in
+  `~` (`--user` Flatpaks, `~/.config`) rather than `steamos-readonly disable`.
+- `sudo` on the Frame asks for the user's Developer Mode password. Hand those
+  steps to the user (open Terminal) and keep automation to non-sudo commands.
+- The Mac uses BSD userland and zsh (no `timeout`, use `head -n`).