chore: pin next release to 3.0.2 (#665)
PR #663 squash-merged as `feat(ce-commit-push-pr):` — adding two short-circuits that skip a blocking prompt when the agent just authored the change. The intent was a UX/flow fix, not a new capability, so the correct conventional prefix is `fix:`. Since the prefix drove a minor bump, the open release PR (#661) is pinning the linked `cli` / `compound-engineering` group at 3.1.0. This empty commit reclassifies the pending release to 3.0.2 via `Release-As:` footers so the patch-level fixes in this window (#660 ce-update, #664 ce-demo-reel, #663 ce-commit-push-pr) land as 3.0.2 instead of 3.1.0. The feat prefix remains in history and may still render under a Features heading in the generated changelog — hand-edit the release PR body before merge if so. Release-As: cli@3.0.2 Release-As: compound-engineering@3.0.2
This commit is contained in: