instar 1.3.163 → 1.3.165

package/dist/commands/server.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"server.d.ts","sourceRoot":"","sources":["../../src/commands/server.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAsSH,UAAU,YAAY;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb;2DACuD;IACvD,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAqwDD,wBAAsB,WAAW,CAAC,OAAO,EAAE,YAAY,GAAG,OAAO,CAAC,IAAI,CAAC,CA0vPtE;AAED,wBAAsB,UAAU,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAsDzE;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,aAAa,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAuD5E"}
+{"version":3,"file":"server.d.ts","sourceRoot":"","sources":["../../src/commands/server.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAsSH,UAAU,YAAY;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb;2DACuD;IACvD,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAqwDD,wBAAsB,WAAW,CAAC,OAAO,EAAE,YAAY,GAAG,OAAO,CAAC,IAAI,CAAC,CA6xPtE;AAED,wBAAsB,UAAU,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAsDzE;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,aAAa,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAuD5E"}

package/dist/commands/server.js

@@ -8779,6 +8779,14 @@ export async function startServer(options) {
                             const r = ownReg.cas({ type: 'place', machineId }, { sessionKey: sk, sender: meshSelfId, nonce: `${meshSelfId}:c:${++routerNonce}` });
                             return { ok: r.ok, epoch: ownReg.read(sk)?.ownershipEpoch ?? 0 };
                         },
+                        // bug #11: confirm the remote owner (placing → active) after the spawn is
+                        // dispatched. The router holds the authoritative ownReg (single-router
+                        // topology); the FSM permits a claim whose machineId equals the placed
+                        // owner, so the router confirms on the target's behalf. Without this the
+                        // record stays 'placing' and every later message for the session queues.
+                        confirmClaim: (sk, machineId) => {
+                            ownReg.cas({ type: 'claim', machineId }, { sessionKey: sk, sender: meshSelfId, nonce: `${meshSelfId}:cl:${++routerNonce}` });
+                        },
                         deliverMessage: async (target, env) => {
                             const url = peerUrl(target);
                             if (!url)
@@ -8844,6 +8852,36 @@ export async function startServer(options) {
                         }
                     };
                     console.log(pc.green('  SessionRouter wired (L4) — inert until rollout stage advances past dark'));
+                    // bug #7: tokenless-standby outbound Telegram relay. TelegramAdapter.sendToTopic
+                    // only invokes this when the adapter has NO bot token (a pool standby serving a
+                    // session moved to it); a token-holding router never calls it. It relays the send
+                    // to the Telegram-OWNING lease holder's /telegram/reply, so a moved session's
+                    // replies reach the user without the standby ever sending on the shared bot
+                    // (preserving the single-Telegram-owner invariant — the 409-conflict guard).
+                    if (telegram) {
+                        telegram.outboundRelay = async (topicId, text, opts) => {
+                            const holder = coordinator.getSyncStatus().leaseHolder;
+                            if (!holder || holder === meshSelfId)
+                                return null; // we ARE the owner, or none known
+                            const url = peerUrl(holder);
+                            if (!url)
+                                return null;
+                            try {
+                                const resp = await fetch(`${url}/telegram/reply/${topicId}`, {
+                                    method: 'POST',
+                                    headers: { 'Content-Type': 'application/json', 'Authorization': `Bearer ${config.authToken}` },
+                                    body: JSON.stringify({ text, ...(opts?.silent ? { silent: true } : {}) }),
+                                });
+                                if (!resp.ok)
+                                    return null;
+                                const j = (await resp.json().catch(() => ({})));
+                                return { messageId: j.messageId ?? 0, topicId };
+                            }
+                            catch {
+                                return null; // relay unreachable → sendToTopic surfaces the failure
+                            }
+                        };
+                    }
                     // ── L4 transfer-by-nickname activation: the "move/run this on <nickname>"
                     // trigger. The recognizer + planner are pure units; this wires them to the
                     // pin store + ownership so a recognized command pins the topic to the named