@agentvault/muse-bridge 0.1.15 → 0.1.17

package/dist/bridge.d.ts

@@ -76,6 +76,23 @@ export declare function attachLifecycle(channel: LifecycleChannel, opts?: {
     }) => void;
 }): void;
 export declare function roomTurnPrefix(roomId: string, senderName: string, roomName?: string): string;
+/**
+ * Does this agent owe a reply to this room message? (#1107)
+ *
+ * This bridge used to answer with `e.senderIsAgent === false` — "reply to any
+ * human". That was a THIRD implementation of the room reply rule, alongside the
+ * OpenClaw plugin and hermes, and #1107 shipped to the other two only. Under the
+ * old rule this agent would still have answered every un-mentioned message while
+ * wren, cortina, smartcode and smartcoder2 stayed quiet: the cascade, half-fixed,
+ * in the half most likely to be read as "the protocol doesn't work".
+ *
+ * Now it defers to the ONE shared implementation exported by
+ * `@agentvault/agentvault`. The message is still pushed into the session either
+ * way — the agent reads the whole room and only the reply obligation changes.
+ */
+export declare function _makeOwesReply(agentName: string | undefined, channel: {
+    ownDisplayName?: string;
+}, log: (msg: string) => void): (e: RoomMessage) => boolean;
 export declare function wireBridge(channel: RoomChannel, session: RoomSession, target: ActiveTarget, opts?: {
     /**
      * #1107: this agent's own name, used to recognise its own @mention. Threaded