Document scene-aware combat extraction

docs/roadmap/future.md

@@ -18,10 +18,6 @@ not as committed release dates.
 
 ### Use D&D Scene Chunking
 
-- 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
-  classification.
 - Use ordered pipeline steps whenever a later artifact needs an accepted
   earlier artifact as context. Keep independent lanes in the same step and do
   not introduce a general DAG or concurrent cross-lane reconciliation model.

docs/roadmap/scene-aware-combat-extraction.md

@@ -2,7 +2,9 @@
 
 ## Status
 
-Proposed near-term scope.
+Implemented. This document preserves the feature contract and rationale; the
+current configuration, operational, integration, and internal behavior is
+maintained in their canonical documentation.
 
 ## Purpose
 
@@ -129,8 +131,7 @@ The maintained complete D&D example should bind the normalized
 `scene-descriptions` lane from the first step to the `scene_descriptions` slot
 in the second step. The minimal example should remain unchanged.
 
-When implemented, current-behavior documentation should be updated in its
-canonical locations:
+Current-behavior documentation is maintained in these canonical locations:
 
 - Configuration owns the new selectable reference slot and binding example.
 - Operations owns the ordered scene-aware workflow.