docs: the twelve questions the specification does not answer, and code does

[sinkog]

Everything closed so far has been a defect — the document says something wrong, or an implementation does not do what it says.

What is left is a different kind, and lumping the two together would hide it:

Places where the specification says nothing, something had to happen, and whatever the first implementation did became the answer. Nobody chose it. It is not written down. It is load-bearing.

In at least three of the twelve, the two implementations answered differently and no vector could see it.

The list, with what was measured

	question	measured
D-1	does scalar_type constrain or describe?	never read during validation, in either implementation
D-2	absent optional position	Go removes the node, Rust materializes null
D-3	may an instance author a primitive?	one vector replaces the declaration; no rule stated
D-4	origin of an injected default	takes the enclosing origin — a value the YAML did not contain is recorded as yaml-authored
D-5	is access a grammar or a shape?	operations checked; nothing inside them
D-6	what characters may a name contain?	a child named a.b has no address that resolves — INV-040 is false for it
D-7	which YAML dialect?	tags and !!binary are whatever each library does
D-8	are stages and codes normative?	they exist only in the fixtures; §8 lists none
D-9	INV-032 in a language that cannot express it	stated as a type-system property Go cannot satisfy
D-10	what does the mapping gate promise?	matches INV-nnn tokens, never reads MUST
D-11	resource budgets	none, at any entry point
D-12	does make release implement INV-045?	it does not compute or verify the subject

Each entry states the question, what happens today, whether that is a decision or an accident, the options with what each costs, and what it blocks.

None is fixed by writing more code. They are settled by choosing — and then by a vector that holds both implementations to the choice.

Two that belong together

D-5 (access has described value domains and no enforced grammar) is the same shape of question as the first audit's F-08 (contract is required to be enforced and nothing evaluates it).

Deciding them separately will produce two different answers to one question.

Also corrected

README called check_spec_vectors.py "negative-tested". Nothing under tests/ references it. It now says what the tool actually checks.

---

make ci passes.