docs: fold the unreleased notes into 0.5.2 and align the benchmark remeasure line

[bompus]

0.5.2 is bumped on main (#124) but was never tagged or published: the tags stop at v0.5.1, GitHub's latest release is v0.5.1, and npm has no 0.5.2. The three entries added since then sat under Unreleased, which would have shipped a 0.5.2 whose notes missed them. They now sit in the 0.5.2 section and the Unreleased heading is gone. No version field changes.

docs/benchmarks.md said the benchmark results "have not been remeasured for 0.4.0". The README says "0.4.0, 0.5.0, 0.5.1 or 0.5.2". Both now say the README's list. The faster who and inbox query are not in the benchmarked build (67e187a) and were not remeasured.

Release audit against what 0.5.2 will contain (every commit since v0.5.1: #121, #123, #96, #124, #125, #126, #127):

• Changelog covers all of them: closeout guidance (docs: retire registrations at whole-session closeout #96), dropped pending registration (fix(register): drop a pending registration whose edit checkout was deleted #123), release listing check (chore: fail the release check for a package with no listing row #121), who (perf(who): look up each T3 thread directory's checkout once #125), inbox bodies (perf(inbox): read message bodies only for pages that include them #126), relay README (docs(mcp-relay): list the memory each launch command costs #127). chore(release): 0.5.2 #124 is the version bump.
• Version fields in package.json, packages/mcp-relay/package.json and both fields in server.json agree on 0.5.2; bun run check passes.
• packages/mcp-relay/index.mjs and the plugin relay.mjs copies are unchanged since v0.5.1, so the relay memory numbers in its README, measured on the published 0.5.1 package, describe the 0.5.2 script.
• Measurements in the new entries state their conditions in their pull requests (perf(who): look up each T3 thread directory's checkout once #125 to docs(mcp-relay): list the memory each launch command costs #127).

Nothing is tagged or published here.

Summary by CodeRabbit

• Documentation
  • The version 0.5.2 changelog now includes notes on swarmail who checking each running T3 thread directory once, inbox fetches avoiding message-body reads when bodies aren’t requested, and memory figures for the swarmail-mcp launch command.
  • The benchmark notice now clarifies that results have not been remeasured for versions 0.4.0, 0.5.0, 0.5.1, and 0.5.2.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8f49d1b6-0745-4fe8-a539-1760ac31ece3

---

📥 Commits

Reviewing files that changed from the base of the PR and between e034ad7 and 5f0a976.

---

📒 Files selected for processing (2)

• CHANGELOG.md
• docs/benchmarks.md

---

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 5 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The changelog entries moved from Unreleased to version 0.5.2. The benchmark notice now lists versions 0.4.0, 0.5.0, 0.5.1, and 0.5.2 as not remeasured.

Changes

Release documentation

Layer / File(s)	Summary
Update release notes and benchmark notice CHANGELOG.md, docs/benchmarks.md	The three changelog entries now appear under version 0.5.2, and the benchmark notice lists versions 0.4.0, 0.5.0, 0.5.1, and 0.5.2.

---

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 5f0a9

The documentation changes match the stated release-note and benchmark-disclosure updates, with no identified issue requiring resolution before merge.

Architecture Summary

Architecture risk: 🔵 Low · up to 5f0a9

The change affects 2 systems.

Changed systems: CHANGELOG.md, docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — CHANGELOG.md (service) was modified; 1 changed file maps to changed impact.
• observed — docs (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in CHANGELOG.md: Removed the Unreleased heading and its three entries; those entries are now listed under version 0.5.2.
• observed — Modified behavior in CHANGELOG.md: Added the three entries to version 0.5.2: swarmail who queries each running T3 thread directory once, inbox fetches skip body reads when include_bodies is off, and the README lists memory figures for three swarmail-mcp launch commands.
• observed — Modified behavior in docs/benchmarks.md: The notice expands the versions not remeasured from only 0.4.0 to 0.4.0, 0.5.0, 0.5.1, and 0.5.2.

---

Pre-merge checks | 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title check		The title clearly summarizes both documentation changes: moving unreleased notes into 0.5.2 and updating the benchmark statement.
Description check		The description clearly explains the changes, their purpose, release context, benchmark scope, version checks, and audit results. It does not reproduce the template checkboxes, but it provides the req…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Suppressions Explained		The pull request changes only CHANGELOG.md and docs/benchmarks.md. The added lines move changelog text and update a benchmark sentence. No added lint, type-check, formatter, or configuration suppr…
Interface Changes Documented		The pull request changes only CHANGELOG.md and docs/benchmarks.md. The diff contains no MCP tool or argument changes, no swarmail command or flag changes, and no environment-variable changes. Th…

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}