v0.3.0

Makes the shipped Vale setup usable out of the box, and corrects three claims this repo's own docs made about tooling it had not actually run.

Install with /plugin install docs-editing@cadasto.

The linter now works on first run

A seeded vocabulary. /docs-lint-setup used to touch an empty accept.txt, so Vale.Spelling ran against a general dictionary with no project terms and reported ordinary jargon — repo, config, frontmatter, validator, stderr — as misspellings, burying every real style finding underneath. On this plugin's own tree that was 190 spelling alerts. The new references/vocab-accept.txt ships as the seed and leaves 11, all product names and cited proper nouns, which is the category a repo appends for itself.

Entries are case-tolerant regexes ([Cc]onfigs?). Vale.Terms requires a term to appear exactly as listed, so a bare lowercase entry silences the spelling warning and then reports every sentence-initial capital instead — one class of false positive traded for another. A product name still goes in with its exact capitalisation, where that rule enforcing it is the point.

The seed carries no British/American spelling pairs, because Vale's dictionary already accepts both: behaviour, organisation, initialise, licence, and catalogue all pass unaided.

Google.Quotes is off. It enforces American punctuation-inside-quotes while the house style is British, which places the comma or period outside unless it belongs to the quote — so the rule fired on correct prose. Seven error-level false positives on this repo's docs, now zero.

The vocabulary is no longer named after an organisation. Vocab = Cadasto became Vocab = Project, a neutral default a repo can rename; scaffolding no longer creates a Cadasto/ directory in someone else's tree. /docs-lint-setup takes the name as a VOCAB variable used for both the directory and the config value, so the two cannot drift apart.

Corrected claims

Each of these was stated in the docs without the tool having been run. All three are now verified against Vale 3.18.0 and cite that version.

• vale does not warn about an unknown rule name. The docs said it "warns but exits 0". The exit-0 half was right; it produces no output at all — empty stderr — which is exactly what makes a renamed upstream rule dangerous. An unknown style package is the loud case: E100 [loadStyles], exit 2. So a broken Packages = line is caught for you and a broken rule line is not.
• vale sync does not warn about a missing vocabulary directory. It reports success and exits 0. The lint then fails hard with E100 [vocab] … vocabulary not found and exit 2, so the config reads as healthy until someone lints.
• The validator enforces four invariants, not two. README.md claimed two and named two — reference resolution, markdown links, tool grants, and doc sync — while docs/testing.md already said four.

Documentation

Sentence-case headings, answer-first openings, and the rules the reference config escalates to error cleared from this repo's own prose. AGENTS.md no longer pins a version: it read v0.1.1, stale by two releases and a version never released at all. CHANGELOG.md and the git tags own that fact.

Full changelog: v0.2.0...v0.3.0