@reticlehq/server 2.9.0 → 2.11.0

package/dist/project/artifact-root.d.ts

@@ -0,0 +1,83 @@
+import { type ProjectCandidate, type ProjectRegistry } from '@reticlehq/core';
+import type { ConfigDiscovery } from '../cli/config-discovery.js';
+/**
+ * Which `.reticle/` a session's artifacts belong in.
+ *
+ * Everything Reticle persists — flows, the capability contract, baselines, capsules, the cross-run
+ * project memory — used to resolve against the DAEMON's own `process.cwd()`. That is a statement
+ * about where the daemon was launched and it was being read as a statement about which project is
+ * being verified. Those are not the same thing and are usually not even the same tree: a user-scoped
+ * MCP registration is the common case, and the editor that spawns it starts it wherever it likes.
+ *
+ * Three field shapes, one defect: `cwd=/` gave `ENOENT: mkdir '/.reticle'`; a daemon started in
+ * project A wrote project B's flow into A's checkout and reported success without naming the path;
+ * and `verify_change` could only answer "unknown" because no flow could be persisted for it to match
+ * against.
+ *
+ * ## Two sources, one rule
+ *
+ * Candidates arrive from config discovery (which walks out from the daemon's own directory) and from
+ * the user-level project registry (which `init` writes, and which reaches checkouts discovery cannot
+ * see). This function takes the merged list and does not know or care which source an entry came
+ * from — a privileged source would be a second rule, and two rules for one question is how the
+ * answers start disagreeing.
+ *
+ * ## Why matching on projectId, and not a new wire field
+ *
+ * HELLO already stamps `projectId`, and `.reticle.json` already declares the same id sitting next to
+ * the code it configures. The join is therefore available today, for every SDK already in the field.
+ * Adding a `root` to HELLO would move the wire contract, strand every older SDK on the fallback, and
+ * buy nothing this does not already give.
+ *
+ * ## Why it can decline to answer
+ *
+ * Every non-matching branch returns the daemon root and SAYS which branch it was. A wrong root is
+ * worse than no root — it writes a caller's evidence into a tree they never drove — so the ambiguous
+ * case refuses rather than picks, exactly as `discoverProjectConfigs` refuses to pick one config.
+ * The reason travels with the answer so callers can report the surprise instead of hiding it.
+ */
+/** Why the root below is the root. Travels with the answer so a caller can say what happened. */
+export declare const ArtifactRootReason: {
+    /** Exactly one discovered config declares this session's project. The good case. */
+    readonly MATCHED_PROJECT: "matched-project";
+    /** The session declared no projectId — a pre-2.0 SDK. Nothing to match on. */
+    readonly NO_PROJECT_ID: "no-project-id";
+    /** The search ran and nothing it found declares this project. */
+    readonly NO_MATCH: "no-match";
+    /** Two or more checkouts declare this project. Refused rather than guessed. */
+    readonly AMBIGUOUS: "ambiguous";
+};
+export type ArtifactRootReason = (typeof ArtifactRootReason)[keyof typeof ArtifactRootReason];
+export interface ArtifactRootQuery {
+    /** The connected session's HELLO projectId, when it sent one. */
+    projectId: string | undefined;
+    /** Every project this machine knows about. Supplied, not gathered here — this stays pure. */
+    candidates: readonly ProjectCandidate[];
+    /** Where artifacts go when the project cannot be identified. Already a `.reticle` path. */
+    daemonRoot: string;
+}
+export interface ArtifactRoot {
+    /** Absolute path to the `.reticle` directory. Always present, on every branch. */
+    root: string;
+    reason: ArtifactRootReason;
+    /**
+     * The competing project directories, on `AMBIGUOUS` only. A caller that has to explain the refusal
+     * needs to name them; a caller that does not can ignore the field.
+     */
+    candidates?: string[];
+}
+/**
+ * Resolve the artifact root for one session.
+ *
+ * Pure: no IO, no cwd, no clock. The filesystem walk belongs to `discoverProjectConfigs` and is
+ * passed in, which is what makes every branch below testable without a fixture tree.
+ */
+export declare function resolveArtifactRoot(query: ArtifactRootQuery): ArtifactRoot;
+/**
+ * Everything this machine knows about where projects live, from both sources.
+ *
+ * Discovery first, deliberately: it read a `.reticle.json` that exists RIGHT NOW, while the registry
+ * is a cache of something `init` saw once. Order only decides which duplicate survives dedupe, and
+ * the one confirmed a moment ago is the better survivor.
+ */
+export declare function projectCandidatesFrom(discovery: ConfigDiscovery, registry: ProjectRegistry): ProjectCandidate[];

