Retire annotated D&D scene plans

docs/internal/modules.md

@@ -177,17 +177,16 @@ window settings used by `Plan`.
 
 The scene chunker prepares a structured Scriptorium request from the full
 transcript, session, and optional D&D reference inputs. It validates the model's
-scene boundaries against source-unit IDs and converts them into deterministic
-plan ranges with optional scene annotations. Preparation injects the shared
-structured LLM client into the chunker; `Plan`
-supplies only the run-specific profile, session, source, references, and
-metadata.
+inclusive source-unit endpoints against document position and converts them
+into deterministic plan ranges. Preparation injects the shared structured LLM
+client into the chunker; `Plan` supplies only the run-specific profile, session,
+source, references, and metadata.
 
 Scene validation requires sequential, contiguous, non-overlapping coverage from
-the first source unit through the last. Scene descriptions, boundaries,
-confidence, and participants are module-owned annotations. Boundary caveats
-become warnings. Malformed
-structured output is returned as an error; there is no fallback chunker.
+the first source unit through the last. Its private response contains only the
+boundary endpoints; the accepted plan has no D&D-specific annotations and
+produces no boundary warnings. Malformed structured output is returned as an
+error; there is no fallback chunker.
 
 The package embeds its prompt and response schema and reports their non-secret
 identity and hashes through singleton module metadata. Shared D&D assets supply

docs/roadmap/future.md

@@ -16,12 +16,8 @@ not as committed release dates.
   validator, and normalizer development. Treat model-quality review as an
   iterative human evaluation aid, not a deterministic correctness gate.
 
-### Minimize And Use D&D Scene Chunking
+### Use D&D Scene Chunking
 
-- Reduce the D&D scene chunker toward its narrow responsibility: identifying
-  coherent scene boundaries. Retain boundary confidence or caveats only when a
-  demonstrated validator or operator workflow consumes them; move title,
-  summary, scene kind, and participant duties to dedicated artifacts.
 - Allow the combat extractor to no-op for chunks classified as non-combat only
   after the scene-description artifact can be supplied through an explicit
   ordered dependency. Do not make generic chunk materialization depend on a D&D

docs/roadmap/minimal-dnd-scene-chunking.md

@@ -1,6 +1,6 @@
 # Minimal D&D Scene Chunking
 
-Status: Proposed
+Status: Implemented
 
 ## Purpose