Document logical prompt profile configuration

docs/operations.md

@@ -25,6 +25,30 @@ Distributor notification is attempted. `--out` writes an extra operator copy;
 it never changes the managed report or upload source. A successful generate
 command prints its summary to stdout unless `--quiet` is used.
 
+## Local Prompt Profile Override
+
+Hourly normally selects the embedded `weather-light` profile. To use a local
+OpenAI-compatible model without changing prompts or application code, copy
+[weather-light-local-profile.yml](../examples/weather-light-local-profile.yml),
+set its `endpoint` and `model` for the local server, and configure the copy as
+`promptkit.profile_file`. The profile file's `weather-light` definition
+completely replaces the embedded definition; it does not affect a report that
+selects another profile ID.
+
+For example, install the profile file at a known absolute path and set:
+
+```yaml
+promptkit:
+  profile_file: /etc/weatherreporter/weather-light-local-profile.yml
+```
+
+Prompt inspection occurs before weather collection. A malformed profile file,
+missing required credential, or unsupported selected backend stops the command
+before collection. A reachable profile can still fail later if its local model
+endpoint is unavailable; Weatherreporter does not switch to a remote profile.
+See the [configuration reference](config.md) for field definitions and the
+[troubleshooting guide](troubleshooting.md) for recovery.
+
 ## Optional Prompt Debug Capture
 
 Use `--llm-debug-dir` only when content-rich prompt diagnostics are required:
@@ -174,5 +198,7 @@ first response; retain it until the failure is understood.
   not publish them unintentionally.
 - Weatherreporter uses one configured Weather API endpoint and local workspace
   state.
+- Promptkit profile resolution does not discover local endpoints or fail over
+  between local and remote profiles.
 - It does not provide automatic resume, cleanup, archival, remote state, daemon
   operation, or automatic storm monitoring.