Reconcile ADR 0009 "controllers reuse the caw loop surface" with the shipped caw verify / caw tournament namespaces

[qinhaihong-red]

What to build

A decision plus a consistency reconciliation across ADR, CLI, and docs — no behavioral change to the controllers.

ADR 0009's Consequences state that further Pattern Controllers "reuse the Run Group layout, the membership mirror, and the caw loop surface." However, #109 (PR #109) shipped the adversarial-verification and tournament controllers as separate top-level command families — caw verify and caw tournament, each exposing run / resume / report / init mirroring caw loop — rather than under the caw loop namespace.

Decide what "surface" was meant to mean and make the three artifacts consistent with that decision:

• Reading A — "surface" = the command shape + Run Group semantics. The per-controller namespaces (caw verify, caw tournament) are correct; ratify them and amend ADR 0009's wording so "surface" unambiguously means the run/resume/report/init shape and the Run Group layout/membership reuse, not the literal caw loop namespace.
• Reading B — "surface" = the literal caw loop namespace. The controllers should share one command surface; consolidate caw verify / caw tournament under the agreed namespace and update the CLI accordingly.

This surfaced during the Wave 1 merge (#109) and the follow-up README reconciliation (#111), where the README's CLI table and "Run Groups and pattern controllers" section had to document the as-shipped caw verify / caw tournament commands.

Acceptance criteria

• The decision is recorded in ADR 0009 (amended Consequences and/or a Decision note) — controllers share one command namespace vs. per-controller namespaces — and "surface" is defined unambiguously.
• The shipped CLI matches the decision: either ADR 0009 is updated to ratify the separate caw verify / caw tournament namespaces, or the controllers are consolidated under the agreed namespace.
• README.md (the CLI commands table and the "Run Groups and pattern controllers" section) matches the final command surface.
• No behavioral change to the controllers themselves (loop-until-done, adversarial verification, tournament); this is a CLI-surface and documentation reconciliation only.

Blocked by

None - can start immediately. (Surfaced during the Wave 1 merge of #109 and the #111 README reconciliation; relates to #17 and ADR 0009.)