docs(changelog): promote develop [Unreleased] to [4.0.2]

[bpamiri]

Summary

The 4.0.2 cut renamed [Unreleased] → [4.0.2] on the release branch only (#2819 squash-merged to main), so develop still shows the 4.0.2 entries under [Unreleased]. Left as-is, the 4.0.3 cut would rename those same already-shipped entries to [4.0.3] and re-publish them.

This promotes them to # [4.0.2] => 2026-05-27 (heading + blockquote copied verbatim from main), so develop's CHANGELOG is now identical to main's. The next 4.0.3 entry PR re-creates [Unreleased] on top, per the existing post-cut convention.

Test plan

• git diff origin/main -- CHANGELOG.md is empty after the rename (develop == main)
• 4.0.2 entries now correctly labelled [4.0.2], not [Unreleased]

🤖 Generated with Claude Code

[wheels-bot]

Wheels Bot — Reviewer A

TL;DR: This is a one-line changelog housekeeping PR that promotes the [Unreleased] heading on develop to [4.0.2] to match main after the squash-merge of #2819. The change is correct, the commit message is clear, and nothing else in the repo is touched. Verdict: approve.

Correctness

git diff origin/main -- CHANGELOG.md returns empty after this commit, confirming the stated goal — develop's CHANGELOG is now identical to main's. The heading format # [4.0.2](https://github.com/wheels-dev/wheels/releases/tag/v4.0.2) => 2026-05-27 matches the adjacent [4.0.1] and [4.0.0] entries exactly, and the blockquote release summary is the verbatim text from the release branch. No off-by-ones or missing entries.

Commits

Single commit docs(changelog): promote develop [Unreleased] to [4.0.2]:

• Type docs is in the allowlist. ✓
• Subject is 45 characters, sentence-case, not ALL-CAPS. ✓
• Body explains the why (squash-merge to main left develop carrying 4.0.2 entries under [Unreleased], which would have caused 4.0.3 cut to re-publish them). ✓
• DCO trailer Signed-off-by: Peter Amiri <peter@alurium.com> present. ✓

No Conventions, Cross-engine, Tests, Docs, or Security sections apply — this is a pure CHANGELOG edit.

[wheels-bot]

Wheels Bot — Reviewer B (round 1)

A's review is accurate and well-justified for a pure CHANGELOG edit. No issues to flag.

A cited the specific check (empty git diff origin/main -- CHANGELOG.md), verified the heading format against adjacent entries, and walked through each commit convention element before approving. All claims check out against the actual diff. For a single-file CHANGELOG heading rename, Cross-engine, Tests, and Security sections correctly do not apply.

Sycophancy

None detected. A justified the approval with concrete evidence rather than "LGTM."

False positives

None detected. The diff, commit message body, and DCO trailer all match what A described.

Missed issues

None detected.

Verdict alignment

APPROVED is consistent with the findings.

Convergence

Aligned. A's review is accurate and the approval is warranted. No changes needed.