docs(agents): Prime Directive 14 — CODEOWNERS routes every Tier H surface

The "Behind it" clause said CODEOWNERS routes review requests for
docs/adr/ only, so nothing summons the maintainer on the other Tier H
surfaces. Since .github/CODEOWNERS routes all six Tier H surfaces to the
GOVERNED_APPROVERS accounts and the fleet relay requests their review at
pr_create / pr_ready on a Tier H diff (governedReviewRequests in
scripts/pm/fleet-write/ops.mjs), the clause stated the opposite of the
repository's behaviour. Rewritten in place, net 0 lines, and worded as a
summons rather than a merge barrier: the main ruleset does not require
code-owner review, so the directive itself stays the barrier.

Claude-Session: https://claude.ai/code/session_0165fj9zYfUrt6ckcUgYBD5a
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

AGENTS.md

@@ -294,8 +294,8 @@ localStorage / auth gotchas.
     membership), so ask the maintainer at once to remove a queued PR by hand — then confirm from the remote that it is
     in neither the queue nor `origin/main`. **Draft is no barrier by itself — the barrier is this directive**, and a
     spent approval or a standing record IS the review record, ⛔ not a relaxation. Behind it: the queue guard refuses a
-    governed diff without its tier's record; CODEOWNERS routes review requests for `docs/adr/` only, so nothing summons
-    the maintainer on the other Tier H surfaces; the post-merge audit (`scripts/pm/check-governed-merges.mjs`) lists
+    governed diff without its tier's record; CODEOWNERS routes every Tier H surface to the approvers, and the relay
+    requests them on drafts — a summons, no barrier; the post-merge audit (`scripts/pm/check-governed-merges.mjs`) lists
     every governed-surface merge with its approver and merger — a merger the maintainer does not recognise, any agent
     approval, or a Tier S merge without a PASS record is a seat violation, filed and rolled back. No seat judges this.