diff --git a/AGENTS.md b/AGENTS.md
index c9eac172..b8d4bc5b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -74,10 +74,10 @@ not the pinned tag, (re)create it:
 
 ```bash
 rm -rf .ct-agents
-git -c advice.detachedHead=false clone --quiet --depth 1 --branch v0.2.0 https://github.com/control-toolbox/ct-agents.git .ct-agents
+git -c advice.detachedHead=false clone --quiet --depth 1 --branch v0.3.0 https://github.com/control-toolbox/ct-agents.git .ct-agents
 ```
 
-**Pinned version: ct-agents v0.2.0.** State it, with the ct-conventions version, in
+**Pinned version: ct-agents v0.3.0.** State it, with the ct-conventions version, in
 plans and reports.
 
 - **Release.** When asked, in any language, to prepare a release, follow
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3e63ab1c..c0ac43f0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,6 +13,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   release) are read from a git-ignored clone in `.ct-agents/` at that tag, not from `main`
   of ct-agents, and the proposal of a release states the versions applied. The clone of the
   conventions is now `.ct-conventions/` (it was `.conventions/`), like `.ct-agents/`.
+- ct-agents pinned at `v0.3.0` in `AGENTS.md`: at the close of a release the agent runs
+  `release.jl audit`, which checks the trail the release left.
 
 ## [0.20.0] - 2026-10-19