Introduce target-aware resolved reference storage

docs/internal/pipeline.md

@@ -37,8 +37,9 @@ bindings override or add lane bindings, runtime `--reference` requests override
 config bindings, and runtime unbinds remove optional bindings. Flat runtime slot
 names are resolved only when exactly one selected lane declares the slot;
 otherwise the CLI requires `lane.slot`. Resolution validates bindings against
-extractor specs and records lane-scoped binding metadata. It does not read
-reference files or include reference bytes in source digests.
+extractor specs and stores the bindings in target-aware resolved reference
+holders. It does not read reference files or include reference bytes in source
+digests.
 
 During run preparation, resolved file references are materialized before any
 LLM-backed pipeline work. Config bindings resolve relative to the config file,
@@ -51,8 +52,8 @@ bound files. Media-type acceptance is checked only when a slot declares
 `AcceptedMediaTypes`; unknown extensions are recorded as
 `application/octet-stream`. Reference content is omitted from diagnostics and
 manifests. The CLI writes provenance-only resolved reference diagnostics, and
-the run manifest records lane-scoped reference provenance separately from source
-digests.
+the run manifest records target-stage reference provenance separately from
+source digests.
 
 Prompt bundles can declare reference slots and use `reference` and
 `hasreference` template functions. Bundle loading validates string-literal slot