@reticlehq/server 2.13.0 → 2.13.1

package/dist/setup/dev-server-wait.d.ts

@@ -25,6 +25,14 @@ export interface WaitFacts {
     readonly quietForMs: number;
     /** Milliseconds since the wait began. */
     readonly elapsedMs: number;
+    /**
+     * How long silence may mean "still starting" on THIS machine. Defaults to QUIET_MEANS_HUNG_MS.
+     *
+     * Passed in rather than read from the platform here, so this stays a pure decision and exactly one
+     * caller owns the platform check. 45s is generous on a laptop and tight on a cold Windows runner,
+     * where a first `npm run dev` optimises dependencies before Vite prints a line.
+     */
+    readonly quietMeansHungMs?: number;
 }
 export declare const WaitVerdict: {
     /** It is up. Carry on. */

package/dist/setup/dev-server-wait.js

@@ -41,7 +41,9 @@ export function judgeWait(facts) {
     if (facts.elapsedMs >= WAIT_CEILING_MS)
         return WaitVerdict.HUNG;
     // Output IS progress. Silence is what distinguishes a build from a wedge.
-    return facts.quietForMs >= QUIET_MEANS_HUNG_MS ? WaitVerdict.HUNG : WaitVerdict.WAITING;
+    return facts.quietForMs >= (facts.quietMeansHungMs ?? QUIET_MEANS_HUNG_MS)
+        ? WaitVerdict.HUNG
+        : WaitVerdict.WAITING;
 }
 /** A url the dev server announced, if it has announced one. Never composed, only read. */
 const URL_IN_OUTPUT = /https?:\/\/(?:localhost|127\.0\.0\.1|\[::1\]):\d+/;

package/dist/setup/run-setup.js

@@ -11,7 +11,20 @@
  * way of going wrong, and the alternative to injecting them is a test that boots a real dev server
  * and a real browser to find out what happens when neither works.
  */
-import { judgeWait, urlToWatch, WaitVerdict } from './dev-server-wait.js';
+import { judgeWait, QUIET_MEANS_HUNG_MS, urlToWatch, WaitVerdict } from './dev-server-wait.js';
+/**
+ * Windows gets longer to say something before silence counts as a wedge.
+ *
+ * A first `npm run dev` on a cold Windows runner optimises dependencies before the bundler prints a
+ * line, and 45s of quiet is inside that window. Measured on the install gate: the Vue scaffold was
+ * declared hung, `init` exited 1, and the gate then started the very same app and connected to it
+ * on the next line. Nothing was wrong with the app; the wait was too impatient for the platform.
+ *
+ * Only the QUIET budget moves. The ceiling is unchanged, and a launcher that exits is still dead
+ * immediately, so this buys patience for a starting server and never for a broken one.
+ */
+const WINDOWS_QUIET_MEANS_HUNG_MS = 3 * 60_000;
+const WINDOWS_QUIET_MEANS_HUNG_MS_APPLIES = 'win32' === process.platform;
 import { pickSession } from './session-pick.js';
 import { readPage, describePage } from './page-probe.js';
 import { remainingSteps } from './remaining-steps.js';
@@ -75,6 +88,9 @@ export async function runSetupPhases(input, fx) {
                 serving,
                 quietForMs: fx.devServerQuietForMs(),
                 elapsedMs: fx.now() - startedAt,
+                quietMeansHungMs: WINDOWS_QUIET_MEANS_HUNG_MS_APPLIES
+                    ? WINDOWS_QUIET_MEANS_HUNG_MS
+                    : QUIET_MEANS_HUNG_MS,
             });
             if (WaitVerdict.READY === verdict && undefined !== watching) {
                 url = watching;

package/docs/docs.json

@@ -32,7 +32,7 @@
   "navigation": {
     "versions": [
       {
-        "version": "2.13.0",
+        "version": "2.13.1",
         "default": true,
         "tabs": [
           {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reticlehq/server",
-  "version": "2.13.0",
+  "version": "2.13.1",
   "description": "Reticle bridge + MCP server. Hosts the browser WS endpoint and exposes MCP tools to the coding agent.",
   "type": "module",
   "main": "./dist/index.js",
@@ -22,7 +22,7 @@
     "@modelcontextprotocol/sdk": "^1.30.0",
     "ws": "^8.21.3",
     "zod": "^3.24.1",
-    "@reticlehq/core": "2.13.0"
+    "@reticlehq/core": "2.13.1"
   },
   "devDependencies": {
     "@types/pngjs": "^6.0.5",