the governance report is removed, not relocated

Superseding the relocation decided earlier the same day. The report was moved under prompts/ as a round record; the maintainer's ruling is that it can go away, and it has. Nothing of it survives, including the PROMPT.md recording that its dispatch was never preserved.

What it contained is elsewhere and current. The checker meaning statements are the docstrings in checkers/ and the table in checkers/README.md; the resource budgets and the permissive path-gate default were confirmed as decisions below; the specification-path enumeration is tests/path_gate.py, which is the source of truth and was never the report; and its four open questions were answered before it was removed. It was a snapshot of a design that has since moved, kept at the root where it read as current.

One registered claim depended on it and was repointed first. simplex.rational-points-sum-to-one named the report as both its verification and human register. Its documents are now checkers/README.md and CONTRIBUTING.md — live, maintained surfaces rather than a dated snapshot, which is what a claim's dual register should have been pointing at. No claim changed class and no statement of record moved, and the registry gate still adjudicates it. This is the second time a deletion at the root has come close to orphaning a registered claim's documentation, the setup report being the first; the pattern is that root-level reports get cited as registers because they are the only prose describing the machinery.

**The round's attribution survives in PROVENANCE.md** and records that no round record exists. That is a real loss of provenance, accepted deliberately: the dispatch was already unrecoverable, so what was lost is a report whose content is superseded, not a trail anyone can follow.