Added a location block to the data package

docs/internal/briefing.md

@@ -16,7 +16,7 @@ Inputs:
 - resolved report definition, generation time, timezone, and valid period
 - forecast bundle with source provenance and warnings
 - derived daily or period summaries where required
-- configured units and timezone
+- configured units, timezone, and descriptive location context
 
 Outputs:
 
@@ -34,6 +34,8 @@ Outputs:
 
 The package receives configured units and timezone from the app layer. Daypart
 configuration is consumed by `internal/forecast` before briefing builders run.
+Configured `location` values are prompt context only; Weather API
+`sourceLocationId` and `sourceLocation` remain source provenance.
 
 ## External Adapters Used
 
@@ -74,6 +76,6 @@ Inspect:
 
 - Briefings contain structured weather facts and source context.
 - Common metadata includes RunID, report ID, prompt ID, valid period, source
-  provenance, source hashes, and source warnings.
+  provenance, source hashes, source warnings, and configured prompt location.
 - LLM prompt input packaging and Scriptorium execution remain outside this
   boundary.

docs/internal/prompt-input.md

@@ -18,8 +18,8 @@ Outputs:
 
 - `promptinput.Package` containing schema version, RunID, report metadata,
   briefing content, Recent Changes, and source warnings. Briefing content
-  includes discussion key messages and short/long-term AFD narratives when the
-  Weather API provides them.
+  includes configured location context, discussion key messages, and
+  short/long-term AFD narratives when the Weather API provides them.
 - optional JSON file written by `promptinput.Save`
 
 ## Boundaries
@@ -30,8 +30,8 @@ Outputs:
 
 ## Config Fields Used
 
-None directly. Config-derived values are already present in briefing metadata
-before this package runs.
+None directly. Config-derived values, including prompt location context, are
+already present in briefing metadata before this package runs.
 
 ## External Adapters Used
 

docs/internal/state.md

@@ -66,8 +66,8 @@ valid-period start date for JSON artifacts, and the RunID.
 ```
 
 Metadata is stored beside briefing snapshots and links the briefing, data
-package, preflight, and report paths. Report listing walks metadata files under
-the snapshots directory.
+package, preflight, report paths, and configured prompt location. Report
+listing walks metadata files under the snapshots directory.
 
 ## Prior Lookup