diff --git a/README.md b/README.md
index 5a1a03f..4a9779e 100644
--- a/README.md
+++ b/README.md
@@ -12,16 +12,18 @@ test runner — both dispatch on
 ## Why this exists
 
 `m-cli` and `m-stdlib` previously bound their test runners to
-[vista-meta](https://github.com/rafael5/vista-meta) — a heavyweight
-YottaDB + VistA + RPC broker + FileMan + Octo SQL stack. For non-VistA
-M development, that's overkill: the tests just need a YottaDB engine.
+**vista-meta** *(a separate VistA-specific repo, not in m-dev-tools)* —
+a heavyweight YottaDB + VistA + RPC broker + FileMan + Octo SQL stack.
+For non-VistA M development, that's overkill: the tests just need a
+YottaDB engine.
 
 `m-test-engine` is exactly that — `yottadb/yottadb-base:latest-master`
 with a keep-alive command. No SSH server, no VistA, no extras. The
 consumer project's source bind-mounts in via `/work`; routines are
 compiled and run from there with no SCP / staging round-trip.
 
-For VistA-specific work, keep using vista-meta. This repo is the
+For VistA-specific work, maintainers can keep using vista-meta via
+m-cli's `SSHEngine` transport (`M_CLI_ENGINE=ssh`). This repo is the
 lightweight default for the rest of the toolchain.
 
 ## Quick start
@@ -73,8 +75,10 @@ routine dirs — derived by mapping the project root through the
 `/work` bind mount. There's no SCP / SFTP step: the consumer's
 filesystem is directly visible inside the container.
 
-`m-stdlib`'s test runner uses the same transport once Track A3 of the
-[m-dev-tools-todo plan](../m-dev-tools-todo.md) lands.
+`m-stdlib`'s test runner uses the same transport (Track A3 of the
+m-dev-tools self-containment sprint shipped 2026-05-09 —
+m-stdlib's Makefile delegates `engine-up` / `engine-down` /
+`engine-status` to this repo).
 
 ## Configuration