Update feature roadmap to include a named pipeline profile configuration model

docs/roadmap/5-seriatim-input-module.md

@@ -21,8 +21,10 @@ In scope:
 - mapping into `SourceDocument` and `SourceUnit`;
 - source-document validation;
 - input adapter registry wiring;
+- module metadata/capabilities for pipeline validation;
 - fixtures and tests;
-- CLI/config path to select the input module if the CLI shell exists.
+- config path to use the input module through a named pipeline profile if
+  config loading exists.
 
 Out of scope:
 
@@ -81,13 +83,19 @@ The resulting `SourceDocument` should pass core source validation.
 
 Register the module under a stable input adapter key, likely `seriatim`.
 
-If CLI support exists, add provisional selection:
+Declare module metadata for pipeline validation. Initial provided capabilities
+should include transcript-oriented metadata such as `speaker` and `timestamps`
+if those fields are preserved from Seriatim input.
+
+If config and CLI support exist, add a minimal pipeline-profile fixture or test
+config using the Seriatim input module:
 
 ```sh
-notarius extract ./transcript.json --input seriatim
+notarius run dnd-session --input ./transcript.json --only spells
 ```
 
-The command may still use fake extractors until checkpoint 6.
+The command may still use fake extract, merge, normalize, and output modules
+until checkpoint 6.
 
 ### Fixtures And Tests
 
@@ -105,7 +113,9 @@ Add fixtures and tests for:
 - `go test ./...` passes.
 - Seriatim minimal transcript JSON maps into `SourceDocument`.
 - Transcript fields do not appear in core runner contracts.
-- The input module is selectable through the registry.
+- The input module is selectable through the registry and pipeline-profile
+  configuration when config support exists.
+- The input module declares capabilities needed for pipeline validation.
 - Tests prove transcript-specific assumptions are isolated to the input module.
 
 ## Review Questions