From de350599ee81ec6b9659183c80489e86bbabbb3f Mon Sep 17 00:00:00 2001 From: Rafael Richards Date: Sat, 9 May 2026 13:48:19 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20README=20=E2=80=94=20drop=20external=20?= =?UTF-8?q?rafael5/vista-meta=20link,=20fix=20stale=20Track=20A3=20note?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - "Why this exists" section: replace explicit https://github.com/rafael5/vista-meta link (vista-meta is intentionally not in the m-dev-tools org) with a parenthetical flagging it as separate. Adds explicit M_CLI_ENGINE=ssh hint for maintainers who keep using vista-meta. - "How m-cli / m-stdlib consume this" no longer references the ../m-dev-tools-todo.md path (the todo plan is local-only, intentionally not committed). Marks Track A3 as shipped. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) 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