docs/how-to/upgrade-to-v0.14.0.md:33-34 says /abcd:memory runs instead of refusing from the release that reuses the name. The page is agents-only (commands/memory.md:6, user-invocable: false), so a person who types /abcd:memory still gets the host's refusal; only an agent's invocation runs it, and it runs the memory-notes page. Same paragraph as open iss-2610151422157749 (release v0.14.2 unnamed; abcd memory ingest refusing without naming library).

Frontmatter

.abcd/work/issues/open/iss-2610251558166678-docs-how-to-upgrade-to-v0-14-0-md-33-34.md
open on GitHub ↗ · commit history ↗

mentions1

• iss-2610151422157749At docs/how-to/upgrade-to-v0.14.0.md:7-9,32-35: The guide says a script that runs an old command name 'gets a refusal that names what replaced it'. The new paragraph covers bare `abcd memory` now running, but on this binary `abcd memory ingest`, `ask` and `lint` refuse as a plain cobra unknown sub-verb (`abcd: unknown command "ingest" for "abcd memory"`, exit 2) with no pointer to `library`. Verified: `abcd source` still names its successor. The paragraph also says only 'a release after v0.14.0' and does not name v0.14.2. / The note says 'A release after v0.14.0' reuses the name memory without naming the release, while the table above still lists `abcd memory` as retired. Verified true of this binary (`abcd memory` answers with a count, `abcd memory ingest` is still unknown command, exit 2). Naming v0.14.2 would be exact. (v0.14.2 release docs-currency review, raised by opus+sonnet.)