[github-actions]

What

Adds the newest kilo-mcp release sections to services/kilo-mcp/CHANGELOG.md.

Why

The kilo-mcp Release job published a release after a production deploy
changed the kilo-mcp bundle (run: https://github.com/Kilo-Org/cloud/actions/runs/42208645706). Main is protected, so the
sections reach main through this PR. Later releases add their sections
to this PR until it is merged.

What to do

1. Required checks show as pending: PRs opened with the default GITHUB_TOKEN
   do not trigger workflow runs. Close and reopen this PR to start CI.
2. Review and merge. Only services/kilo-mcp/CHANGELOG.md changed.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new ## 2026-11-06 (f56fd20) section is accurate and matches the tag's sole kilo-mcp change (#9997), but release 3bdfa87 still has no section, so the tag history remains one release ahead of services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	31	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between 3a0599f and fa32d6b

Verification Notes (click to expand)

• Head re-confirmed as 59979960c09c7bbd022cf2d7571a7ed16402cbf1 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md.
• Incremental delta versus 2963fe3e is the single top ## 2026-11-06 (f56fd20) section (lines 6-9). It pairs with tag kilo-mcp-release/2026-11-06-f56fd20 (annotated tag peeling to f56fd20b24, created 2026-11-06T11:21:15Z, newest tag, bundle c3f72a68… distinct from 5d8c3b1 at d765956d…).
• git log --reverse 5d8c3b1..f56fd20 -- services/kilo-mcp ':(exclude)services/kilo-mcp/CHANGELOG.md' returns exactly b437986848 feat(cloud-agent): delete sessions from history with resilient workspace cleanup (#9997), matching the new bullet verbatim. #9997 is not duplicated elsewhere in the file. Newest-first ordering is correct.
• Carried-forward finding re-verified at current HEAD: 91 kilo-mcp-release/* tags versus 90 ## <date> (<sha>) headings, and a plain-text search finds no 3bdfa87 or 9387 in the file, so 3bdfa87 remains the one tag without a section. fa32d6b..3bdfa87 still returns only 4f895c6293 (#9387) and 3bdfa87..3a0599f only 4bdfefc154 (#9399).
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 31 (subject_type line), so this carried-forward finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff (the catalog.json edit belongs to already-merged feat(cloud-agent): delete sessions from history with resilient workspace cleanup #9997), and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous Review Summaries (8 snapshots, latest commit 2963fe3)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 2963fe3)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new top section ## 2026-11-06 (5d8c3b1) correctly records release 5d8c3b1 and its shipped #9741 commit, but release 3bdfa87 still has no section, so the tag history remains one release ahead of services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	27	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between 3a0599f and fa32d6b

Verification Notes (click to expand)

• Head re-confirmed as 2963fe3e71df4eb8408fd6613bfdae71421ba9d9 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md.
• The previous review SHA 334edfa3 is an ancestor of the head, so the incremental diff was used. The new delta is the top ## 2026-11-06 (5d8c3b1) section.
• refs/tags/kilo-mcp-release/2026-11-06-5d8c3b1 is an annotated tag peeling to 5d8c3b1156c6b9d5f364c0b30353eef03ab39801, created 2026-11-06T10:57:41Z (newest release tag, after 4b2afd4 at 10:22:35Z), with bundle-sha256=d765956d… distinct from 4b2afd4 (3d266d68…), so the deployed bundle changed.
• git log --reverse 4b2afd4..5d8c3b1 -- services/kilo-mcp ':(exclude)services/kilo-mcp/CHANGELOG.md' returns exactly a3335846ca feat(cloud-agent): add built-in agent overrides (#9741), matching the new bullet and PR link verbatim. Newest-first ordering is correct.
• Structural check: 90 kilo-mcp-release/* tags versus 89 ## <date> (<sha>) headings. A plain-text search finds no 3bdfa87 or 9387 anywhere in the file, so that is the one tag without a section; the new 5d8c3b1 tag and heading pair up.
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 27, so this carried-forward finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous review (commit 334edfa)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new top section ## 2026-11-06 (4b2afd4) correctly records release 4b2afd4 and its shipped #10095 commit, but release 3bdfa87 still has no section, so the tag history remains one release ahead of services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	23	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between 3a0599f and fa32d6b

Verification Notes (click to expand)

• Head re-confirmed as 334edfa3b799fd3a77b964aaabcc875332a0c411 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md.
• The previous review SHA 15de715a is no longer an ancestor of the head, so the full PR diff was used. The new delta is the top ## 2026-11-06 (4b2afd4) section.
• refs/tags/kilo-mcp-release/2026-11-06-4b2afd4 is an annotated tag peeling to 4b2afd4b44ccc782ab6f86b321ff61e717f9e35f, created 2026-11-06T10:22:35Z (newest release tag, after 1028d12 at 09:40:11Z), with bundle-sha256=3d266d68… distinct from 1028d12 (6f86164…), so the deployed bundle changed.
• git log --reverse 1028d12..4b2afd4 -- services/kilo-mcp ':(exclude)services/kilo-mcp/CHANGELOG.md' returns exactly 565fea2ad5 fix(kilo-mcp): reclaim expired pending authorizations on create (#10095), matching the new bullet and PR link verbatim. Newest-first ordering is correct.
• Structural check: 89 kilo-mcp-release/* tags versus 88 ## <date> (<sha>) headings. A plain-text search finds no 3bdfa87 or 9387 anywhere in the file, so that is the one tag without a section; the new 4b2afd4 tag and heading pair up.
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 23, so this carried-forward finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous review (commit 15de715)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new top section ## 2026-11-06 (1028d12) correctly records both commits in its range, but release 3bdfa87 remains the one production release with no section, so the tag history is still one release ahead of services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	19	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between fa32d6b and 3a0599f

Verification Notes (click to expand)

• Head confirmed as 15de715a61470f15856369828623be55839d1eab immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md.
• Incremental delta since 3dc974e4 is the new ## 2026-11-06 (1028d12) section. Its 7-char SHA matches kilo-mcp-release/2026-11-06-1028d12 (created 2026-11-06T09:40:11Z, bundle 6f86164…, distinct from the prior f8a25e9 bundle e79b22f…), and git log --reverse f8a25e9..1028d12 -- services/kilo-mcp ':(exclude).../CHANGELOG.md' returns exactly db40323218 … (#10082) and 1028d12a73 … (#9917), matching the section's two bullets in order. Newest-first ordering is correct.
• Structural check: 88 kilo-mcp-release/* tags versus 87 ## <date> (<sha>) headings. The only tag without a heading is kilo-mcp-release/2026-11-05-3bdfa87; the newly added tag 1028d12 and its heading pair up.
• 3bdfa87 covers 4f895c6293 … (#9387), which adds 92 lines to services/kilo-mcp/catalog.json (imported by services/kilo-mcp/src/index.ts), so the deployed bundle did change; a plain-text search of the file for 3bdfa87 or 9387 returns nothing.
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 19, so this carried-forward finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous review (commit 3dc974e)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new top section ## 2026-11-06 (f8a25e9) correctly records its release range, but release 3bdfa87 — a genuine bundle-changing production release that shipped #9387 — still has no section, so the tag history remains one release ahead of services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	14	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between fa32d6b and 3a0599f

Verification Notes (click to expand)

• Head re-confirmed as 3dc974e4a2e025a59d486f2a62844b8997ef628d immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md.
• Incremental delta since a797446e is exactly the 4 added lines of the ## 2026-11-06 (f8a25e9) section. Its heading date and 7-char SHA match kilo-mcp-release/2026-11-06-f8a25e9 (peels to f8a25e94f9…, created 2026-11-06T09:01:13Z, bundle e79b22f…), and git log --reverse 9159151..f8a25e9 -- services/kilo-mcp ':(exclude).../CHANGELOG.md' returns exactly 3e700c573c refactor(cloud-agent): retire fully rolled out feature flags (#9971), matching the section's single bullet and PR link. Newest-first ordering is correct.
• Structural check: 87 kilo-mcp-release/* tags versus 86 ## <date> (<sha>) headings. Every tag has a heading except kilo-mcp-release/2026-11-05-3bdfa87 (created 2026-11-05T16:01:27Z, bundle 06a3309…), and no heading lacks a tag. The gap remains exactly that one release.
• 3bdfa87 covers 4f895c6293 … (#9387), which adds 92 lines to services/kilo-mcp/catalog.json (imported by services/kilo-mcp/src/index.ts), so the deployed bundle did change; a plain-text search of the file for 3bdfa87 or 9387 returns nothing.
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 14, so this carried-forward finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous review (commit a797446)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The newly added ## 2026-11-05 (9159151) section is accurate for its own release range, but release 3bdfa87 — a genuine bundle-changing production release that shipped #9387 — is still missing from services/kilo-mcp/CHANGELOG.md, so the latest changelog content has one fewer section than the tag history.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	10	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between fa32d6b and 3a0599f

Verification Notes (click to expand)

• Head re-confirmed as a797446e44708121188e8aa808d91bfe45dd746b immediately before publication. The branch was rebased onto main at b8a75be, so 5c8a699 is no longer an ancestor; the full PR diff (gh pr diff 7309 --patch) was used instead of a local incremental diff and still contains only services/kilo-mcp/CHANGELOG.md.
• Against the previously reviewed file content, the only delta is the 4 added lines of the ## 2026-11-05 (9159151) section. Its heading date and 7-char SHA match kilo-mcp-release/2026-11-05-9159151 (peels to 91591515ae…, created 2026-11-05T18:05:52Z, bundle 4ef5711…), and git log --reverse 3a0599f..9159151 -- services/kilo-mcp ':(exclude).../CHANGELOG.md' returns exactly b21b9cf5f4 feat(admin): require session-bound passkey step-up for admin access (#9615), matching the section's single bullet and PR link. Newest-first ordering is correct.
• Structural check: 86 kilo-mcp-release/* tags versus 85 ## <date> (<sha>) headings in the current file. Every tag has a heading except kilo-mcp-release/2026-11-05-3bdfa87 (created 2026-11-05T16:01:27Z, bundle 06a3309…), and no heading lacks a tag. Today's tags (6473612, 40a0c10, fa32d6b, 3bdfa87, 3a0599f, 9159151) versus today's headings (9159151, 3a0599f, fa32d6b, 40a0c10, 6473612) leave exactly that one release unrecorded.
• 3bdfa87 covers 4f895c6293 … (#9387), which adds 92 lines to services/kilo-mcp/catalog.json (imported by services/kilo-mcp/src/index.ts), so the deployed bundle did change; a plain-text search of the file for 3bdfa87 or 9387 returns nothing.
• Existing inline comment 4484013734 is active on the current head at services/kilo-mcp/CHANGELOG.md line 10, so this finding was not re-posted.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, no MCP catalog mutation in this diff, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Fix these issues in Kilo Cloud

Previous review (commit 5c8a699)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The new ## 2026-11-05 (3a0599f) section is accurate for its own release range, but it jumps from the 3a0599f release straight to fa32d6b, so release 3bdfa87 — a genuine bundle-changing production release that shipped #9387 — is missing from services/kilo-mcp/CHANGELOG.md.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits; the missing 3bdfa87 section is therefore attributed to a failed or lost land step rather than to hand editing.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
services/kilo-mcp/CHANGELOG.md	6	Release 3bdfa87 (shipped #9387, bundle 06a3309…) is missing between 3a0599f and fa32d6b

Verification Notes (click to expand)

• Head re-confirmed as 5c8a699111933b3d15f9964b5e68ca405bf73c43 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md, and the PR had no inline comments or reviews before this one.
• The incremental delta since faff6e44 is exactly the 4 added lines of the ## 2026-11-05 (3a0599f) section; its heading date and 7-char SHA match kilo-mcp-release/2026-11-05-3a0599f (peels to 3a0599fe538a9cbdbda4c70ec461cc6f3c607c1f, created 2026-11-05T17:49:39Z), and its single bullet matches 4bdfefc154 fix(mobile): replay an accepted manual review start on retry (#9399) verbatim with the correct PR link.
• git log --reverse ... 3bdfa87..3a0599f -- services/kilo-mcp ':(exclude).../CHANGELOG.md' returns only fix(mobile): replay an accepted manual review start on retry #9399, so the new section's contents are correct for its own range; the tag's bundle-sha256=0265117… differs from fa32d6b (348e301…) and 3bdfa87 (06a3309…).
• The gap: kilo-mcp-release/2026-11-05-3bdfa87 (created 2026-11-05T16:01:27Z, bundle 06a3309…) is a third distinct release between fa32d6b and 3a0599f, and its range contains 4f895c6293 … (#9387), which adds 92 lines to services/kilo-mcp/catalog.json — a file imported by services/kilo-mcp/src/index.ts, so the bundle did change. No 3bdfa87 heading and no 3bdfa87/#9387 reference exists anywhere in the changelog (84 sections, 4 dated 2026-11-05), so that release is unrecorded.
• Structural check of today's releases: tags 6473612, 40a0c10, fa32d6b, 3bdfa87, 3a0599f versus changelog headings 3a0599f, fa32d6b, 40a0c10, 6473612 — exactly one release section is missing.
• No MCP write-exposure concern applies to this diff: the PR does not touch services/kilo-mcp/catalog.json, and feat(cloud-agent): add durable history and native v2 runtime #9387's catalog additions are kind: "query" endpoints.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md - 1 warning

Previous review (commit faff6e4)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The incremental delta since the previous review is a single new top section ## 2026-11-05 (fa32d6b) in services/kilo-mcp/CHANGELOG.md, correctly recording the one kilo-mcp bundle-changing commit in that release range.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits. The previous review SHA 7b9ab85a is not an ancestor of the current head (history was rewritten again), so the delta was isolated with a file-scoped diff.

Verification Notes (click to expand)

• Head re-confirmed as faff6e44e22ac1d4229e6cc41dcf99fafe954690 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md, and the PR has no inline comments or reviews.
• git diff 7b9ab85a..HEAD -- services/kilo-mcp/CHANGELOG.md is exactly the 4 added lines of the new section; the branch-wide diff spans unrelated files only because history was rewritten.
• git log --reverse 40a0c10025..fa32d6bc8e -- services/kilo-mcp ':(exclude)services/kilo-mcp/CHANGELOG.md' returns exactly one commit, ad6f753d40 [AISAGE-857] feat(byok): enable organization key priorities (#9915), matching the new bullet verbatim with the matching PR link.
• refs/tags/kilo-mcp-release/2026-11-05-fa32d6b peels to fa32d6bc8eaadaf82071dbd4ac2de9f4f3665660, was created 2026-11-05T14:52:12Z (after kilo-mcp-release/2026-11-05-40a0c10 at 12:44:25Z), carries a new bundle-sha256, and is the newest kilo-mcp-release/* tag, so the section is correctly newest-first and its heading date matches the release. The top of the file orders all tag dates newest-first.
• The release range's kilo-mcp change is catalog.json only: an optional organizationId property (plus tag/searchBlob text) added to the existing byok.reorder mutation schema, which already existed. The handler enforces ORGANIZATION_MANAGE_ROLES for organization scope and writes an audit log, so no mutation is newly published and none issues or rotates credentials, reads or writes secrets, changes membership or authorization, deploys, charges, or deletes data. The MCP write-exposure rule does not apply.
• Docs-only change: no images (markdown-image guidance does not apply), no runtime code or memory-lifetime concerns, and the kilocode-landing content rules do not apply to this repo.

Files Reviewed (1 file)

• services/kilo-mcp/CHANGELOG.md

Previous review (commit 7b9ab85)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The incremental delta since the previous review is a single new top section ## 2026-11-05 (40a0c10) in services/kilo-mcp/CHANGELOG.md, correctly recording the one kilo-mcp bundle-changing commit in that release range.

Assumptions: [INFERENCE] The kilo-mcp Release job output is trusted because the file header forbids hand edits, and kilo-mcp-release/2026-11-05-40a0c10 is taken as the release anchor for this section. The previous review SHA is not an ancestor of the current head (history was rewritten again), so the delta was isolated with a file-scoped diff.

Verification Notes (click to expand)

• Head re-confirmed as 7b9ab85a037bd2f1def9ebeb5da3204d3e6fc077 immediately before publication; gh pr diff 7309 --name-only still shows only services/kilo-mcp/CHANGELOG.md, and the PR has no inline comments or reviews.
• `gi

[Snapshot truncated.]

Additional previous summary content was truncated to keep this comment within platform limits.

---

_{Reviewed by deepseek-flash-latest · Input: 40.2K · Output: 9.2K · Cached: 412.2K}

_{Review guidance: REVIEW.md from base branch main}

[kilo-code-bot]

WARNING: Release 3bdfa87 has no changelog section

The range between the fa32d6b and 3a0599f releases contains a separate production release that changed the deployed bundle: tag kilo-mcp-release/2026-11-05-3bdfa87 (created 2026-11-05T16:01:27Z, bundle sha256=06a330989471c65603eb63b4f6e9965b2384e7b9941e6e0d381447830f8b391d, distinct from both neighbours) over 4f895c6293 feat(cloud-agent): add durable history and native v2 runtime (#9387), which adds 92 lines to services/kilo-mcp/catalog.json (imported by services/kilo-mcp/src/index.ts, so it is part of the bundle).

git log --reverse --format='%h %s' fa32d6b..3bdfa87 -- services/kilo-mcp ':(exclude)services/kilo-mcp/CHANGELOG.md' returns only #9387, and 3bdfa87..3a0599f returns only #9399. This section therefore jumps straight from 3a0599f to fa32d6b, so release 3bdfa87 and its shipped #9387 change are missing from the changelog entirely, contrary to the file header's "one section per production release that changed the deployed bundle".

Suggested follow-up: confirm whether the land step for that release failed and re-run it (or re-land the omitted section) so a ## 2026-11-05 (3bdfa87) section is inserted between these two before this PR merges.