diff --git a/CHANGELOG.md b/CHANGELOG.md
index d8b54cc..8633e04 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,19 @@ For each entry, **Upgrade impact** classifies the change against the [three-buck
 
 ## Unreleased
 
+## v1.2.1 — 2026-10-05 — Drift the prompt audit found
+
+A patch release: fixes to the framework's instruction files, with nothing new to adopt
+([#35](https://github.com/Aplyca/AgenticDevelopmentFramework/pull/35)). Several files had drifted
+from later decisions: `/orchestrate` and the cost model gave the wrong model for some agents, and the
+rules disagreed with each other. Two other habits cost tokens: every agent re-read files it already
+had, and two workflows' prompts kept their agents from sharing a cache.
+
+**Upgrading from v1.2.0:** `/aplyca-adf:upgrade` moves the pin to `v1.2.1`. A packaged project gets the
+agents, `/orchestrate`, the workflows, and the cost model from it, and updates the three rule files it
+commits. A committed project also overwrites its own copies of the rest. The entry below lists each
+file.
+
 ### Drift the prompt audit found
 
 A prompt audit of the framework's instruction files found nothing written for older models: no
diff --git a/README.md b/README.md
index cb3c3a4..d19552a 100644
--- a/README.md
+++ b/README.md
@@ -141,8 +141,8 @@ Updates are deliberate: `/aplyca-adf:upgrade` moves a project from one release t
 pull request and keeps its customizations. Read the **Upgrade impact** of each release in
 [CHANGELOG.md](CHANGELOG.md) first. From v1.0.0, releases follow semantic versioning ([decision
 0017](docs/decisions/0017-semantic-versioning.md)), so a major release asks something of your team.
-The latest, **v1.2.0** (2026-10-05), moves the framework's reference docs out of packaged projects
-and into the plugin.
+The latest, **v1.2.1** (2026-10-05), fixes drift in the instruction files. **v1.2.0** moved the
+framework's reference docs out of packaged projects and into the plugin.
 **v1.0.0** (2026-10-02) renamed the plugin `aplyca-adf` and opens with the order to upgrade in. A
 baseline older than `7383422` takes that release's order first, and one older than `3eb7777` takes its
 three fixes before that — they affect every adopted repository.
diff --git a/plugins/aplyca-adf/.claude-plugin/plugin.json b/plugins/aplyca-adf/.claude-plugin/plugin.json
index b302689..3c65c94 100644
--- a/plugins/aplyca-adf/.claude-plugin/plugin.json
+++ b/plugins/aplyca-adf/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "aplyca-adf",
   "description": "The Agentic Development Framework for Claude Code. /adopt bootstraps a repository — skeleton, optional modules, guardrail hooks, verified facts — committed or packaged; /upgrade moves an adopted repository to a newer release; /cost-report shows what agent sessions cost, from local transcripts. In a packaged project it also carries the framework's skills, agents, workflows, hooks, and reference docs, pinned to a release; in a committed project those step aside for the committed copies.",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "author": {
     "name": "Aplyca",
     "email": "dev@aplyca.com"
diff --git a/plugins/aplyca-adf/README.md b/plugins/aplyca-adf/README.md
index 0e1a774..f728ed4 100644
--- a/plugins/aplyca-adf/README.md
+++ b/plugins/aplyca-adf/README.md
@@ -146,7 +146,7 @@ the plugin by a relative path. A machine where nobody trusts the folder — CI 
 {
   "extraKnownMarketplaces": {
     "aplyca": {
-      "source": { "source": "github", "repo": "aplyca/AgenticDevelopmentFramework", "ref": "v1.2.0" }
+      "source": { "source": "github", "repo": "aplyca/AgenticDevelopmentFramework", "ref": "v1.2.1" }
     }
   },
   "enabledPlugins": { "aplyca-adf@aplyca": true }