{"body":"Current-session evidence from adapter owner emphasys (read-only, PID20196 log): first process log04:37:56.220Z; initial listener reports SID_BIND/BOUND/READY at04:37:59.193Z. Explicit api bind success is not separately logged; preceding bind success is INFERRED from the loaded extension's checked bind-before-listen sequence, not directly timed.\n\nDirectly observed recovery at04:41:57.722Z: emit-silence watchdog LISTENER_RESTART_ON_SILENCE, listener SIGTERM04:41:57.725Z, replacement SID_BIND/BOUND04:41:58.038Z and READY04:41:58.051Z. This is a listener rebind, without a separate api bind command; never describe it as no binding at all. Replacement PID40128 matches current info. Broker PTY parent41420 and harness20196 remain live from04:37:55Z.\n\nThe source-defined loss path is startup.rs resolve_controllable: ListenerOnly with prior=true and proven prior relay death returns None. Relay lifetime is not PTY lifetime. registryhost then converts None into harness_only=true; remote rc refuses from gossip before owner session resolution. Current local and remote snapshots evaluate that refusal predicate true. The exact pre/post controllable transition was not captured; relay-recovery attribution is an evidence-backed inference, while the current false advertisement and refusing predicate are directly verified. Earlier boot-time HOSTING_AUTHORITY_DEMOTED is a separate prior event, not proof of a second demotion at04:41.\n\nDiagnosis did not execute rc --take, mutate info, rebind, or restart the live endpoint. Recovery should be extension-owned and preserve session/relay custody; a supported same-session bind may re-earn authority, but is not a durable fix for subsequent listener recovery. No recovery result claimed.\n\n*\\-doyle@HFENDULEAM*","url":"https://github.com/BigscreenVR/spt-bs-releases/issues/303#issuecomment-5630071313"}