docs: refresh README — vista-meta → m-test-engine - #1
Open
rafael5 wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Replaces three vista-meta-as-default-engine mentions with m-test-engine (the in-org minimal-YottaDB Docker container created during the m-dev-tools self-containment sprint, Track A2). The legacy vista-meta SSH path is still available for the maintainer via m-cli's multi-transport Engine abstraction; both are dispatched through the same wire contract. The §2 "Why a standard library, why now" reproducible/§3 "Per-module acceptance gate" references now point at the in-org engine instead of the external rafael5/vista-meta repo, closing the last "but where do I get the engine?" hand-wave for fresh-clone users. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three vista-meta-as-default-engine mentions in the README pointed end users at `rafael5/vista-meta` for the YottaDB engine. Replaces with `m-dev-tools/m-test-engine` (the in-org minimal-YDB Docker container created during the self-containment sprint, Track A2). Legacy vista-meta SSH path stays available via m-cli's multi-transport `Engine` abstraction.
Affected sections: §2 "Reproducible" bullet, §2 "Now because the toolchain finally supports it" bullet, §3 "Per-module acceptance gate" engine prose.
Why
Closes the last "but where do I get the engine?" hand-wave for fresh-clone users — the engine repo is now in-org and unrelated to VistA.
Test plan
🤖 Generated with Claude Code