chore(release): candidate v2.0.18

[mega-maxwell]

Release candidate v2.0.18 (was 2.0.18).

Merging this PR creates the release branch release-v2.0.18
at the merge commit. It creates no tag; the tag is cut once, at settlement, by release-settle → release-publish.

Changelog: this release's entry drafted under ## v2.0.18 (settle stamps the date on the release branch);
previous release's entry synced from its tag: none.

[mega-maxwell]

Claude review status

Living comment — rewritten in place. The review workflow keeps this single comment up to date instead of posting a new one each round, so it always describes the latest reviewed commit and the earlier text is intentionally gone. No reply is needed here; reply to a finding in its own review thread, and answer an open question in a reply on this PR. The next review round reconciles your answer.

⏭️ Review skipped

Not reviewing head 14bdea6b · updated 2026-09-08T11:24:35+00:00

This pull request is not a review target: opened by mega-maxwell[bot], the reviewer's own identity. No review round runs for it. Anything listed below is from an earlier round.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 14bdea6b74

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Do not cut v2.0.18 a second time

When the previously merged candidate #202 has run its cut job, release-v2.0.18 already points at that earlier merge: the parent is already version 2.0.18, while .github/workflows/release-candidate.yml defines each merged candidate as creating release-vX.Y.Z. Reusing this heading therefore either makes the second cut collide with the existing branch or leaves that branch before #203 even though this changelog now includes it. Advance to a new version, or update and settle the existing release branch instead of opening another v2.0.18 candidate.

Useful? React with 👍 / 👎.