@gotcos/glasses-server 6.36.7 → 6.36.8

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 ## Unreleased
 
+## 6.36.8
+- **The queue now covers the refusal that actually fires.** Device diagnostics, once the
+  path was finally instrumented, recorded `native_target_busy` on every Continue that
+  reached the server — never `native_thread_working`, which is what 6.36.7 was built
+  around. Selecting Continue SUCCEEDS and mints a binding; if the dictation is not
+  completed the binding lingers to its TTL, and every Continue inside that window
+  refuses. Twelve such bindings had stacked up on one thread over an evening.
+- `native_target_busy` and `native_turn_in_progress` are now queueable. Both are
+  transient by construction — a clock clears them — and both are COS's OWN bookkeeping
+  rather than a foreign process holding the thread. Delivery still re-runs the full
+  gate, so nothing about the safety model changes.
+- `native_target_fenced` is deliberately NOT queueable: "may or may not have been
+  delivered" cannot be resolved by waiting, and queueing it risks a duplicate turn in a
+  real conversation.
+
+
 ## 6.36.7
 - **A turn spoken at a busy thread is now queued instead of refused.** Miles: "if
   there's a session that's still running, that would just put it into the queue the same

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gotcos/glasses-server",
-  "version": "6.36.7",
+  "version": "6.36.8",
   "description": "COS Glasses \u2014 self-hosted AI heads-up-display server for Even G2 smart glasses, powered by Claude Code, Codex, or Cursor Agent CLI",
   "type": "module",
   "bin": {

package/server/lib/thread-turn-queue.ts

@@ -120,6 +120,19 @@ export const MAX_DELIVERY_ATTEMPTS = 5
  */
 const QUEUEABLE_REFUSALS: ReadonlySet<string> = new Set([
   'native_thread_working',
+  // COS'S OWN LEFTOVER BINDING, and the reason this feature did not work for a day.
+  // Proven from device diagnostics 2026-08-17: every Continue that reached the server
+  // was refused `native_target_busy` ("already attached to another COS chat"), never
+  // `native_thread_working`. Selecting Continue SUCCEEDS and mints a binding; if the
+  // dictation is not completed the binding lingers to its TTL, and every Continue in
+  // that window refuses. Twelve such bindings had stacked up on one thread.
+  //
+  // It belongs here because it is transient BY CONSTRUCTION -- the binding expires on
+  // a clock -- and because it is COS's own bookkeeping, not a foreign process holding
+  // the thread. Queueing waits it out, and delivery re-runs the whole gate as always.
+  'native_target_busy',
+  // Same shape: a COS turn is mid-flight on this thread and will finish.
+  'native_turn_in_progress',
   'live_desktop_process',
   'thread_busy',
   'binding_conflict',