Fix profile loading with ConfigKit history

docs/releases/v2.0.0.md

@@ -6,7 +6,7 @@ their effective dependency graph directly inspectable.
 
 ## Summary
 
-Pipeline roots now use ConfigKit v0.1.1 for strict YAML loading, explicit
+Pipeline roots now use ConfigKit v0.1.2 for strict YAML loading, explicit
 imports, fixed-path named profiles, provenance, defaults, and typed credential
 references. The recommended production layout keeps production values in the
 base, defines each ordinary artifact and artifact family in its own imported
@@ -32,8 +32,10 @@ notes remain historical descriptions of their releases.
 
 Inspection commands still avoid session, manifest, workspace, adapter, and
 remote-service activity, but they are not credential-free loaders: every
-explicit typed credential reference must resolve. Pipelines containing artifact
-families also require a campaign so the canonical party can be expanded.
+explicit typed credential reference in the selected effective configuration must
+resolve; references replaced or removed by that profile need not resolve.
+Pipelines containing artifact families also require a campaign so the canonical
+party can be expanded.
 `config show` is a secret-safe review projection, not a promised reloadable
 authoring file.
 
@@ -77,7 +79,7 @@ guides.
 
 ## Changes
 
-- Adopted ConfigKit v0.1.1 across pipeline, campaign, session, and party loading
+- Adopted ConfigKit v0.1.2 across pipeline, campaign, session, and party loading
   while keeping Narratio domain validation and post-campaign expansion explicit.
 - Added ConfigKit imports and fixed `profiles/<name>.yml` pipeline overlays,
   unified safe effective show/diff/digest projection, and source provenance.