From f1b1aaddb1dd2e1b26209ed2f6b33756457ada9e Mon Sep 17 00:00:00 2001
From: Rafael Richards <rmrich5@gmail.com>
Date: Sat, 9 May 2026 13:40:48 -0400
Subject: [PATCH] =?UTF-8?q?docs:=20refresh=20README=20=E2=80=94=20replace?=
 =?UTF-8?q?=20m-parser/tree-sitter-m-lint=20refs?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Cleans up references to projects that don't exist in the m-dev-tools
org and updates the downstream-consumer list to reflect what's
actually shipping:

- "m-parser" → "tree-sitter-m" everywhere (m-parser was the project's
  working name during the spec phase; the published repo is
  tree-sitter-m).
- "tree-sitter-m-lint (planned sibling)" → folded into m-cli (m lint).
  The standalone-linter sibling never shipped; m-cli's lint engine
  consumes m-standard directly.
- vista-meta marked as a separate VistA-specific repo, not in
  m-dev-tools (the relative ../vista-meta link is broken anyway).
- Downstream-consumer list expanded with m-cli (lint, formatter
  abbrev↔canonical maps) and the two VS Code extensions, both real
  consumers of m-standard data.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 README.md | 43 ++++++++++++++++++++++++++-----------------
 1 file changed, 26 insertions(+), 17 deletions(-)

diff --git a/README.md b/README.md
index 4dfc8f8..16b868f 100644
--- a/README.md
+++ b/README.md
@@ -78,9 +78,9 @@ Contains every command / function / ISV / operator / pattern code
 from any source, with abbreviation prefix-form expansion already
 done (~954 keyword forms total) and `standard_status` per token.
 
-This is what [`m-parser`](../m-parser/) (the tree-sitter grammar
-project, sibling repo) consumes at build time. See
-[`docs/m-standards-guide.md`](docs/m-standards-guide.md) for the
+This is what [`tree-sitter-m`](https://github.com/m-dev-tools/tree-sitter-m)
+(the tree-sitter grammar project, sibling repo) consumes at build time.
+See [`docs/m-standards-guide.md`](docs/m-standards-guide.md) for the
 human-readable reference.
 
 ### Cross-vendor mappings
@@ -108,19 +108,28 @@ exit code is non-zero if any F/S findings exist (CI-gate-friendly).
 
 ## Downstream consumers
 
-- **[`m-parser`](../m-parser/)** ([spec](../m-parser/docs/spec.md)) —
+- **[`tree-sitter-m`](https://github.com/m-dev-tools/tree-sitter-m)** —
   tree-sitter grammar for M, generated mechanically from
   `integrated/grammar-surface.json`. Single coupling point with
-  m-standard, pinned to a specific `schema_version`. Specification
-  phase as of writing; implementation is a separate project.
-- **`tree-sitter-m-lint`** (planned sibling of m-parser) — consumes
-  m-parser's AST plus m-standard's tier classifications
-  (operational / pragmatic / SAC) to enforce developer-chosen
-  profiles.
-- **[`vista-meta`](../vista-meta/)** — VEHU classification sandbox;
-  joins m-standard's per-concept TSVs against VistA's code-model TSVs.
+  m-standard, pinned to a specific `schema_version`. Production-ready
+  with v0.1 publish-ready (99.06% clean on the 39,330-routine VistA
+  corpus).
+- **[`m-cli`](https://github.com/m-dev-tools/m-cli)** — the
+  `m fmt`/`m lint`/`m test`/`m coverage`/`m doc` toolchain. Consumes
+  m-standard's tier classifications (operational / pragmatic / SAC) to
+  enforce developer-chosen lint profiles, plus the abbrev↔canonical
+  command/ISV/function maps for `m fmt --rules=pythonic` and
+  `--rules=compact`.
+- **[`m-stdlib-vscode`](https://github.com/m-dev-tools/m-stdlib-vscode)
+  and
+  [`tree-sitter-m-vscode`](https://github.com/m-dev-tools/tree-sitter-m-vscode)** —
+  editor extensions that surface m-standard data (token tier, syntax
+  format, hover docs) directly in VS Code.
+- **`vista-meta`** *(separate VistA-specific repo, not in
+  m-dev-tools)* — joins m-standard's per-concept TSVs against
+  VistA's code-model TSVs for VEHU classification work.
 - **AI agents and other M tooling** — the integrated TSV+JSON pair
-  is prompt-pack target. Any agent reasoning about M code can be
+  is a prompt-pack target. Any agent reasoning about M code can be
   loaded with these as ground truth — no hallucination about whether
   `$ZSEARCH` is standard, no guessing at command abbreviations.
 
@@ -182,10 +191,10 @@ m-standard/
   schema changes don't bump the version; breaking changes bump and
   announce in the changelog.
 
-Downstream consumers (m-parser, lint tools, vista-meta, AI agents)
-pin against a specific `schema_version` rather than the project
-version. Additive m-standard updates flow through; breaking ones
-require deliberate adoption.
+Downstream consumers (tree-sitter-m, m-cli, the VS Code extensions,
+vista-meta, AI agents) pin against a specific `schema_version`
+rather than the project version. Additive m-standard updates flow
+through; breaking ones require deliberate adoption.
 
 ## License