fix(cli): parse kebab-case flags (--dry-run) instead of silently ignoring them

[MasonStation]

Problem

stack add <provider> --dry-run (the documented "safe, no-op preview" form) was silently ignored and ran the real provisioning flow — live OAuth / network calls / Phantom vault writes — instead of printing the preview. --dryRun (camelCase) worked; --dry-run (kebab, the form in README/--help/docs) did not.

Root cause

citty 0.1.6 maps kebab CLI tokens onto camelCase arg keys through a Proxy whose fallback uses ??:

get(target, prop) { return target[prop] ?? target[camelCase(prop)] ?? target[kebabCase(prop)]; }

A boolean arg with default: false gets out.dryRun = false populated by citty's defaults pass, so false ?? … short-circuits and the kebab-parsed out["dry-run"] = true is never consulted. Net: --dry-run → dryRun = false → skips the dry-run branch → real addService → provider.login().

Fix

Normalize raw argv (--dry-run → --dryRun) before citty parses it, in packages/cli/src/lib/normalize-args.ts, applied once in index.ts. One change fixes every command:

• --dry-run on add, init, import, swap, upgrade
• --all-orphans, --keep-remote, --keep-from, --continue-on-error, --recipe-id

Deliberately left untouched (so existing behavior is preserved):

• camelCase spellings (--dryRun) — still work.
• --no-* tokens — citty's negation, which is the disable path for the only default-true boolean (templates apply --continue-on-error).
• Everything after a bare -- — stack exec passthrough.
• Flag values — only the name before = is rewritten, so --region=us-east-1 is safe.

Tests

• normalize-args.test.ts — 9 parser-level unit tests (kebab→camel, 3-word flags, =value preserved, hyphenated values not dragged in, --no-* left alone, -- passthrough).
• add-dry-run.test.ts — 3 integration tests: --dry-run prints the preview and never hits SUPABASE_STACK_CLIENT_ID (real login()); --dryRun regression guard; no-flag guard (preview is opt-in).

All pass. Full CLI suite green except one pre-existing, unrelated Windows path-separator assertion in recommend.test.ts (confirmed failing on main).

Known limitation (not addressed here)

The positive noWire/noProvision/noInteractive/noRollback flags are a different mechanism: kebab --no-wire hits citty's negation branch (sets an unused wire=false), so it can't set the positive flag via any alias — even in newer citty. The canonical documented form --noWire (used by the MCP server and generated CLI ref) works and is unchanged. Fixing --no-wire cleanly means renaming these to positive flags (wire, default true) across add/apply/init/swap + the MCP server — out of scope for this patch.

Version

Bumps VERSION to 0.2.1 (the constant in index.ts is not auto-bumped by scripts/publish.sh, so the compiled binary would otherwise report the wrong version).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ashlr-stack	Ready	Preview, Comment	Jun 10, 2026 4:06am