[steipete]

Prepare 0.26.0 with complete browser-chat context, whisper.cpp environment and timestamp fixes, direct-media handling, explicit Antigravity model selection, and stabilized security/dependency updates. The new model-selector form makes this a minor release.

Keep all 13 existing unreleased changelog bullets and contributor credits, add the release highlights and date, synchronize CLI/core/Bun versions, and restore the next empty Unreleased section. Chrome Web Store submission remains pending sign-in; this release publishes the CLI/npm channels and downloadable extension archives.

Validation: all changelog bullets preserved verbatim, version metadata synchronized, and independent review found no actionable P0–P2 issues. Full CI and the signed/notarized release dry run must pass before tagging.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-05T21:47:02.351013Z	92499ee	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[clawsweeper]

Codex review: blocked before merge.

What this changes

This PR prepares version 0.26.0 across the CLI, core library, standalone fallback, changelog, and release instructions.

Example: A standalone binary uses its fallback version.

• Before: It identifies itself as 0.25.3.
• After: It identifies itself as 0.26.0.

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	Focused, consistent release preparation with passing reported checks and no actionable introduced defect.
Proof confidence	🌊 off-meta tidepool	Not applicable: This owner-authored release metadata change is outside the ordinary contributor proof gate; source inspection verifies consistency, while CI supports validation without proving publication.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The accumulated changes need a coherent version and release notes across distribution channels.
Reason: The repository owner explicitly selected this release direction, and the patch performs the necessary preparation without expanding scope.

Merge readiness

⛔ Blocked before merge - 1 item remains

Keep open: this maintainer-authored release preparation synchronizes versions and preserves the changelog without introducing a correctness defect.

Priority: P3
Reviewed head: 92499ee522bf0e21d9c0816930971b297a91a534

Before merge

• Await maintainer action - The release owner must submit the matching 0.26.0 Chrome extension with automatic publishing and verify its exact pending or published version before release closeout.

Findings

None.

Agent review details

How this fits together

Package manifests and the standalone fallback supply release versions to npm packages, CLI output, browser extension builds, and release artifacts.

flowchart LR
  A[Package manifests] --> B[CLI and core packages]
  A --> C[Browser extension build]
  D[Standalone fallback] --> E[Bun binary]
  F[Changelog] --> G[Release notes]

Loading

Technical review

Best possible solution:

Merge the consistent release metadata and complete the documented validation, publication, and Chrome Web Store submission sequence.

Do we have a high-confidence way to reproduce the issue?

No bug reproduction is applicable; source inspection confirms the version changes and preservation of the pending release notes.

Is this the best way to solve the issue?

The patch follows the existing three-source version contract and uses the existing release machinery without adding another path.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 7c2a1536e8fc.

Provenance checked

• CLI, core, and standalone version sources keeps the original intent (24e2250: The previous release preparation synchronized the same three version sources; this PR retains that contract.)
• Release validation instructions keeps the original intent (24e2250: The documented dry run validates the current version without publication; only its version argument changes.)
• Pending changelog entries keeps the original intent (7c2a153: Accumulated merged changes were recorded for the next release; all existing bullet text and credits are retained.)

Testing

Proof path: unit tests only.

Security

None.

Evidence

What I checked:

• Focused release preparation: The pinned introduction diff changes only release notes, release instructions, two package versions, and the standalone fallback; all three version sources become 0.26.0. (src/version.ts:7, 92499ee522bf)
• Changelog preservation: The release section preserves all 13 existing bullets and contributor credits, reorders them, adds highlights and a date, and opens the next Unreleased section. (CHANGELOG.md:3, 92499ee522bf)
• Applicable release policy: The complete root policy requires lockstep versions and matching Chrome Web Store submission; the release checklist places submission after publication and requires it before closeout. (AGENTS.md:14, 92499ee522bf)
• Owner direction and release sequencing: The owner-authored body approves the minor release and acknowledges pending Chrome Web Store sign-in; that acknowledgment does not complete the mandatory submission gate. (92499ee522bf)
• Checks and discussion: All five reported checks succeeded; the complete discussion contains no changed-behavior demonstration or additional owner decision. (92499ee522bf)
• Release ownership history: Feature-history searches identify Peter Steinberger across the original standalone version mechanism, lockstep release documentation, trusted publishing work, and successive release preparations, including chore(release): prepare 0.25.3 #536. (RELEASING.md:18, 7c2a1536e8fc)

Likely related people:

• Peter Steinberger: Raw commit 9756603 adds RELEASING.md:8 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 975660340ba1; files: RELEASING.md)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

• add P3: This is focused release metadata and documentation maintenance with no introduced runtime defect.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: ⏳ waiting on maintainer: Only explicit maintainer approvals or decisions remain; merge is still blocked.

Label justifications:

• P3: This is focused release metadata and documentation maintenance with no introduced runtime defect.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: ⏳ waiting on maintainer: Only explicit maintainer approvals or decisions remain; merge is still blocked.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 5, 2026, 4:58 PM ET / 21:58 UTC.