Update the architecture plan to standardize on input -> chunk -> extract -> merge -> normalize -> output naming conventions

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

@@ -6,7 +6,7 @@ This document describes planned work, not implemented behavior.
 
 ## Goal
 
-Implement the first useful process-stage module: D&D spell casts from a
+Implement the first useful extract-stage module: D&D spell casts from a
 Seriatim transcript source document.
 
 This checkpoint should produce the first meaningful vertical slice from real
@@ -19,7 +19,7 @@ In scope:
 - D&D spell artifact schema and Go structs;
 - structured response schema asset;
 - prompt assets;
-- `internal/modules/process/dnd/spells`;
+- `internal/modules/extract/dnd/spells`;
 - source-reference and schema validators in the extractor chain;
 - fake LLM tests;
 - CLI-level integration test if the CLI path is ready.
@@ -50,7 +50,7 @@ type SpellCast struct {
 }
 ```
 
-Keep this schema inside the D&D spells process module or a D&D artifact package,
+Keep this schema inside the D&D spells extract module or a D&D artifact package,
 not inside core framework packages.
 
 ### Stage 2: Structured Response Schema
@@ -76,7 +76,7 @@ Prompts should:
 
 ### Stage 4: Process Module Implementation
 
-Implement `internal/modules/process/dnd/spells`.
+Implement `internal/modules/extract/dnd/spells`.
 
 The extractor should:
 
@@ -117,13 +117,13 @@ The test should use fake LLM wiring and fixture input.
 - `go test ./...` passes.
 - 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 process module/artifact packages and docs.
+- D&D concepts are contained in extract module/artifact packages and docs.
 - The first meaningful vertical slice is available through tests, and through
   CLI if the CLI path is ready.
 
 ## Review Questions
 
-- Is the spell process module domain-specific without making the framework
+- Is the spell extract module domain-specific without making the framework
   D&D-specific?
 - Are source references valid and useful for downstream validation?
 - Is prompt/schema ownership clear?