@pipod/cli 0.1.23 → 0.1.25

package/docs/keyboard-input.md

@@ -1,9 +1,9 @@
 # Keyboard input in the attached TUI
 
-Three input defects turn one key press into several characters, the same character twice, or
-into escape-sequence gibberish. All live in the local byte path — nothing typed crosses the
-wire — and all are fixed in `src/client/runtime/` rather than by pinning a different pi-tui,
-because the pinned version is what pods and the launcher share.
+Input defects can turn one key press into several characters, the same character twice, or
+into escape-sequence gibberish. These guards run in the local byte path, ahead of both the
+built-in editor and pod-rendered extension editors. They live in `src/client/runtime/` rather
+than pinning a different pi-tui, because pods and the launcher share the pinned version.
 
 ## The path
 
@@ -101,6 +101,25 @@ Left open deliberately: the reversed order (raw text first, then the CSI-u). No
 terminal writes it, and deduping it would mean dropping a key *event* on suspicion — the one
 direction where a mistake loses input.
 
+## 4. Reconnect must not leave the editor unguarded
+
+Session replacement clears Pi's extension UI before asynchronously refreshing the remote
+state. That also removes the launcher's input listeners, even though the same local editor
+continues accepting keys. Previously the guards returned only when the refreshed session
+bound its UI: typing during recovery bypassed both the encoding and repeat guards. A failed
+refresh could leave them absent until a later successful recovery. The socket being connected
+does not mean this refresh has finished.
+
+`remote-runtime.ts` now rewires the launcher's listeners synchronously after invalidating the
+old UI, before awaiting any refresh. The normal UI bind still unsubscribes and rewires them
+against the new context. This keeps one set of guards active throughout reconnect, pod switch,
+and session replacement, including refresh failures, without restarting the terminal or
+suppressing deliberate repeated presses.
+
+Measured on a live pod with the pinned Pi pair: a single dual-encoded press during the real
+reconnect refresh inserted `bb` before the fix and `b` after it. The terminal retained one stdin
+reader; the defect was a missing guard during recovery, not duplicate stdin subscriptions.
+
 ## Accepted rows
 
 Measured with a pty harness against pi 1.0.2 + pi-tui 1.0.2 (the pinned pair), driving

package/man/pipod-config.5

@@ -1,4 +1,4 @@
-.TH "PIPOD\-CONFIG" "5" "November 2026" "0.1.23"
+.TH "PIPOD\-CONFIG" "5" "November 2026" "0.1.25"
 .SH "NAME"
 \fBpipod-config\fR \- pi pod configuration files
 .SH SYNOPSIS

package/man/pipod.1

@@ -1,4 +1,4 @@
-.TH "PIPOD" "1" "November 2026" "0.1.23"
+.TH "PIPOD" "1" "November 2026" "0.1.25"
 .SH "NAME"
 \fBpipod\fR \- run pi coding\-agent sessions in server\-managed pods
 .SH SYNOPSIS
@@ -713,6 +713,12 @@ Quitting detaches: the pod keeps running until the server's idle policy reaps
 it or `pipod stop` stops it\. Raw pod shells are not available\.
 Attaching to an archived pod offers to restore it first\.
 
+The supervisor identifies the exact Pi executable it launched\. Managed installations do not
+start a second Pi just to check its version\. A failed lookup is retried safely during attach
+when possible, without stopping active work; a discovery failure is reported separately from
+an actual version mismatch\. Older supervisors with a cached failed lookup need a stop/attach
+once idle, keeping the workspace files\.
+
 Holding a character key types it once, and a press the terminal reports in both of its
 encodings types once too: key repeat stays available for Backspace, Tab and the arrow keys,
 where it is useful while editing\.

package/man/pipod.1.md

@@ -703,6 +703,12 @@ Quitting detaches: the pod keeps running until the server's idle policy reaps
 it or `pipod stop` stops it. Raw pod shells are not available.
 Attaching to an archived pod offers to restore it first.
 
+The supervisor identifies the exact Pi executable it launched. Managed installations do not
+start a second Pi just to check its version. A failed lookup is retried safely during attach
+when possible, without stopping active work; a discovery failure is reported separately from
+an actual version mismatch. Older supervisors with a cached failed lookup need a stop/attach
+once idle, keeping the workspace files.
+
 Holding a character key types it once, and a press the terminal reports in both of its
 encodings types once too: key repeat stays available for Backspace, Tab and the arrow keys,
 where it is useful while editing.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@pipod/cli",
-  "version": "0.1.23",
+  "version": "0.1.25",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@pipod/cli",
-      "version": "0.1.23",
+      "version": "0.1.25",
       "license": "AGPL-3.0-only",
       "dependencies": {
         "@earendil-works/pi-coding-agent": "1.0.2",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pipod/cli",
-  "version": "0.1.23",
+  "version": "0.1.25",
   "description": "Run pi coding-agent sessions in server-managed pods",
   "type": "module",
   "license": "AGPL-3.0-only",