bug(cli): npm upgrade to @stackbilt/cli@1.0.0 can require --legacy-peer-deps

[stackbilt-admin]

Summary

Upgrading to @stackbilt/cli@1.0.0 can fail under npm's peer resolver in real apps unless users pass --legacy-peer-deps.

Repro

In opsbrain repo:

1. Existing stack includes agents@0.12.3 and zod@^3.22.0.
2. Run: npm install --save-dev @stackbilt/cli@1.0.0
3. npm fails with ERESOLVE peer conflict involving agents peer zod@^4.0.0 and a zod v3-resolved tree.

Workaround

npm install --save-dev @stackbilt/cli@1.0.0 --legacy-peer-deps

Why this matters

This creates upgrade friction and can look like Charter itself is incompatible with existing app stacks, even when runtime behavior is fine after install.

Expected

• Either clean install path without --legacy-peer-deps, or
• Clear documented upgrade guidance for npm users when this conflict pattern exists.

Potential fixes

• Review/transitively constrain peer dependency surface that triggers npm strict resolution conflicts.
• Add release note / docs section with explicit npm upgrade command + explanation.