@agentvault/claude-bridge 0.1.1 → 0.2.0

package/dist/bridge.d.ts

@@ -5,12 +5,39 @@ export interface RoomMessage {
 }
 export interface RoomChannel {
     on(ev: "room_message", cb: (e: RoomMessage) => void): unknown;
+    on(ev: "error", cb: (err: unknown) => void): unknown;
     sendToRoom(roomId: string, text: string): Promise<void>;
 }
 export interface RoomSession {
     push(text: string): void;
     onActiveRoom(roomId: string): void;
 }
+export interface LifecycleChannel {
+    on(ev: "auth_failed", cb: (e: {
+        reason: string;
+    }) => void): unknown;
+    on(ev: "session_replaced", cb: (e: {
+        code?: number;
+    }) => void): unknown;
+    on(ev: "error", cb: (err: unknown) => void): unknown;
+}
+/**
+ * Wire terminal lifecycle events — conditions SecureChannel can't recover from
+ * by reconnecting, after which the daemon would otherwise idle forever. We log
+ * clearly and exit. Three terminal signals:
+ *   - `auth_failed`      — device revoked / JWT expired (needs re-enroll).
+ *   - `session_replaced` — another session took over (close code 4000/4001).
+ *   - `error` matching "Reconnect loop detected" — the one terminal error the
+ *     channel emits AFTER it has given up reconnecting.
+ * All OTHER `error` events are transient (handled + survived by wireBridge's
+ * own `error` listener, #387) and recover via the built-in reconnect — so we
+ * deliberately do NOT exit on the generic `error`/`"error"`-state, which would
+ * regress that survival behavior.
+ */
+export declare function attachLifecycle(channel: LifecycleChannel, opts?: {
+    log?: (msg: string) => void;
+    onTerminal?: (reason: string) => void;
+}): void;
 export declare function wireBridge(channel: RoomChannel, session: RoomSession, opts?: {
     roomFilter?: string;
     log?: (msg: string) => void;