@agfpd/iapeer 0.4.9 → 0.4.11

package/package.json

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

package/src/identity/index.ts

@@ -213,8 +213,11 @@ export function readPeerProfile(cwd: string = process.cwd()): PeerProfile | null
   // the `iapeer init --personality` override (a deliberately-named peer in a folder
   // whose basename differs), so the heal stays a flagged drift, not a silent rewrite.
   const personality = validatePersonality(obj.personality, 'peer-profile personality')
-  // default_runtime is the contract field name (the routing/wake/first-launch default);
-  // `runtime` is the legacy field. Dual-read accepts both during the staged migration.
+  // default_runtime is the contract field name (the routing/wake/first-launch default). Phase-3:
+  // foundation no longer WRITES the legacy `runtime` mirror (see writePeerProfileAtomic), but the
+  // read-fallback is KEPT as a dormant defensive net — it tolerates a legacy-shaped profile (restored
+  // backup / hand-edit) at a 1-token cost. All real writers emit default_runtime (foundation +
+  // telegram-runtime 0.19.4). Consistent with the registry read-fallback (§3 defensive keep).
   const runtime = validateRuntime(obj.default_runtime ?? obj.runtime, 'peer-profile default_runtime')
   const interfaces = normalizeInterfaces(obj.interfaces, `${IAPEER_DIR}/${PEER_PROFILE_FILE}`)
   const intelligence = normalizeIntelligence(obj.intelligence, runtime)
@@ -292,18 +295,20 @@ export function writePeerProfileAtomic(cwd: string, profile: PeerProfileWrite):
   const merged: Record<string, unknown> = {
     ...existing,
     personality: profile.personality,
-    // Phase-2 write-flip (contract Идентичность, staged default_runtime migration):
-    // emit the contract field `default_runtime` AND keep the legacy `runtime` as an
-    // IN-SYNC MIRROR — readers that still read `runtime` only (IAP peers.ts,
-    // Spawned-Peer, external scripts) stay alive with zero blast radius. Phase 3
-    // (gated on every reader shipping dual-read) removes the mirror.
+    // Phase-3 (default_runtime migration complete): emit ONLY the contract field `default_runtime` —
+    // the legacy `runtime` mirror is removed. All readers switched: telegram-runtime 0.19.4 reads
+    // default_runtime and no longer re-seeds the mirror on mutation; foundation reads default_runtime.
     default_runtime: profile.runtime,
-    runtime: profile.runtime,
     runtimes: profile.runtimes,
     description,
     intelligence,
     ...(profile.interfaces ? { interfaces: profile.interfaces } : {}),
   }
+  // Phase-3: actively STRIP the legacy `runtime` mirror — it is a CONTRACT field superseded by
+  // default_runtime (not an owner field to preserve via `...existing`). This removes a lingering mirror
+  // on the next write of any already-migrated profile AND heals a diverged `runtime` (default_runtime
+  // governs). Owner sections (initial_prompt, wake_policy, expansion, notifier, …) stay preserved.
+  delete merged.runtime
   // C2 — initial_prompt: an explicit value in the write wins; otherwise the existing
   // on-disk value is preserved verbatim by `...existing` (a caller that doesn't own
   // it never wipes it). Only a non-empty string sets it.

package/src/launch/codexHooksTrust.ts

@@ -50,9 +50,6 @@ import { dirname } from 'path'
 import { writeFileAtomic } from '../storage/index.ts'
 import { codexGlobalConfigPath } from './nativeMemory.ts'
 
-/** The codex-cli version the hash algorithm + key format were verified on. */
-export const TRUST_HOOKS_TESTED_CODEX_VERSION = '0.138.0'
-
 /** hooks.json event names → the snake_case labels codex keys state with
  *  (upstream `hook_event_key_label`). */
 const EVENT_LABELS: Record<string, string> = {

package/src/registry/index.ts

@@ -158,9 +158,11 @@ function normalizePeer(raw: unknown): PeerRecord {
       )}"`,
     )
   }
-  // default_runtime is the contract field; `runtime` is legacy. Dual-read accepts
-  // both during the staged migration; when both are present default_runtime WINS
-  // (the write emits default_runtime + the legacy mirror since Phase 2).
+  // default_runtime is the contract field. Phase-3 (registry): foundation no longer WRITES the legacy
+  // `runtime` mirror (see writePeersIndexAtomic), but the read-fallback is KEPT as a dormant defensive
+  // net — it tolerates a legacy-shaped entry (restored backup / hand-edit) at a 1-token cost. All real
+  // readers switched (telegram → default_runtime, notifier → cwd-only); registry is single-writer so
+  // new entries are default_runtime-only. Full fallback removal is a future final cleanup.
   const defaultRuntime = obj.default_runtime ?? obj.runtime
   if (!isRuntime(defaultRuntime)) {
     throw new IapError(
@@ -315,15 +317,15 @@ function writePeersIndexAtomic(paths: PeersPaths, index: PeersIndex): void {
   // Persist the RAW intelligence verbatim (legacy-safe round-trip) and DROP the
   // intelligenceRaw shadow field from the on-disk shape — the file carries the
   // legacy vocab the live IAP reads, never the foundation's in-memory normalization.
-  // Phase-2 write-flip (staged default_runtime migration): the disk shape carries the
-  // contract field `default_runtime` PLUS the legacy `runtime` as an in-sync mirror,
-  // so not-yet-dual-read readers keep working. Phase 3 removes the mirror.
+  // Phase-3 (registry): the disk shape carries ONLY the contract field `default_runtime` — the legacy
+  // `runtime` mirror is removed (all registry readers switched: telegram → default_runtime, notifier →
+  // cwd-only, foundation → default_runtime). Local per-peer profiles keep their mirror until the paired
+  // telegram writePeerProfile follow-up.
   const peersForDisk = [...index.peers]
     .sort((a, b) => a.personality.localeCompare(b.personality))
     .map(peer => ({
       personality: peer.personality,
       default_runtime: peer.runtime,
-      runtime: peer.runtime,
       runtimes: peer.runtimes,
       description: peer.description,
       intelligence: peer.intelligenceRaw ?? peer.intelligence,

package/src/supervisor/paths.ts

@@ -1,7 +1,7 @@
 // Supervisor session paths — under a configurable run dir (NOT hardcoded). Prod resolves it to
 // ~/.iapeer/state/supervisor via the storage layer; tests pass a temp dir, so the daemon's
 // socket/pid files never touch a real location.
-import { renameSync, unlinkSync, writeFileSync } from 'node:fs'
+import { renameSync, writeFileSync } from 'node:fs'
 import { readFileSync } from 'node:fs'
 import { join } from 'node:path'
 import { pluginStateDir } from '../storage/index.ts'
@@ -57,12 +57,3 @@ export function readGeometry(runDir: string, session: string): { cols: number; r
   }
   return null
 }
-
-/** Remove the geometry sidecar (shutdown cleanup); best-effort. */
-export function clearGeometry(runDir: string, session: string): void {
-  try {
-    unlinkSync(geometryPath(runDir, session))
-  } catch {
-    /* */
-  }
-}