package/dist/project/artifact-root.js

@@ -0,0 +1,112 @@
+import { join } from 'node:path';
+import { ReticleDir, projectCandidates, } from '@reticlehq/core';
+/**
+ * Which `.reticle/` a session's artifacts belong in.
+ *
+ * Everything Reticle persists — flows, the capability contract, baselines, capsules, the cross-run
+ * project memory — used to resolve against the DAEMON's own `process.cwd()`. That is a statement
+ * about where the daemon was launched and it was being read as a statement about which project is
+ * being verified. Those are not the same thing and are usually not even the same tree: a user-scoped
+ * MCP registration is the common case, and the editor that spawns it starts it wherever it likes.
+ *
+ * Three field shapes, one defect: `cwd=/` gave `ENOENT: mkdir '/.reticle'`; a daemon started in
+ * project A wrote project B's flow into A's checkout and reported success without naming the path;
+ * and `verify_change` could only answer "unknown" because no flow could be persisted for it to match
+ * against.
+ *
+ * ## Two sources, one rule
+ *
+ * Candidates arrive from config discovery (which walks out from the daemon's own directory) and from
+ * the user-level project registry (which `init` writes, and which reaches checkouts discovery cannot
+ * see). This function takes the merged list and does not know or care which source an entry came
+ * from — a privileged source would be a second rule, and two rules for one question is how the
+ * answers start disagreeing.
+ *
+ * ## Why matching on projectId, and not a new wire field
+ *
+ * HELLO already stamps `projectId`, and `.reticle.json` already declares the same id sitting next to
+ * the code it configures. The join is therefore available today, for every SDK already in the field.
+ * Adding a `root` to HELLO would move the wire contract, strand every older SDK on the fallback, and
+ * buy nothing this does not already give.
+ *
+ * ## Why it can decline to answer
+ *
+ * Every non-matching branch returns the daemon root and SAYS which branch it was. A wrong root is
+ * worse than no root — it writes a caller's evidence into a tree they never drove — so the ambiguous
+ * case refuses rather than picks, exactly as `discoverProjectConfigs` refuses to pick one config.
+ * The reason travels with the answer so callers can report the surprise instead of hiding it.
+ */
+/** Why the root below is the root. Travels with the answer so a caller can say what happened. */
+export const ArtifactRootReason = {
+    /** Exactly one discovered config declares this session's project. The good case. */
+    MATCHED_PROJECT: 'matched-project',
+    /** The session declared no projectId — a pre-2.0 SDK. Nothing to match on. */
+    NO_PROJECT_ID: 'no-project-id',
+    /** The search ran and nothing it found declares this project. */
+    NO_MATCH: 'no-match',
+    /** Two or more checkouts declare this project. Refused rather than guessed. */
+    AMBIGUOUS: 'ambiguous',
+};
+/**
+ * Resolve the artifact root for one session.
+ *
+ * Pure: no IO, no cwd, no clock. The filesystem walk belongs to `discoverProjectConfigs` and is
+ * passed in, which is what makes every branch below testable without a fixture tree.
+ */
+export function resolveArtifactRoot(query) {
+    const { projectId, candidates, daemonRoot } = query;
+    if (projectId === undefined || 0 === projectId.length) {
+        return { root: daemonRoot, reason: ArtifactRootReason.NO_PROJECT_ID };
+    }
+    const matches = dedupeByDirectory(candidates.filter((c) => c.projectId === projectId));
+    if (0 === matches.length) {
+        return { root: daemonRoot, reason: ArtifactRootReason.NO_MATCH };
+    }
+    if (matches.length > 1) {
+        return {
+            root: daemonRoot,
+            reason: ArtifactRootReason.AMBIGUOUS,
+            candidates: matches.map((config) => config.directory),
+        };
+    }
+    const [only] = matches;
+    // `matches.length === 1` above, so this is defined — but the codebase forbids `!`, and a default
+    // that can never be taken is cheaper than the alternative spelling.
+    const directory = only?.directory ?? '';
+    if (0 === directory.length) {
+        return { root: daemonRoot, reason: ArtifactRootReason.NO_MATCH };
+    }
+    return { root: join(directory, ReticleDir.ROOT), reason: ArtifactRootReason.MATCHED_PROJECT };
+}
+/**
+ * One entry per directory.
+ *
+ * Discovery and the registry routinely name the SAME checkout — the registry remembers what `init`
+ * wrote, and discovery finds that same file whenever the daemon happens to be in the tree. Counting
+ * it twice would read as two competing checkouts and make the resolver refuse, which is the one
+ * outcome worse than either source alone.
+ */
+function dedupeByDirectory(matches) {
+    const seen = new Set();
+    const out = [];
+    for (const candidate of matches) {
+        if (seen.has(candidate.directory))
+            continue;
+        seen.add(candidate.directory);
+        out.push(candidate);
+    }
+    return out;
+}
+/**
+ * Everything this machine knows about where projects live, from both sources.
+ *
+ * Discovery first, deliberately: it read a `.reticle.json` that exists RIGHT NOW, while the registry
+ * is a cache of something `init` saw once. Order only decides which duplicate survives dedupe, and
+ * the one confirmed a moment ago is the better survivor.
+ */
+export function projectCandidatesFrom(discovery, registry) {
+    const discovered = discovery.found.flatMap((config) => config.projectId === undefined || 0 === config.projectId.length
+        ? []
+        : [{ projectId: config.projectId, directory: config.directory }]);
+    return [...discovered, ...projectCandidates(registry)];
+}

