vale 1.0.0-beta1

First release. Vale checks the prose in text fields against your style guide with the Vale linter, on every save that validates, and reports what stored content already holds.

• A field opts in under Prose checks in its settings, with a minimum level, a level for any rule, and a profile that .vale.ini sections match. Text and plain text fields can opt in, including fields on paragraphs.
• Checks run as a validation constraint, so forms, JSON:API and REST all apply them. An error stops the save and is marked on the field it came from, with every error in the value listed at once. Warnings and suggestions are shown to the author, and in JSON:API they arrive in meta.vale.
• Markdown is linted as Markdown and HTML as HTML, through a format-to-extension map, so code blocks are not checked as prose.
• With publish_only, drafts save with their errors and only the save that publishes is refused. It follows Content Moderation states.
• Publishing a workspace checks its changes first. workspace_mode blocks the publish on errors, lists the alerts, or skips the check.
• Reports > Prose linting lists the alerts in stored content, with filters by bundle, level and rule, a CSV export, a batch scan and a bulk action. Saves and deletes keep its rows current after the response is sent.
• drush vale:lint checks stored content or a workspace's changes and exits with 1 on an error, so a deploy can depend on it. vale:check, vale:rules and vale:status sit beside it.
• POST /vale/check returns the alerts that saving some text in a field would give, with the sentence around each one. It checks field access, and is rate limited per user and capped across the site.
• drush vale:install downloads the latest Vale release for the machine it runs on and checks it against the release's published checksum.
• The binary and .vale.ini paths are read from settings.php only, because Vale's script rules run code. Results are cached until the text or the styles change.

Known limitations: base fields such as the title and a body's summary are not checked, nor is anything saved without validation, such as a migration. Inside a workspace with publish_only, paragraphs save before their page is refused, so the refused page can leave paragraph revisions behind. Sites that ran a development snapshot need to reinstall the module, because pre-release schema changes have no update path.