Updates

docs/troubleshooting.md

@@ -24,12 +24,33 @@ still fails, run `npm run cu-doctor` and confirm `libei` is installed. Observati
 does not need the injector: after a grant, `cu_observe` should return a screenshot
 and accessibility tree even when pointer injection is down.
 
+## Stylesheet parse `errcode:15`
+
+GNOME Shell's St CSS parser rejects comments that contain `--`, `alpha(var())`,
+and `icon-size`. If `journalctl` shows a stylesheet parse error on
+`[email protected]`, copy the current `stylesheet.css` into the live extension
+directory and disable/enable the extension (GNOME 50 cannot `ReloadExtension`).
+See [brand](brand.md).
+
+## Settings window crashes on accent hex
+
+GTK 4 `Gtk.Entry` has no `maxLength` constructor property. The hex field uses
+`entry.get_buffer().set_max_length(7)`. If an older checkout still constructs
+`maxlength`, Settings will abort when opening the Desktop page.
+
+## Panel label shows “Jarv…”
+
+The panel used to show the product name and a state chip at the same time,
+which GNOME truncated. Idle is mark plus **Jarvis**; busy is mark plus one
+state chip (Listening / Thinking / Speaking / Privacy). Never both.
+
 ## The extension is missing
 
 Preferences can open while the panel HUD is gone if the extension is installed
 but not enabled in the running GNOME Shell. Re-run the installer so it copies
-the HUD files and asks Shell to reload/enable `[email protected]`. The
-installer also keeps a copy at
+the HUD files and asks Shell to enable `[email protected]`. On GNOME 50 that
+does not hot-reload; disable/enable the extension or log out if the panel is
+still gone. The installer also keeps a copy at
 `~/.local/share/gnome-shell/extensions/[email protected]`:
 
 ```bash
@@ -46,22 +67,23 @@ journalctl --user -b | grep -i jarvis
 If the extension still does not appear, log out and back in once so GNOME Shell
 reloads its extension search path.
 
-## The service reports `203/EXEC` for `/usr/bin/node`
+## The service reports `203/EXEC`
 
-Older installers wrote a fixed `/usr/bin/node` path. Re-run the current web
-installer; it records the Node executable found in the installing user's PATH
-when it writes the user service. Check the result with:
+Current `jarvisd.service` starts packaged Bare, not `/usr/bin/node`. If
+`ExecStart` still points at a missing `node` or Bare binary, re-run
+`packaging/install.sh --enable` or the web installer. Check the result with:
 
 ```bash
 systemctl --user cat jarvisd.service | grep ExecStart
-command -v node
 ```
 
 ## The daemon restarts
 
-Inspect `journalctl --user -u jarvisd.service`. Common causes are Node version,
-invalid QVAC config, missing session D-Bus, missing GPU visibility, or a stale
-portal grant. Run the three doctor commands before changing model settings.
+Inspect `journalctl --user -u jarvisd.service`. Common causes are a missing
+Bare binary, invalid QVAC config, missing session D-Bus, missing GPU
+visibility, or a stale portal grant. Run the three doctor commands before
+changing model settings. Restarting `jarvisd` also clears an active desktop
+grant.
 
 ## Rolling release did not publish