baldart 3.35.1 → 3.35.2

package/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to BALDART will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.35.2] - 2026-05-30
+
+Resolves the **3.35.1 known follow-up**: a flag introduced in a newer release (e.g. `--on-divergence`, v3.29.0) was rejected by an older global CLI with a cryptic `error: unknown option` **before** the `npx baldart@latest` auto-relaunch could self-upgrade — commander validates options during `program.parse()`, which runs *before* the action handler where the relaunch lives. The `update` command now parses **permissively**, so an unknown flag is captured instead of crashing the parser; the action then transparently relaunches under `@latest` (forwarding the raw argv so the unrecognized flag survives) or, when that isn't possible, emits an **actionable** error instead of commander's cryptic one. **No new `baldart.config.yml` keys** — the schema-propagation rule does not apply.
+
+> **Forward-looking by nature.** This cannot retroactively fix CLIs *already* installed at a pre-3.35.2 version — their commander still throws before any code we control runs. The fix rescues flags introduced *after* this release for anyone on 3.35.2+. For older installs the only path remains `npm i -g baldart@latest` (now surfaced by the helpful error + the update notifier).
+
+### Fixed — self-upgrade survives flags newer than the installed CLI
+
+- **[bin/baldart.js](bin/baldart.js)**: the `update` command gains `.allowUnknownOption()` + `.allowExcessArguments()` (scoped to `update` only — every other command keeps strict validation). Unknown tokens now land in `command.args` instead of throwing `commander.unknownOption` during parse; they are forwarded to `update(options, command.args)`.
+- **[src/commands/update.js](src/commands/update.js)** (`update`): an early unknown-flag block runs **before** any work. When unknown tokens are present it relaunches under `npx baldart@latest`, forwarding `process.argv.slice(3)` (raw flags, with the leading `update` subcommand token stripped so the child isn't spawned as `update update …`). The unrecognized flag never enters `options`, so raw-argv forwarding is the only faithful path.
+- **[src/commands/update.js](src/commands/update.js)** (`maybeRelaunchUnderLatest`): accepts `extra.rawArgs` (forward verbatim instead of reconstructing from parsed `options`) and `extra.unknown` (skip the interactive "proceed with current CLI" prompt — pointless when the CLI literally can't parse the flag; relaunch whenever a newer version exists). The normal stale-CLI relaunch path is unchanged (still reconstructs known flags, still forwards `--on-divergence` / `--json`).
+- **[src/commands/update.js](src/commands/update.js)** (`failOnUnknownArgs`): new helpful terminal error replacing commander's cryptic message — hedges between "recently-added flag → `npm i -g baldart@latest`" and "typo", and **suppresses the upgrade suggestion** when `BALDART_RELAUNCHED=1` (we are already the `@latest` child, so a typo is the only explanation). `--json`-aware: emits a `usage-error` JSON object on stdout.
+- **[src/commands/update.js](src/commands/update.js)**: `--json` mode is now **armed before** the unknown-flag block so the relaunch notice / helpful error route to STDERR — preserving the single-object STDOUT contract for `update --json --yes --<new-flag>` (the agent/CI scenario this machinery exists for).
+
 ## [3.35.1] - 2026-05-30
 
 Fixes a **HIGH-severity** bug where `baldart update --reset` could leave a consumer **committed-without-`.framework/`** (broken install, manual recovery only). The reset path wiped `.framework/`, committed the deletion, then handed off to `add()` **programmatically with no repository** — the bin-layer default (`antbald/BALDART`) only applies on the CLI path, so `repo` arrived `undefined`, crashing at `repo.startsWith(...)` ("Cannot read properties of undefined") *after* the wipe was already committed. Three layers now make this unreachable: (1) repo resolved **before** any destructive step, (2) reinstall failures roll back to the pre-reset backup tag, (3) defensive guards + legible errors. **No new `baldart.config.yml` keys** — the schema-propagation rule does not apply.

package/VERSION

@@ -1 +1 @@
-3.35.1
+3.35.2

package/bin/baldart.js

@@ -81,9 +81,24 @@ program
   .option('--i-know', 'Acknowledges --reset will wipe untracked/ignored files inside .framework/ (required to use --reset --yes).')
   .option('--on-divergence <strategy>', 'Non-interactive resolution when the consumer has local commits on .framework/ (for agents / CI): "scaffold-overlays" (auto-create overlay skeletons, then stop), "pull" (keep commits + merge — non-destructive), or "abort".')
   .option('--json', 'Machine-readable output (agents / CI): emit a single JSON result object on stdout, route all human output to stderr. Requires --yes (non-interactive); rejects --reset.')
-  .action(async (options) => {
+  // Parse permissively so an UNKNOWN flag does not crash commander before the
+  // CLI self-upgrade can kick in (v3.35.2+). The whole point of `update` is to
+  // be the self-healing entrypoint: when a flag introduced in a newer release
+  // reaches an older-but-still-this-or-later CLI, commander used to throw
+  // `error: unknown option` during parse — i.e. BEFORE the action handler runs,
+  // so the auto-relaunch under `npx baldart@latest` (which lives in the action)
+  // never got a chance. With both guards set, unknown tokens land in
+  // `command.args` instead of throwing; the action forwards them to a newer CLI
+  // (or emits a helpful error). Scoped to `update` only — every other command
+  // keeps strict validation.
+  .allowUnknownOption()
+  .allowExcessArguments()
+  .action(async (options, command) => {
     const updateCommand = require('../src/commands/update');
-    await updateCommand(options);
+    // command.args holds any tokens commander could not match to a known
+    // option/positional — for `update` (no positionals) that means unknown
+    // flags + their values. Forward them so update() can self-upgrade.
+    await updateCommand(options, command.args || []);
   });
 
 program

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baldart",
-  "version": "3.35.1",
+  "version": "3.35.2",
   "description": "Claude Agent Framework - Reusable framework for coordinating AI agents and humans in software projects",
   "bin": {
     "baldart": "./bin/baldart.js"

package/src/commands/update.js

@@ -406,7 +406,16 @@ function snapshotCustomEntries(dir) {
 // child inherits stdio (preserves prompts), and BALDART_RELAUNCHED=1 in env
 // is a loop guard: if npm cache somehow serves an older version, the child
 // sees the flag and skips its own relaunch check.
-async function maybeRelaunchUnderLatest(options) {
+// `extra.rawArgs` — when set, forward these verbatim to the child instead of
+// reconstructing flags from the parsed `options`. Used by the unknown-flag path
+// (v3.35.2+): an option this CLI doesn't recognize never lands in `options`, so
+// reconstruction would silently drop it — only the raw argv carries it intact.
+// The caller MUST have already stripped the leading `update` subcommand token.
+// `extra.unknown` — true when triggered by an unknown flag rather than a plain
+// stale-CLI check. In that case the interactive "proceed with current CLI"
+// branch is pointless (the current CLI literally cannot honor the flag), so we
+// relaunch whenever a newer version exists and skip the prompt.
+async function maybeRelaunchUnderLatest(options, extra = {}) {
   if (process.env.BALDART_RELAUNCHED === '1') return false;
   if (process.env.BALDART_NO_RELAUNCH === '1') return false;
 
@@ -424,7 +433,13 @@ async function maybeRelaunchUnderLatest(options) {
 
   const autoYes = options.yes === true;
   let proceed = autoYes;
-  if (!autoYes) {
+  if (extra.unknown) {
+    // Unknown flag + a newer CLI exists: relaunch unconditionally. Asking
+    // "proceed with current CLI?" makes no sense — it can't parse the flag.
+    proceed = true;
+    UI.newline();
+    UI.warning(`Unknown option for the installed CLI (v${cliVersion}); a newer release (v${info.latest}) may support it.`);
+  } else if (!autoYes) {
     UI.newline();
     UI.warning(`The installed CLI is older than npm latest: v${cliVersion} → v${info.latest}.`);
     const choice = await UI.select('How would you like to proceed?', [
@@ -440,17 +455,24 @@ async function maybeRelaunchUnderLatest(options) {
   }
   if (!proceed) return false;
 
-  // Reconstruct the original argv flags for the child.
-  const flags = [];
-  if (options.yes === true) flags.push('--yes');
-  if (options.autoStash === true && options.yes !== true) flags.push('--auto-stash');
-  if (options.commit === false) flags.push('--no-commit');
-  if (options.reset === true) flags.push('--reset');
-  if (options.iKnow === true) flags.push('--i-know');
-  // Forward the non-interactive resolution + machine-readable flags too, else
-  // a stale-CLI self-relaunch would silently drop them (v3.32.0+).
-  if (options.onDivergence) flags.push('--on-divergence', options.onDivergence);
-  if (options.json === true) flags.push('--json');
+  // Build the child argv. The unknown-flag path forwards the raw argv (already
+  // stripped of the `update` token); the normal stale-CLI path reconstructs
+  // from parsed options.
+  let flags;
+  if (Array.isArray(extra.rawArgs)) {
+    flags = extra.rawArgs;
+  } else {
+    flags = [];
+    if (options.yes === true) flags.push('--yes');
+    if (options.autoStash === true && options.yes !== true) flags.push('--auto-stash');
+    if (options.commit === false) flags.push('--no-commit');
+    if (options.reset === true) flags.push('--reset');
+    if (options.iKnow === true) flags.push('--i-know');
+    // Forward the non-interactive resolution + machine-readable flags too, else
+    // a stale-CLI self-relaunch would silently drop them (v3.32.0+).
+    if (options.onDivergence) flags.push('--on-divergence', options.onDivergence);
+    if (options.json === true) flags.push('--json');
+  }
 
   const spawn = require('child_process').spawnSync;
   UI.info(`Auto-relaunching via npx baldart@${info.latest}…`);
@@ -466,7 +488,30 @@ async function maybeRelaunchUnderLatest(options) {
   process.exit(res.status || 0);
 }
 
-async function update(options = {}) {
+// Helpful terminal error when an unknown flag reached this CLI and a relaunch
+// under a newer version was not possible (already on latest / offline / opted
+// out, or we ARE the relaunched child). Replaces commander's cryptic
+// `error: unknown option` with actionable guidance. (v3.35.2+)
+function failOnUnknownArgs(unknownArgs, options) {
+  const tokens = unknownArgs.filter((a) => typeof a === 'string');
+  const firstOpt = tokens.find((a) => a.startsWith('-')) || tokens[0] || '(unknown)';
+  // In the relaunched child we are already on @latest, so "upgrade" is wrong —
+  // an unknown flag here means a genuine typo.
+  const alreadyLatest = process.env.BALDART_RELAUNCHED === '1';
+  const reason = alreadyLatest
+    ? `Unknown option ${firstOpt}. Even the latest CLI does not recognize it — check for a typo.`
+    : `Unknown option ${firstOpt}. If it is a recently-added flag, upgrade with \`npm i -g baldart@latest\`; otherwise check for a typo.`;
+  if (options.json === true) {
+    emitUpdateJson({ ok: false, action: 'usage-error', reason }, 2);
+  }
+  UI.error(reason);
+  if (!alreadyLatest) {
+    UI.info(`Then retry: npx baldart update ${tokens.join(' ')}`.trim());
+  }
+  process.exit(2);
+}
+
+async function update(options = {}, unknownArgs = []) {
   const git = new GitUtils();
   const symlinks = new SymlinkUtils();
   const repo = 'antbald/BALDART'; // Default repo
@@ -478,13 +523,35 @@ async function update(options = {}) {
   const autoStash = autoYes || options.autoStash === true;
   const confirm = async (msg, def = true) => (autoYes ? def : UI.confirm(msg, def));
 
+  // Arm machine-readable mode FIRST (v3.35.2+). The unknown-flag handling below
+  // can emit human lines (relaunch notice / helpful error); they must route to
+  // STDERR before anything reaches STDOUT, or a `--json --yes --new-flag` run
+  // would pollute the single-object stdout contract.
+  JSON_MODE = options.json === true;
+  if (JSON_MODE) UI.setJsonMode(true);
+
+  // Unknown-flag self-upgrade (v3.35.2+). Commander now parses `update`
+  // permissively (see bin/baldart.js), so a flag this CLI doesn't know lands
+  // in `unknownArgs` instead of crashing the parser. That flag was almost
+  // certainly introduced in a newer release — transparently relaunch under
+  // `npx baldart@latest`, forwarding the RAW argv (the unknown token never made
+  // it into `options`, so only raw argv carries it). If we can't relaunch
+  // (already latest / offline / opted out / we ARE the child), fail with an
+  // actionable message instead of a cryptic crash.
+  if (Array.isArray(unknownArgs) && unknownArgs.length > 0) {
+    // process.argv = [node, baldart, 'update', ...flags] — drop the first 3 so
+    // the child isn't spawned as `update update …` (it already gets 'update').
+    const rawArgs = process.argv.slice(3);
+    await maybeRelaunchUnderLatest(options, { rawArgs, unknown: true });
+    // Relaunch did not happen → this (latest-or-offline) CLI can't honor it.
+    failOnUnknownArgs(unknownArgs, options);
+  }
+
   // Machine-readable mode (v3.32.0+). Must be fully non-interactive: --json
   // requires --yes (so no UI.select/confirm can block) and rejects --reset
   // (the nuclear path is a deliberate destructive human escape hatch, not an
   // agent flow — see the autonomous /baldart-update skill, which never resets).
-  JSON_MODE = options.json === true;
   if (JSON_MODE) {
-    UI.setJsonMode(true);
     if (options.reset === true) {
       emitUpdateJson({ ok: false, action: 'usage-error',
         reason: '--json does not support --reset. Reset is an interactive destructive escape hatch; run it manually.' }, 2);