Document identified resource formats and interpretation

docs/internal/observation.md

@@ -25,8 +25,7 @@ other content. Events are values with no mutable containers. Callback panics
 propagate to the caller.
 Resolved prompt and profile IDs are the exact runtime identities selected for
 the invocation, including namespace qualification when supplied by an engine
-view. A prompt's optional version label is descriptive metadata, not a
-selection key.
+view.
 Per-operation callbacks are ordered and synchronous; different operations may
 invoke the same callback concurrently. The recorder marks each measured phase's
 end before delivery, so callback work does not inflate provider duration.

docs/internal/runner.md

@@ -36,8 +36,7 @@ The internal engine applies each namespace view to slashless caller selections
 before they reach the runner. The runner therefore selects captured prompts and
 profiles by the resulting exact runtime IDs. Already-qualified selections pass
 through, while configured defaults and stored references are used as authored
-and are not requalified. Prompt version labels are returned as optional
-descriptive metadata; they are not prompt selectors.
+and are not requalified.
 
 Ordinary preparation selects the full prompt definition and construction-time
 hash. It retains its early request-ID check before direct-session

docs/internal/sources.md

@@ -12,8 +12,8 @@ source semantics. Internal packages are not consumer APIs.
 
 `internal/configuration` is the single adapter from ConfigKit's final
 effective configuration to execution-owned definitions. It performs one
-layered load, captures effective presence (including explicit null), records
-normalization and defaults through resolution, and validates all effective
+layered load, captures effective presence (including explicit null), builds
+detached normalized interpretations during validation, and validates all effective
 root and collection backend, profile, and prompt values. Replaced lower-layer
 domain values are not separately validated. It indexes root resources under
 their unqualified IDs and collection resources under their full
@@ -27,22 +27,22 @@ do not depend on ConfigKit.
 ConfigKit owns source headers, imports, composition, and source evidence.
 Promptkit does not preparse contributions: it validates the final effective
 values once, captures the indexed identities and their original resource
-contexts, and retains ConfigKit's result for explicit operator inspection.
+contexts, and retains ConfigKit's composed result for explicit operator inspection.
 Accepted non-main source headers are consumed during composition; the main
-source declaration remains available in that inspection view. Prompt and
-collection release labels are descriptive metadata, not selection inputs. The
+source declaration remains available in that inspection view. Collection
+release labels are descriptive metadata, not selection inputs. The
 [format reference](../formats.md#source-headers-collections-and-resource-ids)
 owns the exact source-header and collection contracts.
 
 The `ConfigurationInspection.Diff` facade method compares two retained results
 through a private wrapper and a narrow `internal/configuration.Diff` bridge.
 The wrapper keeps `Result[document]` inside the adapter; the bridge delegates
-once to ConfigKit v0.8.0 and returns its public difference records. Comparison
+once to ConfigKit v1.0.0 and returns its public difference records. Comparison
 uses only frozen effective values and does not reopen sources, resolve runtime
 credentials, or enter the execution path. ConfigKit applies sensitivity from
 both results; reports may still contain ordinary application data. See the
 [consumer comparison guide](../consumers/pkg-promptkit.md#inspect-the-captured-configuration)
-and ConfigKit's [v0.8.0 comparison contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.8.0/docs/config.md#effective-configuration-diffs).
+and ConfigKit's [v1.0.0 comparison contract](https://forge.maximumdirect.net/base-layer/configkit/src/tag/v1.0.0/docs/config.md#effective-configuration-diffs).
 
 After resource materialization and effective-profile snapshot construction, the
 adapter captures lexically ordered identity inventories for backends, profiles,
@@ -85,10 +85,12 @@ returning and retains no source capability for public inspection.
 Prompt materialization shares a lazy metadata snapshot across root and collection
 resources during construction, avoiding a full metadata copy per collection.
 
-Role and cache-control normalization is applied to execution-owned message
-copies. ConfigKit v0.8.0 retains effective input message metadata and its
-resource origins; recording a sequence-wide normalization in the retained
-configuration would replace origins of unchanged content-file fields.
+Normalization and defaults are applied to execution-owned interpretations,
+including message roles and cache controls. ConfigKit retains the composed
+values and origins, rather than synthetic Promptkit normalization events. List
+indexes identify fields for presence, validation, sensitivity, and resource
+context; full IDs select captured runtime indexes. Recording a sequence-wide
+normalization would replace origins of unchanged content-file fields.
 
 The runner selects full definitions from this index for preparation and uses
 captured prompt metadata for `InspectPrompt` and `InspectRequirements`; the
@@ -142,7 +144,7 @@ change rendering behavior.
 ## Profiles
 
 ConfigKit resolves profile inheritance before the handoff. Within a collection,
-`extends` names a sibling local key; it is not a cross-collection reference.
+`extends: {id: parent}` names a sibling local ID; it is not a cross-collection reference.
 The configuration adapter validates final effective resource references and
 field values, then builds target
 snapshots with backend defaults and presence/suppression state. A profile can