Launcher: strip the window back to what's worth reading

A pass for less prose and fewer boxes.

- Header shows the version and node; the port is already in the addresses
  below it, and the module list belonged in the log.
- Settings: "Network" over the port (no explanation under it), "Startup"
  instead of "Starting up", and no node chooser — the path stays visible,
  since which node runs is the first thing worth knowing when it won't.
- Permissions: one line per permission — a status dot, its name, and the one
  thing you can do about it. The standing explanation is gone and the
  modules' own reasons moved to each row's tooltip. Local network results
  still appear under their row after a check, with a short line and a link
  only when nothing answered at all. Re-check sits centred at the bottom,
  outside the group.

The app-level "notify me" switch goes with it: macOS's own per-app
notification setting already does that job, so notifications now follow the
permission alone, asked for by the row's Enable button rather than on first
run.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/MODULE-GUIDE.md

@@ -237,8 +237,8 @@ it and ask for it before a service rather than during one:
 | `microphone` | The module reads an audio input (`ltc-capture` and anything like it). |
 | `local-network` | The module talks to gear on this building's network. Not needed for services out on the internet — Planning Center, say. |
 
-`reason` is one line, shown to the operator as-is; modules giving the same
-reason are listed together. A bare `"permissions": ["microphone"]` works when
+`reason` is one line, shown to the operator as-is when they hover the
+permission; modules giving the same reason are listed together. A bare `"permissions": ["microphone"]` works when
 the standing explanation is enough. A `kind` the launcher doesn't manage is
 still listed, so nothing goes unmentioned — the shell itself ignores the key
 entirely, and other platforms ignore it too.