--- status: fixed trigger: "probetest.log line 109 — ECHO-FIRE orphan-path fired immediately after binary handoff (iter 1) while Self listener was only transiently unreachable; grace recheck 21s later confirmed Self alive and suppressed INIT_SIGNOFF, but the echo-commune had already fired and been delivered (line 110, line 120)" created: 2026-05-23T22:55:00-07:00 updated: 2026-05-23T23:10:00-07:00 --- ## Current Focus hypothesis: CONFIRMED — In `src/live/wrapper/orphan.rs::check_orphan`, the Phase 29 Plan 04 orphan-path ECHO-FIRE block (lines 167-199) executes BEFORE the 5-second grace-period sleep + still_gone recheck (lines 201-225). A transient false-orphan signal (Self listener momentarily unreachable during binary handoff, or any other brief probe failure) therefore fires `_echo-commune --force` and delivers a phantom echo_commune envelope to the Psyche inbox even when Self recovers within the grace window and INIT_SIGNOFF is correctly suppressed. The grace-period guard introduced by quick-260520-mth was retrofitted around INIT_SIGNOFF delivery only — the synchronous ECHO-FIRE added later by Phase 29 Plan 04 inherited the unguarded position above the sleep. test: log timeline reconstruction (probetest.log lines 102-115) + direct source reading of orphan.rs + new source-order regression test `test_sync_fire_argv_appears_after_still_gone_recheck_and_recovery_return` (passes, pins new ordering) expecting: ECHO-FIRE log emits AFTER `still_gone` recheck returns true, never before next_action: none — fix applied + 14 orphan_fire_tests pass + 147 wrapper tests pass + 898 lib tests pass ## Symptoms expected: When the Psyche wrapper completes a binary handoff and starts inner-poll iteration 1, `check_orphan` should either (a) observe Self alive and return false silently, OR (b) observe Self apparently gone, sleep 5s, recheck — if Self recovered, log "Self parent recovered" and return false WITHOUT firing ECHO-FIRE or INIT_SIGNOFF. actual: ECHO-FIRE fires unconditionally on the first `self_alive == false` reading, BEFORE the grace period sleep. The synchronous fire blocks ~19s waiting for the haiku subprocess (line 109 → line 113 = 21s wall time). When the grace recheck then succeeds (line 115), the wrapper logs "Self parent recovered" and skips INIT_SIGNOFF — but the phantom echo-commune envelope has already been composed and delivered (line 110 ECHO_COMMUNE block; line 120 wrapper drains its own freshly-emitted envelope). errors: none (silent semantic violation — the ECHO-FIRE succeeds technically; it just shouldn't have run) reproduction: trigger a binary handoff (or any other transient Self-perch probe failure) while the Self listener is mid-cycle. New wrapper boots, iteration 1 calls `check_orphan`, evaluates `self_alive` against a momentarily-stale `parent_pid` liveness probe → enters orphan branch → fires ECHO-FIRE → sleeps 5s → recovers. started: Phase 29 Plan 04 (AUTO-EC-02) — when the synchronous orphan-path `_echo-commune --force` was added to `check_orphan`. The grace guard already existed (per quick-260520-mth) but only covered compose+deliver of INIT_SIGNOFF. ## Evidence - timestamp: 2026-05-23T22:50:20 source: C:\Users\decid\AppData\Local\spt\logs_latest\probetest.log:102-115 finding: | 102: [22:50:20] poll exited code=2 stderr=HANDOFF_DEFER:probetest-psyche 105: [22:50:20] HANDOFF wrapper: new pid=47612, exiting 106: [22:50:20] wrapper started gen=1 ... handoff_hydrated=true 108: [22:50:20] poll iteration 1 starting 109: [22:50:20] [ECHO-FIRE] orphan-path: spawning _echo-commune --force (no timeout) 110: --- ECHO_COMMUNE 2026-05-23T22:50:39-07:00 ... exit=0 stdout_bytes=2830 ... 113: [22:50:41] [ECHO-FIRE] orphan-path: exit=0 stdout_bytes=0 stderr_bytes=245 114: [22:50:41] Self parent session is gone ... entering grace period before INIT_SIGNOFF 115: [22:50:46] Self parent recovered during grace period, continuing normally 120: [22:50:46] [MSG] from=