package/dist/project/memory-fs.d.ts

@@ -0,0 +1,9 @@
+import type { FileSystemPort } from './fs-port.js';
+export interface MemoryFs {
+    fs: FileSystemPort;
+    /** Every file written, keyed by normalised absolute path. */
+    written: Map<string, string>;
+    /** Every directory created. */
+    dirs: Set<string>;
+}
+export declare function createMemoryFs(): MemoryFs;

package/dist/project/memory-fs.js

@@ -0,0 +1,88 @@
+/**
+ * An in-memory `FileSystemPort`, and the map it wrote into.
+ *
+ * Three specs had hand-rolled their own copy of this before it was extracted, each one slightly
+ * different and each one a fresh chance to reintroduce the same fixture bug: the code under test
+ * joins paths with the PLATFORM separator, the fixtures are written with POSIX ones, and a spec that
+ * forgets to normalise passes on macOS and fails on Windows. Normalising at the port — once, here —
+ * is what stops that recurring.
+ *
+ * Exposing `written` is the other reason this exists. A store's return value says what it believes it
+ * did; the map says where the bytes actually went, which is the only way to test a defect about
+ * writing to the wrong directory.
+ */
+/** POSIX form, so a `\`-joined path and a `/`-joined one are the same key. */
+const norm = (path) => path.split('\\').join('/');
+export function createMemoryFs() {
+    const written = new Map();
+    const dirs = new Set();
+    const notFound = () => {
+        const err = new Error('ENOENT: no such file or directory');
+        err.code = 'ENOENT';
+        return err;
+    };
+    const fs = {
+        readFile(path) {
+            const value = written.get(norm(path));
+            return value === undefined ? Promise.reject(notFound()) : Promise.resolve(value);
+        },
+        writeFile(path, data) {
+            written.set(norm(path), data);
+            return Promise.resolve();
+        },
+        appendFile(path, data) {
+            written.set(norm(path), (written.get(norm(path)) ?? '') + data);
+            return Promise.resolve();
+        },
+        readFileBytes(path) {
+            const value = written.get(norm(path));
+            return value === undefined
+                ? Promise.reject(notFound())
+                : Promise.resolve(new TextEncoder().encode(value));
+        },
+        writeFileBytes(path, data) {
+            written.set(norm(path), new TextDecoder().decode(data));
+            return Promise.resolve();
+        },
+        mkdir(path) {
+            dirs.add(norm(path));
+            return Promise.resolve();
+        },
+        exists(path) {
+            const key = norm(path);
+            return Promise.resolve(written.has(key) || dirs.has(key));
+        },
+        readdir(path) {
+            const prefix = `${norm(path)}/`;
+            const names = new Set();
+            for (const key of written.keys()) {
+                if (key.startsWith(prefix)) {
+                    const rest = key.slice(prefix.length).split('/')[0];
+                    if (rest !== undefined && rest.length > 0)
+                        names.add(rest);
+                }
+            }
+            return Promise.resolve([...names]);
+        },
+        rename(from, to) {
+            const value = written.get(norm(from));
+            if (value === undefined)
+                return Promise.reject(notFound());
+            written.set(norm(to), value);
+            written.delete(norm(from));
+            return Promise.resolve();
+        },
+        rm(path) {
+            written.delete(norm(path));
+            dirs.delete(norm(path));
+            return Promise.resolve();
+        },
+        stat(path) {
+            return written.has(norm(path)) ? Promise.resolve({ mtimeMs: 0 }) : Promise.reject(notFound());
+        },
+        isNotFound(error) {
+            return 'ENOENT' === error?.code;
+        },
+    };
+    return { fs, written, dirs };
+}

