Update feature roadmap to include a named pipeline profile configuration model

docs/roadmap/6-dnd-spells-extractor.md

@@ -20,6 +20,7 @@ In scope:
 - structured response schema asset;
 - prompt assets;
 - `internal/modules/extract/dnd/spells`;
+- module metadata/capability requirements for pipeline validation;
 - source-reference and schema validators in the extractor chain;
 - fake LLM tests;
 - CLI-level integration test if the CLI path is ready.
@@ -81,6 +82,7 @@ Implement `internal/modules/extract/dnd/spells`.
 The extractor should:
 
 - satisfy the framework `Extractor` contract;
+- declare module metadata for pipeline-profile validation;
 - build LLM messages from a source document or source chunk;
 - call the structured LLM client;
 - return artifact candidates with source references;
@@ -107,10 +109,11 @@ Add tests using a fake structured LLM client:
 If the CLI path is ready, add an end-to-end test using:
 
 ```sh
-notarius extract ./transcript.json --input seriatim --extractors dnd.spells --output ./artifacts.json
+notarius run dnd-session --input ./transcript.json --only spells
 ```
 
-The test should use fake LLM wiring and fixture input.
+The test should use fake LLM wiring, fixture input, and a named pipeline profile
+with a `spells` artifact lane.
 
 ## Done Criteria
 
@@ -118,6 +121,8 @@ The test should use fake LLM wiring and fixture input.
 - Seriatim input can flow through the runner into the D&D spells extractor.
 - Spell artifacts include valid source references.
 - D&D concepts are contained in extract module/artifact packages and docs.
+- The spells module can be selected as a named artifact lane in pipeline
+  configuration.
 - The first meaningful vertical slice is available through tests, and through
   CLI if the CLI path is ready.