@agfpd/iapeer 0.2.56 → 0.2.57

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.2.56",
+  "version": "0.2.57",
   "description": "Foundation core for the iapeer multi-agent ecosystem: identity, registry, storage, codec.",
   "type": "module",
   "bin": {

package/src/lifecycle/index.ts

@@ -1001,6 +1001,22 @@ export async function wakeOrSpawn(args: WakeArgs, deps: WakeDeps = {}): Promise<
     const firstMessage = composeFirstMessage(cwd, args.task, fresh)
     const result = await launch(spec, adapter, firstMessage, launchCfg)
     if (result.status === 'FAILED') {
+      // enroll-on-FAILED (0.2.57): launch can return FAILED on a ready-gate false-negative
+      // (model-did-not-process-task) while the tmux session + its process actually SURVIVE —
+      // observed live (ttlverify, 13.06). Since 0.2.55 removed the self-TTL, such a remnant
+      // would be an UNBOUNDED orphan: no .session → invisible to superviseTick's idle-reap,
+      // and no wall-clock backstop. If the session is in fact ALIVE, enroll it so the
+      // activity-aware idle-reap stays the UNIVERSAL bound (a genuinely wedged session is
+      // idle-reaped after idleSecs; a false-negative-but-working one keeps working and is
+      // reaped only when truly idle, and its next message reaches it via the has-session fast
+      // path above). We do NOT flip to READY — the wake DID fail its ready-gate, the caller
+      // must still hear FAILED; we only make the live remnant supervised. Best-effort: a write
+      // hiccup must not mask the original FAILED reason.
+      if (sessionAlive(sock, identity)) {
+        try {
+          writeSessionState(cfg, { identity, runtime, personality: args.personality, cwd, wokeAt: Date.now() })
+        } catch { /* keep the original FAILED reason — enroll is best-effort */ }
+      }
       return { status: 'FAILED', woke: false, runtime, reason: result.reason }
     }
     // The session is up and the message delivered. Recording supervise-state must not