Document logical prompt profile configuration

docs/internal/app-orchestration.md

@@ -7,7 +7,10 @@ notification ordering after the CLI has parsed arguments and loaded configuratio
 
 `GenerateDetailed` resolves one of the four report definitions, initializes an
 optional debug root, and inspects the exact Promptkit prompt/profile before it
-collects weather or writes managed state. It then builds facts and modules,
+collects weather or writes managed state. A configured global profile selects
+every report in the action; otherwise the exact prompt selects its default
+logical profile. Inspection keeps only the selected profile ID and effective
+backend/model needed by the project-owned execution contract. It then builds facts and modules,
 saves the YAML data package, persists preparation metadata from the executor
 callback, executes the prepared prompt, saves execution provenance and raw
 output, validates generated text, renders Markdown, and optionally copies or
@@ -25,8 +28,8 @@ persists raw output and execution provenance but does not render a report.
 
 `RunBatchDetailed` constructs a single debug writer and uses the request's
 single executor. Before collection it inspects Today, Tomorrow, and Daily for
-morning, or Tomorrow and Daily for evening, deduplicating effective profile
-inspection. It then collects once, plans eligible Daily dates, and calls the
+morning, or Tomorrow and Daily for evening, deduplicating inspection of a
+shared selected profile. It then collects once, plans eligible Daily dates, and calls the
 same prompt-generation core sequentially for each planned report. Per-report
 notification is suppressed; a failed report does not stop later reports.
 

docs/internal/promptkit-adapter.md

@@ -4,10 +4,18 @@
 The CLI maps `promptkit` configuration to a `PromptExecutorConfig` and constructs one executor
 per action. Promptkit dependency types do not escape the adapter.
 
-The adapter exposes exact prompt and profile inspection plus prepared execution. It maps Promptkit
-inspection values to project-owned prompt input, output-contract, profile, preparation, execution,
-validation, and optional debug values. It classifies adapter failures without copying provider secrets
-or unbounded response bodies into application errors or normal state.
+The adapter supplies Weatherreporter's embedded prompt, schema, and fallback
+profile filesystems to each engine. Promptkit remains responsible for resolving
+the configured operator profile source, application fallback catalog, and its
+built-in catalog; the adapter does not parse profile YAML, merge sources, or
+probe endpoints.
+
+The adapter exposes exact prompt and profile inspection plus prepared execution.
+It maps Promptkit inspection values to project-owned prompt input,
+output-contract, logical profile identity, effective backend/model,
+preparation, execution, validation, and optional debug values. It classifies
+adapter failures without copying provider secrets or unbounded response bodies
+into application errors or normal state.
 
 The app calls the executor's preparation callback before provider execution to persist safe preparation
 provenance. Completed executions are then persisted as safe execution provenance and raw generated text

docs/internal/report-registry.md

@@ -16,16 +16,19 @@ templates, generation eligibility, compatible prior IDs, default modules, and
 batch eligibility flags. `Resolved` combines that definition with the valid
 period and run metadata for one invocation.
 
-| Report ID | Prompt version | Period policy | Comparison | Registry batch flag | Output copy |
-| --- | --- | --- | --- | --- | --- |
-| `daily` | `1.0.1` | Explicit local civil day | Same valid date | Dynamic Daily inclusion is app-owned | `daily.md` |
-| `today` | `1.0.1` | Selected or current local civil day | Same valid date | Morning | `today.md` |
-| `tomorrow` | `1.0.1` | Next local civil day | Same valid date | Evening | `tomorrow.md` |
-| `hourly` | `1.0.1` | Rolling six-hour interval | Rolling window | — | `hourly.md` |
+| Report ID | Prompt version | Default profile | Period policy | Comparison | Registry batch flag | Output copy |
+| --- | --- | --- | --- | --- | --- | --- |
+| `daily` | `1.1.0` | `weather-balanced` | Explicit local civil day | Same valid date | Dynamic Daily inclusion is app-owned | `daily.md` |
+| `today` | `1.1.0` | `weather-balanced` | Selected or current local civil day | Same valid date | Morning | `today.md` |
+| `tomorrow` | `1.1.0` | `weather-balanced` | Next local civil day | Same valid date | Evening | `tomorrow.md` |
+| `hourly` | `1.1.0` | `weather-light` | Rolling six-hour interval | Rolling window | — | `hourly.md` |
 
 Each report pairs its ID and prompt version with matching template and schema
 IDs. Exact template fields and schema assets belong to [report templates](../templates.md)
-and [generated-text internals](generatedtext.md).
+and [generated-text internals](generatedtext.md). Prompt assets own default
+profile selection; the registry deliberately stores no provider setting. The
+[Promptkit integration guide](../integrations/promptkit.md) owns profile
+definitions and resolution.
 
 All valid periods are half-open.
 

docs/internal/state.md

@@ -34,8 +34,10 @@ runs never write V1 records.
 Prompt preparation and execution records are validated on both save and load.
 They require exact report/prompt identity, complete timing, internally
 consistent provenance, and status-appropriate validation or bounded classified
-errors. Completed execution provenance keeps Promptkit's run identity distinct
-from the Weatherreporter run identity.
+errors. Completed preparation and execution provenance retain the selected
+logical profile ID and resolved backend/model, but never profile endpoints or
+credentials. Completed execution provenance keeps Promptkit's run identity
+distinct from the Weatherreporter run identity.
 
 For a completed prompt run, the execution record is atomically replaced after
 each downstream artifact is saved. Its path set therefore records the raw and