@reticlehq/server 3.7.0 → 3.8.1

package/dist/memory/recall/project-memory.js

@@ -14,7 +14,7 @@
 import { cloudFetch } from '../cloud/cloud-sync.js';
 import { callingClientName } from '../../hooks/coding-agents.js';
 import { resolveProjectCloud } from '../cloud/cloud-config.js';
-import { isReadableMemoryScope, MemoryReadHeader, memoryReadUrl, scopedMemoryEntries, scopeOfMemoryResponse, } from '../cloud/memory-scope.js';
+import { isReadableMemoryScope, MemoryReadHeader, readMemoryPages, scopedMemoryEntries, scopeOfMemoryResponse, } from '../cloud/memory-scope.js';
 /**
  * Named so a read from the tool surface is distinguishable from the CLI's and from replay's. The
  * reader is the MCP client that made the call when one can be named; this only when none can.
@@ -106,30 +106,26 @@ export async function readProjectMemory(fs, root, home, env, opts) {
         return { ok: false, reason: MemoryUnavailable.NOT_LINKED };
     if (!cloud.policy.memory)
         return { ok: false, reason: MemoryUnavailable.DISABLED };
+    const config = cloud.config;
     // Scoped to the LINKED project, not to whatever the key happens to cover. A workspace can hold
     // more than one repo, and a read that named no project could be answered with another one's
     // established knowledge — indistinguishable from this project's, and acted on. See memory-scope.
-    const url = memoryReadUrl(cloud.config.url, {
-        projectId: cloud.projectId,
-        subject: opts.subject,
-    });
     try {
-        const res = await cloudFetch(url, {
-            method: 'GET',
-            headers: {
-                authorization: `Bearer ${cloud.config.apiKey}`,
-                // What makes this read COUNT as an agent consulting the corpus rather than a human
-                // browsing — the distinction the dashboard's "times an agent consulted it" rests on.
-                [MemoryReadHeader.AGENT]: callingClientName() ?? MCP_AGENT_ID,
-            },
+        const body = await readMemoryPages(config.url, { projectId: cloud.projectId, subject: opts.subject }, async (url) => {
+            const res = await cloudFetch(url, {
+                method: 'GET',
+                headers: {
+                    authorization: `Bearer ${config.apiKey}`,
+                    // What makes this read COUNT as an agent consulting the corpus rather than a human
+                    // browsing — the distinction the dashboard's "times an agent consulted it" rests on.
+                    [MemoryReadHeader.AGENT]: callingClientName() ?? MCP_AGENT_ID,
+                },
+            });
+            // `cloudFetch` returns a real Response, so the body is a METHOD (see the note in replay).
+            return 200 === res.status ? await res.json() : undefined;
         });
-        if (200 !== res.status)
+        if (body === undefined)
             return { ok: false, reason: MemoryUnavailable.UNREACHABLE };
-        // `cloudFetch` returns a real Response, so the body is a METHOD. Reading `res.json` as a
-        // property yields the function, and every downstream field is undefined — a silent "the project
-        // knows nothing" that is indistinguishable from the honest empty case. It cost a live drive to
-        // find once already.
-        const body = await res.json();
         // The envelope first, and it decides everything. The platform names the project on the response
         // and NOT on each entry, so an entry-level filter alone keeps a whole sibling workspace while
         // looking like it did something — see `memory-scope.ts`. A response that names another project,

package/dist/portal/bridge/auth-failure-reason.d.ts

@@ -30,3 +30,16 @@
  */
 export declare function isAuthRefusalReason(reason: string | undefined): boolean;
 export declare function authFailureReason(servedProjects: ReadonlySet<string>, helloProject: string | undefined, helloToken?: string): string;
+/**
+ * A dial turned away at the ORIGIN gate, in words the reader can act on.
+ *
+ * This is the refusal that used to leave no trace anywhere. It happens before any HELLO, so it
+ * produced no `noteClosure`, no `session_disconnected`, nothing but an `origin_rejected` log line —
+ * and the daemon log is the file nobody opens until they have already lost the afternoon. Reported
+ * from a multi-tenant app resolving its tenant from the `Host` header: on a hosts-file alias every
+ * dial was refused here, `doctor` reported every check green, and the lease hint blamed the port.
+ *
+ * The origin is IN the message because it is the fix: it is either the alias to allow-list, or the
+ * proof that the page is not being served from where the developer thinks it is.
+ */
+export declare function originRejectedReason(origin: string | undefined): string;

package/dist/portal/bridge/auth-failure-reason.js

@@ -71,3 +71,22 @@ export function authFailureReason(servedProjects, helloProject, helloToken) {
         return NO_TOKEN;
     return Buffer.byteLength(WRONG_TOKEN, 'utf8') <= MAX_REASON_BYTES ? WRONG_TOKEN : PLAIN;
 }
