chore(vale): upgrade to Vale 3.24.0

Author: github-actions[bot]

.changeset/vale-3-24-0.md

@@ -0,0 +1,5 @@
+---
+"@taskless/cli": patch
+---
+
+Update the bundled Vale to 3.24.0.

packages/cli/package.json

@@ -92,11 +92,11 @@
     "@ast-grep/cli-win32-arm64-msvc": "0.45.3",
     "@ast-grep/cli-win32-ia32-msvc": "0.45.3",
     "@ast-grep/cli-win32-x64-msvc": "0.45.3",
-    "@taskless/vale-darwin-arm64": "3.23.0-20260930045834",
-    "@taskless/vale-darwin-x64": "3.23.0-20260930045834",
-    "@taskless/vale-linux-arm64": "3.23.0-20260930045834",
-    "@taskless/vale-linux-x64": "3.23.0-20260930045834",
-    "@taskless/vale-win32-arm64": "3.23.0-20260930045834",
-    "@taskless/vale-win32-x64": "3.23.0-20260930045834"
+    "@taskless/vale-darwin-arm64": "3.24.0-20261005234241",
+    "@taskless/vale-darwin-x64": "3.24.0-20261005234241",
+    "@taskless/vale-linux-arm64": "3.24.0-20261005234241",
+    "@taskless/vale-linux-x64": "3.24.0-20261005234241",
+    "@taskless/vale-win32-arm64": "3.24.0-20261005234241",
+    "@taskless/vale-win32-x64": "3.24.0-20261005234241"
   }
 }

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

@@ -1,10 +1,10 @@
-# Vale 3.23.0 vocabulary: divergence report
+# Vale 3.24.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.23.0 binary. This file is what the binary said that its own
+3.24.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.23.0 documents this operand and it never fired, on any fixture probed (.md).
+Vale 3.24.0 documents this operand and it never fired, on any fixture probed (.md).
 
 **Consequence.** It is omitted from the vocabulary, so `validate` 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.23.0 documents this operand and it never fired, on any fixture probed (.md).
+Vale 3.24.0 documents this operand and it never fired, on any fixture probed (.md).
 
 **Consequence.** It is omitted from the vocabulary, so `validate` 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.23.0 documents it nowhere.
+This operand fired and Vale 3.24.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.23.0 documents it nowhere.
+This operand fired and Vale 3.24.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.23.0. Every value here is the recorded answer
+ * Derived against Vale 3.24.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.23.0";
+export const VALE_VOCABULARY_VERSION = "3.24.0";
 
 /**
  * Vale's check types, self-enumerated: an unknown `extends` makes the binary
@@ -199,7 +199,7 @@ export const VALE_SCOPE_PREFIXES = [
 ] as const;
 
 /**
- * Where Vale 3.23.0 and its documentation disagree.
+ * Where Vale 3.24.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.
@@ -208,26 +208,26 @@ export const VALE_DIVERGENCES = [
   {
     subject: "scope: meta",
     finding:
-      "Vale 3.23.0 documents this operand and it never fired, on any fixture probed (.md).",
+      "Vale 3.24.0 documents this operand and it never fired, on any fixture probed (.md).",
     consequence:
       "It is omitted from the vocabulary, so `validate` 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.23.0 documents this operand and it never fired, on any fixture probed (.md).",
+      "Vale 3.24.0 documents this operand and it never fired, on any fixture probed (.md).",
     consequence:
       "It is omitted from the vocabulary, so `validate` 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.23.0 documents it nowhere.",
+    finding: "This operand fired and Vale 3.24.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.23.0 documents it nowhere.",
+    finding: "This operand fired and Vale 3.24.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.23.0";
+export const VALE_VERSION = "3.24.0";
 
 /**
  * Which tier Vale routes an extension to.