Merge the docs and agent Vale configs into one at the repo root

The docs had a Vale config under docs/utils/vale, and the review agent and
the agents-vale check had their own under .opencode/vale. They pinned the
same style packages separately, and nothing pointed a reader from one to
the other.

There's now one config, .vale.ini at the repo root, with the local styles
and vocabulary under .vale/styles. Markdown in general gets the ai-tells
rules and four Google ones, and docs/content gets the docs' full set on top.
The docs lint exactly as before, under both the Vale the flake checks use
and the current release. The Hugo token and block ignores move to the
general section, because Vale 3.14 doesn't apply them from a path-scoped
one.

The section globs match paths relative to the repo root, so the Vale
checks now lint from there, and live in nix/vale.nix rather than
nix/docs.nix. The review workflow takes the config from main, like the
rest of the reviewer's setup, so a PR can't change how its review is
linted.

Signed-off-by: Nic Cope <nicc@rk0n.org>

Author: negz

.agents/skills/writing-style/SKILL.md

@@ -351,15 +351,15 @@ Google developer documentation style run alongside them: `Passive`,
 `Semicolons`, `ExcessiveClaims`, and `Anthropomorphism`. The rest of that style
 stays off, since it bans first person and "we", which this skill relies on.
 
-`.opencode/vale/.vale.ini` holds that config. Sync its styles once, then lint:
+The config is `.vale.ini` at the repo root. The docs under `docs/content`
+get a stricter set of styles from the same file. Sync the styles once, then
+lint from the repo root, since the config matches paths relative to it:
 
 ```bash
-vale sync --config .opencode/vale/.vale.ini
-vale --config .opencode/vale/.vale.ini path/to/doc.md
+vale sync
+vale path/to/doc.md
 ```
 
-The docs under `docs/` have their own, stricter config, which CI runs.
-
 **Fix what it reports.** Nic compared 16 linter-driven rewrites against the
 originals across two design docs. He preferred the rewrite in 14 and called the
 other two a tie. He never preferred the original. His summary: the edits drive

.github/workflows/review.yml

@@ -119,12 +119,13 @@ jobs:
           persist-credentials: false
 
       # Everything opencode reads as config or instructions comes from main, as
-      # does CONTRIBUTING.md, which the skills defer to. That stops a PR
+      # do the Vale config the agent lints its review with, and CONTRIBUTING.md,
+      # which the skills defer to. That stops a PR
       # editing its own review instructions. PR code the agent runs can still
       # rewrite them mid-review, which the design accepts.
       - name: Install the reviewer's config from main
         run: |
-          for f in .opencode .agents .claude opencode.json opencode.jsonc AGENTS.md CLAUDE.md CONTRIBUTING.md; do
+          for f in .opencode .agents .claude .vale .vale.ini opencode.json opencode.jsonc AGENTS.md CLAUDE.md CONTRIBUTING.md; do
             rm -rf "pr/$f"
             if [ -e "reviewer/$f" ]; then cp -r "reviewer/$f" "pr/$f"; fi
           done

.opencode/agents/review.md

@@ -137,9 +137,8 @@ keep composing the PVC once it exists?
 ```
 
 Fix every error the linter reports on these files. When you've written them
-all, run `vale --config .opencode/vale/.vale.ini` over the directory, after
-`vale sync --config .opencode/vale/.vale.ini` if its styles are missing, and fix
-what it reports too.
+all, run `vale` over the directory from the repo root, after `vale sync` if its
+styles are missing, and fix what it reports too.
 
 ## 5. De-slop the review
 

.opencode/vale/.gitignore

@@ -1,13 +1,39 @@
-StylesPath = styles
+# Vale lints the repo's prose. The docs get the full set of styles. Everything
+# else in markdown, such as the skills and prompts agents load, the review
+# agent's output and design docs, gets the ai-tells rules and a few Google ones.
+StylesPath = .vale/styles
 MinAlertLevel = warning
 Packages = Google, Microsoft, write-good, alex, proselint, https://github.com/tbhb/vale-ai-tells/releases/download/v1.37.0/ai-tells.zip
 
 Vocab = Modelplane
 
 [*.md]
-BasedOnStyles = Google, Microsoft, write-good, Modelplane, Vale, alex, proselint, ai-tells
+BasedOnStyles = ai-tells
+
+# Skip Hugo shortcodes, links, URLs and version numbers. These sit here rather
+# than in the docs section because Vale 3.14 only applies them from a section
+# like this one.
+TokenIgnores = (\(#.*\)),(\]\(),(https?://[^\s)]+),(\!\[),(\d.*px),(\d\.\d\.\d),(\{\{<[^>]+>\}\})
+BlockIgnores = (\{\{<\s*\/?.*>\}\}),(\{\{\<\/\*.*\*\/\>\}\})
 
+# "Implementation" is the precise word in engineering prose, and the plainer
+# alternatives this rule suggests are worse.
+ai-tells.FormalRegister = NO
 
+# Four rules from the Google style. The rest of it stays off, since it bans the
+# first person that review comments and designs use.
+Google.Anthropomorphism = error
+Google.ExcessiveClaims = error
+Google.Passive = error
+Google.Semicolons = error
+
+[docs/content/**/*.md]
+# Undo the settings above that are for agents' prose, so the docs get the styles'
+# own levels.
+ai-tells.FormalRegister = error
+Google.Anthropomorphism = suggestion
+Google.ExcessiveClaims = suggestion
+BasedOnStyles = Google, Microsoft, write-good, Modelplane, Vale, alex, proselint, ai-tells
 
 Vale.Spelling = NO
 write-good.Passive = NO
@@ -55,5 +81,3 @@ alex.ProfanityMaybe = NO
 alex.ProfanityUnlikely = NO
 alex.Suicide = NO
 
-TokenIgnores = (\(#.*\)),(\]\(),(https?://[^\s)]+),(\!\[),(\d.*px),(\d\.\d\.\d),(\{\{<[^>]+>\}\})
-BlockIgnores = (\{\{<\s*\/?.*>\}\}),(\{\{\<\/\*.*\*\/\>\}\})

.opencode/vale/.vale.ini

@@ -0,0 +1,6 @@
+# Packages vale sync downloads. Committed styles live under Modelplane/ and
+# config/ only.
+/*
+!/Modelplane/
+!/config/
+!/.gitignore