Migrate examples and guidance and remove legacy test harness

docs/internal/cli-config.md

@@ -7,9 +7,9 @@ CLI wiring, and maintained examples. Definitions of behavior belong to the
 ## Changing Configuration
 
 1. Update fields, defaults, loading, and validation in `internal/core/config`.
-2. Update file, environment, and CLI mapping as applicable, including CLI flag
-   extraction. Preserve the source-specific behavior defined in the
-   [configuration contract](../config.md#effective-precedence), including the
+2. Update file, selected overlay, credential reference, and CLI mapping as
+   applicable. Preserve the precedence defined in the
+   [configuration contract](../config.md#loading-and-precedence), including the
    distinct validation and effective-config commands.
 3. Update redaction when secrets are involved.
 4. Review configuration tests and related CLI tests for precedence, validation,
@@ -35,12 +35,13 @@ From the repository root, validate the maintained configuration examples:
 
 ```sh
 go run ./cmd/audita config validate --config examples/minimal-config.yml
-go run ./cmd/audita config validate --config examples/production-config.yml
-go run ./cmd/audita config print-effective --config examples/minimal-config.yml
+AUDITA_SERVICE_KEY=synthetic-example go run ./cmd/audita config validate --config examples/production-config.yml
+AUDITA_SERVICE_KEY=synthetic-example go run ./cmd/audita config validate --config examples/production-config.yml --overlay testing
+go run ./cmd/audita config print-effective --config examples/minimal-config.yml --view profiles
 ```
 
-The effective-config command incorporates environment settings; use a controlled
-environment when comparing its results. Check affected CLI examples against the
+Only referenced credentials read environment values; use a controlled synthetic
+value when validating the service example. Check affected CLI examples against the
 parser and use schema tests for maintained transcript/glossary inputs. Example
 validation should not invoke a live LLM merely to check documentation.
 
@@ -58,7 +59,8 @@ Select checks according to the [testing policy](../policy/testing.md):
 - Schema or serialization changes: review [output-schema tests](output-schemas.md#key-tests)
   and `internal/core/schema` tests, including supported formats and rejection of
   unsupported schemas.
-- Changes affecting assembled output: inspect CLI parity and release fixtures.
+- Changes affecting assembled output: inspect controlled HTTP subprocess workflows
+  and retained report/artifact assertions.
 
 Use the [contributor guide](../development.md#baseline-validation) for baseline
 commands. These recipes supplement, rather than duplicate, public contracts.

docs/internal/output-schemas.md

@@ -12,7 +12,7 @@ selectable values and defaults belong to
 
 Configuration validation checks registry support. CLI orchestration resolves the
 selected encoder, passes the final transcript to it, and routes the encoded bytes
-to the destination defined by the [CLI contract](../cli.md#process-output-and-exit-behavior).
+to the destination defined by the [CLI contract](../cli.md#streams-and-exit-status).
 An unsupported key fails validation or resolution rather than selecting an
 implicit fallback.
 

docs/internal/overview.md

@@ -50,8 +50,8 @@ Supporting areas:
 Runtime state is held in memory plus per-run diagnostics artifacts. Audita does
 not currently implement a plugin framework, generic workflow engine,
 resume/checkpoint/manifest system, remote storage, or multi-process service mode.
-Its provider adapter is OpenAI-compatible HTTP behind the structured LLM client
-contract. These are current implementation boundaries, not bans on future work.
+Its role-bound PromptKit adapter implements the structured LLM client contract.
+These are current implementation boundaries, not bans on future work.
 
 ## Main Execution Path (`audita process`)
 
@@ -67,8 +67,8 @@ transcript and glossary schemas, normalization and chunking, output encoding,
 diagnostics artifact helpers, and public report structures.
 
 Framework components implement module and validator contracts, proposal
-generation and application, prompt context, runner orchestration, LLM scheduling
-and transport, response schemas, and process-report/correction-ledger assembly.
+generation and application, prompt context, runner orchestration, PromptKit
+execution and observation mapping, response schemas, and process-report/correction-ledger assembly.
 Domain packages provide correction modules, built-in validator chains and
 execution metadata, and embedded prompt assets.
 

docs/internal/pipeline.md

@@ -49,7 +49,7 @@ boundary for the new report summary.
 CLI orchestration labels failures at the phase boundary. Runner execution failures
 can return completed or partial module results, which report assembly preserves.
 [Report fields](../integrations/output-files.md#process-report) define how consumers
-see these outcomes; [CLI semantics](../cli.md#process-output-and-exit-behavior)
+see these outcomes; [CLI semantics](../cli.md#streams-and-exit-status)
 define streams and exits. Diagnostic write failures do not always abort processing.
 
 ## Ordering and State