flowviant 0.28.0 → 0.28.2

package/bin/lib/claude.mjs

@@ -130,25 +130,62 @@ Ground EVERY claim in files you actually read (Read, Grep, Glob, ls, git in the
 repo) — never guess.
 
 THE HUMAN DOCS — docs/ inside the vault. After the vault pages are current,
-COMPILE human documentation FROM them (distill your own vault pages — don't
-re-read the whole repo; spot-check a cited file only when something looks off).
-Docs are for humans: clear prose, short sections, a reading order. Fixed spine:
-- docs/00-start-here.md — "Start Here": what this codebase is, how to run it,
-  the handful of files that matter most, where to go next.
-- docs/01-architecture.md — the big picture: major pieces, how they fit, data
-  flow, and a map of the chapters below.
-- docs/1N-<chapter>.md — ONE chapter per major subsystem (10, 11, 12 …), YOUR
-  choice of chapters, derived from the vault's hub pages.
-- docs/90-decisions.md — notable design decisions and their why.
-- docs/91-glossary.md — the project's terms of art.
-Docs pages use the same frontmatter files: lists and [[wikilinks]] (they may
-link to vault pages); numeric prefixes are the reading order.
+COMPILE professional developer documentation FROM them (distill your own vault
+pages; spot-check a cited file only when something looks off — don't re-read the
+whole repo). These are what a new engineer onboards from and a working engineer
+keeps open: hold them to the standard of Stripe / Google / Microsoft developer
+docs — comprehensive, precisely structured, richly cross-linked. Detailed and
+thorough beats short: a reader should be able to work in a subsystem after
+reading its chapter.
+
+Fixed spine (numeric prefix = reading order):
+- docs/00-start-here.md — the landing page + MASTER TABLE OF CONTENTS: what the
+  product is (2-3 sentences); how to run it locally (prerequisites, install,
+  required env, dev server, tests); then a linked table of contents of EVERY
+  chapter, each with a one-line description; then 2-3 role-based reading paths
+  (e.g. "New to the backend: read 01, then 12, then 14").
+- docs/01-architecture.md — the system at a glance: a Mermaid diagram (a fenced
+  code block whose language is mermaid) of the major components and how they
+  connect, a component-responsibility table, the primary request/data flows, and
+  a link into the chapter for each component.
+- docs/1N-<chapter>.md — ONE chapter per major subsystem (10, 11, 12 …), your
+  choice of chapters, derived from the vault's hub pages. Cover every significant
+  subsystem.
+- docs/90-decisions.md — notable design decisions, each as context, decision,
+  why, and consequences.
+- docs/91-glossary.md — the project's terms of art, alphabetized, each linking to
+  the chapter or vault page that defines it.
+
+EVERY chapter follows this exact anatomy, in order:
+  1. YAML frontmatter listing the real repo files the chapter draws on.
+  2. A "# Title" heading.
+  3. One or two sentences: what the chapter covers and who should read it.
+  4. A "## Contents" section — an in-page table of contents: a bulleted list
+     linking each of the chapter's own "## " sections by anchor. An anchor is the
+     heading text lowercased, spaces turned to hyphens, punctuation removed — so
+     a section "## How dispatch works" is linked "- [How dispatch works](#how-dispatch-works)".
+  5. The body sections ("## " / "### "), including as relevant: an overview and
+     where the subsystem sits in the system; how it works walked step by step
+     with REAL code excerpts (fenced and language-tagged) and file citations; a
+     Mermaid diagram for any non-trivial flow or sequence; and REFERENCE TABLES
+     for the concrete surface — HTTP endpoints (method, path, auth, purpose), key
+     functions/types, env/config keys, DB tables/columns — as markdown tables.
+  6. A "## Gotchas" section: the traps, edge cases, invariants, and non-obvious
+     constraints.
+  7. A "## See also" section: [[wikilinks]] to the deeper vault pages, plus
+     relative links to sibling chapters (e.g. "[Architecture](01-architecture.md)").
+
+Cross-link liberally: [[wikilinks]] point to vault pages; relative "NN-name.md"
+links point to sibling chapters; both are clickable in the reader. Keep every
+claim grounded in code you actually read.
 
 Full-sweep protocol:
 1. If the vault already has pages, read index.md + log.md FIRST — update and
    extend rather than rewrite; delete vault pages whose code no longer exists.
 2. Explore the repo broadly, then write/refresh pages area by area.
-3. Compile/refresh the docs/ chapters from the finished vault pages.
+3. Compile/refresh the docs/ chapters from the finished vault pages, following
+   the docs spine + per-chapter anatomy above (Contents TOC, reference tables,
+   Mermaid diagrams, Gotchas, See also).
 4. Refresh index.md, append a log.md entry, then output exactly WIKI_DONE on
    its own line and stop.
 

package/bin/lib/deploy.mjs

