chore(main): release 2.6.1

[chrischall]

🤖 I have created a release beep boop

2.6.1 (2026-09-08)

Bug Fixes

• extension: deliver the pair code from the value in hand, and say when it cannot (#306) (4c7695b)

---

This PR was generated with Release Please. See documentation.

[claude]

Reviewed this as the standard release-please automation output: the chore(main): release 2.6.1 PR plus the bot's cross-package dep-sync commit.

Checked:

• Every path listed in release-please-config.json's extra-files (bootstrap, cli package.json + src/version.ts, extension-chrome package.json + manifest.json, extension-core, protocol, server, test-helpers) is bumped 2.6.0 → 2.6.1, matching the "all packages share one version" lockstep convention.
• Cross-workspace @fetchproxy/* deps use caret ranges (^2.6.1), consistent with "always caret ... literals get left behind."
• grep -rn '"2\.6\.0"' across the tree (excluding node_modules) returns nothing — no stray unbumped version references.
• CHANGELOG entry correctly reflects the merged fix (fix(extension): deliver the pair code from the value in hand, and say when it cannot #306).

No hand-written logic to review here — purely mechanical, matches the documented release flow. No issues found.

Verdict: pass

[github-actions]

✅ Auto-review verdict: pass — Automated release-please version-bump PR (2.6.0 → 2.6.1) plus its cross-package dep-sync commit; all extra-files entries and caret ranges are bumped consistently with no stray leftovers. No issues found.

[chrischall]

🤖 Created releases:

• v2.6.1

🌻