Add merge references and retry config

docs/cli.md

@@ -49,8 +49,8 @@ Flags:
   use one Scriptorium profile ID.
 - `--session-id id`: pass a stable prompt session identifier through LLM-backed
   module calls.
-- `--reference selector=path`: bind a reference path to a chunk, extractor, or
-  normalizer reference slot. Repeatable.
+- `--reference selector=path`: bind a reference path to a chunk, extractor,
+  merger, or normalizer reference slot. Repeatable.
 - `--without-reference selector`: remove a configured optional reference binding.
   Repeatable. It accepts the same selector forms as `--reference`, without
   `=path`.
@@ -59,12 +59,12 @@ On success, the command prints the completed pipeline ID, normalized output and
 rejected output counts, and the output directory. If the run completes with warnings,
 the warning count is printed to stderr.
 
-Reference flags are resolved against selected chunk, extractor, and normalizer
+Reference flags are resolved against selected chunk, extractor, merger, and normalizer
 targets before the run starts. Flat slot names are accepted only when exactly
 one selected target declares that slot. Bound reference files are read before
 pipeline work starts, validated as UTF-8 text, and recorded as provenance for
 the target that declares the slot. Runtime reference content is passed to the
-chunker, extractor, or normalizer target that declares the slot. Notarius infers
+chunker, extractor, merger, or normalizer target that declares the slot. Notarius infers
 reference media types from file extensions for provenance and for optional slot
 checks. Reference content is not written to diagnostics, logs, errors, or
 manifests.
@@ -81,9 +81,11 @@ Reference binding precedence is:
 
 - `slot=path`: valid when exactly one selected target declares `slot`;
 - `chunk.slot=path`: target the chunker;
-- `lane.slot=path`: valid when exactly one selected extractor or normalizer in
-  that lane declares `slot`;
+- `merge.slot=path`: valid when exactly one selected merger declares `slot`;
+- `lane.slot=path`: valid when exactly one selected extractor, merger, or
+  normalizer in that lane declares `slot`;
 - `lane.extract.slot=path`: target a lane extractor;
+- `lane.merge.slot=path`: target a lane merger;
 - `lane.normalize.slot=path`: target a lane normalizer.
 
 Use `slot=path` when the selected targets declare the slot unambiguously:
@@ -105,7 +107,7 @@ go run ./cmd/notarius run dnd-session \
   --reference spells.extract.glossary=./campaign-glossary.txt
 ```
 
-The same grammar can target chunk and normalize slots when the configured
+The same grammar can target chunk, merge, and normalize slots when the configured
 modules declare them:
 
 ```sh
@@ -113,6 +115,7 @@ go run ./cmd/notarius run dnd-session \
   --config path/to/config.yml \
   --input examples/seriatim-minimal-transcript.json \
   --reference chunk.scene_guide=./campaign-scenes.txt \
+  --reference spells.merge.merge_notes=./merge-notes.txt \
   --reference spells.normalize.normalization_notes=./normalization-notes.txt
 ```
 

docs/config.md

@@ -141,13 +141,13 @@ against the production module catalog and fail fast for unknown or incompatible
 module keys.
 
 Reference bindings are validated against reference slots declared by eligible
-chunk, extract, and normalize targets during pipeline resolution. Required slots
+chunk, extract, merge, and normalize targets during pipeline resolution. Required slots
 must be bound after config defaults, target-local references, lane-level
 compatibility bindings, and run-time `--reference` or `--without-reference`
 overrides are applied. Config-relative paths are resolved relative to the config
 file; CLI reference paths are resolved relative to the current working
 directory. Materialized bound files must be UTF-8 text. Materialized reference
-provenance is recorded for chunk, extractor, and normalizer targets, and runtime
+provenance is recorded for chunk, extractor, merger, and normalizer targets, and runtime
 reference content is passed to the target that declares the slot. Reference
 media types are inferred from file extensions, recorded as canonical base media
 types, and checked only when a module declares `AcceptedMediaTypes`; unknown
@@ -156,8 +156,8 @@ written to diagnostics, logs, errors, or manifests.
 
 Pipeline-level `references` are defaults. They are valid when at least one
 eligible target in the full configured pipeline declares the slot, including
-chunk, extractor, and normalizer targets. During a run, they apply only to the
-selected targets that declare the slot:
+chunk, extractor, merger, and normalizer targets. During a run, they apply only
+to the selected targets that declare the slot:
 
 ```yaml
 pipelines:
@@ -192,15 +192,17 @@ pipelines:
             party: ./campaign/session-party.txt
 ```
 
-`chunk.references` and `normalize.references` are accepted in object-form
-bindings. They override pipeline-level defaults for slots declared by the chunk
-or normalizer module. Extractor-local references apply only to the extractor,
-and normalizer-local references apply only to the normalizer.
+`chunk.references`, `merge.references`, and `normalize.references` are accepted
+in object-form bindings. They override pipeline-level defaults for slots
+declared by that target module. Extractor-local references apply only to the
+extractor, merger-local references apply only to the merger, and
+normalizer-local references apply only to the normalizer.
 
 Target-local reference fields use the same map shape at:
 
 - `pipelines.<id>.chunk.references`
 - `pipelines.<id>.artifacts.<lane>.extract.references`
+- `pipelines.<id>.artifacts.<lane>.merge.references`
 - `pipelines.<id>.artifacts.<lane>.normalize.references`
 
 Each binding is valid only when that target module declares the slot.
@@ -226,13 +228,16 @@ Binding fields:
 - `module`: module key.
 - `llm_profile`: optional Scriptorium profile ID. Empty or omitted lets the
   Scriptorium prompt default select the profile.
+- `retries`: non-negative retry count for runtime stages that support retries.
+  The current runner preserves this value in resolved config.
 - `options`: optional module-specific settings.
 - `references`: optional reference bindings. Supported only for `chunk`,
-  `extract`, and `normalize` bindings. `input`, `merge`, validator, and
+  `extract`, `merge`, and `normalize` bindings. `input`, validator, and
   `output` bindings reject this field during validation.
 
 The `--llm-profile` run flag overrides every effective LLM-capable module
-binding to use one Scriptorium profile ID.
+binding to use one Scriptorium profile ID: chunk, every selected lane extract,
+merge, and normalize binding.
 
 ## Implemented Production Modules
 

docs/internal/llm.md

@@ -41,6 +41,10 @@ The runtime records the actual selected Scriptorium profile, provider, and model
 used during execution. Manifest population does not rely on a precomputed
 profile ID before pipeline execution.
 
+Explicit profile validation and `--llm-profile` overrides apply to LLM-capable
+pipeline stages: chunk, extract, merge, and normalize. Input, output, and
+validator bindings are not part of the current production LLM profile scope.
+
 ## Scriptorium Adapter
 
 `ScriptoriumClient` implements `contracts.StructuredLLMClient` by converting

docs/internal/modules.md

@@ -20,7 +20,7 @@ A production module package should provide:
 Module specs should describe capabilities accurately. Resolution uses specs to
 reject incompatible pipelines before execution.
 
-Chunk, extract, and normalize modules that accept auxiliary reference material
+Chunk, extract, merge, and normalize modules that accept auxiliary reference material
 must declare slots through both `ReferenceSlots()` and
 `ModuleSpec().ReferenceSlots`. The runtime slot list and registry metadata
 should match so config validation can inspect slots without constructing module
@@ -31,10 +31,10 @@ must still be UTF-8 text. When a slot declares accepted media types, Notarius
 compares the canonical base media type inferred from the file extension,
 case-insensitively and without parameters.
 
-The resolver materializes reference content for chunk, extractor, and
+The resolver materializes reference content for chunk, extractor, merger, and
 normalizer targets. Runtime delivery uses `contracts.ChunkRequest.References`,
-`contracts.ExtractionRequest.References`, and
-`contracts.NormalizeRequest.References`. Reference material is not source
+`contracts.ExtractionRequest.References`, `contracts.MergeRequest.References`,
+and `contracts.NormalizeRequest.References`. Reference material is not source
 evidence and must not be converted into `SourceRef` values. If a module prompt
 uses references, pass them as prompt input materials through the structured LLM
 request. Prompt metadata hashes remain based on prompt asset source, not
@@ -48,7 +48,7 @@ Common D&D prompt fragments, reference slot helpers, prompt input assembly, and
 reference rendering live under `internal/modules/sharedassets/dnd`. Module
 contracts should expose prompt IDs, versions, input material names, and
 non-secret prompt/schema hashes through manifest metadata; they should not
-expose Scriptorium public types through chunk, extract, or normalize contracts.
+expose Scriptorium public types through chunk, extract, merge, or normalize contracts.
 
 Chunk modules receive the structured LLM client, configured Scriptorium profile
 ID, prompt session ID, and raw source input material through
@@ -60,6 +60,10 @@ Normalize modules receive the structured LLM client, configured Scriptorium
 profile ID, prompt session ID, and reference material through
 `contracts.NormalizeRequest` when they need model-backed reconciliation.
 
+Merge modules receive the structured LLM client, configured Scriptorium profile
+ID, prompt session ID, raw source input material, and reference material through
+`contracts.MergeRequest` when they need model-backed merge behavior.
+
 ## `seriatim` Input
 
 Package: `internal/modules/input/seriatim`

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.
 

docs/troubleshooting.md

@@ -118,16 +118,18 @@ Symptoms include:
 
 Fix:
 
-- Confirm the selected chunker, extractor, or normalizer declares the slot. The
+- Confirm the selected chunker, extractor, merger, or normalizer declares the slot. The
   implemented `dnd/scenes` chunker and `dnd/spells` extractor declare optional
   `roster` and `glossary` slots.
 - Use a specific selector when more than one selected target declares the same
-  slot. Examples include `chunk.context=./context.txt`,
-  `spells.extract.context=./extract-context.txt`, and
+  slot: `chunk.context=./context.txt`,
+  `spells.extract.context=./extract-context.txt`,
+  `spells.merge.context=./merge-context.txt`, or
   `spells.normalize.context=./normalize-context.txt`.
-- `lane.slot=path` is valid only when exactly one selected extractor or
-  normalizer in that lane declares the slot. If both do, use
-  `lane.extract.slot=path` or `lane.normalize.slot=path`.
+- `lane.slot=path` is valid only when exactly one selected extractor, merger,
+  or normalizer in that lane declares the slot. If more than one does, use
+  `lane.extract.slot=path`, `lane.merge.slot=path`, or
+  `lane.normalize.slot=path`.
 - Use `--without-reference selector` to remove optional config bindings; do not
   pass an empty `--reference selector=`.
 - Check whether a path came from config or CLI. Config paths are relative to