@@ -60,14 +60,19 @@ export async function reportDeployConfig(repoRoot) {
   const targets = readDeployConfig(repoRoot);
   const json = JSON.stringify(targets);
   if (json === lastConfigJson) return;
-  // Strip commands/secrets before the server sees the config (metadata only).
+  // Scrub command strings before the server sees them — a command line can embed
+  // an internal host or a synced secret. Only redacted metadata leaves the box.
+  const scrubCmds = (o) =>
+    o && typeof o === 'object'
+      ? Object.fromEntries(Object.entries(o).map(([k, v]) => [k, scrub(String(v ?? ''))]))
+      : o;
   const meta = targets.map((t) => ({
     id: t.id,
     label: t.label,
     provider: t.provider || 'cloudflare',
-    command: t.command,
-    build: t.build,
-    commands: t.commands,
+    command: scrub(String(t.command ?? '')),
+    build: t.build ? scrub(String(t.build)) : t.build,
+    commands: scrubCmds(t.commands),
     healthcheck: t.healthcheck,
     healthStatus: t.healthStatus,
     pushSecrets: t.pushSecrets,
@@ -100,6 +105,11 @@ function run(command, { cwd, env, input }) {
         /* already gone */
       }
     }, 30 * 60_000);
+    // A broken pipe (child exits before draining stdin — e.g. a fast-failing
+    // `wrangler secret put`) surfaces as an ASYNC 'error' on the stdin stream,
+    // which the try/catch below can't catch. Without a listener it's an uncaught
+    // exception that kills the whole daemon. Swallow it.
+    child.stdin.on('error', () => {});
     if (input != null) {
       try {
         child.stdin.write(input);
@@ -129,7 +139,7 @@ async function verifyHealth(url, status) {
   for (let i = 0; i < 4; i++) {
     try {
       const res = await fetch(url, { signal: AbortSignal.timeout(10_000), redirect: 'manual' });
-      if (res.status === status) return true;
+      if (res.status === Number(status)) return true; // coerce — a string "200" in deploy.json must still match
     } catch {
       /* not up yet */
     }
@@ -148,6 +158,10 @@ const claiming = new Set(); // in-flight guard (single-flight per daemon process
 export function processDeployJobs(jobs, ctx) {
   if (!Array.isArray(jobs) || !jobs.length) return;
   for (const job of jobs) {
+    // Defend against a malformed roster element — `job.id` on a null would throw
+    // synchronously here (outside the per-job try below) and wedge the whole
+    // reconcile loop, since this runs unguarded from the fleet tick.
+    if (!job || typeof job.id !== 'string') continue;
     if (claiming.has(job.id)) continue;
     claiming.add(job.id);
     void (async () => {
@@ -185,6 +199,7 @@ export function processDeployJobs(jobs, ctx) {
 
 async function runDeploy(job, target, ctx) {
   const env = { ...process.env, ...deployCreds() }; // inject infra creds; never a file
+  delete env.FLEET_TOKEN; // the deploy command has no business reading it; keep it out of a command that might echo its env
   const logs = [];
   // Rollback is a single wrangler command; deploy is build → secrets → deploy.
   if (job.kind === 'rollback') {

package/bin/lib/fleet.mjs

@@ -295,6 +295,7 @@ export async function runFleetDaemon() {
   };
   const processMergeJobs = (jobs) => {
     for (const job of jobs ?? []) {
+      if (!job || typeof job.id !== 'string') continue; // a null element would wedge the loop
       if (merging.has(job.id)) continue;
       merging.add(job.id);
       (async () => {
@@ -374,6 +375,7 @@ export async function runFleetDaemon() {
   const cleaning = new Set();
   const processCleanupJobs = (jobs) => {
     for (const job of jobs ?? []) {
+      if (!job || typeof job.id !== 'string') continue; // a null element would wedge the loop
       if (cleaning.has(job.id)) continue;
       cleaning.add(job.id);
       (async () => {
@@ -889,7 +891,10 @@ export async function runFleetDaemon() {
     // turn) until we report reground-done; the bare drain flushes anything
     // whose earlier mint failed.
     enqueueSweep(roster.codeMapJob);
-    for (const j of roster.regroundJobs ?? []) enqueueReground(j.intentId, j.prUrl, j.title);
+    for (const j of roster.regroundJobs ?? []) {
+      if (!j || typeof j.intentId !== 'string') continue; // a null element would throw + wedge the loop
+      enqueueReground(j.intentId, j.prUrl, j.title);
+    }
     void drainWiki();
 
     // Env sync tick: register/bootstrap/wrap/rotate/sync as the roster block

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flowviant",
-  "version": "0.28.0",
+  "version": "0.28.2",
   "description": "Run your own Claude Code as headless build agents for Flowviant — on your own credentials. Claims dispatched work, opens PRs, captures review evidence, and routes questions back to you.",
   "type": "module",
   "bin": {
@@ -30,7 +30,7 @@
   "homepage": "https://flowviant.com",
   "repository": {
     "type": "git",
-    "url": "https://github.com/flowviant/cli.git"
+    "url": "git+https://github.com/flowviant/cli.git"
   },
   "license": "MIT",
   "bugs": {