Consolidate D&D entity documentation

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

@@ -78,9 +78,14 @@ result with retry or fallback diagnostics. Currency denominations, materially
 different item types, and merely nearby objects remain distinct. Source
 references establish registry provenance, not evidence for later artifacts.
 
-## Publication
+## Consumers and publication
 
-The registry is a selectable D&D artifact. See
-[Configuration](../config.md#production-module-keys) for module keys and
-validator chains, and the [JSON output contract](json-output.md) for
-publication. It does not yet define a consumer handoff contract.
+`dnd/item-occurrences` requires one approved item registry through its
+`item_registry` reference slot for both extraction and normalization. Its
+consumer receives only an ordered, source-free `{id,name}` projection; the
+registry’s source references are never occurrence evidence. Unknown IDs and
+mismatched pairs are rejected by the occurrence contract. See the
+[item-occurrence artifact](dnd-item-occurrence-artifacts.md) for that strict
+wire contract, [Configuration](../config.md#d-d-reference-slots) for binding
+rules and validator selection, and the [JSON output contract](json-output.md)
+for publication.