@agentvault/muse-bridge 0.1.21 → 0.1.23

package/README.md

@@ -45,3 +45,25 @@ pruned cache path.
 `--yolo` only when both Access grants are on (`workAllowed` and `gatesRemoved`).
 Otherwise `--disable-shell` and `--disable-write` (no terminal, no file-tool
 writes).
+
+## Meta reasoning recovery
+
+Every native Meta Muse turn uses a temporary loopback adapter pinned to Meta's
+Responses API. It removes opaque reasoning from older settled turns while
+preserving conversation messages, tool calls/results, settings, and the existing
+Muse session. Reasoning in the current tool loop stays until Meta rejects that
+request with the specific encrypted reasoning expiry error. The adapter then
+retries that provider request once with its remaining reasoning removed; Muse and
+its tools are not restarted or replayed. Successful SSE responses stream through.
+Opaque requests using `previous_response_id` pass through without rewriting.
+
+Removed reasoning cannot contribute its previous private reasoning continuity;
+the conversation and tool history remain available. The adapter neither edits
+Muse journals nor rotates session IDs. It binds only to loopback with a fresh
+secret route and closes at turn end. Diagnostics contain counts and fixed outcomes.
+
+If an eligible room or owner-attested DM turn fails before attempting a reply,
+the bridge attempts one generic failure notice on that turn's captured reply
+channel. The notice waits at most ten seconds before the next queued turn advances.
+Echo exec/provider behavior remains unchanged; eligible terminal failure notices
+apply to both providers.

package/dist/enrollment-fingerprint.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Show the device fingerprint the owner must match before clicking Approve.
+ *
+ * The app's Connect card says "Match this with your agent's terminal output",
+ * but only the OpenClaw `setup` printed one. The muse bridge enrols in the
+ * FOREGROUND (`install` refuses without persisted creds), so its log sink —
+ * stderr — is the customer's terminal at that moment.
+ *
+ * The value is the one the enrolment response returns (`SecureChannel.fingerprint`,
+ * set before the channel enters "polling") — the backend's
+ * `_compute_fingerprint`: BLAKE2b-8 of the identity public key as colon-separated
+ * hex (`a1:b2:c3:d4:e5:f6:78:90`), the exact string the app displays. Printed
+ * as-is, never recomputed, so the two cannot drift.
+ */
+/** The lines shown to the customer — same wording as the OpenClaw setup. */
+export declare function fingerprintLines(fingerprint: string): string[];
+interface FingerprintChannel {
+    on(ev: "state", cb: (s: string) => void): unknown;
+    readonly fingerprint?: string | null;
+}
+/** Log the fingerprint when the channel starts waiting for approval. */
+export declare function watchEnrollmentFingerprint(channel: FingerprintChannel, log: (msg: string) => void): void;
+export {};
+//# sourceMappingURL=enrollment-fingerprint.d.ts.map

package/dist/index.d.ts

@@ -11,6 +11,8 @@ export declare function maybeRunRecoverySubcommand(argv?: string[], env?: NodeJS
 export type BootChannel = RoomChannel & LifecycleChannel & {
     start(): Promise<void>;
     stop(): Promise<void>;
+    /** Set by SecureChannel from the enrolment response, before "polling". */
+    readonly fingerprint?: string | null;
 };
 export interface MainOpts {
     env?: NodeJS.ProcessEnv;