@@ -32,11 +32,26 @@ the property only that tier has, since ordinary prose fires in all of them — s
 a version bump that moves a format between tiers fails there instead of silently
 turning the engine off again.
 
-The recipes now say MDX is not supported _yet_, rather than unsupported: Vale
-3.18.0 parses it natively and a CLI update carrying that Vale is expected to
-bring it. The same release adds a Typst converter, which will move `.typ` out of
-the plaintext tier, so the table carries a standing instruction to re-measure
-every row on a version bump.
+The engine moves to Vale 3.18.0 in the same release, and the table carries a
+standing instruction to re-measure every row on a version bump — so every row
+was re-probed against the new binary rather than carried over. Eight moved.
+`.mdx` gains a native parser and leaves the unsupported tier, so a matcher like
+`[*.{md,mdx}]` — the worked example above — is legitimate again, and `[*.{md,typ}]`
+takes its place as the broken one. `.typ` moved the opposite way: Typst now
+parses through `typst2vast`, an external program this build does not ship, so a
+Typst file is excluded from the run rather than read as prose the way 3.17.1
+read it. `.rmd` and the new `.qmd` and `.myst` are parsed as markup, and `.qml`,
+`.scss` and the new `.qdoc` are comment-aware where they previously fell through
+to plain text.
+
+The `.typ` move is the one that mattered to get right. An extension missing from
+the table is read as prose, which is harmless — but the moment Vale routes it to
+a converter, that same omission is a crash that takes down every Vale rule in
+the run. Bumping the binary without re-measuring would have introduced exactly
+the failure this table exists to prevent, under an extension nobody was
+watching. Re-probing also caught one change the release notes do not mention:
+PHP comment extraction now requires a real `<?php` tag, where 3.17.1 linted a
+bare `//` comment without one.
 
 Two details are load-bearing and were both wrong on the first attempt. Vale
 honours exactly one `--glob` and keeps the last, so the `.taskless/` exclusion
@@ -62,10 +77,10 @@ a remedy.
 The comment tier was reconciled against Vale's own documentation at
 docs.vale.sh/formats/code, which adds `.bsh`, `.csx`, `.pod`, `.py3` and `.sbt`
 once measured. It also documents `.pyi`, `.qml` and `.scss` as comment-aware,
-and on the pinned 3.17.1 a bare non-comment line in each of them lints — so they
-stay in the plaintext tier. That divergence is the argument for probing rather
-than transcribing: the docs describe the current Vale, this build pins an older
-one, and copying the list would have shipped `.scss` as comment-aware and been
-wrong. `.pod` is a reminder of how easily this is misread — it lints Perl
+and on 3.17.1 a bare non-comment line in each of them lints. 3.18.0 makes the
+claim true for `.qml` and `.scss` and still not for `.pyi`, which stays in the
+plaintext tier. That divergence is the argument for probing rather than
+transcribing: the docs describe whatever Vale is current, and copying the list
+would have shipped `.pyi` as comment-aware and been wrong for both builds. `.pod` is a reminder of how easily this is misread — it lints Perl
 comments but not POD blocks, so probing it with `=head1` looks like no support
 at all.
@@ -139,9 +139,9 @@ const CONVERTER_TIER_PREFIX = "converter:";
  *   on a bare non-comment line yields ZERO. A type that fires on both is the
  *   plaintext fallback wearing a code extension.
  * - **plaintext** — a bare line yields a finding. Listed only where the tier is
- *   surprising: `.tex`, `.rmd`, `.mkd` and `.mkdn` all look like markup and are
- *   not. Everything unnamed lands here too, which is why this tier does not
- *   need to be exhaustive.
+ *   surprising: `.tex`, `.mkd` and `.mkdn` all look like markup and are not.
+ *   Everything unnamed lands here too, which is why this tier does not need to
+ *   be exhaustive.
  * - **converter** — a non-zero exit whose output carries `E100` and the
  *   program's name.
  *
@@ -158,22 +158,33 @@ const CONVERTER_TIER_PREFIX = "converter:";
  * plain text today, but the moment Vale routes it to a converter the same
  * omission is a crash that takes down every Vale rule in the run.
  *
- * Vale 3.18.0 is the known incoming bump, and it moves rows in three different
- * directions — which is why "re-measure" is not boilerplate here:
+ * The 3.17.1 → 3.18.0 bump is what that warning looks like in practice. Every
+ * row below was re-probed against the 3.18.0 binary, and eight moved, in three
+ * different directions — which is why "re-measure" is not boilerplate here:
  *
