v4.7.3 — R1's acceptance row says nothing asserts it

The first answer from walking the eleven requirements that have no acceptance
row. R1 — one living spec per product — is asserted by nothing: no declared
check, no script that refuses on an ambiguous or unreachable spec home, and
none of validate-spec.py's 53 diagnostic codes. product.spec_home is declared
in config.json and never read back, which makes R1 the requirement most exposed
to the thing it exists to prevent — two allocators both handing out R42.

The row records that, rather than leaving the requirement absent from the table
and indistinguishable from one nobody has looked at yet. The work to fix it is
B14; the row points there.

Recording it exposed a defect in the view, not fixed here: "Requirements with
no test" counts requirements with a ROW, not requirements with a VERIFIER, so
writing an honest "nothing asserts this" moved the count 11 to 10 while nothing
became verified. Telling the truth made the dashboard look better, which is
backwards, and the tile should count what is asserted rather than what is
written down.