create-vale-rule: an empty result is not a clean pass; read notices and vale-parse-error findings

[theCodeDrift]

From the 2026-09-21 dogfood notes.

A front-matter parse error used to abort the entire Vale invocation and check returned [] for the run, indistinguishable from a clean pass. 0.11.2 retries around the file Vale blames and reports it as a vale-parse-error finding (ruleId: "vale-parse-error", severity: "error"; .changeset/one-bad-file-zeroes-the-run.md). This is the same family as the 0.11.1 "absent read as clean" fixes.

create-vale-rule.md mentions notices once (the excluded-file advisory) and never mentions vale-parse-error. A rule author who sees no findings has no prompt to check whether Vale actually read the file.

What to do

• Recipe: a short passage in the verify/check section — an empty result is only a pass if notices is empty and no vale-parse-error finding is present; what each of those looks like; topic version bump.
• Cross-check verify-rule.md for the same gap.
• No changeset (recipe only).