baldart 4.58.0 → 4.59.0

package/framework/templates/baldart.config.template.yml

@@ -410,6 +410,17 @@ git:
   # worktree-isolated and respect the terminal-isolation rule.
   merge_strategy: pr
 
+  # Auto-deploy allowlist (since v4.59.0). Bounds what the `/new` `-auto-ship`
+  # autonomous mode may execute as an OUTWARD/IRREVERSIBLE action (remote schema
+  # deploy, env/feature-flag writes, etc.). A list of deploy targets/intents the
+  # orchestrator is authorized to run unattended; default empty = NOTHING
+  # auto-deploys (bare `-auto` ships nothing outward — outward actions defer to a
+  # follow-up card). This is layered ON TOP of `stack.schema_deploy_from_trunk_only`,
+  # which remains a hard branch floor — the allowlist authorizes WHAT may ship, the
+  # trunk-only invariant still constrains FROM WHERE. Free-form labels matched by
+  # the production-readiness gate, e.g. ["supabase-db-push", "vercel-prod"].
+  auto_deploy: []
+
 # ─── TOOLS ───────────────────────────────────────────────────────────────
 # Which AI CLI tools should the framework target on this machine?
 # Each enabled tool gets its own per-item skill symlinks pointing at the

package/package.json

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

package/src/commands/configure.js

@@ -663,6 +663,19 @@ async function interactivePrompts(merged, detected) {
     UI.warning('You picked `local-push` but develop appears protected on origin — pushes will be rejected. Switch back to `pr` if it fails.');
   }
 
+  // ---- Auto-deploy allowlist (since v4.59.0) ----------------------------
+  // Bounds what `/new -auto-ship` may execute as an OUTWARD action. Empty =
+  // nothing auto-deploys (safe default). Layered ON TOP of
+  // stack.schema_deploy_from_trunk_only, which stays a hard branch floor.
+  const currentAutoDeploy = Array.isArray(merged.git.auto_deploy) ? merged.git.auto_deploy : [];
+  const autoDeployAnswer = (await UI.input(
+    `Auto-deploy allowlist for \`/new -auto-ship\` (comma-separated deploy targets/intents; blank = none) (current: ${currentAutoDeploy.join(', ') || '—'})`,
+    currentAutoDeploy.join(', ')
+  )).trim();
+  merged.git.auto_deploy = autoDeployAnswer
+    ? autoDeployAnswer.split(',').map((s) => s.trim()).filter(Boolean)
+    : [];
+
   UI.section('Features (explicit yes/no — option A: always ask)');
   for (const flag of [
     ['has_design_system', 'Project has a documented design system?'],

package/src/commands/doctor.js

@@ -464,6 +464,21 @@ async function detectState(cwd, opts = {}) {
       }
     } catch (_) { /* never block doctor on i18n probe */ }
 
+    // ---- Auto-deploy allowlist presence (since v4.59.0) ----------------
+    // Purely informational: git.auto_deploy bounds what `/new -auto-ship`
+    // may execute as an OUTWARD action. An empty allowlist is the SAFE
+    // default (nothing auto-deploys), so this is only worth noting — never
+    // a fix. Surfaced so a user who relies on `-auto-ship` knows whether the
+    // gate is open. Empty/unset = closed (the common, safe case).
+    state.autoDeployConfigured = false;
+    try {
+      if (config && !config.__malformed && config.git
+        && Array.isArray(config.git.auto_deploy) && config.git.auto_deploy.length > 0) {
+        state.autoDeployConfigured = true;
+        state.autoDeployTargets = config.git.auto_deploy.slice();
+      }
+    } catch (_) { /* never block doctor on auto_deploy probe */ }
+
     // ---- External-tool version currency (since v4.38.0) ----------------
     // BALDART pins none of the external tools it installs (graphifyy via pipx,
     // language servers via npm/system) — pipx/npm never auto-upgrade, so a
@@ -983,6 +998,24 @@ function planActions(state) {
     });
   }
 
+  // Auto-deploy allowlist (since v4.59.0). Advisory print-only — surfaced ONLY
+  // when the allowlist is non-empty (the safe default of empty/unset opens
+  // nothing, so it warrants no nag). Reminds the user that `/new -auto-ship`
+  // may execute the listed OUTWARD targets unattended. Never a fix; safe in
+  // --auto since run() only prints. The trunk-only branch floor still applies.
+  if (state.autoDeployConfigured) {
+    actions.push({
+      key: 'auto-deploy-allowlist',
+      label: `Auto-deploy allowlist active: ${state.autoDeployTargets.join(', ')}`,
+      why: `git.auto_deploy authorizes \`/new -auto-ship\` to auto-execute these OUTWARD deploy targets unattended. Only relevant when you run with -auto-ship; otherwise nothing auto-deploys. stack.schema_deploy_from_trunk_only still constrains FROM WHERE a schema deploy may run. Empty the list in baldart.config.yml to close the gate.`,
+      autoOk: true, // advisory print-only; run() does NOT mutate config
+      run: () => {
+        UI.info(`git.auto_deploy = [${state.autoDeployTargets.join(', ')}] — \`/new -auto-ship\` may auto-execute these targets.`);
+        UI.info('Empty `git.auto_deploy` in baldart.config.yml to disable all unattended deploys.');
+      },
+    });
+  }
+
   // External-tool version currency (since v4.38.0). One non-blocking upgrade
   // action per managed tool confirmed behind upstream — the tool-dependency
   // analogue of the `baldart` CLI's own UpdateNotifier. `unknown`/`current`

package/src/commands/update.js

@@ -1283,6 +1283,9 @@ async function update(options = {}, unknownArgs = []) {
               .filter((k) => !(k in (cur2.features || {})));
             const missingPaths = Object.keys(tpl.paths || {})
               .filter((k) => !(k in (cur2.paths || {})));
+            // `git.*` has no type filter — ALL new keys surface regardless of
+            // type, so scalars (trunk_branch, merge_strategy) AND ARRAYS
+            // (git.auto_deploy, the allowlist since v4.59.0) are both caught.
             const missingGit = Object.keys(tpl.git || {})
               .filter((k) => !(k in (cur2.git || {})));
             // Scalar top-level stack.* keys — e.g. stack.database,