@adhdev/daemon-core 0.9.82-rc.334 → 0.9.82-rc.336

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adhdev/daemon-core",
-  "version": "0.9.82-rc.334",
+  "version": "0.9.82-rc.336",
   "description": "ADHDev daemon core — CDP, IDE detection, providers, command execution",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -46,7 +46,7 @@
   "author": "vilmire",
   "license": "AGPL-3.0-or-later",
   "dependencies": {
-    "@adhdev/mesh-shared": "0.9.82-rc.334",
+    "@adhdev/mesh-shared": "0.9.82-rc.336",
     "@adhdev/session-host-core": "*",
     "@agentclientprotocol/sdk": "^0.16.1",
     "ajv": "^8.20.0",

package/src/cli-adapters/provider-cli-adapter.ts

@@ -118,6 +118,32 @@ export function appendBoundedText(current: string, chunk: string, maxChars: numb
     return current.slice(-keepFromCurrent) + chunk;
 }
 
+// Force-send (mesh coordinator dispatch / reconcile redelivery) writes raw
+// keystrokes straight into the PTY, bypassing the normal echo-wait submit
+// pipeline.
+//
+// History of this path's failure modes:
+//   1. Originally it wrote `text + sendKey` in a single PTY write with zero
+//      settle time. Injected into an idle TUI input box that was still entering
+//      its input-accepting state, the trailing submit key could be swallowed —
+//      prompt typed but never submitted ("text injected, Enter not pressed").
+//   2. The first fix split inject from submit: write(text) → echo-gated settle →
+//      write(sendKey) as a *separate* PTY write. That broke win32: ConPTY/TUI
+//      does not recognize a lone '\r' that arrives in its own PTY chunk
+//      150ms+ after the text as a submit key, and the win32 echo gate never
+//      matched (ConPTY echo/parsing differences), so the cap was burned and the
+//      same detached lone CR was emitted — adding latency while the Enter still
+//      got swallowed.
+//
+// Current behavior: keep a fixed settle gap so the input handler is in its
+// input-accepting state, then write `content + sendKey` as a SINGLE atomic PTY
+// write — the same verified mechanism the normal `immediate` submit strategy
+// uses (submitImmediatePrompt). With the Enter in the same write unit as the
+// text, win32 ConPTY always sees it as a submit and the race that the split was
+// trying to solve cannot happen (the Enter can never be separated from the
+// text). FORCE_SUBMIT_SETTLE_MS is that minimum pre-submit gap.
+const FORCE_SUBMIT_SETTLE_MS = 150;
+
 // ─── Adapter ────────────────────────────────────────
 
 export class ProviderCliAdapter implements CliAdapter {
@@ -1298,10 +1324,33 @@ export class ProviderCliAdapter implements CliAdapter {
             return;
         }
         LOG.info('CLI', `[${this.cliType}] force-sending prompt while status=${this.engine.currentStatus}`);
+        // Settle, then submit atomically. The previous split-write fix
+        // (write text → settle → write a separate '\r') regressed win32:
+        // ConPTY does not treat a lone CR arriving in its own PTY chunk after a
+        // delay as a submit key, so the Enter was swallowed and the prompt sat
+        // typed-but-unsent. Instead, honor a fixed settle gap so the TUI input
+        // handler is in its input-accepting state, then write `content + sendKey`
+        // as ONE PTY write — the same atomic submit the normal `immediate`
+        // strategy uses. Keeping the Enter in the same write unit as the text is
+        // the invariant that makes win32 ConPTY recognize the submit, and it
+        // also makes the original inject↔submit race impossible (the Enter can
+        // never be separated from the text it submits). The settle still guards
+        // the original concern — that a force-dispatch injected into a freshly
+        // idle session lands before the TUI is ready to accept input.
+        await this.waitForForceSubmitSettle();
         await this.writeToPty(content + this.sendKey);
         this.onStatusChange?.();
     }
 
+    private async waitForForceSubmitSettle(): Promise<void> {
+        // A fixed minimum gap so the input handler is ready to accept the paste.
+        // We deliberately do NOT echo-gate here: the submit key is written in the
+        // same atomic PTY write as the text (forceSendMessage), so there is no
+        // separate Enter that could race the echo, and on win32 the echo gate
+        // never reliably matched anyway.
+        await new Promise<void>(resolve => setTimeout(resolve, FORCE_SUBMIT_SETTLE_MS));
+    }
+
     private enqueuePendingOutboundMessage(text: string, reason: string): void {
         const content = String(text || '');
         const duplicate = this.pendingOutboundQueue.some((message) => message.content === content);