Document Promptkit report generation

docs/policy/testing.md

@@ -54,8 +54,8 @@ Use a classical or Detroit-style approach:
 - Test exact collaborator interactions only when the interaction itself is a
   requirement.
 
-Weatherreporter's important seams include clocks, subprocesses, HTTP services,
-Distributor uploads, filesystem roots, environment-backed secrets, and any
+Weatherreporter's important seams include clocks, Promptkit executors, HTTP
+services, Distributor uploads, filesystem roots, environment-backed secrets, and any
 future source of randomness or nondeterminism.
 
 ## Execution Requirements
@@ -73,7 +73,7 @@ package command while iterating and `go test -race ./...` when the risk crosses
 package boundaries.
 
 Tests in the default suite must be deterministic, offline, and independent of
-real credentials. They must not invoke live Weather API, Scriptorium, or
+real credentials. They must not invoke live Weather API, Promptkit providers, or
 Distributor services or depend on other mutable external infrastructure.
 Tests that require live infrastructure must be explicitly opt-in and clearly
 separated from the default suite.
@@ -198,7 +198,7 @@ Each behavior should have a clear test owner:
 - CLI parser tests own arguments, flags, and command construction.
 - Config tests own loading, precedence, defaults, secrets, and validation.
 - Domain tests own weather transformations and invariants.
-- Adapter tests own HTTP, subprocess, and upload boundaries.
+- Adapter tests own HTTP, Promptkit/provider, and upload boundaries.
 - Orchestrator tests own workflow ordering, persistence, partial success, and
   failure propagation.
 - State tests own path derivation, atomic artifacts, lookup, and round trips.
@@ -220,7 +220,7 @@ observation:
 4. Use mocks when the interaction itself is contractual.
 
 Mocks are appropriate for requirements such as uploading exactly once, saving
-metadata before notification, propagating cancellation to Scriptorium, or
+metadata before notification, propagating cancellation to Promptkit, or
 avoiding an external call after an earlier workflow failure. Do not use mocks
 merely to isolate every object or reproduce the implementation's call graph.
 
@@ -232,7 +232,7 @@ Use:
 - `t.TempDir()` for real filesystem behavior;
 - `httptest.Server` for realistic Weather API interactions;
 - test-controlled clocks for periods and RunIDs;
-- fake command runners for Scriptorium behavior;
+- fake Promptkit executors or provider clients for Promptkit behavior;
 - fake upload clients for Distributor behavior;
 - fuzz tests when parsers, normalization, or path handling have a broad and
   consequential input space;