@reticlehq/init 2.14.0 → 3.2.0

package/dist/index.js

@@ -9,17 +9,41 @@
  * ends up unable to move a file.
  */
 export { runInit, resolveLockfiles, } from './run.js';
-export { buildNodeIo } from './node-io.js';
+/**
+ * Exported for the ONE other place in this repo that spawns a package manager: `reticle update`.
+ *
+ * It is a pure string rule with its own tests, and it was private while a second caller needed it
+ * -- which is exactly the shape that let `reticle setup mcp` reimplement the spawn as a bare
+ * `execFileSync` and break on Windows. Two copies of a quoting rule is the version of this bug that
+ * is hardest to see, so there is one.
+ */
+export { windowsShellArg } from './register/windows-quote.js';
+export { buildNodeIo, probeCli } from './node-io.js';
 export { SILENT_HOST } from './host.js';
 export { RETICLE_VERSION, RETICLE_NPM_PACKAGE } from './version.js';
-export { InitFailure } from './init-failure.js';
-export { NodePlatform } from './platform.js';
-export { DEV_SERVER_PORTS, isLikelyDevServerPort, devServerPortWarning, } from './dev-server-ports.js';
-export { configWithInstallSource } from './install-source-config.js';
-export { projectIdOf, rememberProjectOnDisk } from './remember-project.js';
-export { detectPackageManager, installCommandParts, parseMajor, PackageManager } from './detect.js';
-export { findWorkspaceApps } from './workspace-apps.js';
-export { refreshAgentRules } from './refresh-rules.js';
-export { diagnoseDesktop, isDesktopProject } from './desktop-doctor.js';
-export { diagnoseWebCsp } from './csp-doctor.js';
-export { reticleConfigContent } from './snippets.js';
+export { InitFailure } from './diagnose/init-failure.js';
+export { NodePlatform } from './detect/platform.js';
+export { DEV_SERVER_PORTS, isLikelyDevServerPort, devServerPortWarning, } from './detect/dev-server-ports.js';
+export { configWithInstallSource } from './project/install-source-config.js';
+export { projectIdOf, rememberProjectOnDisk } from './project/remember-project.js';
+export { detectPackageManager, installCommandParts, parseMajor, PackageManager, } from './detect/detect.js';
+export { findWorkspaceApps } from './detect/workspace-apps.js';
+export { refreshAgentRules } from './project/refresh-rules.js';
+export { diagnoseDesktop, isDesktopProject } from './diagnose/desktop-doctor.js';
+export { diagnoseWebCsp } from './diagnose/csp-doctor.js';
+export { reticleConfigContent } from './patch/snippets.js';
+/**
+ * MCP registration, for a caller that has no project.
+ *
+ * `reticle setup mcp` registers the server for the USER across every agent on the machine, which is
+ * what the one-line installer runs before any project exists. It needs the same client table and
+ * the same detection `init` uses — a second copy would be a second answer to "which agents are
+ * here", and the two would disagree the first time a client was added to one of them.
+ */
+export { McpClient, ConfigScope, MCP_CLIENTS, ClientMergeStatus, clientSpec, mergeClientConfig, } from './register/mcp-clients.js';
+export { claudeAddCommand, 
+// The two probes `run.ts` uses to decide about Claude Code. Exported because `reticle setup mcp`
+// asks the same question and had no way to ask it: Claude Code keeps no config file, so the
+// file-reading detector cannot see it, and the installer silently skipped the commonest client.
+claudeAvailableProbe, claudeExistsProbe, } from './register/mcp.js';
+export { detectMcpClients } from './register/detect-clients.js';

package/dist/node-io.d.ts

@@ -10,7 +10,7 @@ import type { InitHost } from './host.js';
  *
  * The set is closed and tiny — the four package managers, `npx`, and the Claude CLI — because those
  * are the only things the plan can ask for. It is a named constant for the same reason every other
- * wire string here is one, and it is CHECKED because of `shellOpt`: on Windows these spawn through
+ * wire string here is one, and it is CHECKED because of the shell: on Windows these spawn through
  * a shell, and a shell turns the command name into something the shell parses rather than a file it
  * executes. Arguments are quoted by `shellSafe`; the command name was the half nothing covered.
  *
@@ -19,4 +19,15 @@ import type { InitHost } from './host.js';
  * as "the command ran and failed" and hide the bug in a retry.
  */
 export declare const RUNNABLE_COMMANDS: readonly string[];
