instar 1.3.70 → 1.3.72

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-05-28T22:59:01.360Z",
-  "instarVersion": "1.3.70",
+  "generatedAt": "2026-05-29T01:04:44.834Z",
+  "instarVersion": "1.3.72",
   "entryCount": 193,
   "entries": {
     "hook:session-start": {
@@ -11,7 +11,7 @@
       "domain": "identity",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/session-start.sh",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:dangerous-command-guard": {
@@ -20,7 +20,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/dangerous-command-guard.sh",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:grounding-before-messaging": {
@@ -29,7 +29,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/grounding-before-messaging.sh",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:compaction-recovery": {
@@ -38,7 +38,7 @@
       "domain": "identity",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/compaction-recovery.sh",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:external-operation-gate": {
@@ -47,7 +47,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/external-operation-gate.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:deferral-detector": {
@@ -56,7 +56,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/deferral-detector.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:post-action-reflection": {
@@ -65,7 +65,7 @@
       "domain": "evolution",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/post-action-reflection.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:external-communication-guard": {
@@ -74,7 +74,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/external-communication-guard.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:scope-coherence-collector": {
@@ -83,7 +83,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/scope-coherence-collector.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:scope-coherence-checkpoint": {
@@ -92,7 +92,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/scope-coherence-checkpoint.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:free-text-guard": {
@@ -101,7 +101,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/free-text-guard.sh",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:claim-intercept": {
@@ -110,7 +110,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/claim-intercept.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:claim-intercept-response": {
@@ -119,7 +119,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/claim-intercept-response.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:stop-gate-router": {
@@ -128,7 +128,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/stop-gate-router.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "hook:auto-approve-permissions": {
@@ -137,7 +137,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/auto-approve-permissions.js",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "job:health-check": {
@@ -1457,7 +1457,7 @@
       "type": "subsystem",
       "domain": "server",
       "sourcePath": "src/server/AgentServer.ts",
-      "contentHash": "fb958a979cb6284188fa299d4e3dcc347a7d752a07a5cfe181f7919e18e0b1c0",
+      "contentHash": "88cfc6c3397a04f59444a78fe95cd23a3d1805a64476f175123fbb59373c1a07",
       "since": "2025-01-01"
     },
     "subsystem:session-manager": {
@@ -1489,7 +1489,7 @@
       "type": "subsystem",
       "domain": "updates",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
-      "contentHash": "c410faa704330138b3bb15f71c78506ee86da3b1a7838328dea59888cd7f451a",
+      "contentHash": "cf0c9bfcfa78083bb0a5f6cd2e0f1f175b16204178f373c95cca674e33eae52a",
       "since": "2025-01-01"
     },
     "subsystem:scheduler": {

package/upgrades/1.3.71.md

@@ -0,0 +1,58 @@
+# Instar Upgrade Guide — NEXT
+
+<!-- bump: patch -->
+
+## What Changed
+
+**Mentor cycle: Stage-A prompt capture no longer silently returns empty.**
+
+The mentor tick's Stage-A step spawns a short haiku session to *generate* the
+mentor prompt, then reads that session's output before delivering it to the
+mentee. Two bugs made that capture silently return empty — so a tick "ran" but
+delivered nothing (`delivered:false`, `stageAMsgLen:0`):
+
+1. **Transcript lookup got lost in a huge directory tree.** The Claude path of
+   `extractMenteeReplyFromTranscript` located the session transcript with a
+   *recursive* walk of `~/.claude/projects` bounded by a 10,000-step guard. On
+   a busy agent that folder holds far more than 10k nested directories, so the
+   depth-first walk burned its whole budget inside an unrelated subtree and gave
+   up *before reaching the right file* — even though the file sits exactly one
+   level down. Replaced with `findClaudeTranscriptShallow`, which scans only the
+   immediate children (the layout Claude actually uses:
+   `<projects>/<encoded-cwd>/<sessionId>.jsonl`). Finds it in milliseconds.
+
+2. **Capture raced the session lifecycle.** `spawnStageA` read the tmux pane
+   *after* the session completed (the reaper had already torn it down → empty),
+   and `claudeSessionId` is only flushed to the session record at completion —
+   a beat after the session leaves the running list. Now Stage-A (a) keeps the
+   last non-empty pane snapshot *while the session is alive* as a fallback, and
+   (b) prefers the persisted transcript, polling for `claudeSessionId` to land
+   and the final assistant block to be written (up to the session's own 5-min
+   max). It uses the *exact* `<claudeSessionId>.jsonl` — never newest-by-mtime,
+   since the agent runs many concurrent Claude sessions and mtime would grab an
+   unrelated transcript.
+
+## What to Tell Your User
+
+The scheduled mentor tick now reliably generates and delivers its prompt — the
+last gap that made the tick "fire but deliver nothing" is closed. No config
+changes; behavior is automatic.
+
+## Summary of New Capabilities
+
+| Capability | How to Use |
+|-----------|-----------|
+| Robust Stage-A prompt capture | Automatic — the generated mentor prompt is read from the session transcript (exact `<claudeSessionId>.jsonl`, depth-1 scan) with a capture-while-alive pane fallback. |
+| `findClaudeTranscriptShallow` | Pure, exported helper in `SessionReplyExtractor` — locates a Claude transcript by session id at its real depth-1 layout (no recursive walk). Unit-tested incl. a regression for the deep-subtree case. |
+
+## Evidence
+
+- Unit: `tests/unit/SessionReplyExtractor.test.ts` — 5 new cases for
+  `findClaudeTranscriptShallow`, including a regression that builds a 50-deep
+  unrelated subtree + 30 sibling encoded-cwd dirs and proves the depth-1 file is
+  still found (the exact shape the old recursive walk failed on).
+- Integration: `tests/integration/mentor-routes.test.ts` (the `/mentor/tick`
+  route) green; full mentor/mentee suite (63 tests) green.
+- Live: tick-driven round-trip verified — `/mentor/tick` → Stage-A generates
+  the prompt → delivered to the mentee → a clean-prose reply persisted to
+  `mentor-replies.jsonl` (evidence captured in the PR).

package/upgrades/1.3.72.md

@@ -0,0 +1,65 @@
+# Upgrade Guide — vNEXT
+
+<!-- bump: patch -->
+
+## What Changed
+
+**Topic-spam, locked down structurally.** A second Telegram topic-flood (after
+the 2026-05-22 sentinel flood) hit a live agent: a housekeeping feature raised one
+attention item per failed peer-resolution every sweep, and because
+`createAttentionItem` spawns a brand-new forum topic per item, that became a wall
+of topics. PR #495 already fixed *that feature* (a per-peer escalation cooldown).
+This change adds the **structural backstop** so the *class* of bug can't recur no
+matter which feature misbehaves next.
+
+**`AttentionTopicGuard` — a per-source + global circuit breaker** at the one
+chokepoint, `TelegramAdapter.createAttentionItem`. If a single attention
+`sourceContext` exceeds its topic budget within a rolling window (default 3 / 10
+min) — or, via a **global ceiling**, all sources collectively exceed it — further
+**non-critical** items are COALESCED into ONE reused "notices coalesced" topic and
+recorded in `state/attention-suppressed.jsonl` — never a wall. Invariants:
+HIGH/URGENT/CRITICAL items are **never** coalesced (critical messages always get
+their own topic), and **no item is dropped** — only its per-item topic is withheld;
+the item is still in the attention store. The global ceiling makes the protection
+hold even when a feature varies its `sourceContext` per item to dodge a per-source
+budget. Ships **enabled by default in code**, so every fleet agent is protected on
+the dist update with zero config.
+
+## What to Tell Your User
+
+- The "wall of topics popping up out of nowhere" problem is now fixed at its root.
+  If any background feature ever tries to flood the chat again, it's capped
+  automatically: a few topics at most, then everything folds into one quiet
+  "notices coalesced" topic, with the detail kept in the logs. Genuinely critical
+  alerts (HIGH/URGENT) are never affected — they always come through on their own.
+- No action or config needed; it's on by default.
+
+## Summary of New Capabilities
+
+| Capability | How to Use |
+|-----------|-----------|
+| Attention topic-flood circuit breaker | Automatic, on by default. Tune via `messaging[].config.attentionTopicGuard` = `{ "enabled": true, "windowMs": 600000, "maxTopicsPerSource": 3, "maxTopicsGlobal": 8 }`. |
+| Suppressed-notice audit trail | When a source is coalesced, each item is logged to `state/attention-suppressed.jsonl` (size-capped). Read it to answer "why are my notices grouped / where did topic X go?" |
+
+## Migration Notes
+
+Pure `src/` logic, **default-ON in code** (`AttentionTopicGuard` +
+`TelegramAdapter`) — no agent-installed file changed, so every agent receives the
+protection through the normal dist update with nothing to patch. A
+`migrateClaudeMd()` entry backfills the **Topic-Flood Guard** awareness section
+into existing agents' CLAUDE.md (idempotent). The redrive-specific offender fix
+shipped separately in PR #495.
+
+## Evidence
+
+- Unit: `tests/unit/AttentionTopicGuard.test.ts` (11) — budget / global-cap /
+  critical-bypass (case-insensitive) / per-source isolation / sustained-flood
+  single episode / post-silence reset / config-validation / key-eviction;
+  `tests/unit/PostUpdateMigrator-topicFloodGuard.test.ts` (2) — migrator backfill
+  + idempotency.
+- Integration: `tests/integration/attention-topic-flood-guard.test.ts` (4) — REAL
+  `TelegramAdapter`: a flooding source is capped at budget+1 topics, HIGH
+  bypasses, concurrent coalesced items create ONE topic, a different source is
+  unaffected, no item dropped, audit log populated.
+- E2E: `tests/e2e/attention-topic-flood-guard-lifecycle.test.ts` (1) — fleet
+  default (NO config) still caps a flood exactly (migration-parity guarantee).

package/upgrades/side-effects/attention-topic-flood-guard.md

@@ -0,0 +1,74 @@
+# Side-Effects Review — Attention Topic-Flood Guard
+
+**Spec:** `docs/specs/attention-topic-flood-guard.md` (converged, 4-reviewer panel)
+**Change:** per-source + global forum-topic circuit breaker at
+`TelegramAdapter.createAttentionItem` (the structural backstop). The redrive
+offender fix shipped separately in PR #495 (merged); the redrive edits originally
+bundled here were dropped to defer to it.
+**Files:** `src/messaging/AttentionTopicGuard.ts` (new),
+`src/messaging/TelegramAdapter.ts`, `src/core/PostUpdateMigrator.ts`, tests,
+`tests/unit/feature-delivery-completeness.test.ts`, `upgrades/NEXT.md`.
+
+## Phase 4 — the seven questions
+
+1. **Over-block.** The guard never blocks an agent action or drops an item — it
+   only changes *delivery form* (own topic vs. one coalesced topic + a log line)
+   for **non-critical** items. The one legitimate behavior it changes: a
+   non-critical source raising >3 items / 10 min has the surplus coalesced. That
+   is the *intended* behavior (the operator asked for exactly this) and is tunable
+   per adapter. HIGH/URGENT are never affected. No agent capability is rejected.
+
+2. **Under-block.** Before the global ceiling was added, a source varying its
+   `sourceContext` per item would have dodged the per-source budget — the review
+   caught this; the global cap + key eviction now bound it regardless of source
+   cardinality. Remaining under-block: a flood composed entirely of HIGH/URGENT
+   items is not coalesced (by design — critical items must always be visible). A
+   feature mis-marking routine noise as HIGH would still flood; that is a
+   mis-classification bug in that feature, not in the guard, and is the correct
+   place to fix it.
+
+3. **Level-of-abstraction fit.** Correct layer: the breaker sits at the single
+   chokepoint (`createAttentionItem`) where every attention item becomes a topic,
+   so it covers all current and future callers. It is deliberately *below* the
+   tone-gate authority on the `/attention` route (a transport-mechanics
+   rate-counter, not a content-judgment filter). The per-feature redrive fix
+   (PR #495) is at the feature layer; the guard is the substrate backstop — two
+   layers, by intent.
+
+4. **Signal vs authority.** Compliant. The guard holds no blocking authority over
+   agent behavior or information flow; it is a delivery *shaper* (the rate-counter
+   / transport-dedup carve-out in `docs/signal-vs-authority.md`), the same class as
+   `SentinelNotifier`. It never withholds a critical notice and never drops an
+   item.
+
+5. **Interactions.** Audited against `SentinelNotifier` (separate path → the
+   single reused system topic; no collision — it never flows through the guard) and
+   the `agent-attention-topic` (not registered in the attention maps, untouched).
+   Restart interaction (coalesced items vs. `loadAttentionItems` reverse-map
+   corruption) and concurrency (double-create race) were both found by review and
+   fixed. `updateAttentionStatus` no longer closes a shared topic when one
+   coalesced sibling resolves (coalesced items aren't in the per-item maps).
+
+6. **External surfaces.** User-visible change: a flooding source now produces one
+   "🔁 …: notices coalesced (flood guard)" topic instead of a wall; the rest goes
+   to `state/attention-suppressed.jsonl`. Fleet-wide via dist update, default-ON,
+   no config. No new network calls; no new external dependency. The CLAUDE.md
+   awareness section is backfilled to existing agents (idempotent migrator).
+
+7. **Rollback cost.** Cheap. Single config flag:
+   `messaging[].config.attentionTopicGuard.enabled = false` restores per-item-topic
+   behavior. No data migration, no agent-state repair (the guard holds only
+   in-memory counters). Worst case is a `src/` revert + patch release.
+
+## Phase 5 — second-pass review (REQUIRED: touches a "guard" + outbound messaging)
+
+An independent four-reviewer convergence panel (adversarial/security, integration,
+architecture, scalability) audited the change against the diff. It raised 7
+material concerns (global-cap dodge, `/ack`+shared-topic-close, case-sensitive
+critical bypass, double-create race, hex plaintext to unverified address, NaN
+config disable, unbounded audit log) plus framing notes. **6 of the 7 were fixed
+in code this iteration; the 7th (hex plaintext) was a finding on the redrive edits
+that are now deferred to the merged PR #495.** Full record:
+`docs/specs/attention-topic-flood-guard.convergence.md`. **Concur with the review —
+the design after this iteration addresses every raised concern; no blocking
+authority on brittle logic remains.**

package/upgrades/side-effects/stage-a-transcript-capture.md

@@ -0,0 +1,76 @@
+# Side-effects review — Stage-A transcript capture (mentor cycle)
+
+**Scope**: Close the last known mentor-cycle gap. The tick-driven path "ran but
+delivered nothing" because the Stage-A prompt-generation session's output was
+captured by (1) a recursive `~/.claude/projects` walk that exhausted its 10k
+guard before reaching the file, and (2) a post-reap tmux read that raced the
+session lifecycle. Make Stage-A capture deterministic and clean-prose.
+
+**Files touched**:
+- `src/monitoring/SessionReplyExtractor.ts` — new pure exported
+  `findClaudeTranscriptShallow(projectsDir, claudeSessionId)`: scans the
+  immediate children of `projects/` (+ root, defensively) for the exact
+  `<id>.jsonl`. Replaces the inline recursive walk. Adds `fs`/`path` imports.
+- `src/server/AgentServer.ts` —
+  - `extractMenteeReplyFromTranscript` is now `async`; its Claude path polls
+    up to ~240s for `claudeSessionId` (re-fetched from `state.getSession`) and
+    the final assistant block, using `findClaudeTranscriptShallow`. Codex path
+    unchanged (rollout-by-mtime, returns before the poll).
+    Caller (mentee role-handler) now `await`s it.
+  - `spawnStageA` keeps the last non-empty pane snapshot while the session is
+    alive (fallback), then prefers the transcript via the same helper; falls
+    back to the snapshot/pane only if no transcript is found. Adds two
+    `[stage-a-diag]` log lines (low frequency — once per tick).
+- `tests/unit/SessionReplyExtractor.test.ts` — 5 new cases for
+  `findClaudeTranscriptShallow` (depth-1 hit, root hit, deep-subtree
+  regression, no-descent guarantee, null-safety).
+- `upgrades/NEXT.md` — release note (patch bump).
+
+**Under-block (false negatives — does it ever now FAIL to capture a real reply?)**:
+- The Claude path requires the exact `<claudeSessionId>.jsonl`. If a session
+  never flushes `claudeSessionId` (e.g. killed before completion), the poll
+  returns null after ~240s — but `spawnStageA` then falls back to the
+  capture-while-alive pane snapshot, so a completed session still yields its
+  text. Net: strictly more robust than before (which had only the post-reap
+  read). The mentee role-handler retains its own tmux-capture fallback too.
+- The 240s poll only runs on the Claude branch. A codex mentee (Codey) returns
+  from the codex branch immediately — no added latency to the proven reply leg.
+
+**Over-block (false positives — does it capture the WRONG thing?)**:
+- Deliberately does NOT use newest-by-mtime for Claude: the agent runs many
+  concurrent Claude sessions, so mtime would grab an unrelated transcript. The
+  exact-id lookup is the correct disambiguator. This is the key reason the
+  helper is not symmetric with the codex (mtime) path.
+- `findClaudeTranscriptShallow` intentionally does NOT recurse: a transcript
+  buried >1 level deep is not matched. Claude never writes there, so this is
+  correct, not a gap (unit-tested: `does NOT descend into nested subdirs`).
+
+**Level-of-abstraction fit**: The transcript-locating logic moved OUT of an
+inline closure in `AgentServer` INTO the `SessionReplyExtractor` module, which
+already owns transcript reading. `AgentServer` keeps only the I/O orchestration
+(poll + fall back). The pure locator is now independently unit-testable — the
+root-cause fix has a real regression test instead of being trapped in a private
+method.
+
+**Signal vs authority**: No authority change. Stage-A capture is signal-only
+into the mentor tick; it gates nothing else. `isMenteeBusy` /
+OutstandingPromptTracker (the actual tick safe-window) is untouched.
+
+**Interactions**:
+- `extractMenteeReplyFromTranscript` becoming async ripples to exactly one
+  caller (the mentee role-handler), which now awaits it — verified by tsc.
+- The mentee codex reply leg (the proven `FULL-…` round-trip path) is behavior-
+  unchanged: same codex rollout extraction, no poll.
+- Adds two `console.log('[stage-a-diag] …')` lines in `spawnStageA`. They fire
+  once per mentor tick (low frequency) and carry only session id / framework /
+  lengths — no transcript content (no Stage-A leak surface).
+
+**Migration parity**: Pure code change in shipped `dist/` — no agent-installed
+files (settings hooks, config defaults, CLAUDE.md template, hook scripts,
+skills) touched. Existing agents pick it up via the normal auto-update of the
+`instar` package. No `PostUpdateMigrator` entry required.
+
+**Spec**: MENTOR-LIVE-READINESS-SPEC §Recipient side (Stage-A is the
+prompt-generation step that feeds `deliverToMentee`). This fix is the third
+instance of the same capture-race class (#480 fixed the mentee-reply and
+isMenteeBusy instances); it completes the §Recipient-side capture story.