Assemble PromptKit profiles for offline configuration inspection

docs/config.md

@@ -1,8 +1,8 @@
 # Audita Configuration
 
 This reference describes the version-2 configuration loader in `internal/core/config`.
-CLI command parsing and profile inspection are being connected in later work; the
-current CLI is not yet a usable entry point for this schema. Complete copyable
+CLI command parsing and offline profile inspection are implemented; process
+execution is being reconnected in later work. Complete copyable
 examples will be migrated with that integration.
 
 ## Loading and precedence
@@ -24,6 +24,15 @@ when that setting can be decoded. ConfigKit retains field origins and derivation
 for effective-configuration inspection. Its effective YAML redacts resolved
 credentials.
 
+Profile files are resolved against the selected main file's directory, or may
+use an absolute `profiles_dir`. Both selected profiles must exist and select a
+registered backend. Their effective endpoints must match that backend's endpoint
+after surrounding whitespace and trailing slashes are removed. Profiles cannot
+supply a competing `api_key_env` lookup. The backend credential supplies the
+runtime key when required; inspection makes no provider call. The
+[CLI inspection views](cli.md#streams-and-exit-status) show selected controls and
+field provenance separately from ConfigKit's redacted settings YAML.
+
 ## Settings
 
 | Field | Default | Rule |
@@ -68,5 +77,4 @@ reference resolves only the replacement; null removes the reference. General
 Secret values are available to the runtime through the resolved reference, while
 ConfigKit's effective output and provenance contain no resolved secret values.
 
-The CLI reference will be updated as the shared input parser and profile inspection
-commands are connected. Current invocation syntax belongs in [CLI](cli.md).
+Current invocation syntax belongs in [CLI](cli.md).