opencode-rgbify-plugin 0.1.3 → 0.1.5

package/README.md

@@ -16,18 +16,20 @@ opencode events ──► src/index.ts (plugin) ──► raw tail ──► lin
 ```
 
 - **`src/index.ts`** — the opencode plugin. Spawns the Python bridge and
-  forwards each delta's last 8 chars as a newline-delimited line. **No
-  sanitization**: both auralizers treat any out-of-range byte as a rest, so
-  raw text is safe. (Sanitization existed for the scrolling-display era, where
+  forwards each delta's tail (last `TAIL_CHARS=4` chars) as a newline-delimited
+  line. **No sanitization**: both auralizers treat any out-of-range byte as a
+  rest, so raw text is safe. (Sanitization existed for the scrolling-display era, where
   tags in the text would scroll across the matrix; the firmware now blits one
   char at a time, so tags are harmless — and the old tag-swallowing state
   machine could stick on an unbalanced `<` and silently discard whole streams.
   That was the long-standing "auralizers go silent" bug.)
-- **`bridge/ble_bridge.py`** — the BLE bridge. Reads lines from stdin, chunks
-  them to the negotiated MTU, writes them to the projector's `TEXT_BRIDGE`
-  characteristic, and auralizes each char on the host at the firmware's native
-  cadence (one ~33ms note per char, log-scale frequency table identical to the
-  firmware).
+- **`bridge/ble_bridge.py`** — the BLE bridge. Reads lines from stdin and
+  writes each to the projector's `TEXT_BRIDGE` characteristic as a
+  write-without-response (fire-and-forget, no ACK wait), and auralizes each
+  char on the host at the firmware's native cadence (one ~33ms note per char,
+  log-scale frequency table identical to the firmware). The plugin feeds stdin
+  via a `ReadableStream` with latest-wins semantics, so opencode never blocks
+  on the bridge and no line ever queues up.
 
 ### Interrupt semantics
 
@@ -78,9 +80,21 @@ path still works.
 | `RGBIFY_STATE_DIR` | `~/.config/opencode/state` | Where `host-volume` is persisted |
 | `RGBIFY_DEBUG_LOG` | — | Append debug log path |
 
-Host volume is mirrored from the projector's `VOLUME` characteristic whenever
-it's connected and persisted to `host-volume` so it survives restarts. While
-the projector is off you can still adjust the host volume by editing that file.
+Desktop (host) volume is controlled independently of the projector via the
+embedded RGBify volume popup (below) and persisted to `host-volume` so it
+survives restarts. It is **not** mirrored from the projector's `VOLUME`
+characteristic.
+
+### Desktop volume via a slash command
+
+Set the local desktop auralizer volume from opencode with `/rgbify volume <0-10>`
+(e.g. `/rgbify volume 7`). No firmware change, no website.
+
+- The plugin defines a `rgbify` command (in `opencode.json`'s `command` map) and
+  handles it in the `command.execute.before` hook: it writes `host-volume`, and
+  the running bridge's `watch_host_volume` task applies it live — even with the
+  projector off.
+- `Ctrl+P` → "rgbify" also lists it like any other command.
 
 ## Development