flowviant 0.79.0 → 0.80.0

package/bin/cli.mjs

@@ -26,7 +26,7 @@
  * running?", which otherwise ends in a pid hunt through `ps`.
  *
  * The daemon: install ONCE with a machine credential, then work entirely from
- * Flowviant. It polls GET /api/v2/fleet/agents, and the roster hands it the
+ * Flowviant. It polls GET /api/fleet/agents, and the roster hands it the
  * project's SESSIONS — the Workbench's tabs. Each session gets one persistent
  * git worktree on its own `session/<id>` branch, held across turns (never reset
  * to base: the branch outlives the tab). A turn spawns the session's CLI with a
@@ -44,7 +44,7 @@
  *
  * Env:
  *   FLOWVIANT_FLEET     the machine credential (or use `flowviant login`).
- *   FLOWVIANT_API_URL   default https://api.flowviant.com/api/v2
+ *   FLOWVIANT_API_URL   default https://api.flowviant.com/api
  *   FLOWVIANT_MCP_URL   default <API_URL>/mcp
  *   FLOWVIANT_FLEET_URL default <API_URL>/fleet/agents
  *   RECONCILE_SECONDS   roster poll cadence (default 10)

package/bin/lib/config.mjs

@@ -41,7 +41,28 @@ function argFlag(name) {
   return i >= 0 ? process.argv[i + 1] : undefined;
 }
 
-const API_BASE = process.env.FLOWVIANT_API_URL || 'https://api.flowviant.com/api/v2';
+/**
+ * THE SERVER'S API ROOT.
+ *
+ * `/api`, not `/api/v2`. The server collapsed its two prefixes into one
+ * namespace on 2026-09-08 — they had held DISJOINT resources and neither was
+ * ever a version of the other, so there was nothing to choose between.
+ *
+ * ── DEPLOY ORDER IS NOW LOAD-BEARING FOR THIS LINE ──
+ *
+ * A daemon on this version calls `/api/fleet/agents`. An older SERVER does not
+ * serve that path, so publishing this release before the server that answers it
+ * 404s the roster poll for anyone who updates. The order in the app repo's
+ * ARCHITECTURE.md already says it and now it matters: deploy `flowviant-api`
+ * FIRST, publish this SECOND. The same applies to a rollback — rolling the
+ * server back past that merge strands every daemon at this version or newer.
+ *
+ * The other direction is safe and needs nothing: the server keeps `/api/v2` as
+ * an alias onto the same router precisely because every daemon published before
+ * this one has that string baked in and cannot be upgraded by a deploy. That
+ * alias retires when the app's `DAEMON_MIN_VERSION` clears this release.
+ */
+const API_BASE = process.env.FLOWVIANT_API_URL || 'https://api.flowviant.com/api';
 export const MCP_URL = process.env.FLOWVIANT_MCP_URL || `${API_BASE}/mcp`;
 export const FLEET_URL = process.env.FLOWVIANT_FLEET_URL || `${API_BASE}/fleet/agents`;
 // Push channel: the daemon holds this WebSocket open and the server nudges it

package/bin/lib/fleet.mjs

@@ -1,6 +1,6 @@
 /**
  * Fleet daemon. Install ONCE with a fleet credential; manage everything from
- * Flowviant. The daemon polls GET /api/v2/fleet/agents, reconciles one persistent
+ * Flowviant. The daemon polls GET /api/fleet/agents, reconciles one persistent
  * git worktree + worker loop per roster agent, rotates each worker's short-lived
  * MCP token, and only spawns Claude when the server says an agent has work.
  */

package/bin/lib/vault.mjs

@@ -6,7 +6,7 @@
  * private `git init` so every pass is versioned locally for free — the user's
  * repository is never touched.
  *
- * Sync protocol (POST /api/v2/fleet/wiki-vault, fleet-token auth): only files
+ * Sync protocol (POST /api/fleet/wiki-vault, fleet-token auth): only files
  * whose sha256 changed since the last successful sync are uploaded, chunked;
  * the LAST request carries the finalize.manifest of a completed full sweep so
  * the server prunes pages the sweep no longer has. The last-synced hashes live

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flowviant",
-  "version": "0.79.0",
+  "version": "0.80.0",
   "description": "Run your own coding CLIs as build agents for Flowviant — Claude Code, Codex or Antigravity, on your own credentials. Holds your sessions, keeps a worktree per tab, and ships branches on your word.",
   "type": "module",
   "bin": {