diff --git a/CHANGELOG.md b/CHANGELOG.md
index 71fac03..e4995b6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,7 +2,7 @@
 
 Notable changes to Swarmail. Versions follow [semantic versioning](https://semver.org).
 
-## Unreleased
+## 0.5.2 - 2026-10-09
 
 - Require agents to record whole-session closeouts and retire their own project
   registrations, with read-only verification and task/pause boundaries.
@@ -11,6 +11,9 @@ Notable changes to Swarmail. Versions follow [semantic versioning](https://semve
   worktree that is gone, so the hook warned on every prompt until the session ended. The pending entry is dropped;
   the session's next edit registers it again.
 
+- The release check fails for a package that has no row in the listings section of
+  `CONTRIBUTING.md`, so a new package cannot ship without a listing decision.
+
 ## 0.5.1 - 2026-10-09
 
 - A session whose usual name is already held by another session in a project
diff --git a/README.md b/README.md
index fbfffa0..43a809e 100644
--- a/README.md
+++ b/README.md
@@ -267,7 +267,7 @@ registering a second one. Where another session already holds that name in the p
 `sdk-cli` registers on its first edit instead, so a read-only one-shot run adds no agent. A
 child that inherited `sdk-ts` from an SDK-hosted session still registers at start. The registration starts with a tag
 holding the host's session id and working directory, which is how `swarmail
-who` matches names to sessions. A failure is retried on the next prompt or edit. State
+who` matches names to sessions. A failure is retried on the next prompt or edit; a retry for an edit checkout that has since been deleted is dropped. State
 lives in `~/.local/state/swarmail-register/`, under your profile on Windows.
 After upgrading, run `bun scripts/configure-hooks.ts` again to add the
 session-start hook.
@@ -342,7 +342,7 @@ wake an idle session.
 
 Measured on 2026-10-04 at
 [`67e187a`](https://github.com/bompus/swarmail/tree/67e187a6b4beb7319c6ab30466448742297e2a01).
-These results have not been remeasured for 0.4.0, 0.5.0 or 0.5.1.
+These results have not been remeasured for 0.4.0, 0.5.0, 0.5.1 or 0.5.2.
 The measurements used one machine with one small workload (40 agents, 250 seed messages,
 1,560 messages by the end). Each server started on empty storage. Startup is
 hyperfine's mean of 20 runs; every other number is the median of three rounds,
diff --git a/package.json b/package.json
index ab03014..b202f98 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "swarmail",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "private": true,
   "description": "Local mail, roster and file reservations for coding-agent sessions on one machine, served over MCP.",
   "license": "MIT",
diff --git a/packages/mcp-relay/package.json b/packages/mcp-relay/package.json
index c6ad131..d2ca5a3 100644
--- a/packages/mcp-relay/package.json
+++ b/packages/mcp-relay/package.json
@@ -1,6 +1,6 @@
 {
   "name": "swarmail-mcp",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Stdio MCP relay to a running Swarmail server, for MCP clients that install servers from a registry.",
   "keywords": [
     "coding-agents",
diff --git a/server.json b/server.json
index 29bc776..95e82eb 100644
--- a/server.json
+++ b/server.json
@@ -8,12 +8,12 @@
     "source": "github"
   },
   "websiteUrl": "https://github.com/bompus/swarmail#install",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "swarmail-mcp",
-      "version": "0.5.1",
+      "version": "0.5.2",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"