chore(release): prepare v0.9.13 by Hmbown · Pull Request #6000 · Hmbown/Codewhale

Hmbown · 2026-09-07T14:35:59Z

No-Issue: release preparation (docs/RELEASE_CHECKLIST.md)

Version bumps to 0.9.13 across the workspace, npm packages, VS Code extension, and facts surfaces; CHANGELOG 0.9.13 section with the missing #5989 receipts (ACP schema, queue data loss, metrics, goal-loop), the truncated-tool-args fix, the paste regression fix, allow_insecure_http, and the Computer Use 0.2.0 bundle refresh; contributor credits (@nsfoxer, @Nefelibata1024, @Gabriel-Degret, @Lujc0523, @gaord, @goransh-walia); compare link.

Headline fixes in this release: 0.9.12's multiline-paste regression (#5981), the ACP initialize schema violation that broke JetBrains (#5969), concurrent-instance queue data loss, truncated tool arguments being executed (#5986), and the dropped allow_insecure_http provider key (#5991). Computer Use ships as a bundled default plugin option at plugin 0.2.0.

check-versions: OK (workspace/npm/npm-binary/lockfile = 0.9.13). Feature release-note receipts: 15 OK.

After this merges, remaining steps are founder-only per the checklist: tag v0.9.13, release workflow, notarized assets, npm/crates publish, runtime-providers.json regen.

Note

Low Risk
Version and documentation-only changes; runtime behavior is whatever already landed on main—the PR does not modify core logic in the shown diff.

Overview
This PR cuts the v0.9.13 release by bumping 0.9.12 → 0.9.13 across the Rust workspace, Cargo.lock, npm packages, the VS Code extension, and internal path dependency pins—without touching application .rs sources in this diff.

It writes the 0.9.13 ship narrative in CHANGELOG.md (and the mirrored crates/tui/CHANGELOG.md): integrity fixes called out in the PR (multiline paste, ACP initialize schema, per-session offline queues, truncated tool-arg fail-closed, codewhale metrics paths, goal-loop stall bounds, fleet role fail-closed, allow_insecure_http, Computer Use bundle 0.2.0), plus contributor credits, upgrade notes, and the v0.9.12…v0.9.13 compare link.

Public surfaces stay aligned: install/docs version strings, docs/CONTRIBUTORS.md, docs/public-surface-facts.json, generated web changelog/facts, telemetry trust copy (EN/ZH), web/lib/release-credits.ts required credits for this candidate, and the remote-smoke default RELEASE_TAG.

^{Reviewed by Cursor Bugbot for commit 8f5da80. Bugbot is set up for automated code reviews on this repo. Configure here.}

chatgpt-codex-connector · 2026-09-07T14:36:05Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

cursor · 2026-09-07T14:36:14Z

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_e99bba36-32d3-48c6-9dfe-c2d2146c670a)

cursor · 2026-09-07T14:36:56Z

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4196d9d5-1191-4e2f-b257-002630a9ca1b)

claude · 2026-09-07T14:37:00Z

Claude finished @Hmbown's task in 3m 8s —— View job

Claude finished the review

Todo list

Gather context (PR body, diff, changed files)
Understand request (review this release-prep PR per repo custom instructions)
Review CHANGELOG.md / crates/tui/CHANGELOG.md content
Review version bump consistency across workspace/npm/vscode/facts
Check for correctness bugs, provider/model safety issues, reuse/dead code, tests, security
Post final review

Summary

This is a mechanical release-prep PR (no runtime logic changes) and it's mostly clean: Cargo.lock/Cargo.toml version + path-dependency-pin bumps to 0.9.13 are consistent across every workspace crate, npm packages, the VS Code extension, and web/lib/facts.generated.ts. The CHANGELOG.md / crates/tui/CHANGELOG.md content lines up (same new ## [0.9.13] section, Thanks block, and compare link in both). No provider/model-routing code is touched, so the EPIC #2608 invariant doesn't apply here.

🔴 One real issue: stale generated changelog will fail its own drift-gate test

