chore(vale): move VALE_VERSION to 3.22.0 and regenerate the vocabulary

The pin bump in #368 left VALE_VERSION at 3.21.0, which is what
engine-version-consistency fails on. The vocabulary re-derived against
the 3.22.0 binary changes only in its version stamp: no operand, prefix
or divergence moved. The v3.21.0...v3.22.0 tree adds no
internal/lint/<format>.go, so no tier row moves either; the docblock on
the tier table records the check and points at what did change.

Author: theCodeDrift

packages/cli/src/generated/vale-vocabulary-report.md

@@ -1,10 +1,10 @@
-# Vale 3.21.0 vocabulary: divergence report
+# Vale 3.22.0 vocabulary: divergence report
 
 GENERATED FILE — DO NOT EDIT. Produced by `pnpm generate:vale-schema`
 alongside `vale-vocabulary.ts`.
 
 Every value in the vocabulary is the recorded answer of the vendored Vale
-3.21.0 binary. This file is what the binary said that its own
+3.22.0 binary. This file is what the binary said that its own
 documentation does not, in both directions. A generator that dropped these
 would be quietly deciding which of the two to believe.
 
@@ -28,25 +28,25 @@ the worse failure.
 
 ### `scope: meta`
 
-Vale 3.21.0 documents this operand and it never fired, on any fixture probed (.md).
+Vale 3.22.0 documents this operand and it never fired, on any fixture probed (.md).
 
 **Consequence.** It is omitted from the vocabulary, so `verify` rejects it. A rule written from the documentation would otherwise load, run, and match nothing, with no error reported anywhere.
 
 ### `scope: meta.class.title`
 
-Vale 3.21.0 documents this operand and it never fired, on any fixture probed (.md).
+Vale 3.22.0 documents this operand and it never fired, on any fixture probed (.md).
 
 **Consequence.** It is omitted from the vocabulary, so `verify` rejects it. A rule written from the documentation would otherwise load, run, and match nothing, with no error reported anywhere.
 
 ### `scope: frontmatter`
 
-This operand fired and Vale 3.21.0 documents it nowhere.
+This operand fired and Vale 3.22.0 documents it nowhere.
 
 **Consequence.** It is included in the vocabulary. It is also the standing counterexample to trusting the candidate list: a real operand nobody proposes is simply absent, and the schema then rejects a rule the binary honors.
 
 ### `scope: frontmatter.title`
 
-This operand fired and Vale 3.21.0 documents it nowhere.
+This operand fired and Vale 3.22.0 documents it nowhere.
 
 **Consequence.** It is included in the vocabulary. It is also the standing counterexample to trusting the candidate list: a real operand nobody proposes is simply absent, and the schema then rejects a rule the binary honors.
 

packages/cli/src/generated/vale-vocabulary.ts

@@ -6,7 +6,7 @@
  * `scripts/generate-vale-schema.ts`, and its header explains what each value
  * below was measured with and what it is worth.
  *
- * Derived against Vale 3.21.0. Every value here is the recorded answer
+ * Derived against Vale 3.22.0. Every value here is the recorded answer
  * of that binary to a rule the generator wrote and ran; nothing is transcribed
  * from documentation. Where the binary and the documentation disagree, the
  * disagreement is in `vale-vocabulary-report.md` rather than dropped.
@@ -15,7 +15,7 @@
  */
 
 /** The binary this vocabulary was derived from. */
