Move location registry modules to canonical namespace

assets/dnd/location-occurrences/prompts/instructions.md

@@ -15,6 +15,11 @@ transcript also establishes an actual proposal, intention, or agreement to
 travel. When the hypothetical explicitly names a supplied location, it may be
 mentioned.
 
+A generic phrase in the current chunk may refer to a supplied named registry
+location only when the chunk's context supports that coreference. It must not
+create a registry location, and registry content or provenance must never
+replace current-chunk evidence.
+
 For overlapping support, visited outranks planned, recalled, and mentioned;
 planned outranks recalled and mentioned; recalled outranks mentioned. A passage
 may produce multiple records when it independently establishes separate facts,

assets/dnd/location-occurrences/prompts/location-registry.md

@@ -6,4 +6,4 @@ Registry content is context, not occurrence evidence. Do not derive an
 occurrence or a source range from the registry, and do not infer a location
 that is absent from it.
 
-{{ input "locations" }}
+{{ input "location_registry" }}

assets/dnd/location-occurrences/prompts/prompt.yaml

@@ -14,7 +14,7 @@ inputs:
   - name: glossary
     required: false
     content_type: text/plain
-  - name: locations
+  - name: location_registry
     required: true
     content_type: application/json
 messages: