release: v0.3.0 — promote rc.1 to @latest

[kokevidaurre]

Summary

Promotes 0.3.0-rc.1 (published on @next since 2026-04-24) to the stable 0.3.0 release.

After merge, tag v0.3.0 triggers release.yml → publishes to @latest via OIDC trusted publishing.

Changes

• package.json: 0.3.0-rc.1 → 0.3.0
• package-lock.json: synced

v0.3.0 highlights (since 0.2.2)

• Run engine rewrite, conversation protocol (agents talk + use tools)
• New commands: review, credentials, goals, log
• Project-level config system (.squads/config.yml)
• Role-based timeouts + anti-collision in org runs
• PreToolUse guardrail hooks
• OIDC trusted publishing (no more NPM_TOKEN)
• Audit remediation: no hardcoded values, extracted prompts, parameterized config

Post-merge steps

git checkout main && git pull
git tag v0.3.0
git push origin v0.3.0   # release.yml publishes to @latest

Test plan

• CI green on release branch
• rc.1 burn-in completed on @next (24+ hours)
• Tested npm i -g squads-cli@next on Mac
• Tested on Windows

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gemini-code-assist]

Code Review

This pull request updates the version of the squads-cli package from 0.3.0-rc.1 to 0.3.0 in both package.json and package-lock.json. I have no feedback to provide.