Harden item occurrence grounding

docs/integrations/dnd-item-occurrence-artifacts.md

@@ -27,11 +27,13 @@ an earlier normalized `dnd/item-registry` artifact. The registry is immutable
 for an operation and contributes only its ordered `{id,name}` projection after
 the shared evidence message. It is never occurrence evidence.
 
-Each occurrence must use one exact registry ID/name pair. Extraction omits an
-unknown ID or mismatched name rather than creating an item. Normalization
-canonicalizes a recognized name by ID, preserves unknown values for the
-registry validator, and the registry validator rejects unknown or mismatched
-pairs.
+Each occurrence must use one exact registry ID/name pair. An extraction response
+with an unknown ID or mismatched name is rejected as invalid model output; the
+configured pipeline may retry it and never accepts a partial artifact.
+Normalization and validation remain defense in depth for artifacts entering
+through other boundaries: normalization canonicalizes a recognized name by ID,
+preserves unknown values for the registry validator, and the registry validator
+rejects unknown or mismatched pairs.
 
 ## Wire shape
 

docs/internal/dnd.md

@@ -160,6 +160,11 @@ These projections are guidance only and never event evidence.
 The following differences are intentional and should remain explicit when a
 shared helper changes.
 
+Shared D&D text comparison is identified by `dnd.text_comparison.v1`. Any
+semantic change requires an explicit policy-version review for every affected
+identity, mapping, normalization, and validator policy; helper source is not a
+checkpoint fingerprint.
+
 | Lane | Intentional behavior |
 | --- | --- |
 | Spells | May use a spell-catalog overlay and optional NPC grounding; the catalog validator supplies domain-specific semantic checks. |