fix(hypatia-rules): align HYP-S005 state_keys with real schema

Seam check against boj-server's STATE.a2ml revealed the canonical state
keys HYP-S005 cites ([external-targets], [issues-fed-back], [field-signal])
don't exist yet — only legacy [dogfooding-status] and [grade-b-status] do.

[grade-b-status] in practice mixes internal capabilities with external
targets (the boj-server audit's six items were all internal), so it cannot
be a trustworthy B-eligibility signal on its own.

Adds a @schema_conventions block naming the canonical sections, notes
which are established vs pending adoption, and preserves [grade-b-status]
as a fallback read with an explicit re-classification caveat.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

hypatia-rules/crg-overclaim-detector.a2ml

@@ -96,28 +96,64 @@ B:
   requires:
     - state_key: "external-targets"
       in_file: ".machine_readable/6a2/STATE.a2ml"
-      reason: "B requires 6+ diverse external targets tested"
+      reason: "B requires 6+ diverse external targets tested (canonical key)"
+      fallback_key: "grade-b-status"
+      fallback_caveat: "legacy key; entries are often internal capabilities and must be re-classified"
     - state_key: "issues-fed-back"
       in_file: ".machine_readable/6a2/STATE.a2ml"
-      reason: "B requires an issues-fed-back pipeline"
+      reason: "B requires an issues-fed-back pipeline (canonical key)"
   evidence_of:
     - "6+ diverse external-target entries, each with identity + date + outcome"
     - "external-issue label in the repo's issue tracker with >=1 closed issue"
     - "feedback log or changelog entry attributing a change to an external target"
   negative_signal:
     - "internal-capability items (QUIC, multinode, etc.) do NOT count as external targets"
+    - "legacy [grade-b-status] entries that describe internal infrastructure must be moved"
 
 A:
   requires_all_of: "B"
   requires:
     - state_key: "field-signal"
       in_file: ".machine_readable/6a2/STATE.a2ml"
-      reason: "A requires real-world external feedback confirming value"
+      reason: "A requires real-world external feedback confirming value (canonical key)"
   evidence_of:
     - "multi-source external usage confirmation (testimonials, third-party writeups, papers citing)"
     - "no harm signal: no unresolved safety / correctness incidents in last 90 days"
 @end
 
+@schema_conventions:
+# Canonical STATE.a2ml section names this rule expects. Repos that pre-date
+# these conventions should migrate. `[grade-b-status]` is retained as a
+# fallback read for B but its entries must be re-classified — the boj-server
+# 2026-04-18 audit demonstrated that internal-capability items under
+# [grade-b-status] do not satisfy v2.0 B ("6+ diverse external targets").
+sections:
+  - name: "[dogfooding-status]"
+    grade: C
+    shape: "key-value of capability -> \"done | in-progress | planned — <evidence>\""
+    established: true
+  - name: "[external-targets]"
+    grade: B
+    shape: "key-value of target-identity -> \"<date> — <test outcome> — <contact or URL>\""
+    established: false
+    notes: "at least 6 diverse entries; targets must be outside the hyperpolymath estate"
+  - name: "[issues-fed-back]"
+    grade: B
+    shape: "key-value of issue-id -> \"<date> — <external reporter> — <resolution>\""
+    established: false
+    notes: "links to closed issues on the repo's tracker carrying an external-reporter label"
+  - name: "[field-signal]"
+    grade: A
+    shape: "key-value of signal-source -> \"<date> — <confirmation type> — <reference>\""
+    established: false
+    notes: "multi-source; e.g. testimonial, third-party writeup, paper citation"
+  - name: "[grade-b-status]"
+    grade: B (legacy)
+    shape: "freeform — mixes internal + external in practice"
+    established: true
+    notes: "superseded by [external-targets]; entries need re-classification per audit"
+@end
+
 @action:
 emit_signal: compliance.finding.new
 message_template: >-