chore: release main

[github-actions]

🤖 I have created a release beep boop

compound-engineering: 3.14.0

3.14.0 (2026-06-23)

Features

• antigravity: replace retired Gemini CLI target with Antigravity (agy) (#978) (16442e8)
• ce-brainstorm: add visual feedback to brainstorming process (#962) (9be868d)

Bug Fixes

• ce-brainstorm: make visual-probe gate fire reliably before first shape decision (#964) (c759a26)
• ce-code-review: annotate model tier in Stage 3 team announce; read it at Stage 4 dispatch (#979) (ff6e26e)
• ce-compound: add Pi session history support (#974) (ea389f9)
• ce-plan: capability-based tracker access + reference conventions from context (#971) (4ebd867)
• ce-work-beta: thread Execution note into Codex delegation prompt (#976) (6d5cb5c)
• Codex marketplace install (#973) (8581289)
• harden simplification safety and add review deletion signal (#969) (06e2eb0)
• opencode: generate slash-command stubs for each skill (#977) (46352ac)
• release: include refactors in release notes (#970) (ded28b0)

Refactoring

• plugin: make plugin skills-only and root-native (#967) (02b72bc)

---

This PR was generated with Release Please. See documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4ad1d68b53

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep the OpenCode release pin in sync

After this release bump to 3.14.0, the pinned OpenCode install example still uses compound-engineering-v3.13.1 in .opencode/INSTALL.md:17. Users who follow the documented pinned-install path for this release will install the previous tag and miss the 3.14.0 fixes/features; update that tag alongside the release version or make the example intentionally versionless.

Useful? React with 👍 / 👎.