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.