+/**
+ * A dial turned away at the ORIGIN gate, in words the reader can act on.
+ *
+ * This is the refusal that used to leave no trace anywhere. It happens before any HELLO, so it
+ * produced no `noteClosure`, no `session_disconnected`, nothing but an `origin_rejected` log line —
+ * and the daemon log is the file nobody opens until they have already lost the afternoon. Reported
+ * from a multi-tenant app resolving its tenant from the `Host` header: on a hosts-file alias every
+ * dial was refused here, `doctor` reported every check green, and the lease hint blamed the port.
+ *
+ * The origin is IN the message because it is the fix: it is either the alias to allow-list, or the
+ * proof that the page is not being served from where the developer thinks it is.
+ */
+export function originRejectedReason(origin) {
+    const named = origin === undefined || 0 === origin.length ? 'a page sending no Origin' : origin;
+    return (`a browser dialled this daemon and was REFUSED at the origin gate: ${named} is not allowed. ` +
+        'Off localhost the SDK needs BOTH `allowNonLocalhost: true` AND a pairing token, and the ' +
+        'daemon needs that origin allow-listed (RETICLE_ALLOWED_ORIGINS). The app is running and ' +
+        'instrumented — it was turned away, so do not go looking for a stopped dev server.');
+}

package/dist/portal/bridge/bridge.d.ts

@@ -1,6 +1,8 @@
 import * as http from 'node:http';
 import { Session } from '../session/session.js';
 import { SessionManager } from '../session/session-manager.js';
+import { SessionNonces } from './session-nonces.js';
+import type { FollowNavigation } from './origin/origin-follow.js';
 import { type HarnessRequest } from './harness-request.js';
 import { pairingTokenSource } from './pairing-token.js';
 /** A human clicked ▶ on a saved flow in the panel — replay it with no agent. Wired by the daemon. */
@@ -41,12 +43,19 @@ export declare const WS_CLOSE_REASON: {
     readonly HANDSHAKE_POOL_FULL: string;
     /**
      * A page's HELLO failed the wire schema for a reason other than its protocol number — the SDK and
-     * this daemon are different releases whose contracts no longer agree. The socket is still closed
-     * with the short `invalid message` the SDK already prints; this is the sentence the no-session
-     * diagnosis records, because "never dialled the bridge" was what `init` said about a page this
-     * daemon had just turned away. Same `cause — fix` shape as the protocol-skew reasons.
+     * this daemon are different releases whose contracts no longer agree. The socket is closed with
+     * INVALID_HELLO_CLOSE, the short form of this that fits the 123-byte close-reason limit; this is
+     * the sentence the no-session diagnosis records, because "never dialled the bridge" was what `init`
+     * said about a page this daemon had just turned away. Same `cause — fix` shape as the
+     * protocol-skew reasons.
      */
     readonly INVALID_HELLO: string;
+    /**
+     * The close-frame form of INVALID_HELLO. The full sentence is far over the 123-byte close-reason
+     * limit, so this is the same `cause - fix` in one line. ASCII only: a multi-byte dash would
+     * spend the budget faster than the character count suggests.
+     */
+    readonly INVALID_HELLO_CLOSE: "invalid hello: version skew. Put SDK, build plugin and server on one release.";
 };
 interface BridgeOptions {
     port: number;
@@ -72,6 +81,8 @@ interface BridgeOptions {
      * it get the no-project fallback.
      */
     sdkFix?: (projectId?: string) => string;
+    /** Lets a session follow its own navigation to an origin not allow-listed. See origin-follow.ts. */
+    followNavigation?: FollowNavigation;
 }
 /**
  * The browser-facing half of the relay: a localhost WebSocket server. Each connection
@@ -81,6 +92,8 @@ interface BridgeOptions {
 export declare class Bridge {
     #private;
     readonly sessions: SessionManager;
+    /** Single-use HELLO tokens for pages that cannot hold the pairing token. Minted by local callers only. */
+    readonly nonces: SessionNonces;
     /** Resolves with the actually-bound port once the server is listening. */
     readonly ready: Promise<number>;
     constructor(options: BridgeOptions);
@@ -119,6 +132,8 @@ export declare class Bridge {
     attachSigninRequest(handler: (from: Session) => void): void;
     /** Register a handler to run when a session connects. Additive — every handler runs. */
     attachSessionCreate(handler: (session: Session) => void): void;
+    /** Run `handler` when a session that connected without a project id names one in a later HELLO. */
+    attachProjectAdopted(handler: (session: Session) => void): void;
     close(): Promise<void>;
 }
 export {};