- * - `.mdx` gains a native parser, so it moves `converter:mdx2vast` → `markup`
- *   and becomes supported.
- * - `.typ` gains a parser that shells out to `typst2vast`
- *   (https://docs.vale.sh/formats/typst), so it moves `plaintext` →
- *   `converter:typst2vast`. That is the dangerous direction: today it is read
- *   as prose, and after the bump the same row would crash the run. It also
- *   stays unsupported permanently, since we do not support formats needing an
- *   external program.
- * - MyST, Quarto and QDoc arrive with parsers needing no external program, so
- *   they become genuinely supportable and want `markup` rows once measured.
+ * - `.mdx` gained a native parser: `converter:mdx2vast` → `markup`. It is
+ *   supported now, and `[*.{md,mdx}]` is a legitimate matcher again.
+ * - `.typ` gained a parser that shells out to `typst2vast`
+ *   (https://docs.vale.sh/formats/typst): `plaintext` →
+ *   `converter:typst2vast`. That is the dangerous direction — 3.17.1 read it as
+ *   prose, and the same row on 3.18.0 crashes the run. It stays unsupported
+ *   permanently, since we do not support formats needing an external program.
+ * - `.rmd` gained a real Markdown parser, so it left the "looks like markup and
+ *   is not" list above: `plaintext` → `markup`.
+ * - `.qml` and `.scss` gained parsers that see their comments: `plaintext` →
+ *   `comment`. Vale's docs had claimed both for years; on 3.17.1 the claim was
+ *   measurably false and on 3.18.0 it is true.
+ * - `.qmd` (Quarto) and `.myst` (MyST) measured as `markup`, and `.qdoc` as
+ *   `comment` — QDoc documentation lives in a doc-comment block, so it is
+ *   comment extraction rather than the markup tier a first reading of the
+ *   release notes suggests, and probing it with bare prose reads as no support
+ *   at all. All three are new rows, none of them reachable on 3.17.1.
  *
- * All four are documented as requiring v3.18.0 or later, so none of them is
- * reachable from {@link VALE_VERSION}. Re-probe every row on the bump.
+ * PHP also changed without the release notes saying so: comment extraction now
+ * needs a real `<?php` tag, where 3.17.1 linted a bare `//` comment without
+ * one. The tier did not move, but the probe had to. Re-probe every row on the
+ * next bump, by the discriminating property and by each language's own comment
+ * syntax — a wrong delimiter reads exactly like absent support.
  */
 export const VALE_FORMAT_TIERS: Readonly<Record<string, ValeFormatTier>> = {
   // markup — parsed, the format's own constructs skipped
@@ -183,6 +194,7 @@ export const VALE_FORMAT_TIERS: Readonly<Record<string, ValeFormatTier>> = {
   ".md": "markup",
   ".mdx": "markup",
   ".mdown": "markup",
+  ".myst": "markup",
   ".org": "markup",
   ".qmd": "markup",
   ".rmd": "markup",
@@ -235,11 +247,12 @@ export const VALE_FORMAT_TIERS: Readonly<Record<string, ValeFormatTier>> = {
   ".mkd": "plaintext",
   ".mkdn": "plaintext",
   ".tex": "plaintext",
-  // plaintext HERE, though Vale's own docs list them as comment-tier. The docs
-  // describe the CURRENT Vale; we pin 3.17.1. Measured on the pinned binary a
-  // bare non-comment line lints, which is the plaintext signature. Transcribing
-  // the docs would have shipped these as comment-tier and been wrong for this
-  // build — the case for probing rather than copying.
+  // plaintext HERE, though Vale's own docs list it as comment-tier. Measured on
+  // the pinned 3.18.0 binary a bare non-comment line lints, which is the
+  // plaintext signature. `.qml` and `.scss` sat here for the same reason until
+  // 3.18.0 made the docs true for them; `.pyi` is the row where transcribing
+  // the docs would still ship the wrong tier — the case for probing rather than
+  // copying.
   ".pyi": "plaintext",
   // converter-dependent — Vale supports the format, we ship no converter
   ".adoc": "converter:asciidoctor",
@@ -339,10 +352,12 @@ function groupByConverter(): ValeConverterFormat[] {
  *
  * The blast radius is what makes this worth surfacing at routing time rather
  * than at authoring time: Vale exits 2 with an `E100` runtime error and
- * abandons the run, and `--no-exit` does not suppress it. One `.mdx` file
+ * abandons the run, and `--no-exit` does not suppress it. One `.typ` file
  * caught by a rule's glob takes down the entire Vale pass, including every
- * other rule and every other file — so `[*.{md,mdx}]` is not a slightly wider
- * matcher than `[*.md]`, it is a broken one.
+ * other rule and every other file — so `[*.{md,typ}]` is not a slightly wider
+ * matcher than `[*.md]`, it is a broken one. (`[*.{md,mdx}]` was that example
+ * until 3.18.0 gave MDX a native parser — the membership of this tier is a
+ * property of {@link VALE_VERSION}, and so is the worked example.)
  */
 export const VALE_CONVERTER_DEPENDENT: readonly ValeConverterFormat[] =
   groupByConverter();
 
@@ -385,7 +385,11 @@ describe("recipes state engine reach from the pinned versions", () => {
     // author `.mdx` is unsupported costs them a format Vale reads fine, and
     // telling them `.typ` is readable takes their whole Vale pass down.
     expect(route).toContain("`.mdx` is supported");
-    expect(route).toContain("`.typ`");
+    // `.typ` alone would pass on the converter list rendered above, which names
+    // it whatever the prose says. Pin the hazard sentence instead, so dropping
+    // the warning fails here even while the extension is still mentioned.
+    expect(route).toContain("`.typ` moved the other way");
+    expect(route).toContain("`[*.{md,typ}]`");
   });
 
   it("names ast-grep's languages in rendered create-sg-rule.txt", async () => {
 
@@ -388,8 +388,10 @@ withVale("Vale vendor contract", () => {
  * - **plaintext** is the tier that needs no separating — a bare line fires —
  *   but the entries listed in it do: each names a construct a parser WOULD have
  *   skipped, and the probe asserts Vale lints it. That is the assertion that
- *   `.tex` and `.rmd` are not markup, and it is the one the first hand-written
- *   table got backwards.
+ *   `.tex`, `.mkd` and `.mkdn` are not markup, and it is the one the first
+ *   hand-written table got backwards. It is also the assertion that expires: on
+ *   3.17.1 `.rmd` belonged here, and 3.18.0 gave it a real parser and moved it
+ *   into MARKUP_FIXTURES.
  * - **converter-dependent** is separated from everything by failing.
  *
  * See taskless/cli#151.
@@ -467,12 +469,17 @@ withVale("Vale engine capabilities", () => {
       skipped: "Fine.\n\n```\nsimply\n```\n",
     },
     ".org": { prose: "We simply do it.\n", skipped: "# simply\nFine.\n" },
-    // Native as of 3.18.0. `.mdx` arrived from the converter tier and `.rmd`
-    // and `.qmd` from plaintext, so all three are new claims, not carried over.
+    // Native as of 3.18.0. `.mdx` arrived from the converter tier, `.rmd` from
+    // plaintext, and `.qmd` and `.myst` are new rows — four new claims, none of
+    // them carried over from the 3.17.1 table.
     ".mdx": {
       prose: "We simply do it.\n",
       skipped: "Fine.\n\n```\nsimply\n```\n",
     },
+    ".myst": {
+      prose: "We simply do it.\n",
+      skipped: "Fine.\n\n```\nsimply\n```\n",
+    },
     ".qmd": {
       prose: "We simply do it.\n",
       skipped: "Fine.\n\n```{r}\nsimply <- 1\n```\n",
@@ -498,11 +505,10 @@ withVale("Vale engine capabilities", () => {
   it("reports the pinned version", () => {
     // VALE_VERSION is rendered beside the reach lists in route.txt and
     // create-vale-rule.txt, so it is the attribution for every claim below.
-    // It also gates two of them, in opposite directions: Vale 3.18.0 parses MDX
-    // natively, so a bump past it moves `.mdx` from converter-dependent to
-    // markup — and the same release adds a Typst converter, so it moves `.typ`
-    // from plaintext to `converter:typst2vast`. A bump re-measures the whole
-    // table; these two are only the rows already known to move.
+    // 3.18.0 moved rows in both directions: `.mdx` gained a native parser and
+    // left the converter tier, while `.typ` gained a `typst2vast` converter and
+    // entered it. A bump re-measures the whole table — the fixtures below are
+    // the record of the last time that was done, not a forecast of the next.
     const result = spawnSync(binary as string, ["--version"], {
       encoding: "utf8",
     });
@@ -564,7 +570,7 @@ withVale("Vale engine capabilities", () => {
    * its spelling suggests would have skipped.
    *
    * Vale lints it, which is the whole finding: `.tex` is not TeX to Vale and
-   * `.rmd` is not R Markdown. The mirror image of the markup fixtures — same
+   * `.mkd` is not Markdown. The mirror image of the markup fixtures — same
    * documents, opposite expectation.
    */
   const PLAINTEXT_FIXTURES: Record<string, string> = {
@@ -573,8 +579,9 @@ withVale("Vale engine capabilities", () => {
     ".tex": "% simply in a comment\nFine.\n",
     // Documented by Vale as comment-aware, measured as plaintext on the pinned
     // binary — the construct here is the comment a parser would have skipped.
-    // `.qml` and `.scss` were here until 3.18.0 gave them real parsers, which
-    // is why the tier is re-measured on every bump rather than carried over.
+    // `.qml` and `.scss` were here until 3.18.0 gave them real parsers, and
+    // `.rmd` left for MARKUP_FIXTURES in the same bump, which is why the tier is
+    // re-measured on every bump rather than carried over.
     ".pyi": "# simply\nFine.\n",
   };