docs: record cycle-3 client release

docs/ClientPackaging.md

@@ -140,13 +140,16 @@ publish while the version constants still read the already-published
 0.2.0/0.2.1 numbers above — see `clients/python/README.md` for the
 user-facing warning. **0.2.0 is superseded by 0.2.1; do not install it.**
 
-As of this remediation (CLI-46), the in-source version constants for the
-.NET, Go, Python, and Rust clients (plus Contracts) read **0.2.1**, and the
-Java client reads **0.2.2**. These are not yet published — the numbers
-above (0.2.0 four clients + Contracts, 0.2.1 Java) remain the live registry
-state until the next `pack-clients.ps1` / `tag-go-module.ps1` run. Once that
-publish lands, update this section with the new coordinates and commit(s),
-the same way the 2026-08-07 record above was written after the fact.
+On 2026-08-25 the superseding release shipped from commit
+`5776021970cbbe59813ba57579abe00d9fc61a46`. Published coordinates on
+`gitea.dohertylan.com` are `nuget` `ZB.MOM.WW.MxGateway.Client` **0.2.1** and
+`ZB.MOM.WW.MxGateway.Contracts` **0.2.1**, `pypi`
+`zb-mom-ww-mxaccess-gateway-client` **0.2.1**, `cargo`
+`zb-mom-ww-mxgateway-client` **0.2.1**, and `maven`
+`com.zb.mom.ww.mxgateway:zb-mom-ww-mxgateway-client` **0.2.2**. The Go module
+tag `clients/go/v0.2.1` points to that same commit. Every exact package
+coordinate returned HTTP 200 through the Gitea package API after publication,
+and `go list -m` resolved `v0.2.1` to the tagged commit.
 
 ## .NET