diff --git a/.planning/phases/18.1-payment-gateway-subscriptions/18.1-09-SUMMARY.md b/.planning/phases/18.1-payment-gateway-subscriptions/18.1-09-SUMMARY.md
index 0b858ee..12cc93a 100644
--- a/.planning/phases/18.1-payment-gateway-subscriptions/18.1-09-SUMMARY.md
+++ b/.planning/phases/18.1-payment-gateway-subscriptions/18.1-09-SUMMARY.md
@@ -254,7 +254,7 @@ The plan proposed framework tag `v0.1.27`. Since the plan was written, `v0.1.27`
 **Push sheet.** Every repository was 0 commits behind its origin after `git fetch origin --tags`. Unpushed commits:
 - summercms.go master: 27 ahead before this SUMMARY.
   - This phase's commits: plans 07 to 09.
-  - Other sessions' committed work, approved for this push: quick-261016-0fm (admin theme and locale preferences, the dist rebuild for v0.2.1), quick-261015-w7f (docs since v0.1.14, deployed on v0.2.0), the fast task "summercms.io Alpha 0.2 copy", and `9921768` docs(19.3-05).
+  - Other sessions' committed work, approved for this push: quick-261016-0fm (admin theme and locale preferences, the dist rebuild for v0.2.1), the closing docs of quick-261015-w7f (summercms.io deployed on v0.2.0), and the fast task "summercms.io Alpha 0.2 copy". (Correction made after the release: an earlier version of this line also named `9921768` docs(19.3-05). That commit was already on origin as `v0.1.27`.)
 - pgsub main: 7 ahead (plans 07 to 09).
 - pgstripe main: 8 ahead (plans 07 to 09).
 - layer main: 3 ahead (plans 08 and 09).
@@ -267,6 +267,44 @@ The plan proposed framework tag `v0.1.27`. Since the plan was written, `v0.1.27`
 
 Replace lines stay in both plugins. Nothing is force-pushed. The pushed hashes and tag objects are recorded in the release record below, which is added after the pushes.
 
+### Release record
+
+This is what was done, in the order of the push sheet. Nothing was force-pushed. Every repository was 0 commits behind its origin right before its push (`git fetch origin --tags`, then `rev-list --count HEAD..origin/<branch>`).
+
+**Framework**
+- master pushed: `f3e8a98..f64ae79`. `f64ae79` is this SUMMARY's commit.
+- Annotated tag `v0.2.1` created on `f64ae79` (tag object `f067801`) and pushed. `v0.1.27` and `v0.2.0` are untouched.
+
+**pgsub**
+- Commit `41b68f6` raises the require to `git.golem15.com/golem15/summercms v0.2.1`; the replace onto `../summercms.go` is unchanged.
+- `go mod tidy` added the framework's indirect dependencies since v0.1.26: aws-sdk-go-v2 (S3), go-redis, otter, google/wire, go.uber.org/atomic. This is +24 lines in each of go.mod and go.sum, matching the framework's own go.mod; no direct dependency was added.
+- vet and the `-short` tests pass.
+- main pushed: `472b75b..41b68f6`.
+- Annotated tag `v0.1.0` created on `41b68f6` (tag object `8b6a1f0`) and pushed.
+
+**pgstripe**
+- Commit `2a427fd` raises the requires to summercms `v0.2.1` and sm-paymentgatewaysubscriptions-plugin `v0.1.0`; the replace lines are unchanged.
+- tidy added the same indirect dependencies as in pgsub. vet and `-short` pass.
+- main pushed: `baf3c55..2a427fd`.
+- Annotated tag `v0.1.0` created on `2a427fd` (tag object `da39829`) and pushed.
+
+**Layer**
+- main pushed: `30046f5..22368c5`.
+- Annotated tag `v0.2.1` created on `22368c5` (tag object `b7a6fe7`, package.json 0.2.1) and pushed.
+
+No GOPROXY or GOPRIVATE resolution was needed during tidy, because the replace lines resolve the framework and pgsub locally.
+
+**Check:** after the pushes, each local branch equals its origin branch:
+
+| Repository | Branch | Hash | Tag (`ls-remote ^{}`) |
+|------------|--------|------|-----------------------|
+| summercms.go | master | `f64ae79`, before the later docs commits, which are pushed afterwards | `v0.2.1` → `f64ae79` |
+| pgsub | main | `41b68f6` | `v0.1.0` → `41b68f6` |
+| pgstripe | main | `2a427fd` | `v0.1.0` → `2a427fd` |
+| layer | main | `22368c5` | `v0.2.1` → `22368c5` |
+
+`grep "summercms v0.2.1"` finds a line in both plugin go.mod files, and `grep "sm-paymentgatewaysubscriptions-plugin v0.1.0"` finds one in pgstripe's go.mod.
+
 **Open item:** the layer's `scripts/check-git-install.sh` still targets `vue-journal-layer`, so an install check of layer `v0.2.1` needs that script fixed first. See `deferred-items.md`.
 
 ## Decisions Made