@reticlehq/init 3.1.0 → 3.2.0

package/dist/detect/detect.js

@@ -301,7 +301,11 @@ const INSTALL_ARGS = {
  * hard failure, which is the opposite of the problem being fixed.
  */
 const QUIET_INSTALL_ARGS = {
-    [PackageManager.NPM]: ['--no-audit', '--no-fund'],
+    // `--no-update-notifier` joined the other two for the same reason and from the same measurement:
+    // a re-capture of a pristine Vite first run spent five of its lines on an `npm notice` block
+    // announcing a newer npm, its changelog url and the command to install it. Advice about npm,
+    // printed in the middle of somebody wiring up a different tool.
+    [PackageManager.NPM]: ['--no-audit', '--no-fund', '--no-update-notifier'],
 };
 /** Build a dev-dependency install command for one or more packages (e.g. the kit + its build plugin). */
 export function installCommandParts(pm, pkgs, 

package/dist/index.d.ts

@@ -9,6 +9,15 @@
  * ends up unable to move a file.
  */
 export { runInit, resolveLockfiles, type InitIo, type InitOptions, type InitResult, } from './run.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 { type InitHost, SILENT_HOST } from './host.js';
 export { RETICLE_VERSION, RETICLE_NPM_PACKAGE } from './version.js';

package/dist/index.js

@@ -9,6 +9,15 @@
  * ends up unable to move a file.
  */
 export { runInit, resolveLockfiles, } from './run.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';

package/dist/patch/snippets.js

@@ -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`.

package/dist/run-types.d.ts

@@ -111,6 +111,16 @@ export interface InitResult {
     ok: boolean;
     applied: number;
     manual: number;
+    /**
+     * The MCP server was registered by THIS run, rather than having been there already.
+     *
+     * `outcome.mcpRegistered` cannot answer this: it is true for both APPLY and ALREADY, and the two
+     * have opposite answers to the only question that matters here — must the agent reading this
+     * restart before it can call a `reticle_*` tool. An agent client reads its server list when it
+     * STARTS and never re-reads it, so on the run that first registers Reticle on a machine the tools
+     * are not in the session that just asked for them.
+     */
+    mcpNewlyRegistered?: boolean;
     /** What this run established. Absent only where init exits before establishing anything. */
     context?: InitContext;
     /**

package/dist/run.js

@@ -441,9 +441,14 @@ continuesToRuntime = false) {
             for (const line of detail.split('\n'))
                 io.print(`      ${line}`);
         }
-        else if (detail.length > 0) {
-            io.print(`      ${detail}`);
-        }
+        // Everything else gets its row and nothing more. The detail on a step that needs no decision
+        // restates its own title — "reticle already registered with Cursor" under
+        // `[·] MCP server (Cursor)` — and a measured Vite first run spent twelve of its forty-six lines
+        // that way, six tool names deep, before saying anything about the reader's own app.
+        //
+        // The ROW stays on every step: `apps/e2e/install-gate.mjs` reads `[mark] title → target` out of
+        // this report and diffs the shape against a recorded baseline, so a row that stopped printing
+        // would take that guard down with it while looking like tidying.
     }
     io.print('');
     if (connectPending) {
@@ -451,10 +456,20 @@ continuesToRuntime = false) {
             '"no browser session connected" until then. Everything else is already in place.');
         io.print('');
     }
+    const mcpStatus = resolvedStatus(plan, MCP_TARGET, failed, skipped);
     if (!continuesToRuntime) {
-        io.print(restartHint(resolvedStatus(plan, MCP_TARGET, failed, skipped), devCommand));
+        io.print(restartHint(mcpStatus, devCommand));
     }
-    return { ok: !connectPending, applied, manual };
+    // Carried out even when the hint above was printed, because the RUNTIME path needs the same fact
+    // and could not reach it: `restartHint` is only printed when this run stops at the files, and the
+    // full run -- the one the installer sends everybody to -- ended by telling an agent to call
+    // `reticle_act_and_wait` in a session whose tool list was read before Reticle existed.
+    return {
+        ok: !connectPending,
+        applied,
+        manual,
+        ...(StepStatus.APPLY === mcpStatus ? { mcpNewlyRegistered: true } : {}),
+    };
 }
 /**
  * Perform the apply-step side effects; return the targets whose side effect failed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reticlehq/init",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Reticle project scaffolder — detects the framework, writes the config, patches the build and registers the MCP server. The build-time half of `reticle init`.",
   "type": "module",
   "main": "./dist/index.js",
@@ -13,7 +13,7 @@
     "./package.json": "./package.json"
   },
   "dependencies": {
-    "@reticlehq/core": "3.1.0"
+    "@reticlehq/core": "3.2.0"
   },
   "license": "FSL-1.1-ALv2",
   "author": "Reticle contributors",