+/**
+ * Run one allowed CLI quietly and say whether it succeeded — the `probe` above, without an `InitIo`.
+ *
+ * Exported because `reticle setup mcp` needs exactly this and had reimplemented it as a bare
+ * `execFileSync(command, args)`. That works everywhere except Windows, where `claude` is a `.cmd`
+ * shim that cannot be spawned without a shell: the probe threw ENOENT, the installer concluded the
+ * machine had no Claude Code on it, and said so. The three rules that make this correct —
+ * `runnable`, `shellSafe` and the shell decision — already lived here and were private, which is the whole
+ * reason a second, broken copy existed.
+ */
+export declare function probeCli(command: string, args: readonly string[]): boolean;
 export declare function buildNodeIo(cwd: string, host: InitHost): InitIo;

package/dist/node-io.js

@@ -4,25 +4,14 @@
  * command, not the MCP stdio transport.
  */
 import { readFileSync, writeFileSync, existsSync, mkdirSync, readdirSync, statSync, accessSync, constants, } from 'node:fs';
-import { NodePlatform } from './platform.js';
+import { NodePlatform } from './detect/platform.js';
 import { join, dirname, isAbsolute } from 'node:path';
 import { homedir } from 'node:os';
 import { spawnSync } from 'node:child_process';
-import { windowsShellArg } from './windows-quote.js';
-/**
- * `shell: true` ONLY where it earns its keep.
- *
- * It exists so package-manager shims (`pnpm.cmd`, `npx.cmd`) resolve on Windows. On POSIX it buys
- * nothing and costs correctness: under a shell, arguments are re-parsed, so a path containing a
- * space — `/Users/ada/My Projects/app` — silently becomes two arguments and registration fails with
- * no error anyone can read.
- */
-function shellOpt() {
-    return NodePlatform.WINDOWS === process.platform ? { shell: true } : {};
-}
+import { windowsShellArg } from './register/windows-quote.js';
 /**
  * Under a shell, quote what the shell would otherwise split or interpret. Windows only, where
- * `shell: true` is required (see shellOpt). The rule itself lives in windows-quote.ts as a pure
+ * `shell: true` is required (see spawnAllowed). The rule itself lives in windows-quote.ts as a pure
  * function so it can be tested on every platform — keeping it inside this branch is why it was
  * wrong for as long as it was.
  */
@@ -36,7 +25,7 @@ function shellSafe(args) {
  *
  * The set is closed and tiny — the four package managers, `npx`, and the Claude CLI — because those
  * are the only things the plan can ask for. It is a named constant for the same reason every other
- * wire string here is one, and it is CHECKED because of `shellOpt`: on Windows these spawn through
+ * wire string here is one, and it is CHECKED because of the shell: on Windows these spawn through
  * a shell, and a shell turns the command name into something the shell parses rather than a file it
  * executes. Arguments are quoted by `shellSafe`; the command name was the half nothing covered.
  *
@@ -53,6 +42,53 @@ function runnable(command) {
     }
     return found;
 }
+/**
+ * Every spawn `init` makes, in the one shape Node does not deprecate.
+ *
+ * Passing an args ARRAY together with `shell: true` is DEP0190, and on Windows — the only platform
+ * where this turns the shell on — every single `init` and `curl | sh` install printed this
+ * into the middle of its output:
+ *
+ *   [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead
+ *   to security vulnerabilities, as the arguments are not escaped, only concatenated.
+ *
+ * A security warning in the middle of an install is a bad first thing to show somebody, and on the
+ * platform with the most users it was every install. The deprecation is also RIGHT about the
+ * reason: Node does not escape, it concatenates. We already escape — `windowsShellArg` implements
+ * the `CommandLineToArgvW` rule and is tested on every platform — so the fix is to own the
+ * concatenation rather than hand Node an array it will join unsafely. Same command line, same
+ * quoting, no warning.
+ *
+ * POSIX keeps the array and no shell, where argv is passed through untouched and a path with a
+ * space cannot be re-split.
+ */
+function spawnAllowed(command, args, options) {
+    const name = runnable(command);
+    if (NodePlatform.WINDOWS !== process.platform) {
+        return spawnSync(name, [...args], options);
+    }
+    // The name is one of RUNNABLE_COMMANDS, so it never needs quoting itself.
+    return spawnSync([name, ...shellSafe(args)].join(' '), [], { ...options, shell: true });
+}
+/**
+ * Run one allowed CLI quietly and say whether it succeeded — the `probe` above, without an `InitIo`.
+ *
+ * Exported because `reticle setup mcp` needs exactly this and had reimplemented it as a bare
+ * `execFileSync(command, args)`. That works everywhere except Windows, where `claude` is a `.cmd`
+ * shim that cannot be spawned without a shell: the probe threw ENOENT, the installer concluded the
+ * machine had no Claude Code on it, and said so. The three rules that make this correct —
+ * `runnable`, `shellSafe` and the shell decision — already lived here and were private, which is the whole
+ * reason a second, broken copy existed.
+ */
+export function probeCli(command, args) {
+    try {
+        const result = spawnAllowed(command, args, { stdio: 'ignore' });
+        return 0 === result.status;
+    }
+    catch {
+        return false;
+    }
+}
 export function buildNodeIo(cwd, host) {
     // Project-relative by default; absolute paths (e.g. ~/.cursor/mcp.json) pass through unchanged.
     const abs = (rel) => (isAbsolute(rel) ? rel : join(cwd, rel));
@@ -116,11 +152,7 @@ export function buildNodeIo(cwd, host) {
         },
         exec(command, args) {
             // Inherit stdio so the install's own progress is visible to the user.
-            const result = spawnSync(runnable(command), shellSafe(args), {
-                cwd,
-                stdio: 'inherit',
-                ...shellOpt(),
-            });
+            const result = spawnAllowed(command, args, { cwd, stdio: 'inherit' });
             return 0 === result.status;
         },
         /** One access check, rather than discovering it as an EACCES stack four phases later. */
@@ -135,11 +167,7 @@ export function buildNodeIo(cwd, host) {
         },
         probe(command, args) {
             // Quiet yes/no check (CLI availability, existing registration). Never throws.
-            const result = spawnSync(runnable(command), shellSafe(args), {
-                cwd,
-                stdio: 'ignore',
-                ...shellOpt(),
-            });
+            const result = spawnAllowed(command, args, { cwd, stdio: 'ignore' });
             return 0 === result.status;
         },
         print(line) {

package/dist/{astro-patch.d.ts → patch/astro-patch.d.ts}

@@ -12,7 +12,7 @@
  * Half-editing a build config is worse than a documented manual step.
  */
 import { type SourcePatch } from './patch-kind.js';
-import { UiLibrary } from './detect.js';
+import { UiLibrary } from '../detect/detect.js';
 export declare function patchAstroConfig(source: string): SourcePatch;
 export declare function patchAstroLayout(source: string, port: number | undefined, projectId: string | undefined, uiLibrary?: UiLibrary, testids?: readonly string[]): SourcePatch;
 /** Where Astro keeps ambient types — `create-astro` ships this file. */

package/dist/{astro-patch.js → patch/astro-patch.js}

@@ -13,7 +13,7 @@
  */
 import { RETICLE_DEFAULT_PORT, bridgeWsUrl } from '@reticlehq/core';
 import { PatchKind } from './patch-kind.js';
-import { UiLibrary } from './detect.js';
+import { UiLibrary } from '../detect/detect.js';
 import { registerCapabilitiesCall, sdkImport } from './snippets.js';
 import { patchViteOwningConfig } from './vite-owning-config.js';
 /** Present in a patched layout and in the printed recipe's script. */

package/dist/{cra.js → patch/cra.js}

@@ -13,7 +13,7 @@
  * mechanism and is gitignored by CRA's own template.
  */
 import { bridgeWsUrl } from '@reticlehq/core';
-import { CLI } from './agent-rules.js';
+import { CLI } from '../project/agent-rules.js';
 import { registerCapabilitiesCall } from './snippets.js';
 /** The line added to `src/index.tsx` / `src/index.js`. Side-effect import: the module guards itself on NODE_ENV. */
 export const CRA_DEV_MODULE_IMPORT = "import './reticle-dev';";

package/dist/{electron-patch.js → patch/electron-patch.js}

@@ -7,7 +7,7 @@
  * (zero, several, a factory) is MANUAL carrying the doctor's existing fix text, not a guess.
  */
 import { matchingParenEnd } from './brace-scan.js';
-import { CAPTURE_REQUIRE, ELECTRON_CAPTURE_FIX, PRELOAD_REQUIRE } from './desktop-doctor.js';
+import { CAPTURE_REQUIRE, ELECTRON_CAPTURE_FIX, PRELOAD_REQUIRE, } from '../diagnose/desktop-doctor.js';
 import { PatchKind } from './patch-kind.js';
 const ESM_PRELOAD_EXT = /\.(?:ts|mts|mjs)$/i;
 const WINDOW_DECL = /const\s+(\w+)\s*=\s*new\s+BrowserWindow\s*\(/g;

package/dist/{next-patch.d.ts → patch/next-patch.d.ts}

@@ -2,8 +2,8 @@
  * Pure, conservative patchers for the two files a Next app needed edited BY HAND: `next.config.*`
  * (wrap the export in `withReticle`) and `app/layout.tsx` (mount `<ReticleDev />`). Same contract as
  * the Vite patcher — recognise the obvious shape, bail to `manual` on anything ambiguous, never
- * half-edit. Leaving these manual is why Next connected 0% of the time: both edits are silent when
- * skipped, and one of them is JSX.
+ * half-edit. These must not be left manual: both edits fail silently when skipped, and one of them
+ * is JSX.
  */
 import { type SourcePatch } from './patch-kind.js';
 /** Where the generated connect component goes, and how the mount file should import it. */

package/dist/{next-patch.js → patch/next-patch.js}

@@ -2,8 +2,8 @@
  * Pure, conservative patchers for the two files a Next app needed edited BY HAND: `next.config.*`
  * (wrap the export in `withReticle`) and `app/layout.tsx` (mount `<ReticleDev />`). Same contract as
  * the Vite patcher — recognise the obvious shape, bail to `manual` on anything ambiguous, never
- * half-edit. Leaving these manual is why Next connected 0% of the time: both edits are silent when
- * skipped, and one of them is JSX.
+ * half-edit. These must not be left manual: both edits fail silently when skipped, and one of them
+ * is JSX.
  */
 import { PatchKind } from './patch-kind.js';
 const RETICLE_NEXT_PACKAGE = '@reticlehq/next';

package/dist/{nuxt-patch.js → patch/nuxt-patch.js}

@@ -14,7 +14,7 @@
  */
 import { patchViteOwningConfig } from './vite-owning-config.js';
 import { sdkImport } from './snippets.js';
-import { UiLibrary } from './detect.js';
+import { UiLibrary } from '../detect/detect.js';
 /** The config filenames Nuxt itself accepts, in the order `init` should prefer them. */
 export const NUXT_CONFIG_CANDIDATES = ['nuxt.config.ts', 'nuxt.config.js', 'nuxt.config.mjs'];
 /**

package/dist/{snippets.d.ts → patch/snippets.d.ts}

@@ -2,8 +2,8 @@
  * Generated file contents and copy-paste snippets for `reticle init`. Kept as named constants/builders
  * so the runner never inlines free strings.
  */
-import { UiLibrary } from './detect.js';
-import type { FoundStore } from './capabilities.js';
+import { UiLibrary } from '../detect/detect.js';
+import type { FoundStore } from '../detect/capabilities.js';
 /**
  * The connect argument literal: a non-default port adds a `url`, and a projectId is always passed
  * (so the app is identifiable across port changes). Empty string only when neither applies.
@@ -140,15 +140,11 @@ export declare function djangoMiddlewareSnippet(connectArgLiteral: string): stri
 export declare function htmlManual(port: number | undefined, projectId?: string, pairingToken?: string): string;
 export declare const NEXT_RETICLE_DEV_PATH = "app/reticle-dev.tsx";
 export declare const SVELTEKIT_HOOKS_PATH = "src/hooks.client.ts";
-/**
- * Said to the user's face rather than discovered later. React, Next, Remix and Astro each have an
- * app and a CI gate; SvelteKit has neither, so "it generated some wiring" is not evidence it works.
- */
 /**
  * Said out loud when the app does not render through React. The SDK is framework-agnostic — DOM,
  * network, console and routing all still work — but `@reticlehq/react` is a React adapter, so
- * component names and source mapping do not, and no CI gate covers this stack. Reporting all-green
- * here is the one thing this project exists not to do.
+ * component names and source mapping do not, and no CI gate covers this stack. Saying so beats
+ * reporting all-green.
  */
 export declare function unverifiedUiLibraryNote(library: string): string;
 export declare const UNVERIFIED_FRAMEWORK_NOTE = "Reticle has no SvelteKit app and no CI gate for one, so this wiring is untested \u2014 it may work, but nothing proves it and nothing will tell us if it breaks. Supported and gated today: Vite + React, Next.js, Remix and Astro. If the hook does not register a session, please open an issue.";
@@ -244,20 +240,14 @@ export declare function nuxtPluginFile(port: number | undefined, projectId?: str
  */
 export declare const NUXT_PLUGIN_NOTICE: string;
 /**
- * The Nuxt recipe, written out in full because every trap in it is one somebody actually hit.
- *
- * Reported from the field, in the order they were hit: `init` classified a Nuxt 4 app as `html`, so
- * it installed a package named `@reticlehq/react` (with `react` in its peer dependencies) into a Vue
- * codebase — the reporter only continued after auditing our dist to confirm there are no React
- * imports at runtime, which most people will not do. It then handed over a snippet guarded on
- * `window.location.hostname === 'localhost'`, which fails twice over in Nuxt: `window` does not
- * exist during SSR, and the dev host here was a hosts-file alias (required for the backend's
- * white-label origin detection), so the guard was false and the connect never ran — no error, no log
- * line, nothing to debug. And nothing said a running dev server does not pick up a new plugin.
+ * The Nuxt recipe, written out in full because each trap in it is one a Nuxt 4 app actually hit:
+ * a Vue codebase classified as `html` and handed `@reticlehq/react`, a connect guarded on
+ * `window.location.hostname === 'localhost'` (false on any hosts-file alias, and `window` does not
+ * exist during SSR), and a running dev server that never picked up the new plugin.
  *
- * So: `import.meta.dev` (build-time, host-independent) instead of a hostname check, `.client.ts`
- * instead of an SSR guard, the framework-neutral sensor instead of the React kit, the non-localhost
- * flag named up front, and the restart said out loud.
+ * So: `import.meta.dev` instead of a hostname check, `.client.ts` instead of an SSR guard, the
+ * framework-neutral sensor instead of the React kit, the non-localhost flag named up front, and the
+ * restart said out loud.
  */
 export declare function nuxtManual(port: number | undefined, projectId?: string): string;
 /**

package/dist/{snippets.js → patch/snippets.js}

@@ -3,8 +3,8 @@
  * so the runner never inlines free strings.
  */
 import { RETICLE_DEFAULT_PORT, ReticleDir, bridgeWsUrl, RETICLE_CLIENT_HOST, RETICLE_WS_PATH, } from '@reticlehq/core';
-import { UiLibrary } from './detect.js';
-import { RETICLE_VERSION } from './version.js';
+import { UiLibrary } from '../detect/detect.js';
+import { RETICLE_VERSION } from '../version.js';
 /**
  * The SDK as one import a plain page can actually resolve.
  *
@@ -113,11 +113,13 @@ pointers, not the app.`;
   import { reticle } from '@reticlehq/vite-plugin';
 
   export default defineConfig({
-    plugins: [${frameworkPluginExample(uiLibrary)}, ${call}],
+    plugins: [${call}, ${frameworkPluginExample(uiLibrary)}],
   });
 
-Keep \`reticle()\` LAST so it sees the output of your other plugins. It only applies during \`vite\`
-(dev) — it is dropped from \`vite build\`.${note}`;
+The position in the array does not matter: the plugin declares \`enforce: 'pre'\`, so Vite runs it
+before every normal plugin wherever you put it. Shown first only because that is where \`init\`
+writes it when it patches the config for you. It applies during \`vite\` (dev) only — it is dropped
+from \`vite build\`.${note}`;
 }
 /**
  * The electron-vite recipe: the plugin belongs in `renderer`, never in `main` or `preload`.
@@ -573,15 +575,11 @@ ${staticPageSnippet(withToken)}
 }
 export const NEXT_RETICLE_DEV_PATH = 'app/reticle-dev.tsx';
 export const SVELTEKIT_HOOKS_PATH = 'src/hooks.client.ts';
-/**
- * Said to the user's face rather than discovered later. React, Next, Remix and Astro each have an
- * app and a CI gate; SvelteKit has neither, so "it generated some wiring" is not evidence it works.
- */
 /**
  * Said out loud when the app does not render through React. The SDK is framework-agnostic — DOM,
  * network, console and routing all still work — but `@reticlehq/react` is a React adapter, so
- * component names and source mapping do not, and no CI gate covers this stack. Reporting all-green
- * here is the one thing this project exists not to do.
+ * component names and source mapping do not, and no CI gate covers this stack. Saying so beats
+ * reporting all-green.
  */
 export function unverifiedUiLibraryNote(library) {
     // Preact is not in the same position as Vue or Svelte and must not be told it is. The React
@@ -812,20 +810,14 @@ export const NUXT_PLUGIN_NOTICE = 'Restart the dev server: one that is already r
     'needs TWO additions, not one: allowNonLocalhost: true AND the token from ~/.reticle/pairing-token. ' +
     'The flag alone is NOT sufficient off localhost.';
 /**
- * The Nuxt recipe, written out in full because every trap in it is one somebody actually hit.
- *
- * Reported from the field, in the order they were hit: `init` classified a Nuxt 4 app as `html`, so
- * it installed a package named `@reticlehq/react` (with `react` in its peer dependencies) into a Vue
- * codebase — the reporter only continued after auditing our dist to confirm there are no React
- * imports at runtime, which most people will not do. It then handed over a snippet guarded on
- * `window.location.hostname === 'localhost'`, which fails twice over in Nuxt: `window` does not
- * exist during SSR, and the dev host here was a hosts-file alias (required for the backend's
- * white-label origin detection), so the guard was false and the connect never ran — no error, no log
- * line, nothing to debug. And nothing said a running dev server does not pick up a new plugin.
+ * The Nuxt recipe, written out in full because each trap in it is one a Nuxt 4 app actually hit:
+ * a Vue codebase classified as `html` and handed `@reticlehq/react`, a connect guarded on
+ * `window.location.hostname === 'localhost'` (false on any hosts-file alias, and `window` does not
+ * exist during SSR), and a running dev server that never picked up the new plugin.
  *
- * So: `import.meta.dev` (build-time, host-independent) instead of a hostname check, `.client.ts`
- * instead of an SSR guard, the framework-neutral sensor instead of the React kit, the non-localhost
- * flag named up front, and the restart said out loud.
+ * So: `import.meta.dev` instead of a hostname check, `.client.ts` instead of an SSR guard, the
+ * framework-neutral sensor instead of the React kit, the non-localhost flag named up front, and the
+ * restart said out loud.
  */
 export function nuxtManual(port, projectId) {
     const base = connectArg(port, projectId);
@@ -884,11 +876,10 @@ export function reticleConfigContent(framework, port, projectId, installSource)
         fields['projectId'] = projectId;
     if (port !== undefined && port !== RETICLE_DEFAULT_PORT)
         fields['port'] = port;
-    // How this install arrived, recorded HERE because it is a property of the install and the only
-    // moment anything knows it is the moment it happens. It reaches us as an environment variable set
-    // by whichever channel ran the install, and an environment variable is gone by the next command,
-    // so every event after this one reported `unknown` and the question "which channel actually
-    // converts" could not be asked at all. Written once, read for the life of the project.
+    // How this install arrived, recorded HERE because this is the only moment anything knows it. It
+    // arrives as an environment variable set by whichever channel ran the install, and an environment
+    // variable is gone by the next command, so every later event reported `unknown`. Written once,
+    // read for the life of the project.
     //
     // A closed vocabulary, narrowed before it gets here, so this can never carry a path or a URL.
     if (installSource !== undefined && installSource.length > 0) {

package/dist/{tanstack-start.d.ts → patch/tanstack-start.d.ts}

@@ -1,9 +1,8 @@
 /**
  * The TanStack Start connect recipe.
  *
- * Its own module rather than another entry in `snippets.ts`, which was at the 1000-line backstop:
- * Start is the one framework whose document module `init` deliberately refuses to write, so the
- * recipe and the reasoning behind that refusal are a unit.
+ * Its own module because Start is the one framework whose document module `init` deliberately
+ * refuses to write, so the recipe and the reasoning behind that refusal are a unit.
  */
 /** TanStack Start's document module — the file that SSRs `<html>`. */
 export declare const TANSTACK_START_ROOT_PATH = "src/routes/__root.tsx";

package/dist/{tanstack-start.js → patch/tanstack-start.js}

@@ -1,11 +1,10 @@
 /**
  * The TanStack Start connect recipe.
  *
- * Its own module rather than another entry in `snippets.ts`, which was at the 1000-line backstop:
- * Start is the one framework whose document module `init` deliberately refuses to write, so the
- * recipe and the reasoning behind that refusal are a unit.
+ * Its own module because Start is the one framework whose document module `init` deliberately
+ * refuses to write, so the recipe and the reasoning behind that refusal are a unit.
  */
-import { UiLibrary } from './detect.js';
+import { UiLibrary } from '../detect/detect.js';
 import { connectArg, sdkImport, UNVERIFIED_TANSTACK_START_NOTE } from './snippets.js';
 /** TanStack Start's document module — the file that SSRs `<html>`. */
 export const TANSTACK_START_ROOT_PATH = 'src/routes/__root.tsx';

package/dist/{vite-config.js → patch/vite-config.js}

@@ -10,19 +10,18 @@ const RETICLE_MARKER = '@reticlehq/vite-plugin';
 /**
  * The `reticle(...)` call — the bridge port so the injected connect targets it.
  *
- * **`captureNetworkBodies` is OPT-IN.** It was written in by default, and the argument for that was
- * a good one: without a body, a write that answers 2xx grades `unknown / outcome_unread`, because a
- * 200 describes the transport and not the result. Measured on a real payments UI — a refund posted
- * rupees into a paise field, the server answered 200 having refunded a hundredth of it, the page
- * rendered the amount the user had typed, and every DOM-level check passed.
+ * **`captureNetworkBodies` is OPT-IN.**
  *
- * That argument justifies the CAPABILITY. It does not justify the default, and the distinction is
- * what #705 is about. A healthcare workspace proxying authenticated API traffic through Vite ran
- * `init`, and on the first drive their login tokens and patient payloads were in the daemon's
- * buffer. The old comment here conceded the exact gap — "the credential classes are redacted ... but
- * an address or an email is not, and nothing here should decide that for someone silently" — and
- * then decided it for them, because writing the line into their config IS deciding. `init` is run
- * unattended by an agent; the person who knows the data is sensitive is not in the room.
+ * The case FOR capturing bodies is real: without one, a write that answers 2xx grades
+ * `unknown / outcome_unread`, because a 200 describes the transport and not the result. A request
+ * that posts a wrong amount can answer 200, render the amount the user typed, and pass every
+ * DOM-level check.
+ *
+ * That justifies the CAPABILITY, not the default. Any app proxying authenticated API traffic through
+ * Vite puts request bodies in the daemon's buffer on the first drive, and the credential classes are
+ * redacted while an address or an email is not. Writing the line into someone's config IS deciding
+ * that for them — and `init` is run unattended by an agent, so the person who knows whether the data
+ * is sensitive is not in the room.
  *
  * So the default is off and the ways in are all deliberate:
  *   - `reticle init --capture-bodies` writes the line, for someone who has decided
@@ -77,7 +76,10 @@ function insertImport(source) {
  * single-line array needs the space, or the result reads `[reticle(),react()]`.
  */
 function insertPlugin(source, call) {
-    return source.replace(PLUGINS_ARRAY, (match, _g, offset) => {
+    // `(match, offset, source)` — PLUGINS_ARRAY has no capture group. Reading the second argument as
+    // one put the whole source string in `offset`, so the index below was `undefined` and the
+    // separator was empty every single time.
+    return source.replace(PLUGINS_ARRAY, (match, offset) => {
         const next = source[offset + match.length] ?? '';
         const separator = '' === next || /\s/.test(next) ? '' : ' ';
         return `${match}${call},${separator}`;

package/dist/{connect-steps.d.ts → plan/connect-steps.d.ts}

@@ -1,9 +1,9 @@
 /**
  * The step titles `init` emits, and which of them decide whether the app can dial the daemon.
  *
- * Lifted out of `plan.ts` when that file reached the size backstop. A cohesive unit on its own
- * terms: one question, asked of a step title, with one consequence — a manual step in this set makes
- * `init` exit non-zero instead of reporting a success over an app that can never connect.
+ * A cohesive unit on its own terms: one question, asked of a step title, with one consequence — a
+ * manual step in this set makes `init` exit non-zero instead of reporting a success over an app that
+ * can never connect.
  *
  * The membership used to be matched against free strings written out a second time here, so
  * renaming a step in `plan-framework.ts` silently dropped it out of the set and nothing went red.

package/dist/{connect-steps.js → plan/connect-steps.js}

@@ -1,16 +1,16 @@
 /**
  * The step titles `init` emits, and which of them decide whether the app can dial the daemon.
  *
- * Lifted out of `plan.ts` when that file reached the size backstop. A cohesive unit on its own
- * terms: one question, asked of a step title, with one consequence — a manual step in this set makes
- * `init` exit non-zero instead of reporting a success over an app that can never connect.
+ * A cohesive unit on its own terms: one question, asked of a step title, with one consequence — a
+ * manual step in this set makes `init` exit non-zero instead of reporting a success over an app that
+ * can never connect.
  *
  * The membership used to be matched against free strings written out a second time here, so
  * renaming a step in `plan-framework.ts` silently dropped it out of the set and nothing went red.
  * `StepTitle` is now the one place a title is spelled: both files import it, so a rename is a
  * compile error and `plan-framework.test.ts` pins that no builder has drifted back to a literal.
  */
-import { CSP_STEP_TITLE } from './csp-check.js';
+import { CSP_STEP_TITLE } from '../diagnose/csp-check.js';
 /** Every fixed title a plan step can carry. The one spelling; nothing writes a title inline. */
 export const StepTitle = {
     VITE_PLUGIN: 'Vite plugin',

package/dist/{framework-adapter.d.ts → plan/framework-adapter.d.ts}

@@ -18,9 +18,9 @@
  *
  * `framework-adapter.test.ts` asserts the seam between the two halves.
  */
-import { Framework } from './detect.js';
+import { Framework } from '../detect/detect.js';
 import { StepTitle } from './connect-steps.js';
-import type { PlanInput, Step } from './plan.js';
+import type { PlanInput, Step } from './plan-types.js';
 export declare const RETICLE_REACT_KIT = "@reticlehq/react";
 /** The framework-neutral sensor, for stacks the React adapter has nothing to attach to. */
 export declare const RETICLE_BROWSER_SDK = "@reticlehq/browser";
@@ -58,3 +58,12 @@ export interface FrameworkAdapter {
     readonly carriesOwnUnverifiedNote: boolean;
 }
 export declare const FRAMEWORK_ADAPTERS: Record<Framework, FrameworkAdapter>;
+/**
+ * The per-framework half of the plan, looked up rather than switched.
+ *
+ * `FRAMEWORK_ADAPTERS` is a `Record<Framework, FrameworkAdapter>`, so a member added to `Framework`
+ * is a compile error in that one table instead of a framework the plan quietly does not serve. The
+ * exhaustive switch this replaced gave the same guarantee for the steps alone; the record gives it
+ * for the packages, the connect-step titles and the unverified-note flag in the same edit.
+ */
+export declare function frameworkSteps(input: PlanInput): Step[];

package/dist/{framework-adapter.js → plan/framework-adapter.js}

@@ -18,7 +18,7 @@
  *
  * `framework-adapter.test.ts` asserts the seam between the two halves.
  */
-import { Framework } from './detect.js';
+import { Framework } from '../detect/detect.js';
 import { StepTitle } from './connect-steps.js';
 import { VITE_PLUGIN_DETAIL, astroSteps, craSteps, htmlSteps, nextSteps, nuxtSteps, reactRouterSteps, svelteKitSteps, tanstackStartSteps, viteSteps, } from './plan-framework.js';
 import { electronViteSteps } from './plan-electron-vite.js';
@@ -136,3 +136,14 @@ export const FRAMEWORK_ADAPTERS = {
         carriesOwnUnverifiedNote: false,
     },
 };
+/**
+ * The per-framework half of the plan, looked up rather than switched.
+ *
+ * `FRAMEWORK_ADAPTERS` is a `Record<Framework, FrameworkAdapter>`, so a member added to `Framework`
+ * is a compile error in that one table instead of a framework the plan quietly does not serve. The
+ * exhaustive switch this replaced gave the same guarantee for the steps alone; the record gives it
+ * for the packages, the connect-step titles and the unverified-note flag in the same edit.
+ */
+export function frameworkSteps(input) {
+    return FRAMEWORK_ADAPTERS[input.detection.framework].steps(input);
+}

package/dist/plan/notices.d.ts

@@ -0,0 +1,23 @@
+import type { PlanInput, Step } from './plan-types.js';
+/**
+ * The two things a containerised dev server does differently, said before they go wrong.
+ *
+ * Null for every project with no container marker near it, which is almost all of them — so this
+ * adds nothing to the ordinary plan and does not move the install baseline.
+ */
+export declare function containerisedStep(input: PlanInput): Step | null;
+/** Windows only. The reported install never reached mcpManual because `claude mcp add` succeeded. */
+export declare function windowsMcpNoteStep(input: PlanInput): Step | null;
+/**
+ * A step that says out loud when the app isn't React. SvelteKit already carries its own unverified
+ * note, so it isn't doubled up here.
+ */
+export declare function uiLibraryStep(input: PlanInput): Step[];
+/**
+ * A WebGL subtree is pixels, and Reticle reads the DOM.
+ *
+ * react-three-fiber and its relatives render into a canvas, so the tools that find and drive
+ * elements have nothing to find. Disclosed rather than blocked: the rest of the app is still
+ * verifiable and a NOTICE says which part is not.
+ */
+export declare function webGlCanvasStep(input: PlanInput): Step[];