web/lib/changelog.generated.ts is derived from CHANGELOG.md via node web/scripts/derive-changelog.mjs (run as part of npm run prebuild, alongside derive-facts.mjs). This PR regenerated web/lib/facts.generated.ts (version bumped to "0.9.13") but did not regenerate web/lib/changelog.generated.ts, even though CHANGELOG.md gained a whole new ## [0.9.13] release section.

Concretely, web/lib/changelog.generated.ts still has (unchanged by this PR):

{
  "version": "Unreleased",
  ...
  "compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD",
  ...
},
{
  "version": "0.9.12",
  "date": "2026-09-03",
  ...

i.e. all the content that this PR moved out of "Unreleased" and into "0.9.13" in CHANGELOG.md is still sitting under the stale "Unreleased" entry here.

This isn't just cosmetic — web/lib/changelog.test.ts (the "drift gate", per its own header comment) has two assertions that will now fail:

renderChangelogModule(parseChangelog(CHANGELOG.md)) must byte-for-byte equal the committed changelog.generated.ts — it won't, since the source changed and the generated file didn't.
expect(CHANGELOG[1].version).toBe(FACTS.version) — FACTS.version is now "0.9.13" (correctly bumped), but CHANGELOG.generated.ts[1].version is still "0.9.12".

Fix: run npm run prebuild (or node web/scripts/derive-changelog.mjs) inside web/ and commit the resulting web/lib/changelog.generated.ts.

Fix this →

Minor / nit

CHANGELOG.md and crates/tui/CHANGELOG.md both have a double blank line between ## [0.9.13] - 2026-09-07 and the first ### Fixed heading — harmless but inconsistent with the rest of the file's single-blank-line spacing.
scripts/remote-smoke/setup-vm.sh now defaults RELEASE_TAG to v0.9.13, which doesn't exist as a published tag/release yet (tagging is called out as a founder-only follow-up step). This is fine as long as nobody runs the smoke script with the default before the tag is actually pushed — worth a one-line note if that's not already understood by whoever runs it.

Good choices

Version bumps are fully consistent across Cargo.toml/Cargo.lock, all path-dependency pins ({ path = "...", version = "..." }), npm packages, and the VS Code extension — no strays left at 0.9.12.
docs/public-surface-facts.json correctly leaves latestPublishedRelease at v0.9.12 (unpublished 0.9.13 shouldn't be advertised as released yet) while sourceCandidate.version moves to 0.9.13.
Dropping the duplicated 0.8.67 history from crates/tui/CHANGELOG.md in favor of pointing at the root changelog/archive is a reasonable dedup, and the content that moved matches verbatim.

Copilot

🔵 Needs a closer look

The root CHANGELOG [Unreleased] compare link wasn’t advanced to start from v0.9.13, so it will include already-released commits in the Unreleased diff.

Pull request overview

This PR prepares the v0.9.13 release by bumping versions across the Rust workspace and npm/VS Code packages, updating generated “facts” surfaces, updating the remote-smoke default release tag, and adding the 0.9.13 release notes + credits to the changelogs.

Changes:

Bump workspace crate versions and path-dependency pins to 0.9.13 (including Cargo.lock).
Bump npm packages / VS Code extension versions to 0.9.13 (and lockfiles).
Add 0.9.13 sections to changelogs and refresh generated/public facts surfaces.

File summaries

File	Description
web/lib/facts.generated.ts	Updates generated repo facts timestamp/version to `0.9.13`.
scripts/remote-smoke/setup-vm.sh	Advances default `RELEASE_TAG` to `v0.9.13`.
package-lock.json	Updates workspace npm package versions to `0.9.13`.
npm/runtime-sdk/package.json	Bumps `@codewhale/runtime-sdk` to `0.9.13`.
npm/codewhale/package.json	Bumps `codewhale` + `codewhaleBinaryVersion` to `0.9.13`.
extensions/vscode/package.json	Bumps VS Code extension version to `0.9.13`.
extensions/vscode/package-lock.json	Updates VS Code extension lockfile version to `0.9.13`.
docs/public-surface-facts.json	Updates public surface facts `version` to `0.9.13`.
crates/tui/CHANGELOG.md	Adds `0.9.13` notes/credits; trims duplicated older history.
crates/tui/Cargo.toml	Updates crate dependency pin versions to `0.9.13`.
crates/tools/Cargo.toml	Updates `codewhale-protocol` pin to `0.9.13`.
crates/telemetry/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/state/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/secrets/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/lane/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/hooks/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/execpolicy/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/core/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/config/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/command-contract/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/cli/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/app-server/Cargo.toml	Updates internal dependency pins to `0.9.13`.
crates/agent/Cargo.toml	Updates internal dependency pins to `0.9.13`.
CHANGELOG.md	Adds `0.9.13` notes/credits and a compare link.
Cargo.toml	Bumps workspace package version to `0.9.13`.
Cargo.lock	Updates locked crate versions to `0.9.13`.

Review details

Files not reviewed (1)

extensions/vscode/package-lock.json: Generated file

Suppressed comments (1)

CHANGELOG.md:8184

The bottom reference links should advance the [Unreleased] compare base to the new tag (v0.9.13) now that the 0.9.13 section and compare link are being added; otherwise the Unreleased link keeps including already-released commits from 0.9.12→0.9.13.

for the exact-alias-first slash-completion ordering idea in #1811, landed
with a focused regression test. Thanks to **Bevis** and the community reports

Files reviewed: 23/26 changed files
Comments generated: 0
Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

codewhale-agent

Codewhale review

Mechanical v0.9.13 release preparation: bumps workspace/npm/VS Code/facts versions, adds CHANGELOG 0.9.13 section and thanks, and removes an inlined TUI changelog history block in favor of the root archive. No application code or tests changed.

Findings

[WARNING] Unreleased compare link still points to v0.9.12 after adding the v0.9.13 section (CHANGELOG.md:8193)
The new [0.9.13] link is added, but the [Unreleased] link at the bottom of CHANGELOG.md still uses v0.9.12...HEAD. Once v0.9.13 is tagged, Unreleased should compare v0.9.13...HEAD; leaving v0.9.12 will show all 0.9.13 changes as unreleased while the Unreleased section is empty. The same pattern was correctly used for the new [0.9.13] link.
[INFO] Extra blank line between release header and first subsection (CHANGELOG.md:10)
Both CHANGELOG.md and crates/tui/CHANGELOG.md insert two blank lines between ## [0.9.13] - 2026-09-07 and ### Fixed. The rest of the changelog uses a single blank line between version headers and subsections.

Suggestions

CHANGELOG.md:8193 — Advance the Unreleased comparison base to the new version so the empty Unreleased section does not duplicate the v0.9.13 changes after the tag is created.
```
[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD
```

Assessment

Release preparation is mechanically complete and consistent across version surfaces. The only correctness-affecting release artifact is the Unreleased compare link, which should be advanced before or immediately after tagging v0.9.13.

Advisory review by Codewhale (codewhale review --pr 6000 --post, head 7c2efa5d127f80aa17070d5c0245721815c43307). Line-specific findings are also posted as inline review comments; mechanical fixes arrive as committable suggestions you can apply from the Files tab. CODEOWNERS approval still governs merge.

codewhale-agent · 2026-09-07T14:54:20Z

@@ -8144,6 +8191,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
 Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

 [Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD


[WARNING] Unreleased compare link still points to v0.9.12 after adding the v0.9.13 section

The new [0.9.13] link is added, but the [Unreleased] link at the bottom of CHANGELOG.md still uses v0.9.12...HEAD. Once v0.9.13 is tagged, Unreleased should compare v0.9.13...HEAD; leaving v0.9.12 will show all 0.9.13 changes as unreleased while the Unreleased section is empty. The same pattern was correctly used for the new [0.9.13] link.

codewhale-agent · 2026-09-07T14:54:20Z


 ## [Unreleased]

+## [0.9.13] - 2026-09-07


[INFO] Extra blank line between release header and first subsection

Both CHANGELOG.md and crates/tui/CHANGELOG.md insert two blank lines between ## [0.9.13] - 2026-09-07 and ### Fixed. The rest of the changelog uses a single blank line between version headers and subsections.

codewhale-agent · 2026-09-07T14:54:21Z

@@ -8144,6 +8191,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
 Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

 [Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD


Advance the Unreleased comparison base to the new version so the empty Unreleased section does not duplicate the v0.9.13 changes after the tag is created.

Suggested change

[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD

[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD

Version bumps across the workspace, npm packages, VS Code extension, and facts surfaces; CHANGELOG 0.9.13 section with the release narrative, the missing #5989 receipts (ACP schema, queue data loss, metrics, goal-loop), the truncated-tool-args fix, the paste regression fix, allow_insecure_http, the Computer Use 0.2.0 bundle refresh, an upgrade-notes subsection (re-trust Computer Use), and the 0.9.13 contributor ledger; derived web surfaces regenerated (changelog.generated, facts.generated, GT catalogs); contributor credits chain in parity (CHANGELOG ledger = website arrays = docs/CONTRIBUTORS.md band = facts requiredCandidateCredits); INSTALL.md and the trust/telemetry copy bumped to 0.9.13. Gates: web 407/407 (npm test); check:facts OK; check:locales OK; check-versions OK (workspace/npm/npm-binary/lockfile = 0.9.13); feature release-note receipts OK (15); prepare-release transaction completed. Signed-off-by: CodeWhale Bot <bot@codewhale.net>

cursor · 2026-09-07T14:58:20Z

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_792edc00-ad4b-4d13-bc67-4f1b4f0f5bbe)

claude · 2026-09-07T14:58:26Z

Claude finished @Hmbown's task in 2m 57s —— View job

Codewhale v0.9.13 release-prep review

Todo list

Gather context (PR body, diff, changed files, prior bot reviews)
Verify web/lib/changelog.generated.ts drift claim
Verify [Unreleased] compare link claim
Check version bump consistency across workspace/npm/vscode/facts
Check for correctness bugs, provider/model safety, reuse/dead code, tests, security
Post final review

Summary

This is a mechanical release-prep PR — no application/runtime code changed, only version surfaces, changelogs, and generated docs. No provider/model-routing code is touched, so the EPIC #2608 prefix-inference invariant doesn't apply.

Update on the earlier bot findings on this thread: the "Claude finished" review above flagged web/lib/changelog.generated.ts as stale relative to CHANGELOG.md. I re-checked against the current HEAD (7c2efa5/8f5da80) and that's no longer true — web/lib/changelog.generated.ts now correctly carries the 0.9.13 entry (CHANGELOG[1].version === "0.9.13" === FACTS.version, matching changelog.test.ts's drift-gate assertions), so this appears to have already been fixed in a later push to the branch. I wasn't able to execute vitest/npx in this sandbox to run the test directly, so this is a byte-level manual comparison of both files rather than a green CI run — worth a final npm run prebuild + npm test locally to be certain, but the content itself is in sync now.

🟡 Confirmed: `[Unreleased]` compare link still anchors to v0.9.12

CHANGELOG.md:8212 (and the mirrored crates/tui/CHANGELOG.md) still has:

[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD

Now that a [0.9.13] section exists, this should advance to v0.9.13...HEAD so the empty [Unreleased] section doesn't silently include all of 0.9.13's already-released commits once the tag lands. Both copilot-pull-request-reviewer and codewhale-agent flagged this independently and I agree it's real — low severity since it's inert until something is actually added under Unreleased, but cheap to fix now while touching this file.

Fix this →

🔵 Minor: stale version reference in a comment

web/lib/release-credits.ts:29 — the doc-comment above RELEASE_HELPERS still reads:

/**
 * Contributors who helped with reports, reproductions, and verification.
 * Each name points at a landed change in the 0.9.12 changelog.
 */

The array itself was correctly updated to the 0.9.13 helpers (@nsfoxer, @Nefelibata1024, @Gabriel-Degret, @Lujc0523, matching the new ### Contributors block in CHANGELOG.md:265-274), but the comment text wasn't bumped and now points readers at the wrong changelog section. Cosmetic, not worth blocking on.

Good choices

Version bumps are fully consistent: no stray 0.9.12 left in any Cargo.toml/Cargo.lock, npm packages, the VS Code extension, or docs/public-surface-facts.json / web/lib/facts.generated.ts.
The new CHANGELOG.md ### Contributors block and web/lib/release-credits.ts arrays are in parity (@gaord, @goransh-walia as contributors; @nsfoxer, @Nefelibata1024, @Gabriel-Degret, @Lujc0523 as helpers) — matches the PR description's credit list exactly.
docs/public-surface-facts.json correctly keeps latestPublishedRelease at v0.9.12 while sourceCandidate.version moves to 0.9.13, since 0.9.13 isn't tagged/published yet.
Dropping the duplicated [0.8.67]-and-earlier inline history from crates/tui/CHANGELOG.md in favor of the root changelog archive is a reasonable dedup; spot-checked the retained 0.9.13 section text is verbatim-identical between the root and TUI changelogs.

Not checked

I don't have permissions to run npm test / vitest / node scripts in this sandbox, so I could not execute the web/lib/changelog.test.ts drift-gate or check-versions/check:facts scripts directly — the assessment above is from manual/static comparison of the committed files. Recommend running those before merge if not already green in CI.

codewhale-agent

Codewhale review

Release-prep PR bumps 0.9.12 to 0.9.13 across Rust/npm/VSCode, updates changelogs and generated web facts. No runtime code changes. Review found stale changelog compare links, a likely accidental deletion from crates/tui changelog, and outdated install-doc version references.

Findings

[WARNING] Unreleased changelog compare link still points at v0.9.12 (CHANGELOG.md:8212)
After cutting v0.9.13, the [Unreleased] compare link should be v0.9.13...HEAD. It remains v0.9.12...HEAD, so the empty Unreleased section will show all v0.9.13 changes and duplicate the new release on the generated web changelog.
[WARNING] crates/tui/CHANGELOG.md deletes the v0.8.67 section (crates/tui/CHANGELOG.md:5289)
The diff removes the entire 0.8.67 release block from crates/tui/CHANGELOG.md while the root CHANGELOG retains it. This is not mentioned in the PR description and looks accidental or at least unexplained; verify whether the TUI changelog is intentionally dropping old entries.
[WARNING] INSTALL.md still refers to public latest v0.9.11 (docs/INSTALL.md:50)
The source candidate was bumped to 0.9.13, but the surrounding sentence still says public latest is v0.9.11, and a separate line still links 'latest stable v0.9.11'. Since v0.9.12 is already in the changelog, these are stale and user-facing.
[INFO] Stale release-credits comment says 0.9.12 (web/lib/release-credits.ts:29)
web/lib/release-credits.ts updated the contributor/helper lists for v0.9.13 but the comment above RELEASE_HELPERS still references the 0.9.12 changelog.

Suggestions

CHANGELOG.md:8212 — Point the Unreleased compare link at the new release tag to avoid duplicating 0.9.13 in the Unreleased view.
```
[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD
```
web/lib/changelog.generated.ts:28 — Keep the generated web changelog Unreleased compareUrl in sync with the source changelog.
```
    "compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD",
```
docs/INSTALL.md:50 — Update the public-latest sentinel to v0.9.12, otherwise the corrected source candidate contradicts the release it claims is public.
```
check: a newer development build is kept, including v0.9.13 when public latest
is v0.9.12. Use a separate directory for deliberate rollback.
```

docs/INSTALL.md:101 — Update the latest stable reference and release URL from v0.9.11 to v0.9.12.

As checked on 2026-09-04, [latest stable v0.9.12](https://github.com/Hmbown/CodeWhale/releases/tag/v0.9.12)

Assessment

Generally a clean release-prep diff. No runtime logic is touched. The main risks are documentation/link drift and an unexplained historical changelog deletion in the TUI changelog; these should be corrected before merging to keep release artifacts and web surfaces consistent.

Advisory review by Codewhale (codewhale review --pr 6000 --post, head 8f5da804a9e12e085e9f2769a91dfba44a71ae89). Line-specific findings are also posted as inline review comments; mechanical fixes arrive as committable suggestions you can apply from the Files tab. CODEOWNERS approval still governs merge.

codewhale-agent · 2026-09-07T15:13:53Z

@@ -8144,6 +8210,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
 Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

 [Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD


[WARNING] Unreleased changelog compare link still points at v0.9.12

After cutting v0.9.13, the [Unreleased] compare link should be v0.9.13...HEAD. It remains v0.9.12...HEAD, so the empty Unreleased section will show all v0.9.13 changes and duplicate the new release on the generated web changelog.

codewhale-agent · 2026-09-07T15:13:53Z

@@ -5221,313 +5287,6 @@ reproductions shaped v0.9.0:
  now map to Act + Full Access permissions via a compatibility shim and
  show a one-shot deprecation notice; removal is planned for 0.9.0.



[WARNING] crates/tui/CHANGELOG.md deletes the v0.8.67 section

The diff removes the entire 0.8.67 release block from crates/tui/CHANGELOG.md while the root CHANGELOG retains it. This is not mentioned in the PR description and looks accidental or at least unexplained; verify whether the TUI changelog is intentionally dropping old entries.

codewhale-agent · 2026-09-07T15:13:54Z

 manifest and binary must come from the same source, and checksum failure never
 permits replacement. An explicit version or mirror cannot bypass the version
-check: a newer development build is kept, including v0.9.12 when public latest
+check: a newer development build is kept, including v0.9.13 when public latest


[WARNING] INSTALL.md still refers to public latest v0.9.11

The source candidate was bumped to 0.9.13, but the surrounding sentence still says public latest is v0.9.11, and a separate line still links 'latest stable v0.9.11'. Since v0.9.12 is already in the changelog, these are stale and user-facing.

codewhale-agent · 2026-09-07T15:13:54Z


 /**
 * Contributors who helped with reports, reproductions, and verification.
 * Each name points at a landed change in the 0.9.12 changelog.


[INFO] Stale release-credits comment says 0.9.12

web/lib/release-credits.ts updated the contributor/helper lists for v0.9.13 but the comment above RELEASE_HELPERS still references the 0.9.12 changelog.

codewhale-agent · 2026-09-07T15:13:54Z

@@ -8144,6 +8210,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
 Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

 [Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD


Point the Unreleased compare link at the new release tag to avoid duplicating 0.9.13 in the Unreleased view.

Suggested change

[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD

[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD

codewhale-agent · 2026-09-07T15:13:54Z

@@ -26,23 +26,49 @@ export const CHANGELOG: ChangelogRelease[] = [
    "date": null,
    "unreleased": true,
    "compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD",


Keep the generated web changelog Unreleased compareUrl in sync with the source changelog.

Suggested change

"compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD",

"compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD",

codewhale-agent · 2026-09-07T15:13:54Z

+check: a newer development build is kept, including v0.9.13 when public latest
 is v0.9.11. Use a separate directory for deliberate rollback.


Update the public-latest sentinel to v0.9.12, otherwise the corrected source candidate contradicts the release it claims is public.

Suggested change

check: a newer development build is kept, including v0.9.13 when public latest

is v0.9.11. Use a separate directory for deliberate rollback.

check: a newer development build is kept, including v0.9.13 when public latest

is v0.9.12. Use a separate directory for deliberate rollback.

codewhale-agent · 2026-09-07T15:13:54Z

@@ -101,7 +101,7 @@ commands update their own copies, so verify PATH again afterward.
 As checked on 2026-09-04, [latest stable v0.9.11](https://github.com/Hmbown/CodeWhale/releases/tag/v0.9.11)


Update the latest stable reference and release URL from v0.9.11 to v0.9.12.

Suggested change

As checked on 2026-09-04, [latest stable v0.9.11](https://github.com/Hmbown/CodeWhale/releases/tag/v0.9.11)

As checked on 2026-09-04, [latest stable v0.9.12](https://github.com/Hmbown/CodeWhale/releases/tag/v0.9.12)

Main tip Lint was red: 424 allows vs a 420 ceiling after #6000. Five attributes were covering symbols that production and tests already call (entry_count, entry_index_for_tool, virtual_cell_count, SettingsPickerController::options, HookEvent::as_str). Remove them and lock the budget at 419.

Copilot AI lite review requested due to automatic review settings September 7, 2026 14:36

Copilot started reviewing on behalf of Hmbown September 7, 2026 14:36 View session

Hmbown force-pushed the chore/prepare-0.9.13 branch from c1428ec to 7c2efa5 Compare September 7, 2026 14:36

Hmbown enabled auto-merge September 7, 2026 14:36

Copilot AI reviewed Sep 7, 2026

View reviewed changes

codewhale-agent Bot reviewed Sep 7, 2026

View reviewed changes

Hmbown force-pushed the chore/prepare-0.9.13 branch from 7c2efa5 to 8f5da80 Compare September 7, 2026 14:58

codewhale-agent Bot reviewed Sep 7, 2026

View reviewed changes

Hmbown merged commit aedb88b into main Sep 7, 2026
38 checks passed

Hmbown deleted the chore/prepare-0.9.13 branch September 7, 2026 15:19

		@@ -8144,6 +8191,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
		Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

		[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD

		@@ -8144,6 +8210,7 @@ overflow report and `/theme` picker edge-wrapping patch in #1814.
		Older releases (v0.8.39 and earlier) are archived in [docs/CHANGELOG_ARCHIVE.md](docs/CHANGELOG_ARCHIVE.md).

		[Unreleased]: https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD

		@@ -5221,313 +5287,6 @@ reproductions shaped v0.9.0:
		now map to Act + Full Access permissions via a compatibility shim and
		show a one-shot deprecation notice; removal is planned for 0.9.0.

	"compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.12...HEAD",
	"compareUrl": "https://github.com/Hmbown/CodeWhale/compare/v0.9.13...HEAD",

		check: a newer development build is kept, including v0.9.13 when public latest
		is v0.9.11. Use a separate directory for deliberate rollback.

		@@ -101,7 +101,7 @@ commands update their own copies, so verify PATH again afterward.
		As checked on 2026-09-04, [latest stable v0.9.11](https://github.com/Hmbown/CodeWhale/releases/tag/v0.9.11)

Conversation

Hmbown commented Sep 7, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented Sep 7, 2026

Uh oh!

cursor Bot commented Sep 7, 2026

Bugbot couldn't run - usage limit reached

Uh oh!

cursor Bot commented Sep 7, 2026

Bugbot couldn't run - usage limit reached

Uh oh!

claude Bot commented Sep 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude finished the review

Summary

🔴 One real issue: stale generated changelog will fail its own drift-gate test

Minor / nit

Good choices

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🔵 Needs a closer look

Files not reviewed (1)

Suppressed comments (1)

Uh oh!

codewhale-agent Bot left a comment

Choose a reason for hiding this comment

Codewhale review

Findings

Suggestions

Assessment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot commented Sep 7, 2026

Bugbot couldn't run - usage limit reached

Uh oh!

claude Bot commented Sep 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codewhale v0.9.13 release-prep review

Summary

🟡 Confirmed: [Unreleased] compare link still anchors to v0.9.12

🔵 Minor: stale version reference in a comment

Good choices

Not checked

Uh oh!

codewhale-agent Bot left a comment

Choose a reason for hiding this comment

Codewhale review

Findings

Suggestions

Assessment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

codewhale-agent Bot Sep 7, 2026

Hmbown commented Sep 7, 2026 •

edited by cursor Bot

Loading

claude Bot commented Sep 7, 2026 •

edited

Loading

claude Bot commented Sep 7, 2026 •

edited

Loading

🟡 Confirmed: `[Unreleased]` compare link still anchors to v0.9.12