Consolidate D&D entity documentation

docs/internal/dnd.md

@@ -50,7 +50,10 @@ such as a catalog, registry, grounding projection, or candidate collection are
 local only when that module needs them. New extractor content uses its feature
 subtree, while families with both extraction and normalization content use their
 `extract` and `normalize` subtrees. Shared visual-provenance fragments use
-the `common-dnd-` prefix.
+the `common-dnd-` prefix. Production lane code belongs with its D&D codec,
+extractor, normalizer, and validator packages; registry projections and
+identity helpers remain in their owning entity packages rather than in a
+consumer lane.
 
 The owning module’s manifest is the source of truth for which local and shared
 assets are selected, their mount paths, their message order, cache controls,
@@ -83,7 +86,7 @@ source. Deployment profile selection is documented in
 
 The transcript assets have distinct consumers. Scene chunking consumes the
 complete-session `common-dnd-transcript-full.md`; extraction prompts consume
-the current-chunk `common-dnd-transcript-chunk.md`; and NPC and location
+the current-chunk `common-dnd-transcript-chunk.md`; and NPC, location, and item
 normalization consume `common-dnd-transcript-windows.md` alongside their
 candidate collections. Player, party, glossary, and compatible campaign
 references provide disambiguating context, not evidence. Reference material is
@@ -141,17 +144,16 @@ producer provenance; consumers resolve the handed-off artifact into an
 immutable, validated projection for each operation. External files are checked
 during preparation, while generated artifacts are resolved at the handoff.
 
-NPC registries are names-only grounding projections: they may canonicalize
-actors for spells and combat turns and are required for NPC occurrences, but
-they do not supply evidence. Scene-description registries are eligibility-only
-projections: they retain the current chunk’s classification data, not scene
-prose or evidence, and exist to route combat extraction. Enemy-event extraction
-also projects combat turns to `actor` and `turn_kind` and filters NPC
-occurrences to `combat_opponent` names and kinds. Location registries project
-ordered `{id, name}` pairs to location-occurrence extraction and normalization;
-exact ID/name matching keeps same-name locations distinguishable. These compact
-projections, like NPC grounding, are source-free guidance and never event
-evidence.
+NPC, location, and item registries project ordered, source-free `{id, name}`
+pairs to their respective occurrence extractors and normalizers. Exact ID/name
+matching preserves every identity the registry recognizes, including same-name
+locations with distinct source anchors. The NPC registry additionally supplies
+names-only actor grounding to spells, combat turns, and enemy events.
+Scene descriptions are eligibility-only projections: they retain current-chunk
+classification data, not scene prose or evidence, and exist to route combat
+extraction. Enemy-event extraction also projects combat turns to `actor` and
+`turn_kind` and filters NPC occurrences to `combat_opponent` names and kinds.
+These projections are guidance only and never event evidence.
 
 ## Lane-Specific Rules
 
@@ -161,9 +163,9 @@ shared helper changes.
 | Lane | Intentional behavior |
 | --- | --- |
 | Spells | May use a spell-catalog overlay and optional NPC grounding; the catalog validator supplies domain-specific semantic checks. |
-| NPCs | Does not consume an NPC registry. Its normalizer is the LLM-assisted reconciliation exception described above. |
+| NPC registry | Does not consume an NPC registry. Its normalizer is the LLM-assisted reconciliation exception described above. |
 | Combat turns | Requires a scene-description artifact. It calls the LLM only for an exact `combat` classification; exact non-combat classifications return an accepted empty result, while missing or mismatched classifications return an empty result with a bounded warning. Optional NPC grounding never becomes evidence. |
-| Item occurrences | Uses campaign context for disambiguation but has no NPC-registry or scene-description dependency. |
+| Item occurrences | Requires the normalized item registry for exact ID/name grounding at extraction and normalization. Campaign context may disambiguate, but the registry never becomes occurrence evidence. |
 | Item registry | Produces source-grounded item types and unique designations. Its LLM-assisted reconciliation is proposal-only, preserves distinct currency denominations and item types, and does not create per-instance identities. |
 | NPC occurrences | Requires the normalized NPC registry at extraction and normalization, using it for canonical actor grounding only. |
 | Scene descriptions | Produces the classifications consumed by combat routing; it does not consume an NPC registry or provide evidence for combat artifacts. |