Serialize typed artifacts at durable boundaries

docs/integrations/json-output.md

@@ -15,7 +15,7 @@ The encoder writes:
 
 - `index.json`
 - `manifest.json`
-- `lanes/<lane-id>.json`, one file per normalized raw lane output
+- `lanes/<lane-id>.json`, one file per normalized serialized artifact
 - `rejected.json`
 - `warnings.json`
 
@@ -112,8 +112,8 @@ Reference `stage` is `chunk`, `extract`, `merge`, or `normalize`. `lane_id` is
 omitted for chunk references and present for extract, merge, and normalize
 references.
 
-`validation_status` is `approved` when no raw outputs were rejected and
-`rejected` when one or more raw outputs were rejected.
+`validation_status` is `approved` when no outputs were rejected and `rejected`
+when one or more outputs were rejected.
 
 `validator_chains` records the resolved validator chain for each validation
 point. Entries include stage, lane ID when applicable, module key, and validators
@@ -131,12 +131,13 @@ message, attempt count, and optional diagnostic artifact path.
 
 ## Output Payload Files
 
-Each normalized raw output is written to `lanes/<sanitized-lane-id>.json`.
-The JSON output encoder accepts only `application/json` normalized outputs. The
-file contains the raw JSON payload pretty-printed.
+Each normalized serialized artifact is written to
+`lanes/<sanitized-lane-id>.json`. The JSON output encoder is domain-neutral and
+accepts only artifacts whose codec media type is `application/json`. The file
+contains the codec-owned JSON bytes pretty-printed.
 
 The schema of each lane payload is owned by that artifact contract. For the
-current D&D spell lane, see [D&D Spell Raw Output](dnd-spell-artifacts.md).
+current D&D spell lane, see [D&D Spell Artifact](dnd-spell-artifacts.md).
 
 ## `rejected.json`
 
@@ -148,7 +149,7 @@ Shape:
 }
 ```
 
-When raw output validation rejects an output, each entry contains `stage` and
+When output validation rejects an output, each entry contains `stage` and
 `message`. It includes `lane_id`, `module_key`, `chunk_id`, `chunk_index`,
 `validator_name`, `reason_code`, `attempt_count`, and
 `diagnostic_artifact_path` when applicable.