Rename configuration selection to overlays

docs/cli.md

@@ -12,8 +12,8 @@ defined in [Operations](operations.md).
 notarius help
 notarius --version
 notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
-notarius config validate [--config path/to/config.yml] [--config-profile name] [--pipeline pipeline-id] [--only lane-a,lane-b]
-notarius pipelines list [--config path/to/config.yml] [--config-profile name] [--json]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 Running Notarius without arguments, or with **help**, **--help**, or **-h**,
@@ -42,7 +42,7 @@ pipeline ID and **--input** are required.
 | Flag | Meaning |
 | --- | --- |
 | **--config path** | Use this configuration file. When omitted, configuration discovery applies; see [Configuration](config.md). |
-| **--config-profile name** | Select a ConfigKit configuration overlay. Empty and **default** select the composed base configuration. |
+| **--config-overlay name** | Select a ConfigKit configuration overlay. Empty and **default** select the composed base configuration. |
 | **--input path** | Source input file to process. Required. |
 | **--output-dir path** | Override the configured output root for this run. |
 | **--json** | Write the successful run-result receipt as JSON to standard output. |
@@ -155,7 +155,7 @@ OPENROUTER_API_KEY=your-api-key \
 ## config validate
 
 ~~~
-notarius config validate [--config path/to/config.yml] [--config-profile name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
 ~~~
 
 This command loads and validates the selected composed configuration. With **--pipeline**, it also
@@ -184,7 +184,7 @@ validation; it cannot run a provider-backed pipeline.
 ## config effective
 
 ~~~
-notarius config effective [--config path/to/config.yml] [--config-profile name]
+notarius config effective [--config path/to/config.yml] [--config-overlay name]
 ~~~
 
 This command writes the selected composed configuration as deterministic,
@@ -194,19 +194,19 @@ pipeline, prepare modules, materialize references, or contact a provider.
 ## config explain
 
 ~~~
-notarius config explain [--config path/to/config.yml] [--config-profile name] <json-pointer>
+notarius config explain [--config path/to/config.yml] [--config-overlay name] <json-pointer>
 ~~~
 
 This command writes ConfigKit's redacted, human-readable explanation for one
 canonical JSON Pointer. Supply `""` explicitly to explain the root. A malformed
 pointer is a syntax error; a well-formed unknown path is a command failure.
-The explanation can describe a value displaced by a selected profile. Standard
+The explanation can describe a value displaced by a selected overlay. Standard
 output contains only the explanation.
 
 ## pipelines list
 
 ~~~
-notarius pipelines list [--config path/to/config.yml] [--config-profile name] [--json]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 This command lists configured pipeline IDs in sorted order. By default, it
@@ -225,7 +225,7 @@ errors are written to standard error.
 
 Configuration load errors include ConfigKit's field diagnostics and source
 coordinates, followed by a source-ID legend identifying the acquired files or
-source labels. This includes imported files and the selected configuration profile.
+source labels. This includes imported files and the selected configuration overlay.
 
 For **run --json**, actionable process warnings remain on standard error and standard output is a
 machine-readable success result only. Syntax and runtime diagnostics remain on

docs/config.md

@@ -20,12 +20,13 @@ For configuration values, precedence is:
 
 1. built-in defaults;
 2. composed YAML sources, including imports;
-3. the selected ConfigKit profile; and
+3. the selected ConfigKit overlay; and
 4. explicitly supplied configuration-valued run flags.
 
-`--config-profile` selects a ConfigKit overlay from `profiles/<name>.yml`
+`--config-overlay` selects a ConfigKit overlay from `overlays/<name>.yml`
 beneath the selected configuration root. Empty and `default` select no overlay.
-Configuration profiles are distinct from PromptKit LLM profiles selected by
+`profiles/<name>.yml` is not a fallback location, and `--config-profile` is no
+longer accepted. Configuration overlays are distinct from PromptKit LLM profiles selected by
 `llm_profile` or `--llm-profile`. The retired operational environment variables
 have no effect; `NOTARIUS_CONFIG` remains a source-discovery input.
 
@@ -79,14 +80,14 @@ umask, setgid inheritance, and default ACLs; see [Operations](operations.md#cach
 
 Every nonempty relative configured destination or reference path resolves from
 the canonical directory of the file that supplies its surviving declaration.
-This includes imported fragments and selected configuration profiles. Built-in
+This includes imported fragments and selected configuration overlays. Built-in
 relative destinations use the selected main configuration file's directory;
 explicit `--output-dir` and `--debug-dir` values use the invocation working
 directory. Absolute values remain unchanged.
 
 The root file can use ConfigKit imports to compose disjoint definitions. Imports
-and selected profiles remain under the configuration root; they do not merge or
-append a pipeline's `steps` sequence. A profile replaces sequences as defined
+and selected overlays remain under the configuration root; they do not merge or
+append a pipeline's `steps` sequence. An overlay replaces sequences as defined
 by ConfigKit, so changing an individual ordered binding requires supplying the
 whole replacement sequence.
 
@@ -201,7 +202,7 @@ debug:
 **concurrency.total_llm** must be greater than zero. The only supported
 **concurrency.stage_workers** key is **extract**; its value must be from 1
 through **total_llm**. When omitted, it is recalculated from the effective
-**total_llm** after imports, profile selection, and explicit ConfigKit
+**total_llm** after imports, overlay selection, and explicit ConfigKit
 overrides.
 
 **cache.chunk_plans.mode** accepts **auto**, **bypass**, or **refresh**.
@@ -440,7 +441,7 @@ pipeline, lane, and binding scopes and precedence are defined by the
 replace a configured generated artifact handoff. Required slots must be bound
 after configuration and CLI reference actions are applied. A YAML reference
 path resolves from the file that supplies its surviving declaration, including
-an imported fragment or selected profile. CLI reference paths resolve relative
+an imported fragment or selected overlay. CLI reference paths resolve relative
 to the process working directory.
 
 ### D&D Reference Slots
@@ -601,5 +602,5 @@ Use [config effective](cli.md#config-effective) to write the selected composed
 configuration as deterministic, redacted YAML. Use
 [config explain](cli.md#config-explain) with a canonical JSON Pointer to inspect
 the effective or historical provenance for one path, including a value displaced
-by a selected profile. Neither command resolves a pipeline, prepares modules,
+by a selected overlay. Neither command resolves a pipeline, prepares modules,
 materializes references, or requires provider credentials.

docs/consumers/subprocess.md

@@ -15,10 +15,10 @@ configured lane inventory, and downstream acceptance checklist, see
 Optionally preflight a selected configuration and pipeline before work starts:
 
 ```sh
-notarius config validate --config /path/to/notarius.yml --config-profile production --pipeline pipeline-id
+notarius config validate --config /path/to/notarius.yml --config-overlay production --pipeline pipeline-id
 ```
 
-Omit `--config-profile` when the composed base configuration is the intended
+Omit `--config-overlay` when the composed base configuration is the intended
 selection; it is independent from any `--llm-profile` run override.
 
 Invoke the run with explicit paths and machine-readable output. Capture
@@ -28,7 +28,7 @@ processing the result.
 ```sh
 notarius run pipeline-id \
   --config /path/to/notarius.yml \
-  --config-profile production \
+  --config-overlay production \
   --input /path/to/source.json \
   --output-dir /path/to/output-root \
   --json

docs/integrations/pkg-configkit.md

@@ -2,7 +2,7 @@
 
 Notarius uses the public root package
 [`gitea.maximumdirect.net/eric/ConfigKit`](https://gitea.maximumdirect.net/eric/ConfigKit)
-at v0.3.0 for version 5 configuration acquisition, imports, profiles, explicit
+at v0.4.0 for version 5 configuration acquisition, imports, overlays, explicit
 overrides, diagnostics, and safe inspection rendering.
 
 Notarius owns the typed document, domain defaults and validation, runtime

docs/internal/cli.md

@@ -35,7 +35,7 @@ options before dispatch so that a missing production dependency fails as a
 command error rather than reaching execution.
 
 Commands that need configuration use one shared ConfigKit-backed loader. The
-CLI discovers the file, passes the requested profile and only explicit
+CLI discovers the file, passes the requested overlay and only explicit
 configuration-valued run overrides, and receives a **LoadedConfig**. The
 configured discovery and precedence contract is in
 [Configuration](../config.md), while the loading and resolution mechanics are

docs/internal/configuration.md

@@ -28,7 +28,7 @@ at their respective [CLI](cli.md), [pipeline](pipeline.md), and
 
 ## Loading And Validation
 
-ConfigKit acquires the selected root, imports, optional selected profile, and
+ConfigKit acquires the selected root, imports, optional selected overlay, and
 explicit CLI overrides in precedence order. Its document definition supplies
 typed defaults, source-aware path normalization, and structural validation
 before conversion to the independently owned runtime **Config**. Only
@@ -112,7 +112,7 @@ recording arbitrary environment values or provider requests.
 
 ## Invariants To Preserve
 
-- ConfigKit composition applies defaults, imports, an optional profile, and
+- ConfigKit composition applies defaults, imports, an optional overlay, and
   explicit overrides in one direction with retained origin metadata.
 - A configuration is structurally valid before it is resolved, and a resolved
   pipeline is compatible with the supplied catalog before preparation begins.
@@ -126,7 +126,7 @@ recording arbitrary environment values or provider requests.
 
 - **internal/core/config/document_test.go** and
   **operational_document_test.go** cover ConfigKit document loading,
-  normalization, imports, profiles, and overrides.
+  normalization, imports, overlays, and overrides.
 - **internal/core/config/validation_contract_test.go** covers configuration
   invariants and contextual failures.
 - **internal/core/config/effective_config_contract_test.go** covers defaults,

docs/internal/pipeline.md

@@ -52,7 +52,7 @@ consumers do not repeat profile inheritance or configuration resolution.
 Each LLM request receives its own copy of that resolved value. PromptKit spends
 it only for structural correction inside one completion; the runner's binding
 retry policy remains the separate outer budget for complete stage attempts.
-Configuration resolution supplies the selected profile and catalog; see
+Configuration resolution supplies the selected overlay and catalog; see
 [Configuration Internals](configuration.md).
 
 External reference materialization happens before preparation. The materializer

docs/operations.md

@@ -319,7 +319,7 @@ content. Neither surface is a cache input. Do not treat a debug bundle as safe
 to share merely because its configuration summary is redacted. Invocation
 metadata omits reasoning effort when it is inherited, records the replacement
 value when one is supplied, and records an empty value when inherited reasoning
-was explicitly cleared. It records `config_profile` only when a non-base
+was explicitly cleared. It records `config_overlay` only when a non-base
 configuration overlay was selected.
 
 Notarius never creates debug state without an explicit request and never

docs/roadmap/implementation.md

@@ -50,6 +50,8 @@ Do not repeat passed checks for unchanged content merely to make a commit.
 
 ## Stage 1 — Cut Over Configuration Selection To Overlays
 
+**Status:** Completed 2026-09-25.
+
 **Goal:** Adopt ConfigKit v0.4.0 and finish its narrow operator-facing rename in
 one coherent change. This is one prompt: it is a naming migration, not a new
 configuration engine.