rivet-design 0.24.0 → 0.26.0

package/dist/services/VariantHistoryService.js

@@ -671,7 +671,9 @@ class VariantHistoryService {
                 if (!vStat?.isDirectory())
                     continue;
                 const manifest = await readManifest(path_1.default.join(variantDir, MANIFEST_FILENAME));
-                if (!manifest)
+                if (!manifest ||
+                    manifest.sessionId !== sessionId ||
+                    manifest.variantId !== variantId)
                     continue;
                 if (args.status && manifest.status !== args.status)
                     continue;

package/dist/services/VariantRunService.d.ts

@@ -59,11 +59,6 @@ export declare class VariantRunService {
     private prepareRequest;
     private recordGuidance;
     private startStaticPreviewRefinements;
-    commitVariant(args: {
-        sessionId: string;
-        variantId: string;
-        skipTeardown?: boolean;
-    }): ReturnType<AgentVariantsOrchestrator['commitVariant']>;
     cancelVariants(args: {
         sessionId: string;
         reason?: string;

package/dist/services/VariantRunService.js

@@ -351,9 +351,6 @@ class VariantRunService {
         }
         return { success: true };
     }
-    commitVariant(args) {
-        return this.orchestrator.commitVariant(args);
-    }
     cancelVariants(args) {
         this.executor?.cancelSession(args.sessionId);
         return this.orchestrator.cancel(args);

package/dist/services/WorktreeManager.d.ts

@@ -23,8 +23,6 @@ export declare class WorktreeManager {
     createWorktrees(sessionId: string, count: number, instanceKeyPrefix?: string): Promise<string[]>;
     forkWorktreesFrom(sourceWorktreePath: string, sessionId: string, count: number, instanceKeyPrefix?: string): Promise<string[]>;
     getDiff(worktreePath: string): Promise<string>;
-    applyDiff(diff: string, reverse: boolean): Promise<void>;
-    applyDiffToProject(diff: string, projectPath: string): Promise<void>;
     getFreePort(): Promise<number>;
     findFreePortFrom(startPort: number, scanWindow?: number): Promise<number>;
     releasePort(port: number): void;
@@ -34,7 +32,6 @@ export declare class WorktreeManager {
     cleanupSession(sessionId: string, freshDestinationParent?: string): Promise<void>;
     createFreshWorktrees(sessionId: string, count: number, template: TemplateBundle, designContext: ReadonlyArray<DesignContextEntry | undefined> | undefined, destinationParent: string): Promise<string[]>;
     private writeDesignContext;
-    moveWorktreeToHistory(srcWorktreePath: string, historyDir: string, folderName: string): string;
     cleanupFreshWorktrees(sessionId: string, destinationParent: string, preserve?: ReadonlySet<string>): void;
     private assertSafeSessionId;
 }

package/dist/services/WorktreeManager.js

@@ -272,44 +272,9 @@ class WorktreeManager {
     }
     async getDiff(worktreePath) {
         const git = (0, simple_git_1.simpleGit)(worktreePath);
-        await git.raw(['add', '--intent-to-add', '.']).catch(() => {
-        });
+        await git.raw(['add', '--intent-to-add', '.']).catch(() => { });
         return git.diff(['--binary', '--full-index', 'HEAD']);
     }
-    async applyDiff(diff, reverse) {
-        if (!diff.trim())
-            return;
-        const args = ['apply', '--whitespace=nowarn'];
-        if (reverse)
-            args.push('--reverse');
-        args.push('-');
-        return new Promise((resolve, reject) => {
-            const cp = (0, child_process_1.spawn)('git', args, {
-                env: (0, subprocessEnvironment_1.subprocessEnvironment)('git'),
-                cwd: this.projectPath,
-                stdio: ['pipe', 'pipe', 'pipe'],
-            });
-            let stderr = '';
-            cp.stderr.on('data', (d) => {
-                stderr += d.toString();
-            });
-            cp.on('close', (code) => {
-                if (code !== 0)
-                    reject(new Error(`git apply failed: ${stderr}`));
-                else
-                    resolve();
-            });
-            cp.stdin.write(diff);
-            cp.stdin.end();
-        });
-    }
-    async applyDiffToProject(diff, projectPath) {
-        if (!diff.trim())
-            return;
-        const git = (0, simple_git_1.simpleGit)(projectPath);
-        const gitRoot = (await git.revparse(['--show-toplevel'])).trim();
-        return this.applyPatchViaStdin(diff, gitRoot);
-    }
     getFreePort() {
         return new Promise((resolve, reject) => {
             const server = net_1.default.createServer();
@@ -473,8 +438,7 @@ class WorktreeManager {
                 isForceful: true,
             });
         }
-        catch {
-        }
+        catch { }
         return fail('timeout');
     }
     async stopDevServer(proc, timeoutMs = 5_000) {
@@ -494,8 +458,7 @@ class WorktreeManager {
                 isForceful: false,
             });
         }
-        catch {
-        }
+        catch { }
         let timeout;
         const timedOut = await Promise.race([
             exited.then(() => false),
@@ -513,8 +476,7 @@ class WorktreeManager {
                 isForceful: true,
             });
         }
-        catch {
-        }
+        catch { }
         await exited;
     }
     async cleanupSession(sessionId, freshDestinationParent) {
@@ -605,12 +567,6 @@ class WorktreeManager {
         }
         log.warn(`Fresh worktree ${slot}: unknown design system slug '${entry.slug}' — DESIGN.md skipped`);
     }
-    moveWorktreeToHistory(srcWorktreePath, historyDir, folderName) {
-        fs_1.default.mkdirSync(historyDir, { recursive: true });
-        const dest = path_1.default.join(historyDir, folderName);
-        fs_1.default.renameSync(srcWorktreePath, dest);
-        return dest;
-    }
     cleanupFreshWorktrees(sessionId, destinationParent, preserve) {
         this.assertSafeSessionId(sessionId);
         if (!destinationParent || !path_1.default.isAbsolute(destinationParent)) {
@@ -636,8 +592,7 @@ class WorktreeManager {
                     fs_1.default.rmdirSync(freshRoot);
                 }
             }
-            catch {
-            }
+            catch { }
         }
         catch (e) {
             if (e.code !== 'ENOENT') {
@@ -697,8 +652,7 @@ const cleanupOrphanedWorktrees = () => {
             });
         }
     }
-    catch {
-    }
+    catch { }
     const roots = loadFreshWorktreeRoots();
     const survivingRoots = [];
     for (const root of roots) {
@@ -729,8 +683,7 @@ const pruneWorktrees = async (projectPath) => {
     try {
         await (0, simple_git_1.simpleGit)(projectPath, GIT_OPTS).raw(['worktree', 'prune']);
     }
-    catch {
-    }
+    catch { }
 };
 exports.pruneWorktrees = pruneWorktrees;
 //# sourceMappingURL=WorktreeManager.js.map

package/dist/services/createAgentVariantsOrchestrator.js

@@ -54,6 +54,7 @@ const createAgentVariantsOrchestrator = (options) => {
         ? (0, exports.withVariantsSessionReplayLinking)(options.telemetry, options.bridge)
         : undefined;
     return new agent_variants_1.AgentVariantsOrchestrator({
+        getProjectPath,
         store: new agent_variants_1.SessionStore(),
         variantHistory: options.history,
         worktreeManager: options.worktreeManager ?? new WorktreeManager_1.WorktreeManager(getProjectPath),
@@ -89,7 +90,6 @@ const createAgentVariantsOrchestrator = (options) => {
                 };
             }),
         switchPreviewPort: (port) => options.bridge.switchPreviewPort(port),
-        setCommittedDevServerHealth: (port) => options.bridge.setCommittedDevServerHealth(port),
     });
 };
 exports.createAgentVariantsOrchestrator = createAgentVariantsOrchestrator;

package/dist/services/profiles/DesignProfiles.js

@@ -42,6 +42,7 @@ const design_profile_3 = require("../../types/design-profile");
 const errorMessage_1 = require("../../utils/errorMessage");
 const APPROVAL_TIMEOUT_MS = 45_000;
 const SAVED_REFERENCE_IMAGE_LIMIT = 20;
+const VERIFICATION_TARGET_INSTRUCTIONS = 'Choose tools for the actual browser, simulator, or other target. Do not assume a URL, DOM, CSS, or Playwright. If required tools or the target are unavailable, report unable to verify.';
 const librarySources = (records) => records.sources().map(({ id, title, provider, isIncluded }) => ({
     id,
     title,
@@ -403,7 +404,7 @@ class DesignProfiles {
                     verifierState: 'missing',
                     nextAction: {
                         action: 'create_context_verifier',
-                        instructions: 'Author and execute a focused verifier against this source and the user-selected target. Record observable checks and evidence before offering to save it for reuse.',
+                        instructions: `Author and execute a focused verifier against this source and the user-selected target. ${VERIFICATION_TARGET_INSTRUCTIONS} Record observable checks and evidence before offering to save it for reuse.`,
                     },
                 };
             if (verifier.sourceDigest !== sourceDigest)
@@ -413,7 +414,7 @@ class DesignProfiles {
                     verifierState: 'stale',
                     nextAction: {
                         action: 'revise_context_verifier',
-                        instructions: 'The source changed after this verifier was saved. Revise and execute a temporary recipe against the supplied source before offering to replace the saved verifier.',
+                        instructions: `The source changed after this verifier was saved. ${VERIFICATION_TARGET_INSTRUCTIONS} Revise and execute a temporary recipe against the supplied source before offering to replace the saved verifier.`,
                     },
                 };
             return {
@@ -430,7 +431,7 @@ class DesignProfiles {
                     : {}),
                 nextAction: {
                     action: 'run_context_verifier',
-                    instructions: 'Execute the saved verifier against this source and the user-selected target. Report pass, fail, or unable to verify with evidence. Retrieval has not executed any checks.',
+                    instructions: `Execute the saved verifier against this source and the user-selected target. ${VERIFICATION_TARGET_INSTRUCTIONS} Report pass, fail, or unable to verify with evidence. Retrieval has not executed any checks.`,
                 },
             };
         }, expectedAccountId);

package/dist/types/preview-bridge.d.ts

@@ -0,0 +1,4 @@
+export declare const PREVIEW_BRIDGE_CHANNEL = "rivet-preview-bridge";
+export declare const PREVIEW_BRIDGE_FORWARDED_KEYS: readonly ["ArrowUp", "ArrowDown"];
+export type PreviewBridgeForwardedKey = (typeof PREVIEW_BRIDGE_FORWARDED_KEYS)[number];
+//# sourceMappingURL=preview-bridge.d.ts.map

package/dist/types/preview-bridge.js

@@ -0,0 +1,6 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PREVIEW_BRIDGE_FORWARDED_KEYS = exports.PREVIEW_BRIDGE_CHANNEL = void 0;
+exports.PREVIEW_BRIDGE_CHANNEL = 'rivet-preview-bridge';
+exports.PREVIEW_BRIDGE_FORWARDED_KEYS = ['ArrowUp', 'ArrowDown'];
+//# sourceMappingURL=preview-bridge.js.map

package/dist/utils/editorAccess.d.ts

@@ -1,6 +1,7 @@
 export declare const EDITOR_ACCESS_TOKEN_HEADER = "x-rivet-editor-token";
 export declare const EDITOR_ACCESS_TOKEN_FRAGMENT = "editorToken";
 export declare const EDITOR_ACCOUNT_PATHS: string[];
+export declare const isEditorApiPath: (path: string, method?: string) => boolean;
 export declare const createEditorUrl: ({ port, token, }: {
     port: number;
     token: string;

package/dist/utils/editorAccess.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.createEditorUrl = exports.EDITOR_ACCOUNT_PATHS = exports.EDITOR_ACCESS_TOKEN_FRAGMENT = exports.EDITOR_ACCESS_TOKEN_HEADER = void 0;
+exports.createEditorUrl = exports.isEditorApiPath = exports.EDITOR_ACCOUNT_PATHS = exports.EDITOR_ACCESS_TOKEN_FRAGMENT = exports.EDITOR_ACCESS_TOKEN_HEADER = void 0;
 exports.EDITOR_ACCESS_TOKEN_HEADER = 'x-rivet-editor-token';
 exports.EDITOR_ACCESS_TOKEN_FRAGMENT = 'editorToken';
 exports.EDITOR_ACCOUNT_PATHS = [
@@ -12,6 +12,16 @@ exports.EDITOR_ACCOUNT_PATHS = [
     '/api/integrations',
     '/api/reference-profiles',
 ];
+const VARIANT_MEDIA_PATH = /^\/api\/variants\/(?:[^/]+\/static\/|history\/[^/]+\/[^/]+\/(?:preview(?:\/|$)|site\/)|[^/]+\/[^/]+\/references\/[^/]+\/image\/?$)/;
+const isEditorApiPath = (path, method = 'GET') => {
+    const pathname = path.split(/[?#]/)[0].toLowerCase();
+    if (/^\/api\/variants(?:\/|$)/.test(pathname)) {
+        return (!['GET', 'HEAD'].includes(method.toUpperCase()) ||
+            !VARIANT_MEDIA_PATH.test(pathname));
+    }
+    return exports.EDITOR_ACCOUNT_PATHS.some((prefix) => pathname === prefix || pathname.startsWith(`${prefix}/`));
+};
+exports.isEditorApiPath = isEditorApiPath;
 const createEditorUrl = ({ port, token, }) => {
     const url = new URL(`http://127.0.0.1:${port}/rivet`);
     url.hash = new URLSearchParams({

package/dist/utils/skills/claude-skill.d.ts

@@ -1,4 +1,4 @@
-export declare const CLAUDE_SKILL_VERSION = 60;
+export declare const CLAUDE_SKILL_VERSION = 61;
 export declare const CLAUDE_SKILL_DIR = "rivet";
 export declare const CLAUDE_SKILL_FILENAME = "SKILL.md";
 export declare const CLAUDE_SKILL_CONTENT: string;

package/dist/utils/skills/claude-skill.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CLAUDE_SKILL_CONTENT = exports.CLAUDE_SKILL_FILENAME = exports.CLAUDE_SKILL_DIR = exports.CLAUDE_SKILL_VERSION = void 0;
 const cli_guidance_1 = require("./cli-guidance");
-exports.CLAUDE_SKILL_VERSION = 60;
+exports.CLAUDE_SKILL_VERSION = 61;
 const CLAUDE_SKILL_VERSION_MARKER = `[//]: # (rivet-skill-version: ${exports.CLAUDE_SKILL_VERSION})`;
 exports.CLAUDE_SKILL_DIR = 'rivet';
 exports.CLAUDE_SKILL_FILENAME = 'SKILL.md';

package/dist/utils/skills/cli-guidance.d.ts

@@ -1,4 +1,4 @@
-export declare const CLI_GUIDANCE_VERSION = 54;
+export declare const CLI_GUIDANCE_VERSION = 56;
 export declare const CLI_GUIDANCE_BODY: string;
 export declare const CLI_GUIDANCE_DESCRIPTION = "Rivet \u2014 open the visual editor or explore design directions for a web app.";
 //# sourceMappingURL=cli-guidance.d.ts.map

package/dist/utils/skills/cli-guidance.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CLI_GUIDANCE_DESCRIPTION = exports.CLI_GUIDANCE_BODY = exports.CLI_GUIDANCE_VERSION = void 0;
 const displayLocale_1 = require("../displayLocale");
-exports.CLI_GUIDANCE_VERSION = 54;
+exports.CLI_GUIDANCE_VERSION = 56;
 const DISPLAY_LOCALE = (0, displayLocale_1.resolveDisplayLocale)();
 exports.CLI_GUIDANCE_BODY = `Rivet helps you **explore multiple design directions** for a web app. You drive it by running \`rivet\` CLI commands. Every command prints exactly one JSON envelope on stdout (\`{ schemaVersion, ok, command, data | error }\`), routes progress to stderr, and never prompts for input.
 
@@ -30,7 +30,6 @@ Use these independently exposed tools for their named purposes:
 
 - \`rivet_explore_designs\` starts directions with \`project\`, \`instruction\`, \`runLabel\`, and one authored \`briefs\` entry per direction. Use \`baseDirectionId: "sessionId:variantId"\` to vary a result.
 - \`rivet_get_exploration\` reads progress and results with \`project\`. Add \`sessionId\`, \`variantId\`, \`includeHistory\`, or the start response's \`workId\` for recorded context receipts.
-- \`rivet_apply_design\` applies the user's chosen \`project\`, \`sessionId\`, and \`variantId\`.
 - \`rivet_cancel_exploration\` cancels the named \`project\` and \`sessionId\` only when the user asks.
 - \`rivet_find_references\` searches retained titles, text, notes, and analysis with \`query\`, optional \`sourceId\`, and optional \`limit\`. Its \`saved_text\` ranking is lexical. It does not start workers, create an index, or perform semantic model search.
 - \`rivet_get_design_context\` reads enabled instructions or selected \`instructionIds\`, plus references selected by \`referenceSelection: {profileId, keys}\`. Ordinary reads include source digests but exclude checking recipes and package files. For requested verification, add \`includeChecks: true\` with selected \`instructionIds\` to read recipe text and package metadata, without executable code or execution.
@@ -78,14 +77,14 @@ Every generation resolves current saved instructions once and supplies the same
 
 **Custom verification on demand.** When asked to check a property such as "verify this used my motion principles," locate its existing context document with \`context list\`/\`show\`. Save missing user-provided principles or pointers through \`context add\` when the user wants them in context; do not invent principles or ingest source snapshots. Retrieve only the selected document with \`rivet context verifier <id>\` (MCP: \`rivet_get_design_context\` with \`instructionIds: ["<id>"]\` and \`includeChecks: true\`). Its \`sourceDigest\` binds the saved text and reference metadata; URL and directory contents remain live and are not frozen by this digest. Inspect the actual relevant references without copying them into persistent context. The CLI packet has \`execution: "host_required"\`. The MCP read returns the saved checking recipe and metadata. Neither read has checked the output.
 
-Identify the target from the user's app or \`variants get\`. For an earlier generation, read \`context inspect <workId>\` before claiming the source was delivered. Disclose missing receipts, changed principles, and live-source limitations. A current-source assessment does not establish historical compliance. For CLI packets follow \`nextAction\`. For MCP use the returned source digest and saved recipe to determine whether to create or revise a recipe. Execute a recipe only when the user requests verification and authorizes its required privileges. Keep recipes short and specific about applicability, actions, observable assertions, and evidence. Use code inspection for source-level rules and real interaction for behavioral rules; a screenshot alone cannot verify motion timing or reduced-motion behavior. Execute the recipe once and write a uniquely named local report containing target identity, context ID/digest, each check, evidence locations, and pass/fail/unable-to-verify outcomes. Missing evidence is unable to verify, not a pass. Report failures without silently repairing the app.
+Identify the target from the user's app or \`variants get\`. Choose verification tools for the actual browser, simulator, or other target. Do not assume a URL, DOM, CSS, or Playwright. Use the host's available tools for that target; unavailable tools or inaccessible targets mean unable to verify. Keep reusable assertions separate from target-specific bindings and execution steps, and record applicability when a rule requires a particular platform. For an earlier generation, read \`context inspect <workId>\` before claiming the source was delivered. Disclose missing receipts, changed principles, and live-source limitations. A current-source assessment does not establish historical compliance. For CLI packets follow \`nextAction\`. For MCP use the returned source digest and saved recipe to determine whether to create or revise a recipe. Execute a recipe only when the user requests verification and authorizes its required privileges. Keep recipes short and specific about applicability, actions, observable assertions, and evidence. Use code inspection for source-level rules and real interaction for behavioral rules; a screenshot alone cannot verify motion timing or reduced-motion behavior. Execute the recipe once and write a uniquely named local report containing target identity, context ID/digest, each check, evidence locations, and pass/fail/unable-to-verify outcomes. Missing evidence is unable to verify, not a pass. Report failures without silently repairing the app.
 
 After showing the actual result, offer to save a reusable recipe unless the user already requested reuse. With that agreement, run \`rivet context update <id> --verifier <Markdown path> --source-digest <packet digest>\` (MCP: \`rivet_save_design_check\` with \`contextId\`, \`recipeFile\`, and \`sourceDigest\`). A source-change conflict requires retrieving the source and revising the recipe before saving. Source edits and verifier saves are separate updates. Remove just the recipe with \`context update <id> --remove-verifier\` (MCP: \`rivet_remove_design_check\` with \`contextId\`). Saved verifiers run only when requested; saving does not schedule checks or enable automatic reruns. The source retains its existing generation defaults, while recipe text stays out of planning and worker context.
 
 
-For reusable executable checks, author an optional package with a named \`verify(input)\` export in a retained \`.mjs\` entrypoint. Store only authored verifier code and helpers, never a source-repository snapshot. A local JSON manifest is \`{runtime:"node",entrypoint:"verify.mjs",files:[{name:"verify.mjs",path:"./verify.mjs"}]}\`. Paths resolve relative to the manifest. Use Node built-ins, retained relative imports, and \`await import(input.modules.playwright)\` for Rivet's installed Playwright ESM module. Rivet installs no dependencies or browser. Inputs are \`source\` (prepared saved context), \`projectPath\`, \`target\` (opaque target JSON), \`evidenceDirectory\`, and \`modules.playwright\`. The code executes locally with the invoking process's permissions and environment, not a sandbox. Only run trusted authored code when the user requests verification.
+For reusable executable checks, author an optional package with a named \`verify(input)\` export in a retained \`.mjs\` entrypoint. Store only authored verifier code and helpers, never a source-repository snapshot. A local JSON manifest is \`{runtime:"node",entrypoint:"verify.mjs",files:[{name:"verify.mjs",path:"./verify.mjs"}]}\`. Paths resolve relative to the manifest. Use Node built-ins and retained relative imports to drive the target's available tools. For browser checks only, \`await import(input.modules.playwright)\` provides Rivet's installed Playwright ESM module. Rivet installs no dependencies, browser, or simulator. Inputs are \`source\` (prepared saved context), \`projectPath\`, \`target\` (opaque target JSON), \`evidenceDirectory\`, and \`modules.playwright\` (a browser helper whose use is optional). Target bindings can include simulator/device identifiers, app identifiers, accessibility identifiers, source files, or browser URLs and selectors as applicable. Missing required tools or bindings produce blocked checks. The code executes locally with the invoking process's permissions and environment, not a sandbox. Only run trusted authored code when the user requests verification.
 
-Read expected brand values from the independent source. Bind target elements and modes explicitly in package-specific JSON rather than derive expected values from the app being checked. For color, distinguish Mapped-token provenance from rendered color, including pseudo-element paint. For spacing, bind semantic gaps or padding and density rather than check arbitrary multiples. For typography, compare the complete role and establish that the intended font loaded. Missing or ambiguous targets and unavailable prerequisites must be blocked. Prove the package on a compliant target and intentional violations before saving it for reuse.
+Read expected brand values from the independent source. Bind target elements and modes explicitly in package-specific JSON rather than derive expected values from the app being checked. For color, distinguish token provenance from rendered color, including platform-specific paint layers. For spacing, bind semantic gaps or padding and density rather than check arbitrary multiples. For typography, compare the complete role and establish that the intended font loaded. Use evidence appropriate to the target, such as browser computed styles, native view/accessibility data, source inspection, or measured interactions; screenshots alone cannot prove every property. Missing or ambiguous targets and unavailable prerequisites must be blocked. Prove the package on a compliant target and intentional violations before saving it for reuse.
 
 The export returns \`{checks:[{id,category,status:"pass"|"fail"|"blocked",rule,target,expected,observed,evidence?:["relative-file.png"]}]}\`. IDs must be unique, checks nonempty, expected/observed bounded JSON, and referenced evidence real regular files inside \`evidenceDirectory\`. Save with \`context update <id> --verifier <Markdown path> --verifier-package <manifest.json> --source-digest <packet digest>\`. Run with \`rivet context verify <id> --project <absolute target> --input <target.json>\`; with MCP use \`rivet_run_design_check\` with \`contextId\`, \`project\`, and \`inputFile\`, then execute its returned arguments through the host. The MCP call itself runs no code. Saving through \`rivet_save_design_check\` adds \`packageFile\`. A recipe-only update preserves the saved package for the same source digest; changed source requires a replacement package or explicit verifier removal before a Markdown-only save. Rivet bounds runtime/output, cleans up the process tree even after normal returns, and derives fail before blocked before pass. A pass exits 0; fail or blocked exits 1 with the completed report in \`error.details\`. Runtime errors have \`execution: "error"\` and a normalized reason. Report runtime failures separately from assertion failures. Missing/stale recipes and recipes without packages do not execute. Retrieval still runs no checks. Generation excludes executable code and checking recipes. Only explicit \`includeChecks: true\` context reads include recipe text and package metadata; ordinary context reads exclude both, and executable code is never returned. Saving adds no automatic gate, dependency install or source maintenance.
 
@@ -102,11 +101,10 @@ The export returns \`{checks:[{id,category,status:"pass"|"fail"|"blocked",rule,t
 - \`rivet status --project <path> [--watch]\` — session, resolved runner, active run, and the variants snapshot. \`--watch\` streams NDJSON.
 - \`rivet variants status --project <path>\` / \`rivet variants list --project <path> [--history]\` — inspect live or past directions.
 - \`rivet variants get <projectId>/<sessionId>:<variantId> [--detail]\` — resolve a copied direction from any working directory through the local project library, even when its editor is closed. The default response is compact metadata and an artifact path; add \`--detail\` for the full diff, file list, and design notes.
-- \`rivet variants commit <variantId> --project <path> [--session <id>]\` — send the chosen direction to the project.
 - \`rivet variants cancel <sessionId> --project <path>\` — cancel a running variants session.
 - \`rivet evidence capture --url <url>\` — rendered design evidence (root variables, element styles, fonts) for a reference URL.
 - \`rivet reference fetch <url>\` — Pinterest / Are.na reference data via the user's connected account. Accepts full pin/board URLs and \`pin.it\` share links. Pinterest images are downloaded into \`.rivet/references/\` and returned as absolute paths (\`data.images\`, plus \`local_path\` per pin) — view them directly and pass them to variants via \`--context-images\` instead of relaying URLs. If Pinterest returns \`status: not_connected\`, present the returned \`authUrl\` to the user and retry after they authorize. On failure the error message says exactly what to tell the user (e.g. save the pin to a board first).
-- \`rivet auth status\` — signed-in state. If \`authenticated: false\`: call the \`rivet_login\` MCP tool when this host has it — it opens a browser sign-in for the user and returns immediately; after they finish, retry the blocked action (the session is picked up automatically). Without MCP tools, tell the user to run \`rivet login\` themselves — never run login in your own terminal (it blocks waiting on the browser).
+- \`rivet auth status\` — signed-in state. A signed-out \`rivet open\` starts Rivet sign-in in the browser itself and exits 3 with \`AUTH_REQUIRED\` and \`error.nextAction.authUrl\` if the user has not finished within a short wait. Share that \`authUrl\` as a clickable link (with \`--no-browser\` it is the only way in), ask the user to finish signing in, then rerun \`rivet open\`; it picks up the finished sign-in. For \`AUTH_REQUIRED\` from other commands, run \`rivet open\` the same way, or call the \`rivet_login\` MCP tool when this host has it. \`rivet login\` stays available for the user to run themselves — never run login in your own terminal (it blocks waiting on the browser).
 - \`rivet version status\` — check the installed and latest published CLI versions without changing the installation. Returns \`installedVersion\`, \`publishedVersion\`, and \`isUpdateAvailable\`.
 - \`rivet update\` — bypass the automatic-update cache, install the latest published CLI when available, and refresh existing host registrations and agent guidance. Run it when version status reports an available update, or for explicit verification or recovery.
 - \`rivet stop [--project <path>]\` — stop the CLI-owned server.
@@ -117,13 +115,13 @@ The export returns \`{checks:[{id,category,status:"pass"|"fail"|"blocked",rule,t
 
 Before every agent-initiated variants start, including fresh apps and \`--target\` requests, author a 1–3 word batch label plus one or more direction briefs as \`[{"label":"…","body":"…"}]\`. Write the user-visible \`runLabel\`, brief \`label\`, and brief \`body\` naturally in ${DISPLAY_LOCALE}, the computer's preferred display locale. The batch label summarizes the shared request and is passed through \`runLabel\` (MCP) or \`--run-label\` (CLI). Each brief \`label\` names what that direction concretely changes, not a vibe or numbered placeholder. Each \`body\` is a concise subtitle describing that direction. Add an optional \`notes\` string per brief for richer implementation intent (design tokens, motion specs, constraints) — it is delivered verbatim to that direction's worker and never shown in UI chips. Use one brief for a single visualization when the user wants Rivet's visualization framework without divergent ideas. For multiple directions, make every brief meaningfully different. Pass the array through the \`rivet_explore_designs\` \`briefs\` field or CLI \`--briefs <json>\`, and omit \`--count\` because the array length is authoritative. Human-direct CLI calls may omit the batch label and briefs and use Rivet's deterministic fallback.
 
-Existing app, using CLI commands when MCP is unavailable. With MCP use \`rivet_get_design_context\` before briefs, \`rivet_explore_designs\` to start, \`rivet_get_exploration\` for progress, \`rivet_complete_variant_work\` for assigned completion, and \`rivet_apply_design\` after selection. Lifecycle open remains CLI.
+Existing app, using CLI commands when MCP is unavailable. With MCP use \`rivet_get_design_context\` before briefs, \`rivet_explore_designs\` to start, \`rivet_get_exploration\` for progress, \`rivet_complete_variant_work\` for assigned completion. Lifecycle open remains CLI.
 
 1. \`rivet open --project <path> --caller-agent cursor --caller-model <model> --caller-session <id>\` → note \`editorUrl\`, \`sessionId\`, and \`resolvedRunner\`.
 2. Author a batch label and three distinct title/subtitle briefs, then call \`rivet variants start --project <path> --instruction "try three hero layouts" --run-label "Hero layouts" --briefs '[{"label":"Split hero","body":"Moves supporting proof beside the primary call to action."},{"label":"Layered hero","body":"Stacks product imagery behind a compact centered headline."},{"label":"Product-led hero","body":"Lets the product preview dominate the opening composition."}]' --caller-agent cursor --caller-model <model> --caller-session <id>\` → note \`workId\`.
 3. Agent-initiated runs return \`nextAction.action="complete_host_variant_work"\`. Each item carries a server-authored \`workerPrompt\` pointing at its complete briefing. Follow \`nextAction.parallelism\` exactly. For \`strategy="direct"\`, implement the single item in the current host. For \`strategy="one_worker_per_work_item"\`, spawn one native subagent per item in the same turn, passing each \`workerPrompt\` VERBATIM as its entire prompt. Preserve current permissions and approvals. Inherit the current model unless that item's \`workerSelection\` requires native selection. Do not substitute a fixed-model worker definition. If native delegation or the requested model is unavailable, report failure before editing. Briefs are final; do not re-plan them. Standalone jobs may use server workers; when there is no \`nextAction\`, watch status and do not implement their work. For \`mode="vary"\` the workspace entry already contains the source direction's finished code: read it first, apply the requested delta with targeted \`Edit\` operations in place, and never rewrite or re-emit the full file — unchanged sections must remain untouched. For \`workspace.kind="artifact_directory"\` the deliverable is \`workspace.rootPath/workspace.entryPath\` (write it in full only when it starts empty, i.e. \`mode="create"\`); for \`workspace.kind="git_worktree"\`, edit the app under \`workspace.projectPath\`.
 4. The briefing file ends with the item's exact \`completeCommand\`: the worker runs \`rivet variants complete <workId> --project <path> --session <sessionId>\` itself as its final step, the moment its workspace is done. Completions are never held back or batched by the coordinator — and because workers self-report, the coordinator does NOT poll status while workers run: check \`rivet status\` once after workers return (or on a single ≥60s wakeup), only to confirm terminal states and surface failures. Rivet reads static HTML from \`workspace.entryPath\` and captures git-worktree changes itself. Do not send inline HTML or repeat project context in the completion payload. If the result says \`requeuedForRegeneration\`, poll status for the renewed lease, address its QA summary, and complete that item once more. If a worker cannot complete it, use \`--status failed --error <message>\`.
-5. Show the user the \`editorUrl\` to compare directions; \`rivet variants commit <variantId> --project <path>\` when they pick one.
+5. Show the user the \`editorUrl\` to compare directions. Retrieve their chosen prototype with \`rivet variants get <projectId>/<sessionId>:<variantId> --detail\` (MCP: \`rivet_get_exploration\` with the selected session and variant). The host agent owns implementation and verification in the user project; Rivet retains prototype artifacts and context.
 
 Fresh 0-to-1: with MCP use \`rivet_explore_designs\` with \`fresh: true\` after reading \`rivet_get_design_context\`. For the CLI flow, create or use an empty directory and run \`rivet open --project <path> ...\`. Resolve the selected saved instructions with \`rivet context resolve\`, then author a batch label and one distinct brief per direction from the user's request, supplied references, and saved instructions. Include concrete section, layout, typography, and interaction choices in each brief's notes. Run \`rivet variants start --project <path> --fresh --instruction "build a SaaS landing page" --run-label "Landing layouts" --briefs '<json>' ...\`, omitting \`--count\` because the briefs set the count. Rivet uses those briefs directly without a hosted planning call. Pass local reference images via \`--context-images '["/abs/path.png"]'\` (\`rivet_explore_designs\` \`contextImages\`) — Rivet copies them into the run context and every worker views them natively. Pass reference page URLs via \`--reference-pages '["https://example.com"]'\` (\`referencePages\`) — Rivet renders each page server-side for design evidence + a screenshot; never capture evidence or screenshot pages yourself. Pass local reference videos via \`--reference-videos '["/abs/clip.mp4"]'\` (\`referenceVideos\`) — Rivet samples keyframes server-side; never run ffmpeg yourself. Never substitute a prose description of media you can pass directly.
 

package/dist/utils/skills/codex-skill.d.ts

@@ -1,3 +1,3 @@
 export declare const CODEX_SKILL_MARKER = "[//]: # (managed-by: rivet install codex)";
-export declare const CODEX_SKILL_CONTENT = "---\nname: rivet\ndescription: Open Rivet for the current project when asked or invoked as $rivet.\n---\n\n[//]: # (managed-by: rivet install codex)\n\n# Open Rivet\n\nOpen the current project when the user invokes `$rivet` alone. Use the current directory unless they specify another project.\n\nFor a CLI-installed integration, before the first Rivet command in this conversation, run `rivet version status` with the caller flags below. Report installed and published versions; if an update is available, run `rivet update` and report whether it caught up. Report check or update failures, then continue if the installed CLI works.\n\nRun the installed CLI as a standalone shell command:\n\n```sh\nrivet open --project \"<absolute project path>\" --caller-agent codex --caller-model \"<your actual model>\"\n```\n\nReplace the placeholders with the actual path and model. Include `--caller-session` when the current session ID is available. If another host invokes this skill, use its actual caller agent instead of codex.\n\nIn the local ChatGPT desktop app, run `rivet open --no-browser` with the project and caller flags when its in-app browser reaches localhost, then open the returned `data.editorUrl` (including its fragment) with the browser tool. Otherwise run `rivet open` without `--no-browser` to launch the system browser. To switch browsers later, open the existing URL in the requested browser without rerunning `rivet open`; clarify ambiguous terms such as \"native\". Attach to an already-running app with `--user-port <port>`.\n\nRead the returned JSON envelope. On success, share `data.editorUrl`; if browser navigation or launch failed, tell the user to open that link manually. On failure, explain the reported error and address its cause before retrying. If sign-in is required, use Rivet's available login tool or ask the user to run `rivet login` in their own terminal.\n\nFor a bundled plugin, follow its pinned lifecycle instructions and do not run a global install or updater.\n\nRead `data.guidance` as the user's saved defaults for this conversation. Report `data.guidanceError` if context could not load. Before authoring direction briefs for later generations, read `rivet_get_design_context` when the explicit MCP tools are registered. Use the selected saved instructions in full and keep checking recipes out of generation briefs. A current explicit user request overrides those defaults. For a one-run exclusion, omit the selected instruction locally and pass its ID in `excludedGuidanceIds` to `rivet_explore_designs`. Use `guidance: \"off\"` to exclude all saved instructions. Author a batch label and one brief per direction, including for fresh apps, and pass `runLabel` and `briefs` to `rivet_explore_designs`. Poll `rivet_get_exploration` for progress. Follow the full installed guidance for worker handoff and the separate apply, cancellation, and verification tools. Do not substitute CLI commands for operations absent from the MCP catalog.\n\nWithout MCP, run `rivet context resolve` before briefs. Pass `--exclude-guidance '[\"<documentId>\"]'` to both resolve and variants start, or `--guidance off` to exclude all saved instructions. Pass the authored batch label and briefs with `--run-label` and `--briefs`. Rivet delivers selected saved instructions to workers without a direction-planning model call.\n\nOpening Rivet alone does not request variant generation. If the user also asks for design work, open Rivet first and then follow their request using the installed Rivet CLI guidance.\n";
+export declare const CODEX_SKILL_CONTENT = "---\nname: rivet\ndescription: Open Rivet for the current project when asked or invoked as $rivet.\n---\n\n[//]: # (managed-by: rivet install codex)\n\n# Open Rivet\n\nOpen the current project when the user invokes `$rivet` alone. Use the current directory unless they specify another project.\n\nFor a CLI-installed integration, before the first Rivet command in this conversation, run `rivet version status` with the caller flags below. Report installed and published versions; if an update is available, run `rivet update` and report whether it caught up. Report check or update failures, then continue if the installed CLI works.\n\nRun the installed CLI as a standalone shell command:\n\n```sh\nrivet open --project \"<absolute project path>\" --caller-agent codex --caller-model \"<your actual model>\"\n```\n\nReplace the placeholders with the actual path and model. Include `--caller-session` when the current session ID is available. If another host invokes this skill, use its actual caller agent instead of codex.\n\nIn the local ChatGPT desktop app, run `rivet open --no-browser` with the project and caller flags when its in-app browser reaches localhost, then open the returned `data.editorUrl` (including its fragment) with the browser tool. Otherwise run `rivet open` without `--no-browser` to launch the system browser. To switch browsers later, open the existing URL in the requested browser without rerunning `rivet open`; clarify ambiguous terms such as \"native\". Attach to an already-running app with `--user-port <port>`.\n\nRead the returned JSON envelope. On success, share `data.editorUrl`; if browser navigation or launch failed, tell the user to open that link manually. On failure, explain the reported error and address its cause before retrying. If sign-in is required, `rivet open` has already started Rivet sign-in in the browser: share `error.nextAction.authUrl` as a clickable link, ask the user to finish signing in, then rerun `rivet open`. Rivet's login tool works too when available, and the user can still run `rivet login` themselves.\n\nFor a bundled plugin, follow its pinned lifecycle instructions and do not run a global install or updater.\n\nRead `data.guidance` as the user's saved defaults for this conversation. Report `data.guidanceError` if context could not load. Before authoring direction briefs for later generations, read `rivet_get_design_context` when the explicit MCP tools are registered. Use the selected saved instructions in full and keep checking recipes out of generation briefs. A current explicit user request overrides those defaults. For a one-run exclusion, omit the selected instruction locally and pass its ID in `excludedGuidanceIds` to `rivet_explore_designs`. Use `guidance: \"off\"` to exclude all saved instructions. Author a batch label and one brief per direction, including for fresh apps, and pass `runLabel` and `briefs` to `rivet_explore_designs`. Poll `rivet_get_exploration` for progress. Follow the full installed guidance for worker handoff and the separate apply, cancellation, and verification tools. Do not substitute CLI commands for operations absent from the MCP catalog.\n\nWithout MCP, run `rivet context resolve` before briefs. Pass `--exclude-guidance '[\"<documentId>\"]'` to both resolve and variants start, or `--guidance off` to exclude all saved instructions. Pass the authored batch label and briefs with `--run-label` and `--briefs`. Rivet delivers selected saved instructions to workers without a direction-planning model call.\n\nOpening Rivet alone does not request variant generation. If the user also asks for design work, open Rivet first and then follow their request using the installed Rivet CLI guidance.\n";
 //# sourceMappingURL=codex-skill.d.ts.map

package/dist/utils/skills/codex-skill.js

@@ -25,7 +25,7 @@ Replace the placeholders with the actual path and model. Include \`--caller-sess
 
 In the local ChatGPT desktop app, run \`rivet open --no-browser\` with the project and caller flags when its in-app browser reaches localhost, then open the returned \`data.editorUrl\` (including its fragment) with the browser tool. Otherwise run \`rivet open\` without \`--no-browser\` to launch the system browser. To switch browsers later, open the existing URL in the requested browser without rerunning \`rivet open\`; clarify ambiguous terms such as "native". Attach to an already-running app with \`--user-port <port>\`.
 
-Read the returned JSON envelope. On success, share \`data.editorUrl\`; if browser navigation or launch failed, tell the user to open that link manually. On failure, explain the reported error and address its cause before retrying. If sign-in is required, use Rivet's available login tool or ask the user to run \`rivet login\` in their own terminal.
+Read the returned JSON envelope. On success, share \`data.editorUrl\`; if browser navigation or launch failed, tell the user to open that link manually. On failure, explain the reported error and address its cause before retrying. If sign-in is required, \`rivet open\` has already started Rivet sign-in in the browser: share \`error.nextAction.authUrl\` as a clickable link, ask the user to finish signing in, then rerun \`rivet open\`. Rivet's login tool works too when available, and the user can still run \`rivet login\` themselves.
 
 For a bundled plugin, follow its pinned lifecycle instructions and do not run a global install or updater.
 

package/dist/utils/skills/cursor-rules.d.ts

@@ -1,4 +1,4 @@
-export declare const CURSOR_RULES_VERSION = 56;
+export declare const CURSOR_RULES_VERSION = 57;
 export declare const CURSOR_RULES_FILENAME = "rivet.mdc";
 export declare const CURSOR_RULES_CONTENT: string;
 //# sourceMappingURL=cursor-rules.d.ts.map

package/dist/utils/skills/cursor-rules.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CURSOR_RULES_CONTENT = exports.CURSOR_RULES_FILENAME = exports.CURSOR_RULES_VERSION = void 0;
 const cli_guidance_1 = require("./cli-guidance");
-exports.CURSOR_RULES_VERSION = 56;
+exports.CURSOR_RULES_VERSION = 57;
 exports.CURSOR_RULES_FILENAME = 'rivet.mdc';
 const CURSOR_RULES_VERSION_MARKER = `rivet-rules-version: ${exports.CURSOR_RULES_VERSION}`;
 exports.CURSOR_RULES_CONTENT = `---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rivet-design",
-  "version": "0.24.0",
+  "version": "0.26.0",
   "description": "Local visual web development tool with AI-powered code modification",
   "main": "dist/index.js",
   "workspaces": [
@@ -56,8 +56,13 @@
     "bench:typecheck": "tsc -p benchmarks/tsconfig.json",
     "smoke:preview-dependencies": "node scripts/smoke-preview-dependencies.cjs",
     "smoke:plugin-telemetry": "node scripts/smoke-plugin-telemetry.mjs",
+    "test:release-candidate": "node --test scripts/release-candidate.test.mjs",
+    "release:review": "node scripts/release-review.mjs",
+    "release:candidate": "node scripts/release-candidate-cli.mjs",
     "smoke:cli": "node scripts/smoke-cli.mjs && yarn test:plugin-runtime",
     "test:plugin-runtime": "node --test scripts/plugin-runtime.test.mjs scripts/plugin-telemetry.test.mjs",
+    "test:source-maps": "node --test scripts/*source-maps*.test.mjs",
+    "export:source-maps": "node scripts/export-source-maps.mjs",
     "smoke:runtime-upgrade": "node scripts/smoke-runtime-upgrade.mjs",
     "smoke:embedded-prototypes": "node --import tsx scripts/smoke-embedded-prototypes.mjs",
     "smoke:library-preview-origins": "node scripts/smoke-library-preview-origins.mjs",
@@ -144,6 +149,7 @@
     "dist/",
     "src/ui/dist/",
     "bin/",
+    "!**/*.map",
     "scripts/verify-node-version.cjs",
     "README.npm.md"
   ],
@@ -204,6 +210,7 @@
     "nwsapi": "2.2.24"
   },
   "rivetPlugin": {
-    "toolContract": "intent-v1"
-  }
+    "toolContract": "intent-v2"
+  },
+  "gitHead": "5c923f2228fa50986ef4dceb5b3bba3cfe29e692"
 }