Add repo-memory CLI test docs

docs/tests/repo-memory-skill/README.md

@@ -5,13 +5,16 @@
 This directory tracks human-readable test plans for the `skills/repo-memory/`
 Codex skill bundle.
 
-These documents are not package-level unit tests for `briefdb`.
-Those live with the runtime under `packages/repo-memory-runtime/`.
+These documents are not direct CLI command-contract specs for `repo-memory`.
+That coverage now lives under [../repo-memory/](../repo-memory/).
+
+These documents are also not package-level unit tests for the runtime.
+Those live under `packages/repo-memory-runtime/`.
 
 This directory covers a different surface:
 
 - whether an agent can actually use the packaged `repo-memory` skill
-- whether the bundled `./assets/briefdb` CLI works inside real skill-guided
+- whether the bundled `./assets/repo-memory` CLI works inside real skill-guided
   repository work
 - whether durable repository knowledge is stored and retrieved correctly
 
@@ -27,7 +30,7 @@ Use these defaults unless a case file explicitly overrides them:
 
 - run the scenario with one real agent using the bundled `repo-memory` skill
 - create an isolated temporary directory, repository fixture, and SQLite DB path
-- require the agent to use the bundled `./assets/briefdb` CLI instead of ad hoc
+- require the agent to use the bundled `./assets/repo-memory` CLI instead of ad hoc
   notes
 - validate final database state independently from the main thread after the
   agent stops
@@ -59,12 +62,13 @@ Each case file should use this structure:
 In scope:
 
 - explicit `$repo-memory` skill invocation
-- bundled `./assets/briefdb` CLI usage
+- bundled `./assets/repo-memory` CLI usage
 - durable knowledge add/search/list/event flows
 - package-backed SQLite memory database behavior as surfaced through the skill
 
 Out of scope:
 
-- package-level unit tests for `briefdb`
+- direct CLI contract coverage that now belongs under [../repo-memory/](../repo-memory/)
+- package-level unit tests for `packages/repo-memory-runtime`
 - future auto-export flows such as `repo-brief` generation
 - implicit skill triggering without `$repo-memory`