@agfpd/iapeer 0.4.6 → 0.4.7

package/README.md

@@ -9,6 +9,12 @@
 
 iapeer keeps a team of AI agents, humans, and services on one host **always reachable — every one of them a single message away.** Each participant is a **peer**: a Claude Code or Codex CLI agent, a person on Telegram, or a scheduler/watcher service. Any agent reaches any other with one call — `send_to_peer(<name>, <text>)` — and a peer that is asleep is still reachable: the daemon wakes it and delivers. Agents on Claude and on Codex — different AI runtimes from different vendors — talk as equal peers; humans take part over Telegram, or directly in the terminal — attached to a peer's live session with `iapeer attach`.
 
+<p align="center">
+  <img src=".github/assets/iapeer-pingpong.gif" width="800" alt="A person messages one peer on Telegram; heterogeneous peers (Claude + Codex) relay a baton over one protocol and report back to Telegram.">
+  <br>
+  <em>One Telegram message in → Claude and Codex peers pass a baton over the same protocol → a report back in Telegram.</em>
+</p>
+
 ## How it works
 
 ```text

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.4.6",
+  "version": "0.4.7",
   "description": "Foundation core for the iapeer multi-agent ecosystem: identity, registry, storage, codec.",
   "license": "Apache-2.0",
   "author": "agfpd",

package/src/launch/readyGateModel.ts

@@ -134,9 +134,15 @@ export async function paneLogViewport(log: string, cols: number, rows: number, s
  * validated `composerOccupancyFromModel` (REUSED, not reimplemented). The hosted equivalent of
  * `targetComposerBlocksDelivery`'s capture-pane occupancy. @xterm loads dynamically here (flag-on
  * hosted only; the leaf `composerOccupancyFromModel` import is type-only at runtime, so the warm path
- * stays @xterm-free with the flip off). UNCERTAINTY → BUSY (true): a model-build failure mirrors the
- * tmux predicate's capture-fail-is-busy stance — prefer a false-busy hold over a false-free paste into
- * a human composer.
+ * stays @xterm-free with the flip off). UNREADABLE PANE-LOG → NOT busy (false): the hold exists ONLY to
+ * avoid clobbering VISIBLE human composer text; if the model can't be built there is NO observed text to
+ * protect. This deliberately does NOT mirror the tmux predicate's capture-fail-is-busy stance: tmux
+ * `capture-pane` fails ~only when the session is GONE (then the queue's session-token/alive check fails
+ * the job loudly), but a hosted pane-log can be absent/unreadable while the session is ALIVE (e.g. a
+ * long-lived session whose lifecycle pane-log was rotated/removed) — so "uncertainty → busy" would stall
+ * EVERY delivery to such a peer until the 120 s force-timeout, starving the core addressed-delivery
+ * feature. The narrow cost (no composer protection while the log is unreadable) is acceptable: a session
+ * actively being typed into is precisely one whose pane-log IS being written.
  *
  * NB (sequence): this is the DETECTION primitive. The end-to-end gate (attached-supervisor-
  * client + enqueue + host-aware drain) lands with the attach client in Ф0b-3 — until a human can
@@ -145,7 +151,7 @@ export async function paneLogViewport(log: string, cols: number, rows: number, s
  */
 export async function paneLogComposerOccupied(log: string, cols: number, rows: number, runtime: string): Promise<boolean> {
   const term = await loadPaneLogModel(log, cols, rows)
-  if (!term) return true // uncertainty → busy: never paste into a maybe-occupied composer
+  if (!term) return false // unreadable pane-log → no observed human composer text → deliver, never stall (see JSDoc)
   const { composerOccupancyFromModel } = await import('../shadow/render.ts')
   return composerOccupancyFromModel(term, cols, rows, runtime)
 }