Add merge references and retry config

docs/internal/pipeline.md

@@ -33,18 +33,19 @@ The CLI writes the resolved pipeline and digest to diagnostics.
 
 Pipeline profiles and artifact lanes may include reference binding maps keyed by
 reference slot name. During resolution, pipeline-level bindings act as defaults
-for selected chunk, extractor, and normalizer targets that declare the slot;
-target-local bindings override or add bindings for that target. Runtime
+for selected chunk, extractor, merger, and normalizer targets that declare the
+slot; target-local bindings override or add bindings for that target. Runtime
 `--reference` requests override target config bindings, and runtime unbinds
 remove optional target bindings. Flat runtime slot names are resolved only when
 exactly one selected target declares the slot; otherwise the CLI requires a more
-specific selector such as `chunk.slot`, `lane.extract.slot`, or
-`lane.normalize.slot`. Resolution validates bindings against the declaring
-target specs and stores the bindings in target-aware resolved reference holders.
-It does not read reference files or include reference bytes in source digests.
+specific selector such as `chunk.slot`, `lane.extract.slot`,
+`lane.merge.slot`, or `lane.normalize.slot`. Resolution validates bindings
+against the declaring target 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 for chunk, extractor, and
-normalizer targets are materialized before any LLM-backed pipeline work. Config
+During run preparation, resolved file references for chunk, extractor, merger,
+and normalizer targets are materialized before any LLM-backed pipeline work. Config
 bindings resolve relative to the config file, and CLI bindings resolve relative
 to the current working directory. Materialization accepts UTF-8 text files,
 computes `sha256:` content digests, records file origins, infers canonical base
@@ -55,8 +56,8 @@ empty bound files. Media-type acceptance is checked only when a slot declares
 manifests. The CLI writes provenance-only resolved reference diagnostics, and
 the run manifest records target-stage reference provenance separately from
 source digests. Runtime reference content is passed to the matching chunker,
-extractor, or normalizer request. LLM-backed modules pass that material onward
-as named Scriptorium prompt inputs.
+extractor, merger, or normalizer request. LLM-backed modules pass that material
+onward as named Scriptorium prompt inputs.
 
 The CLI carries raw input bytes into `pipeline.RunInput`. Input adapters parse
 those bytes into the source document, while LLM-backed modules that need the
@@ -65,9 +66,9 @@ origin metadata. The raw input payload is not written to manifests or default
 diagnostics.
 
 The CLI also carries an optional run `session_id`. The runner makes it available
-to chunk, extract, and normalize requests; LLM-backed modules forward it through
-their structured completion requests so Scriptorium can include it in prompt
-execution metadata.
+to chunk, extract, merge, and normalize requests; LLM-backed modules forward it
+through their structured completion requests so Scriptorium can include it in
+prompt execution metadata.
 
 ## Registries And Module Specs
 
@@ -83,10 +84,9 @@ Every production module registers a `ModuleSpec` with:
 - `Provides`: capabilities added after that module runs;
 - `Requires`: capabilities that must already be available.
 
-Chunk, extract, and normalize specs may also declare reference slots. Slot
+Chunk, extract, merge, and normalize specs may also declare reference slots. Slot
 declarations are available from registry metadata without constructing module
-instances. Input, merge, validate, and output specs must not declare reference
-slots.
+instances. Input, validate, and output specs must not declare reference slots.
 
 Capability checks prevent incompatible pipeline composition before a run starts.