Updates

docs/operations.md

@@ -30,9 +30,13 @@ npm test
 npm run gpu-doctor
 npm run cu-doctor
 npm run voice-doctor
-bare daemon/bare-entry.js
+bash packaging/bare-launch.sh daemon/bare-entry.js
 ```
 
+`packaging/bare-launch.sh` selects the vendored Bare binary and is the same
+wrapper the packaged service uses. Do not reload the daemon with
+`node --watch`; Bare is the production loop.
+
 Use `npm run qvac:serve:diagnostic` only when a separate local client needs the
 OpenAI-compatible endpoint. Keep its host at `127.0.0.1`.
 
@@ -45,9 +49,28 @@ systemctl --user status jarvisd.service
 journalctl --user -u jarvisd.service -f
 ```
 
-The packaged service uses `~/.local/share/jarvis-qvac` and the generated config
-at `~/.config/jarvis/qvac.config.json`. The repository development unit uses
-the checkout path; use the packaged unit when testing installation behavior.
+The unit at `packaging/jarvisd.service` (installed to
+`~/.config/systemd/user/jarvisd.service`) starts Bare on
+`daemon/bare-entry.js` with working directory `~/.local/share/jarvis-qvac` and
+`QVAC_CONFIG_PATH=~/.config/jarvis/qvac.config.json`. The repository
+development unit uses the checkout path; use the packaged unit when testing
+installation behavior.
+
+Restart after daemon code changes:
+
+```bash
+systemctl --user restart jarvisd.service
+```
+
+## Desktop launcher
+
+`packaging/install.sh` writes:
+
+- `~/.local/share/applications/io.qvac.Jarvis.Control.desktop`
+- `~/.local/share/icons/hicolor/scalable/apps/io.qvac.Jarvis.Control.svg`
+
+The **Jarvis** launcher opens Control Center (`gjs -m …/apps/control-center/main.js`).
+See [brand](brand.md) and [settings](settings.md).
 
 ## Extension development
 
@@ -56,8 +79,21 @@ gnome-extensions enable [email protected]
 dbus-run-session -- gnome-shell --nested --wayland
 ```
 
-Keep inference and long-running work in `jarvisd`. Reloading the Shell is only
-needed for extension changes; daemon changes can use `node --watch`.
+Keep inference and long-running work in `jarvisd`. Live HUD files are
+`~/.local/share/gnome-shell/extensions/[email protected]`. Copy the checkout
+tree there, then reload the extension.
+
+GNOME 50 does not implement `ReloadExtension`. Calling
+`org.gnome.Shell.Extensions.ReloadExtension` on the standalone Extensions
+helper can also hit a stale cache. After copying files:
+
+1. Disable then enable on the real Shell (`org.gnome.Shell` at
+   `/org/gnome/Shell`), or
+2. Log out and back in.
+
+A stylesheet or JS parse error (for example St CSS `errcode:15`) will not
+hot-reload until that disable/enable or a new session. See
+[troubleshooting](troubleshooting.md).
 
 ## State and storage