peertable 0.4.13 → 0.4.14

package/README.ja.md

@@ -107,7 +107,7 @@ Codex では、スキルが所有する room MCP block をプロジェクトの
 
 動いており、**自分自身の開発に使っている**。2026-08-08 に end-to-end 検証済み——オーケストレーターなしの完全な一周（2 メンバーが相談し、claim し、インターフェースを交渉し、見つけた罠を共有して小さなプロジェクトを出荷）を**外部介入ゼロ**で完走。2026-08-13の実席ライフサイクルでは、作業席が親を通じてsession contextを保ったままmodel / effortを変更し、再起動後はroomと工程正本から再着任した。2026-08-14にはGrok 4.6席の着席、room参加、同一sessionの4.6↔4.5変更、DM起床を実機で確認した。2026-08-17にGrok席はidle待ち、broadcastは本文を残し、tmuxの無い親でbridge cursorが止まらないよう直した。
 
-現在のnpm releaseは **peertable 0.4.13**。
+現在のnpm releaseは **peertable 0.4.14**。
 
 設計文書と決定履歴（**91 決定**）は [docs/plan.md](docs/plan.md)。
 

package/README.md

@@ -143,7 +143,7 @@ It interviews you, names the members, scaffolds `.team/` (charter + roles, isola
 
 Working, and used to build itself. First verified end-to-end on 2026-08-08 with a full no-orchestrator loop: two members consulted, claimed, negotiated an interface, shared a discovered pitfall, and shipped a small project with **zero external intervention**. A 2026-08-13 real-seat lifecycle verified in-place model/effort changes and restart recovery. On 2026-08-14, a Grok 4.6 seat joined the room, changed 4.6↔4.5 in the same session, and woke on a direct message in a live acceptance run. On 2026-08-17 the wake-up path was corrected so Grok seats wait for idle, broadcasts keep their body, and a parent without a tmux seat cannot stall the bridge cursor.
 
-The current npm release is **peertable 0.4.13**.
+The current npm release is **peertable 0.4.14**.
 
 The design document and decision log (**91 decisions**, in Japanese) live in [docs/plan.md](docs/plan.md).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peertable",
-  "version": "0.4.13",
+  "version": "0.4.14",
   "description": "A round table of peer agents. No orchestrator at the head. Turn Claude Code, Codex, and Grok sessions into a team of equal, long-lived peers.",
   "type": "module",
   "license": "MIT",

package/room/client.mjs

@@ -11,7 +11,7 @@ import { fileURLToPath } from 'node:url'
 
 // client.mjs 側のハードコード版数。package.json の version と一致していることを
 // diagnostics の version_consistency が見る（2 つの版数源の drift 検出。決定45）
-const MCP_VERSION = '0.4.13'
+const MCP_VERSION = '0.4.14'
 const PKG_ROOT = join(dirname(fileURLToPath(import.meta.url)), '..')
 
 const USAGE = `usage:
@@ -297,6 +297,7 @@ async function runDiagnostics(asJson) {
       'scripts/seat-identity.mjs',
       'scripts/pid-alive.mjs',
       'scripts/parent-watch.mjs',
+      'scripts/parent-watch-logic.mjs',
       'scripts/seat-credential.mjs',
       'scripts/ensure-room-mcp.mjs',
       'scripts/leave-seat.sh',

package/skill/scripts/parent-watch-logic.mjs

@@ -0,0 +1,11 @@
+export function latticeStaffingChanged(previous, next) {
+  if (!next || next.error) return false
+  if (!previous || previous.error) return true
+  return previous.ready !== next.ready || previous.active !== next.active
+}
+
+export function addressedToParent(message, parent) {
+  return message?.from !== parent
+    && (message?.to === 'all' || message?.to === parent
+      || (Array.isArray(message?.to_names) && message.to_names.includes(parent)))
+}

package/skill/scripts/parent-watch.mjs

@@ -11,6 +11,7 @@ import { execFileSync } from 'node:child_process'
 import { existsSync, readFileSync, renameSync, statSync, unlinkSync, writeFileSync } from 'node:fs'
 import { join } from 'node:path'
 import { resolveLatticeExecutable } from './seat-usage.mjs'
+import { addressedToParent as messageAddressedToParent, latticeStaffingChanged } from './parent-watch-logic.mjs'
 
 const args = process.argv.slice(2)
 const project = args.shift()
@@ -154,9 +155,17 @@ function releaseLock() {
 acquireLock()
 process.on('exit', releaseLock)
 
-const addressedToParent = message => message?.from !== parent
-  && (message?.to === 'all' || message?.to === parent
-    || (Array.isArray(message?.to_names) && message.to_names.includes(parent)))
+const addressedToParent = message => messageAddressedToParent(message, parent)
+
+function exitWhenParentStdinCloses() {
+  if (mode !== '--follow') return
+  const stdin = process.stdin
+  if (!stdin || stdin.destroyed) return
+  const quit = () => process.exit(0)
+  stdin.on('end', quit)
+  stdin.on('close', quit)
+  if (typeof stdin.resume === 'function') stdin.resume()
+}
 
 async function writeEvent(event) {
   await new Promise((resolve, reject) => {
@@ -180,8 +189,7 @@ async function acceptLatticeState(next) {
     })
     return true
   }
-  const changed = Number.isSafeInteger(previous?.ready) && Number.isSafeInteger(previous?.active)
-    && previous.ready + previous.active !== next.ready + next.active
+  const changed = latticeStaffingChanged(previous, next)
   state = { ...state, lattice: next, last_event_at: now() }
   saveState(state)
   if (!changed) return false
@@ -241,11 +249,29 @@ if (mode === '--next' && (!Number.isFinite(nextWindowMs) || nextWindowMs < 100))
   process.exit(2)
 }
 
+exitWhenParentStdinCloses()
+
 let consecutiveFailures = 0
+let snapshotSent = false
 for (;;) {
   const deadline = mode === '--next' ? Date.now() + nextWindowMs : Number.POSITIVE_INFINITY
   try {
     if (await catchUp()) process.exit(0)
+    if (mode === '--follow' && !snapshotSent) {
+      snapshotSent = true
+      const lattice = state.lattice
+      await writeEvent({
+        schema: 'peertable.parent-watch-event.v1',
+        type: 'parent_watch_snapshot',
+        parent,
+        last_seq: state.last_seq,
+        ready: lattice?.ready ?? null,
+        active: lattice?.active ?? null,
+        body: lattice && !lattice.error
+          ? staffingBody(lattice)
+          : '親番犬を張り直した。room の親宛と工程件数を追従する。',
+      })
+    }
     const controller = new AbortController()
     const remaining = Number.isFinite(deadline) ? Math.max(1, deadline - Date.now()) : null
     const timer = remaining === null ? null : setTimeout(() => controller.abort(), remaining)

package/skill/templates/parent.md

@@ -54,8 +54,10 @@ export は親 shell に伝播しないため**、これをしないまま `latti
   張り替え時は旧Monitorを止めてから起動する。
 
 どちらも`parent-join.sh`が先に作る`.team/parent-watch.json`のcursorを共有する。watcher不在中のDMは
-次回起動時にcatch-upされ、親以外宛・親自身の発言・pingでは親を起こさない。`watch_error`が届いたら
-通常のDMとして扱わず、番犬の再着卓を行う。
+次回起動時にcatch-upされ、親以外宛・親自身の発言・pingでは親を起こさない。Lattice の ready 件数と
+active 件数は合計ではなくそれぞれ変化したら起こす（実装が全部閉じて親手番1件だけになっても起こす）。
+`--follow` は親セッションの stdin が閉じたら終了する。切れた番犬が seq だけ進めて親が起きない状態を作らない。
+`watch_error`が届いたら通常のDMとして扱わず、番犬の再着卓を行う。
 
 ## 試験結果の監査