Finish the documentation refresh

docs/integrations/dnd-combat-turn-artifacts.md

@@ -15,8 +15,8 @@ complete initiative tracker, combat summary, or state model.
 | Media type | `application/json` |
 
 `v1` is a strict JSON object with required `combat_turns`; the array may be
-empty. Turn and source-reference objects reject unknown fields. A future
-incompatible shape requires a new schema version.
+empty. Turn and source-reference objects reject unknown fields. An incompatible
+shape change requires a new schema version.
 
 ## Wire shape
 

docs/integrations/dnd-item-event-artifacts.md

@@ -15,8 +15,8 @@ changes; it does not maintain an inventory, balance, or ledger.
 | Media type | `application/json` |
 
 `v1` is a strict JSON object with required `events`; the array may be empty.
-Event and source-reference objects reject unknown fields. A future incompatible
-shape requires a new schema version.
+Event and source-reference objects reject unknown fields. An incompatible
+shape change requires a new schema version.
 
 ## Wire shape
 

docs/integrations/dnd-npc-artifacts.md

@@ -16,8 +16,8 @@ character sheet or a relationship summary.
 | Identity policy | `dnd.npcs.identity.v1` |
 
 `v1` accepts one strict JSON object with required `npcs`; the array may be
-empty. NPC and source-reference objects reject unknown fields. A future
-incompatible artifact shape or identity policy uses a new version or policy.
+empty. NPC and source-reference objects reject unknown fields. An incompatible
+artifact shape or identity-policy change uses a new version or policy.
 
 ## Wire shape and identity
 

docs/integrations/dnd-npc-interaction-artifacts.md

@@ -16,8 +16,8 @@ or summarize the session.
 | Media type | `application/json` |
 
 `v1` is a strict JSON object with required `interactions`; the array may be
-empty. Interaction and source-reference objects reject unknown fields. A future
-incompatible shape requires a new schema version.
+empty. Interaction and source-reference objects reject unknown fields. An
+incompatible shape change requires a new schema version.
 
 ## Wire shape
 

docs/integrations/dnd-scene-description-artifacts.md

@@ -15,7 +15,7 @@ source-grounded title and summary.
 | Media type | `application/json` |
 
 `v1` is a strict JSON object with required non-empty `scenes`. Scene and
-source-reference objects reject unknown fields. A future incompatible shape
+source-reference objects reject unknown fields. An incompatible shape change
 requires a new schema version.
 
 ## Wire shape

docs/integrations/dnd-spell-artifacts.md

@@ -16,7 +16,7 @@ spellbook, a rules lookup result, or a record of hypothetical casts.
 
 `v1` is a single strict JSON object. It requires `spell_casts`; the array may
 be empty. Each spell-cast object and source-reference object rejects unknown
-fields. A future incompatible shape requires a new schema version.
+fields. An incompatible shape change requires a new schema version.
 
 ## Wire shape
 

docs/roadmap/future.md

@@ -16,11 +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.
 
-### Use D&D Scene Chunking
+### Evaluate The Shared D&D Scene Plan
 
-- 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.
 - Reassess whether one shared scene plan provides enough context for NPC,
   spell, combat, interaction, and scene-description lanes after real-world use.
   Add more complex chunking only in response to demonstrated failures.