package/dist/project/project-store.d.ts

@@ -32,6 +32,23 @@ export declare class ProjectStore {
      * concurrent browser sessions accumulate rather than overwriting one another.
      */
     recordRoutes(routes: readonly string[]): Promise<void>;
+    /**
+     * The best observability this project has reached, and the raiser of that bar.
+     *
+     * Read returns undefined on a first run or an unreadable file, which is the honest "no best to
+     * fall from" — never a zero, which would make every first run look like a recovery.
+     */
+    bestObservability(): Promise<{
+        percent: number;
+    } | undefined>;
+    /**
+     * Raise the bar, if this run cleared it. Lowering is deliberately impossible.
+     *
+     * A best that could fall would let a weakened run quietly redefine what good looks like, which is
+     * precisely the gaming the figure exists to resist. Serialized per file so two sessions racing
+     * cannot lose the higher of the two.
+     */
+    raiseObservability(percent: number): Promise<void>;
     /** The most-recent run for `name` (undefined on missing/malformed/none). Powers diff-vs-last. */
     lastRun(name: string): Promise<RunRecord | undefined>;
 }

package/dist/project/project-store.js

@@ -101,6 +101,39 @@ export class ProjectStore {
             await this.#fs.writeFile(path, this.#serialize(next));
         });
     }
