Move location registry modules to canonical namespace

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

@@ -25,7 +25,7 @@ Each occurrence has these required fields:
 
 | Field | Contract |
 | --- | --- |
-| `location_id` | Exact ID from the required normalized [location registry](dnd-location-artifacts.md). |
+| `location_id` | Exact ID from the required normalized [location registry](dnd-location-registry-artifacts.md). |
 | `name` | Exact canonical display name for `location_id` in that registry. |
 | `kind` | One of `visited`, `planned`, `recalled`, or `mentioned`. |
 | `source_refs` | One or more current-transcript evidence ranges for this occurrence. |
@@ -71,7 +71,7 @@ complete canonical evidence sequence.
 
 ## Required grounding and evidence
 
-Both extraction and normalization require exactly one `locations` reference of
+Both extraction and normalization require exactly one `location_registry` reference of
 kind `dnd/location-registry`, media type `application/json`, and at most 1 MiB. The
 registry provides identity grounding only: unknown IDs and mismatched ID/name
 pairs are rejected rather than guessed or reassigned. The current transcript is

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

@@ -1,7 +1,7 @@
 # D&D Location Registry Artifact
 
 This contract defines the durable, source-grounded location registry produced
-by `dnd/locations`. It records transcript-established physical places for one
+by `dnd/location-registry`. It records transcript-established physical places for one
 source document; it is not a map, location hierarchy, campaign-wide world
 registry, or location description.
 
@@ -64,12 +64,14 @@ anchors differ, so a generic name does not force distinct places to collapse.
 
 ## Scope, reconciliation, and evidence
 
-Locations are physical or spatial places established by the transcript, such
-as planes, regions, settlements, districts, buildings, rooms, landmarks,
-routes, and geographic features. A generic label is permitted only when it
-identifies a specific place in the transcript. Notarius does not infer an
-unstated place or add hierarchy, coordinates, descriptions, participants, or
-ownership.
+Locations are physical or spatial places established by the transcript with a
+stable proper name or unique in-world designation, such as named planes,
+regions, settlements, districts, buildings, rooms, landmarks, routes, and
+geographic features. Generic, temporary, relative, and descriptive phrases
+such as “the room,” “the bar,” “the hallway,” “outside,” and “upstairs” are not
+registry locations. Capitalization alone does not establish eligibility.
+Notarius does not infer an unstated place or add hierarchy, coordinates,
+descriptions, participants, or ownership.
 
 Normalization first applies deterministic display, evidence, and ID rules. It
 then may use a bounded LLM-assisted proposal to reconcile semantically duplicate
@@ -81,7 +83,7 @@ not evidence for later artifacts.
 ## Consumers and publication
 
 `dnd/location-occurrences` requires one approved location registry through its
-`locations` reference slot. Its prompt receives an ordered source-free `{id,
+`location_registry` reference slot. Its prompt receives an ordered source-free `{id,
 name}` projection and must not treat registry references as occurrence
 evidence. See the [location-occurrence artifact](dnd-location-occurrence-artifacts.md)
 for that contract, [Configuration](../config.md#references-and-ordered-handoffs)

docs/integrations/json-output.md

@@ -77,7 +77,7 @@ than infer a lane schema from its name. The current D&D payload contracts are
 [item events](dnd-item-event-artifacts.md),
 [scene descriptions](dnd-scene-description-artifacts.md), and
 [enemy events](dnd-enemy-event-artifacts.md),
-[locations](dnd-location-artifacts.md), and
+[location registry](dnd-location-registry-artifacts.md), and
 [location occurrences](dnd-location-occurrence-artifacts.md).
 
 ## `manifest.json`