docs/adr/0021-plugin-descriptions-state-a-domain-boundary.md

@@ -14,8 +14,9 @@ A plugin's published description is one string authored twice — in `plugins/<n
 the matching `marketplace.packages[]` entry of the root `apm.yml` — and compiled into four generated
 files per plugin edit: the plugin's `.claude-plugin/plugin.json` and `.github/plugin/plugin.json`,
 plus the repo-wide `.claude-plugin/marketplace.json` and its `.github/plugin/marketplace.json`
-mirror. (`.agents/plugins/marketplace.json`, apm's codex profile, carries no per-package
-`description` or `version` at all and is unaffected.) It is the only text a consumer sees in a marketplace listing before
+mirror. (`.agents/plugins/marketplace.json`, apm's codex profile, carried no per-package
+`description` or `version` at all and was unaffected — that file and the profile producing it were
+removed 2026-09-13; see the note below.) It is the only text a consumer sees in a marketplace listing before
 installing. It is **not** a SKILL.md `description`: it is never preloaded into an agent's context and
 routes nothing at runtime. ADR-0020 governs that other artifact; this one governs this one. The
 overlap is a finding, not a scope: ADR-0020 established that capability enumeration in a description