-export const VALE_VOCABULARY_VERSION = "3.21.0";
+export const VALE_VOCABULARY_VERSION = "3.22.0";
 
 /**
  * Vale's check types, self-enumerated: an unknown `extends` makes the binary
@@ -197,7 +197,7 @@ export const VALE_SCOPE_PREFIXES = [
 ] as const;
 
 /**
- * Where Vale 3.21.0 and its documentation disagree.
+ * Where Vale 3.22.0 and its documentation disagree.
  *
  * Carried in the artifact rather than only in the report, so that a consumer
  * can render them and a reviewer cannot miss them in a diff.
@@ -206,26 +206,26 @@ export const VALE_DIVERGENCES = [
   {
     subject: "scope: meta",
     finding:
-      "Vale 3.21.0 documents this operand and it never fired, on any fixture probed (.md).",
+      "Vale 3.22.0 documents this operand and it never fired, on any fixture probed (.md).",
     consequence:
       "It is omitted from the vocabulary, so `verify` rejects it. A rule written from the documentation would otherwise load, run, and match nothing, with no error reported anywhere.",
   },
   {
     subject: "scope: meta.class.title",
     finding:
-      "Vale 3.21.0 documents this operand and it never fired, on any fixture probed (.md).",
+      "Vale 3.22.0 documents this operand and it never fired, on any fixture probed (.md).",
     consequence:
       "It is omitted from the vocabulary, so `verify` rejects it. A rule written from the documentation would otherwise load, run, and match nothing, with no error reported anywhere.",
   },
   {
     subject: "scope: frontmatter",
-    finding: "This operand fired and Vale 3.21.0 documents it nowhere.",
+    finding: "This operand fired and Vale 3.22.0 documents it nowhere.",
     consequence:
       "It is included in the vocabulary. It is also the standing counterexample to trusting the candidate list: a real operand nobody proposes is simply absent, and the schema then rejects a rule the binary honors.",
   },
   {
     subject: "scope: frontmatter.title",
-    finding: "This operand fired and Vale 3.21.0 documents it nowhere.",
+    finding: "This operand fired and Vale 3.22.0 documents it nowhere.",
     consequence:
       "It is included in the vocabulary. It is also the standing counterexample to trusting the candidate list: a real operand nobody proposes is simply absent, and the schema then rejects a rule the binary honors.",
   },

packages/cli/src/rules/capabilities.ts

@@ -209,7 +209,7 @@ export const AST_GREP_TSX_SPLIT: Readonly<
  * Pinned against the binary by `test/vale-vendor-contract.test.ts`
  * ("engine capabilities" → "reports the pinned version").
  */
-export const VALE_VERSION = "3.21.0";
+export const VALE_VERSION = "3.22.0";
 
 /**
  * Which tier Vale routes an extension to.
@@ -271,6 +271,19 @@ 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.
  *
+ * 3.21.0 → 3.22.0 LEARNED NO FORMAT. Every row was re-probed against the
+ * 3.22.0 binary and none moved. The v3.21.0...v3.22.0 tree adds no
+ * `internal/lint/<format>.go` (its additions there are two `_test.go` files);
+ * `md.go`, `mdx.go`, `html.go`, `dita.go`, `code.go` and `metadata.go` change
+ * in what they do with a file, not in which files reach them. What did move
+ * is beside this table: an empty `BasedOnStyles` in a rule's `.vale.ini`
+ * clears every earlier matcher's settings for the file (see
+ * `src/schemas/vale-config.ts`, which now refuses the key, and migration
+ * 0008), a negated inline scope blanks the element's text out of its block,
+ * a `[formats]` key may be a file name or glob, and `lint.go`'s directory walk
+ * now skips the `StylesPath` tree unless a path inside it is named. All of it
+ * is pinned in `test/vale-vendor-contract.test.ts`.
+ *
  * 3.20.0 → 3.21.0 LEARNED ONE FORMAT, AND THE SOURCE CHECK IS WHAT FOUND IT.
  * Every existing row was re-probed against the 3.21.0 binary and none moved.
  * The v3.20.0...v3.21.0 tree adds `internal/lint/notebook.go` and routes

packages/cli/test/reconcile-marker.test.ts

@@ -86,7 +86,7 @@ describe("recording a rules reconciliation", () => {
     expect(rules?.reconciledTo).toBe(version);
     // Engine versions are the input a later differential needs. Recorded here
     // and nowhere else, so an upgrade cannot silently refresh them.
-    expect(rules?.engines).toEqual({ sg: "0.45.3", vale: "3.21.0" });
+    expect(rules?.engines).toEqual({ sg: "0.45.3", vale: "3.22.0" });
   });
 
   it("reports the marker through info", async () => {