+    /**
+     * The best observability this project has reached, and the raiser of that bar.
+     *
+     * Read returns undefined on a first run or an unreadable file, which is the honest "no best to
+     * fall from" — never a zero, which would make every first run look like a recovery.
+     */
+    async bestObservability() {
+        const existing = await this.read();
+        return existing.ok ? existing.file.learned?.bestObservability : undefined;
+    }
+    /**
+     * Raise the bar, if this run cleared it. Lowering is deliberately impossible.
+     *
+     * A best that could fall would let a weakened run quietly redefine what good looks like, which is
+     * precisely the gaming the figure exists to resist. Serialized per file so two sessions racing
+     * cannot lose the higher of the two.
+     */
+    async raiseObservability(percent) {
+        const path = reticleDirPaths(this.#root).project;
+        await withFileLock(path, async () => {
+            const existing = await this.read();
+            const base = existing.ok ? existing.file : EMPTY_PROJECT;
+            const current = base.learned?.bestObservability?.percent;
+            if (current !== undefined && percent <= current)
+                return;
+            const learned = {
+                ...base.learned,
+                bestObservability: { percent, at: this.#clock.now() },
+            };
+            await this.#fs.mkdir(reticleDirPaths(this.#root).root);
+            await this.#fs.writeFile(path, this.#serialize({ ...base, learned }));
+        });
+    }
     /** The most-recent run for `name` (undefined on missing/malformed/none). Powers diff-vs-last. */
     async lastRun(name) {
         const read = await this.read();

package/dist/project/remember-project.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Record where this project lives, so a daemon started somewhere else can still find it.
+ *
+ * Called at the end of `init`, which is the one moment both halves are known for certain: the
+ * directory being initialised, and the projectId that was just written into its `.reticle.json`.
+ *
+ * Deliberately runs on EVERY init, not only the first. Most init runs report "already wired", and a
+ * re-run in a re-cloned or moved checkout is exactly when the remembered path has gone stale — so
+ * the run that would have been a no-op is the one that repairs the entry.
+ *
+ * Every failure is swallowed. This is a cache that makes a later resolution better; a read-only home
+ * directory, a full disk or a hand-mangled file must not turn a successful init into a failed one.
+ * The user's project is wired either way, and `init`'s report is the first thing a new user reads.
+ */
+/** The sync filesystem seam `init` already carries. Narrowed to what this needs. */
+export interface RegistryIo {
+    readFile(path: string): string | null;
+    writeFile(path: string, content: string): void;
+    exists(path: string): boolean;
+    homeDir(): string;
+}
+/** The `projectId` a `.reticle.json` declares, or undefined when it declares none we can use. */
+export declare function projectIdOf(configSource: string | null): string | undefined;
+export declare function rememberProjectOnDisk(io: RegistryIo, projectId: string, directory: string, now: number): boolean;

package/dist/project/remember-project.js

@@ -0,0 +1,40 @@
+import { join } from 'node:path';
+import { PROJECT_REGISTRY_FILE, ReticleDir, emptyProjectRegistry, parseProjectRegistry, rememberProject, } from '@reticlehq/core';
+/** The `projectId` a `.reticle.json` declares, or undefined when it declares none we can use. */
+export function projectIdOf(configSource) {
+    if (null === configSource || 0 === configSource.length)
+        return undefined;
+    try {
+        const parsed = JSON.parse(configSource);
+        if ('object' !== typeof parsed || null === parsed || Array.isArray(parsed))
+            return undefined;
+        const id = parsed['projectId'];
+        return 'string' === typeof id && id.length > 0 ? id : undefined;
+    }
+    catch {
+        return undefined;
+    }
+}
+export function rememberProjectOnDisk(io, projectId, directory, now) {
+    if (0 === projectId.length || 0 === directory.length)
+        return false;
+    try {
+        const path = join(io.homeDir(), ReticleDir.ROOT, PROJECT_REGISTRY_FILE);
+        const existing = io.exists(path) ? io.readFile(path) : null;
+        const registry = null === existing ? emptyProjectRegistry() : parseProjectRegistry(safeJson(existing));
+        const next = rememberProject(registry, projectId, directory, now);
+        io.writeFile(path, `${JSON.stringify(next, null, 2)}\n`);
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+function safeJson(raw) {
+    try {
+        return JSON.parse(raw);
+    }
+    catch {
+        return undefined;
+    }
+}

package/dist/project/session-root.d.ts

@@ -0,0 +1,15 @@
+import type { ToolDeps } from '../tools/tool-kit.js';
+/**
+ * The `.reticle` directory a tool call's artifacts belong in.
+ *
+ * Every call site that reads or writes a project artifact goes through here, and that is the whole
+ * point of the function existing rather than each site asking `deps.artifactRootFor` itself. The
+ * write half and the read half MUST agree: a `flow_save` that resolves to the project while
+ * `verify_change` still reads the daemon's own directory would be a worse defect than the one being
+ * fixed — the flow would save successfully and then be invisible to the tool that exists to replay
+ * it, which reads as "no flows covered this change" rather than as an error.
+ *
+ * Falls back to `deps.reticleRoot` whenever resolution cannot name a project, which is exactly the
+ * behaviour every call site had before the resolver existed.
+ */
+export declare function sessionRoot(deps: ToolDeps, sessionId: string | undefined): string;

package/dist/project/session-root.js

@@ -0,0 +1,31 @@
+/**
+ * The `.reticle` directory a tool call's artifacts belong in.
+ *
+ * Every call site that reads or writes a project artifact goes through here, and that is the whole
+ * point of the function existing rather than each site asking `deps.artifactRootFor` itself. The
+ * write half and the read half MUST agree: a `flow_save` that resolves to the project while
+ * `verify_change` still reads the daemon's own directory would be a worse defect than the one being
+ * fixed — the flow would save successfully and then be invisible to the tool that exists to replay
+ * it, which reads as "no flows covered this change" rather than as an error.
+ *
+ * Falls back to `deps.reticleRoot` whenever resolution cannot name a project, which is exactly the
+ * behaviour every call site had before the resolver existed.
+ */
+export function sessionRoot(deps, sessionId) {
+    return deps.artifactRootFor?.(sessionProjectIdOf(deps, sessionId)).root ?? deps.reticleRoot;
+}
+/**
+ * The connected session's projectId, or undefined when there is no session to ask.
+ *
+ * `sessions.resolve` throws when nothing is connected, when the id names no session, and when
+ * several are connected and none was named. All three mean the same thing here — we cannot tell
+ * which project this call is about — and none of them is a reason to fail the caller's tool.
+ */
+function sessionProjectIdOf(deps, sessionId) {
+    try {
+        return deps.sessions.resolve(sessionId).projectId;
+    }
+    catch {
+        return undefined;
+    }
+}

package/dist/runs/run-tools.js

@@ -1,4 +1,5 @@
 import { z } from 'zod';
+import { sessionRoot } from '../project/session-root.js';
 import { RunReadError } from '@reticlehq/core';
 import { ReticleTool } from '../tools/tool-names.js';
 import { asString } from '../tools/tools-helpers.js';
@@ -36,7 +37,7 @@ export const RUN_TOOLS = [
             error: z.string().optional(),
         },
         handler: async (deps, args) => {
-            const store = new RunStore(deps.fs, deps.reticleRoot);
+            const store = new RunStore(deps.fs, sessionRoot(deps, asString(args['sessionId'])));
             // format:"diff" is a whole-history operation (two most-recent runs), not a single-run read.
             if ('diff' === asString(args['format'])) {
                 const pair = await store.latestTwo();

package/dist/session/lease-availability.d.ts

@@ -0,0 +1,40 @@
+/**
+ * Whether the self-serve escape hatch can actually be taken, said in the same breath as the offer.
+ *
+ * `reticle_lease` is what `status`, `doctor` and the no-session diagnosis all recommend when no tab
+ * is connected: it opens a browser Reticle drives itself, so the agent does not have to wait for a
+ * human. It is the right advice and it is the one thing that cannot work when Chromium is missing or
+ * sitting at a revision this Playwright will not use — and the command giving the advice is usually
+ * the command that just diagnosed exactly that.
+ *
+ * Reported from the field, verbatim in shape: `doctor` printed `chromium ✗ wrong revision — the
+ * bundled playwright wants chromium-1234; the cache holds chromium-1228`, and then offered the lease
+ * as the way out. The reporter followed it, and could not have succeeded.
+ *
+ * Two things this refuses to do:
+ *
+ * **It does not fire on an absent probe.** A probe that could not run is not evidence the browser is
+ * missing, and a caveat asserting otherwise would be the same overclaiming this file exists to stop.
+ *
+ * **It does not tell the agent to install the browser.** A ~150MB download on somebody else's
+ * machine is not an agent's call to make unprompted, so the message names the command and hands it
+ * to the human rather than implying the agent should just run it.
+ */
+/** What the caller learned about the browser. Gathered by the caller so this stays pure. */
+export interface LeaseBrowserState {
+    /** Does the executable this Playwright wants actually exist on disk? */
+    exists: boolean;
+    /** The install command, already pinned to the bundled Playwright by `chromium-hint`. */
+    installCommand?: string | undefined;
+    /** The revision this Playwright wants, when the path names one. */
+    wantedRevision?: string | undefined;
+    /** Chromium revisions actually present, wanted or not. */
+    installedRevisions?: readonly string[] | undefined;
+}
+/**
+ * The sentence to append to a lease recommendation, or undefined when the lease is fine.
+ *
+ * Undefined rather than an empty string on the healthy path: a caller composing a message should not
+ * have to filter blanks, and a healthy install must pay nothing at all for this check.
+ */
+export declare function leaseCaveat(state: LeaseBrowserState | undefined): string | undefined;

package/dist/session/lease-availability.js

@@ -0,0 +1,43 @@
+/**
+ * Whether the self-serve escape hatch can actually be taken, said in the same breath as the offer.
+ *
+ * `reticle_lease` is what `status`, `doctor` and the no-session diagnosis all recommend when no tab
+ * is connected: it opens a browser Reticle drives itself, so the agent does not have to wait for a
+ * human. It is the right advice and it is the one thing that cannot work when Chromium is missing or
+ * sitting at a revision this Playwright will not use — and the command giving the advice is usually
+ * the command that just diagnosed exactly that.
+ *
+ * Reported from the field, verbatim in shape: `doctor` printed `chromium ✗ wrong revision — the
+ * bundled playwright wants chromium-1234; the cache holds chromium-1228`, and then offered the lease
+ * as the way out. The reporter followed it, and could not have succeeded.
+ *
+ * Two things this refuses to do:
+ *
+ * **It does not fire on an absent probe.** A probe that could not run is not evidence the browser is
+ * missing, and a caveat asserting otherwise would be the same overclaiming this file exists to stop.
+ *
+ * **It does not tell the agent to install the browser.** A ~150MB download on somebody else's
+ * machine is not an agent's call to make unprompted, so the message names the command and hands it
+ * to the human rather than implying the agent should just run it.
+ */
+/**
+ * The sentence to append to a lease recommendation, or undefined when the lease is fine.
+ *
+ * Undefined rather than an empty string on the healthy path: a caller composing a message should not
+ * have to filter blanks, and a healthy install must pay nothing at all for this check.
+ */
+export function leaseCaveat(state) {
+    if (state === undefined || state.exists)
+        return undefined;
+    // Present-at-the-wrong-revision and absent-entirely have different fixes and different readings,
+    // and collapsing them is what made the reported loop unbreakable — "the check is broken" and
+    // "none of these count" look identical from a flat `missing`.
+    const installed = state.installedRevisions ?? [];
+    const mismatch = state.wantedRevision !== undefined && installed.length > 0
+        ? ` This Playwright wants ${state.wantedRevision} and the cache holds ${installed.join(', ')}, so the builds already on this machine will not be used.`
+        : '';
+    const command = state.installCommand === undefined ? '' : ` The fix is: ${state.installCommand}.`;
+    return ('NOTE — reticle_lease cannot run here: it drives a Reticle-owned Chromium and that browser is ' +
+        `not available.${mismatch}${command} That download is the human's call, not something to run ` +
+        'unprompted on their machine, so hand this back rather than treating the lease as a way forward.');
+}

package/dist/session/no-session-diagnosis.d.ts

@@ -18,6 +18,7 @@
  * Pure: everything it needs is passed in, so the probe that discovers listening ports stays out of
  * the hot resolve() path and this stays unit-testable.
  */
+import { type LeaseBrowserState } from './lease-availability.js';
 export interface NoSessionFacts {
     /** Whether ANY session has connected to this daemon since it booted. */
     everConnected: boolean;
@@ -36,6 +37,15 @@ export interface NoSessionFacts {
     slowListeners?: readonly number[];
     /** The port this daemon is on — half of the mismatch the old message asked about. */
     port: number;
+    /**
+     * What the caller knows about the Chromium a lease would drive.
+     *
+     * Every branch below offers `reticle_lease` as the way not to wait for a human. When that browser
+     * is missing or at a revision this Playwright will not use, the offer is the one thing that cannot
+     * help — and it was being made by the same output that had just diagnosed exactly that. Optional:
+     * absent means the caller did not probe, which is not evidence the browser is missing.
+     */
+    leaseBrowser?: LeaseBrowserState | undefined;
     /**
      * The directory `initialized` was decided in, named in the message when it is known.
      *
@@ -100,6 +110,13 @@ export interface NoSessionFacts {
      * that a reader deserves to check it.
      */
     searchedDirectories?: readonly string[];
+    /**
+     * How long this daemon has been running with no app connected, in milliseconds.
+     *
+     * Present only when the stall clock is active and no app has arrived. Used to surface "the
+     * install never finished" to the user-facing diagnosis rather than only to telemetry.
+     */
+    daemonUpMs?: number;
 }
 /**
  * Every branch ends with this, and `recoveryFor` keys on it to suppress the generic no-session