chore: remove the Vue grammar (moved to vuejs/language-tools) (#50)

Author: johnsoncodehk

KNOWN-GAPS.md

@@ -14,7 +14,7 @@ commits) so the ledger is deterministic and commit-trackable.
 
 Regenerate: `node test/gap-ledger.ts --write` · verify up-to-date: `node test/gap-ledger.ts --check`.
 
-**0 gaps** across 7 grammars · 0 dropped.
+**0 gaps** across 6 grammars · 0 dropped.
 
 _No gaps currently surface._ The generative check reports no valid-input flat-highlighter
 divergence on the derived corpus. (This is the ledger MECHANISM; it lists what the check finds.)

README.md

@@ -9,7 +9,15 @@ Write a language's grammar **once**, as an executable definition. Monogram runs
 - **TypeScript** ([`typescript.ts`](typescript.ts)) — mature: 100% valid-code coverage, 97.8% bidirectional vs `tsc`.
 - **JavaScript** ([`javascript.ts`](javascript.ts)) — the standalone ECMAScript base TypeScript [builds on](#adding-a-language) (subset → superset); parses real-world JS, with less conformance-corpus depth than TS so far.
 - **HTML** ([`html.ts`](html.ts)) — the engine reaching *past token streams into markup*; ~95 lines, validated against [`parse5`](https://github.com/inikulin/parse5).
-- **Vue** ([`vue.ts`](vue.ts)) — a dialect of `html.ts`: SFC blocks that embed Monogram's own TS/JS/CSS, plus directives and `{{ }}` interpolation.
+- **YAML** ([`yaml.ts`](yaml.ts)) — indentation-sensitive markup on the shared engine; validated against the maintained [RedCMD/YAML-Syntax-Highlighter](https://github.com/RedCMD/YAML-Syntax-Highlighter).
+
+## Used by
+
+Projects shipping Monogram-derived grammars:
+
+- [**vuejs/language-tools**](https://github.com/vuejs/language-tools) — the Vue TextMate grammars + VS Code language configuration ([vuejs/language-tools#6085](https://github.com/vuejs/language-tools/pull/6085)).
+
+Using Monogram in your project? Open a PR to add it here.
 
 ## Quick start
 
@@ -77,7 +85,6 @@ This matters because `tsc`'s *parser* is not the same thing as the language. It
 | TSX | 96.7% · 65.7% | 95.6% vs 95.4% |
 | HTML | 95.3% · 49.3% | 100.0% vs 98.8% |
 | YAML | 100.0% · 73.9% | 100.0% vs 99.5% |
-| Vue | — | 98.0% vs 98.0% |
 <!-- coverage:end -->
 
 Measured against the *maintained* official grammar where it matters, not a dead bundle: JS/TS use Microsoft's maintained [TypeScript-TmLanguage](https://github.com/microsoft/TypeScript-TmLanguage); YAML uses the maintained [RedCMD/YAML-Syntax-Highlighter](https://github.com/RedCMD/YAML-Syntax-Highlighter) that VS Code switched to ([microsoft/vscode#232244](https://github.com/microsoft/vscode/pull/232244)); only HTML's baseline is the unmaintained [textmate/html.tmbundle](https://github.com/textmate/html.tmbundle) — the #203212 case Monogram targets.
@@ -88,7 +95,7 @@ Take the bugs reported against each *hand-written* official grammar and ask whet
 
 <!-- issues:start -->
 <!-- generated by `npm run bench:issues` — do not edit by hand -->
-_Each hand-written **official** grammar vs Monogram's **derived** one, on the bugs filed against it: **TypeScript 26/26** (official 8/26) · **TSX 11/11** (official 5/11) · **HTML 20/20** (official 13/20) · **Vue 23/23** (official 18/23) · **YAML 8/8** (official 8/8). Per-issue detail below — auto-generated by `npm run bench:issues`._
+_Each hand-written **official** grammar vs Monogram's **derived** one, on the bugs filed against it: **TypeScript 26/26** (official 8/26) · **TSX 11/11** (official 5/11) · **HTML 20/20** (official 13/20) · **YAML 8/8** (official 8/8). Per-issue detail below — auto-generated by `npm run bench:issues`._
 
 #### TypeScript
 | issue | Monogram | official |
@@ -180,40 +187,6 @@ _Each hand-written **official** grammar vs Monogram's **derived** one, on the bu
 
 </details>
 
-#### Vue
-| issue | Monogram | official |
-|---|:--:|:--:|
-| [#6007](https://github.com/vuejs/language-tools/issues/6007)/[#2096](https://github.com/vuejs/language-tools/issues/2096)/[#520](https://github.com/vuejs/language-tools/issues/520) — `as` type assertion in directive value | ✓ | · |
-| [#2060](https://github.com/vuejs/language-tools/issues/2060)-inline — `` const a = 1;</script> `` (content on the close line) embeds + clean close | ✓ | · |
-| [#2060](https://github.com/vuejs/language-tools/issues/2060)-inline-adjacent — an unterminated union before a same-line `` </script> ``, then a second `<script setup>` block | ✓ | · |
-| [#5660](https://github.com/vuejs/language-tools/issues/5660) — `as const` cast in a v-for value | ✓ | · |
-| [#4716](https://github.com/vuejs/language-tools/issues/4716)/[#5571](https://github.com/vuejs/language-tools/issues/5571) — `as` cast followed by another attribute | ✓ | · |
-
-<details><summary>… and 18 more both grammars already handle (✓ / ✓)</summary>
-
-| issue | Monogram | official |
-|---|:--:|:--:|
-| [#3400](https://github.com/vuejs/language-tools/issues/3400) — `instanceof` in {{ }} | ✓ | ✓ |
-| [#5370](https://github.com/vuejs/language-tools/issues/5370) — `typeof x !==` in v-if | ✓ | ✓ |
-| [#5118](https://github.com/vuejs/language-tools/issues/5118) — `?.` / `??` in {{ }} | ✓ | ✓ |
-| [#1675](https://github.com/vuejs/language-tools/issues/1675) — arrow `=>` in {{ }} | ✓ | ✓ |
-| [#6039](https://github.com/vuejs/language-tools/issues/6039)/[#4741](https://github.com/vuejs/language-tools/issues/4741) — `<` operator in {{ }} (not a tag!) | ✓ | ✓ |
-| [#5722](https://github.com/vuejs/language-tools/issues/5722) — negated ternary + quotes in {{ }} | ✓ | ✓ |
-| [#5538](https://github.com/vuejs/language-tools/issues/5538)/[#2060](https://github.com/vuejs/language-tools/issues/2060) — trailing `export type` before `` </script> `` | ✓ | ✓ |
-| [#3999](https://github.com/vuejs/language-tools/issues/3999) — a force-wrapped multi-line `<script lang="ts">` start tag keeps the body as the `ts` family (no .ts→.js flip) | ✓ | ✓ |
-| [#4769](https://github.com/vuejs/language-tools/issues/4769) — tag name starting with `template` | ✓ | ✓ |
-| [#5701](https://github.com/vuejs/language-tools/issues/5701) — `{{` inside a `<script>` string | ✓ | ✓ |
-| [#6070](https://github.com/vuejs/language-tools/issues/6070) — capitalized component then a `<style>` block | ✓ | ✓ |
-| [#4291](https://github.com/vuejs/language-tools/issues/4291) — `<script lang="tsx">` body embeds the DECLARED `source.tsx` (not a source.js fallback) | ✓ | ✓ |
-| [#4291](https://github.com/vuejs/language-tools/issues/4291)-jsx — `<script lang="jsx">` body embeds the DECLARED `source.js.jsx` | ✓ | ✓ |
-| generic="T" — `generic="T extends U">` type-param list embeds as TS | ✓ | ✓ |
-| [#4410](https://github.com/vuejs/language-tools/issues/4410) — dynamic directive argument `:[attr]` | ✓ | ✓ |
-| [#3727](https://github.com/vuejs/language-tools/issues/3727) — `.prop` modifier shorthand | ✓ | ✓ |
-| [#2666](https://github.com/vuejs/language-tools/issues/2666) — dynamic slot name from a template literal | ✓ | ✓ |
-| [#2560](https://github.com/vuejs/language-tools/issues/2560)/[#1290](https://github.com/vuejs/language-tools/issues/1290) — `type` as a v-for loop variable | ✓ | ✓ |
-
-</details>
-
 #### YAML
 _No asymmetries — both grammars handle all 8 filed bugs below._
 
@@ -233,7 +206,7 @@ _No asymmetries — both grammars handle all 8 filed bugs below._
 </details>
 <!-- issues:end -->
 
-<sub>A sampled ledger of real tracker issues, not an exhaustive audit. Run `npm run bench:issues` to regenerate (needs the official grammars: VS Code's installed TS/JS/HTML, and the Vue fixtures — see [`test/vue-bench.ts`](test/vue-bench.ts)). Sources: [`test/issue-cases.ts`](test/issue-cases.ts), [`test/html-issue-cases.ts`](test/html-issue-cases.ts), [`test/vue-issue-cases.ts`](test/vue-issue-cases.ts).</sub>
+<sub>A sampled ledger of real tracker issues, not an exhaustive audit. Run `npm run bench:issues` to regenerate (needs the official grammars: VS Code's installed TS/JS/HTML). Sources: [`test/issue-cases.ts`](test/issue-cases.ts), [`test/html-issue-cases.ts`](test/html-issue-cases.ts).</sub>
 
 
 ### The ceiling — and the bar for claiming it
@@ -363,7 +336,7 @@ const Regex = token(seq(
 });
 ```
 
-[`test/agnostic.ts`](test/agnostic.ts) proves it directly — the same engine parses a toy grammar whose identifier token is `Word`, with no templates or regex. The deeper proof is [`html.ts`](html.ts): markup shares *nothing* with TypeScript's token stream, yet the same engine handles it (and Vue layers SFC blocks + `{{ }}` interpolation on top).
+[`test/agnostic.ts`](test/agnostic.ts) proves it directly — the same engine parses a toy grammar whose identifier token is `Word`, with no templates or regex. The deeper proof is [`html.ts`](html.ts): markup shares *nothing* with TypeScript's token stream, yet the same engine handles it.
 
 ## Adding a language
 
@@ -373,7 +346,7 @@ A new language is **one grammar file** on the unchanged engine:
 2. **Prove it as a parser** against the language's own official test suite, measured **bidirectionally** (accept what the reference accepts, reject what it rejects).
 3. **Drop in the official TextMate grammar** as the baseline, so highlighter coverage is measured against what you're replacing, not asserted.
 
-The lexer, CST types, and all three highlighters fall out of step 1; a *dialect* (`.tsx`/`.jsx` via [`jsx.ts`](jsx.ts), or Vue on [`html.ts`](html.ts)) reuses a base grammar's rules by name in a few lines. The conformance/highlighter harnesses are currently TypeScript-specific (they call `tsc` and read VS Code's grammar) — point them at your own reference compiler.
+The lexer, CST types, and all three highlighters fall out of step 1; a *dialect* (`.tsx`/`.jsx`, or a markup dialect on [`html.ts`](html.ts)) reuses a base grammar's rules by name in a few lines. The conformance/highlighter harnesses are currently TypeScript-specific (they call `tsc` and read VS Code's grammar) — point them at your own reference compiler.
 
 ## Known differences from the official highlighter
 

TESTING.md

@@ -17,7 +17,7 @@ The suite produces **four kinds of report**, each answering a different question
 The CI-blocking pass/fail checks (no external corpus needed). One runner, one ✓/✗ table, one
 exit code — instead of a dozen scripts with a dozen formats. Covers: sanity / agnostic /
 refactor-guard / issue-cases · conformance (js, tsx, jsx, html) · highlighter guards + RedCMD
-diagnostics + Monarch + HTML embed/lexer · Vue directives/embeds/interpolation · YAML
+diagnostics + Monarch + HTML embed/lexer · YAML
 issue-12 + depth-witnesses · the generative **scope≡role** check + the gap-ledger selftest +
 `--check`. `node test/check.ts <substr>` runs a subset (e.g. `… yaml`).
 
@@ -64,7 +64,7 @@ Neither subsumes the other. `check` (self-consistency) does **not** replace the
 
 ## 4. Bench — on demand
 
-`npm run bench:perf`, `bench:html-official`, `bench:vue-*`, `bench:issues` (the README bug ledger),
+`npm run bench:perf`, `bench:html-official`, `bench:issues` (the README bug ledger),
 `gate:treesitter`, `compat`. Informational — perf, official-comparison detail, repo-compat. Not gates.
 
 ---