[release] v2.7.0

[realproject7]

EPIC Context

• Parent: none — standalone release bump
• Epic goal: Standalone v2.7.0 release bump to ship the feature merged since v2.6.0.
• This ticket's role: Bump package versions from 2.6.0 to 2.7.0 and release the Add GPT-5.6 Sol/Terra/Luna to the codex model dropdown #999 GPT-5.6 Codex model dropdown addition.
• Depends on: Add GPT-5.6 Sol/Terra/Luna to the codex model dropdown #999 Enables: v2.7.0 GitHub release after merge; npm publish remains an operator gate
• Contracts to respect/expose: Version string only in package.json and package-lock.json; package root and lockfile root/packages."" versions must all be 2.7.0; no source or dependency changes.
• Out of scope here (later tickets): npm publish and upgrade rollout are operator-gated post-merge steps — do not perform them in this ticket.

Release v2.7.0

Version bump 2.6.0 → 2.7.0 (minor). Ships the feature merged since v2.6.0.

Included since v2.6.0

• Add GPT-5.6 Sol/Terra/Luna to the codex model dropdown #999 — Add GPT-5.6 Sol/Terra/Luna to the codex model dropdown (PR [#999] Add GPT-5.6 Sol/Terra/Luna to codex model dropdown #1000, merged f280d57).

Scope

• package.json + package-lock.json version string only (npm version 2.7.0 --no-git-tag-version). No source changes.

Process (standard QuadWork release flow)

1. PO creates branch task/<this-issue>-release-v2-7-0, bumps version, opens PR (operator-authored, like Release v2.6.0 — folded + operational improvements #997/[#997] 2.6.0 #998).
2. @dev is review driver (no code); @re1 + @re2 review; after both APPROVE + CI green, @Head merges.
3. PO runs gh release create v2.7.0 --target main --generate-notes.
4. STOP at npm publish — operator gate. VPS/local global upgrade follows only after the operator publishes.

Acceptance criteria

• package.json version === 2.7.0; package-lock.json root + packages."" version === 2.7.0.
• No non-version diff in the PR.
• Full CI suite green (prepublishOnly gate).