@aion0/forge 0.10.69 → 0.10.71

package/RELEASE_NOTES.md

@@ -1,13 +1,11 @@
-# Forge v0.10.69
+# Forge v0.10.71
 
 Released: 2026-06-11
 
-## Changes since v0.10.68
+## Changes since v0.10.70
 
 ### Other
-- fix(idp): decouple probe host from IdP login host (probe_host)
-- fix(terminal): resolve absolute claude binary on tab restore
-- feat(pipeline): git OTP/2FA preflight + auth-blocked alerts
+- fix(auth): persist AUTH_SECRET so sessions survive refresh/restart
 
 
-**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.10.68...v0.10.69
+**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.10.70...v0.10.71

package/bin/forge-server.mjs

@@ -123,6 +123,19 @@ const workspacePort = parseInt(getArg('--workspace-port')) || (webPort + 2);
 // second instance (dev-test on a different webPort) collided with the
 // main instance. Offset from webPort like every other service.
 const mcpPort = parseInt(getArg('--mcp-port')) || (webPort + 3);
+// Browser-bridge standalone. Was hardcoded to 8407 everywhere (standalone,
+// bridge-info route, extension fallback), so a second instance (e.g. --port
+// 4000) reused the 8403 instance's bridge → the extension connected to the
+// wrong instance and its token was rejected. Offset from webPort like the
+// others; default 8403+4 = 8407 keeps existing single-instance pairings.
+const bridgePort = parseInt(getArg('--bridge-port')) || (webPort + 4);
+// Chat standalone. Was hardcoded to 8408 everywhere — a second instance
+// (--port 4000) failed to bind it, then its next-server fell back to the
+// 8408 default and hit the FIRST instance's chat standalone with a token
+// signed for the wrong instance → "Sync failed: unauthorized" on
+// settings/marketplace. Offset like bridge; default 8403+5 = 8408 keeps
+// existing single-instance behaviour.
+const chatPort = parseInt(getArg('--chat-port')) || (webPort + 5);
 const DATA_DIR = getArg('--dir')?.replace(/^~/, homedir()) || join(homedir(), '.forge', 'data');
 
 const PID_FILE = join(DATA_DIR, 'forge.pid');
@@ -245,8 +258,29 @@ process.env.PORT = String(webPort);
 process.env.TERMINAL_PORT = String(terminalPort);
 process.env.WORKSPACE_PORT = String(workspacePort);
 process.env.MCP_PORT = String(mcpPort);
+process.env.BRIDGE_PORT = String(bridgePort);
+process.env.CHAT_PORT = String(chatPort);
 process.env.FORGE_DATA_DIR = DATA_DIR;
 
+// Persist AUTH_SECRET so every next-server worker uses the same key.
+// lib/auth.ts generates a random one per process when unset, and Next prod
+// mode spawns multiple workers — without a stable secret, a cookie signed
+// by worker A is rejected by worker B, so the user randomly gets bounced
+// to /login every few requests. Forge-server.mjs is the only common parent
+// of all workers; lib/auth.ts is intentionally untouched.
+if (!process.env.AUTH_SECRET) {
+  const SECRET_FILE = join(DATA_DIR, '.auth-secret');
+  let secret = '';
+  try { if (existsSync(SECRET_FILE)) secret = readFileSync(SECRET_FILE, 'utf-8').trim(); } catch {}
+  if (!secret) {
+    const { randomBytes } = await import('node:crypto');
+    secret = randomBytes(32).toString('hex');
+    if (!existsSync(DATA_DIR)) mkdirSync(DATA_DIR, { recursive: true });
+    writeFileSync(SECRET_FILE, secret, { mode: 0o600 });
+  }
+  process.env.AUTH_SECRET = secret;
+}
+
 // ── Password setup (first run or --reset-password) ──
 // Skipped in --add-enterprise-key persist-and-exit mode: registering a
 // key from install.sh must not block on an interactive prompt.
@@ -318,6 +352,7 @@ if (!isStop && !addEnterpriseKeyOnly) {
   }
 }
 
+
 // ── Enterprise keys (--enterprise-key=…) ──
 //
 // Each key is encrypted with AES-256-GCM via the same `.encrypt-key`

package/lib/pipeline.ts

@@ -1068,6 +1068,10 @@ export function startPipeline(
       pipeline.error = `${blocked.message}${blocked.action ? `\nRun: ${blocked.action}` : ''}`;
       pipeline.completedAt = new Date().toISOString();
       savePipeline(pipeline);
+      // Same settle housekeeping every other failure path gets — without it
+      // schedule/binding-fired runs linger as "running" in pipeline_runs
+      // until zombie reconciliation catches them.
+      finalizePipeline(pipeline);
       void notifyAuthBlocked({
         title: `Pipeline aborted — git auth required (${workflowName})`,
         body: blocked.message,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aion0/forge",
-  "version": "0.10.69",
+  "version": "0.10.71",
   "description": "Unified AI workflow platform — multi-model task orchestration, persistent sessions, web terminal, remote access",
   "type": "module",
   "scripts": {