[github-actions]

The @taskless/vale-* packages are published ahead of what
@taskless/cli pins.

This moves all six pins from 3.24.0-20261005234241 to
3.25.1-20261028215110 — Vale 3.25.1 — and regenerates
pnpm-lock.yaml. The pins move together on purpose: the platform
packages are selected by optional dependency, so a straggler left at
the old version is a different Vale on one platform than on the others.

It also moves VALE_VERSION in capabilities.ts to
3.25.1 and regenerates src/generated/vale-vocabulary.ts
from the new binary, and the workflow ran
engine-version-consistency against the result before pushing. What
this does not carry is judgment: if the contract suites below
report a failure, Vale 3.25.1 changed a measured behaviour,
and that edit, the update ledger, any migration, and the release
note's prose belong in a child pull request. So does a row for each
format reader listed below.

This is the half that reaches a user. Republishing the platform
packages changes nobody's install, because the CLI pins each one
exactly; merging this is what ships the new Vale.

This pull request rolls: if another set is published before it merges,
the branch, title, and body are rewritten to the newer version rather
than a second pull request being opened. Push a commit to the branch
and that stops — the workflow will not force-push over a commit it did
not write.

Measured against Vale 3.25.1

Compared with 3.24.0, which is what main pins. Validate on a pull request this workflow opens waits for a maintainer to approve it, so this section is the check that ran.

Contract suites

All 221 tests in vale-schema-contract and vale-vendor-contract pass against the new binary. No recorded verdict changed.

Format readers upstream added

None under internal/lint/ (diff). No extension can have changed tier without a row that re-probes it.

---

Upstream release notes — 3.25.1

https://github.com/vale-cli/vale/releases/tag/v3.25.1

Changelog

• d7a379da fix: A percent-encoded link target no longer drops a later alert
• d59ad842 fix: A .tsx file is parsed with the TSX grammar
• cafff9f9 fix: A phrase in a rule matches across a line wrap
• f41c1eda fix: Compile the spelling exception pattern once per vocabulary
• 4f013daf feat: Find vale.ini in a project's .config directory
• 9f822e9d docs: Add FLOSS
• a7817766 fix: A tag inside a link's text no longer crashes scope: link
• 8e88d55a test: Guard the casing-and-code scenario on rst2html
• 10744bd6 fix: A wrapped list item or blockquote is placed by runs, not by searching for its text
• b41932c5 fix: A doc-comment mask drops only an alert whose match lies inside it
• 91041463 fix: An alert in a comment is placed by what extraction took off its line
• 1a84507d fix: A sequence match holding inline markup is placed through the block's runs
• 3d89b9e4 fix: An occurrence message's count fills %s as well as %d
• a07aa34c fix: .mjs, .cjs, .mts, and .cts are JavaScript and TypeScript, and a mapped file's grammar comes from the format it is read as
• 82f20fc2 fix(lint): take the tree-sitter grammar from a [formats] mapping when the extension has none (#1204)
• 61cb142a fix: AsciiDoc cross-references without text render as empty links
• cfb21a4c fix: MDX elements that span lines no longer lose later alerts, and a list that takes a non-item no longer panics
• a0fc3a96 fix: MDX reads JSX inside expressions, escapes in attributes, and multiline template literals
• b5b8e429 fix: An unreadable document no longer stops the run, and a package's dropped styles are named
• 25270feb fix: Vocab works in [*], and Vocab = NONE clears inherited vocabularies
• fce33f19 feat: Spelling alerts say when a word is a casing mistake or looks like code
• fb4f161f fix: Vale.Terms finds terms that start or end with punctuation, like C++ and .NET
• 775511b8 feat: YAML vocabularies, and affix flags in vocabularies and rules
• c8fcacf2 feat: The default dictionary knows common technical vocabulary
• 2b345462 docs: remove studio
• c74f4da2 docs: Remove DO