Context presents `.abcd/corpus.json` as an existing, seeded validation-corpus list; the naming page says the name is reserved and not yet in the tree

Context presents .abcd/corpus.json as an existing, seeded validation-corpus list; the naming page says the name is reserved and not yet in the tree

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/01-product/02-context.md:47 — "Validation corpus: user-maintained list in .abcd/corpus.json, seeded with:"
• End B: .abcd/development/brief/02-constraints/04-naming.md:80 — "corpus.json, which is reserved here as a name and is not yet in the tree"

The context page, which the platform page names as the canonical validation-corpus source, says the corpus is a user-maintained list in .abcd/corpus.json, seeded with three repositories. The naming page says corpus.json is only a reserved name and not yet in the tree. A list cannot be seeded in a file that does not exist.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 11.