Clarify Notarius compatibility requirements

docs/integrations/notarius.md

@@ -25,9 +25,12 @@ duplicate the complete schemas.
 
 When `pipeline.notarius.enabled` is true, Narratio resolves the executable,
 configuration path, input path, output directory, and working directory to
-absolute paths. Narratio requires the Notarius v0.7.0 CLI contract when
-references are configured and invokes each binding as a separate argument
-before `--json`:
+absolute paths. Configured references require support for the `--reference`
+contract introduced in Notarius v0.6.0. Cache controls require support for the
+selected `--resume` and `--chunk_cache` flags. Notarius v0.7.0 is the tested
+cache integration baseline, not an unconditional minimum version; Narratio
+does not impose a runtime version gate. Each reference binding is a separate
+argument before `--json`:
 
 ```text
 notarius run <pipeline_id> --config <config_path> --input <trimmed_json> --output-dir <staging_dir> [--resume] [--chunk_cache <mode>] [--reference <selector>=<verified_snapshot_path>]... --json

docs/roadmap/remediation.md

@@ -1,6 +1,6 @@
 # Notarius Cache Reuse Review Remediation
 
-Status: Open
+Status: Complete
 
 Review scope: commits `5086596` through `a0312ed`, compared with the accepted
 cache roadmap and implementation plan. The core cache integration works,
@@ -55,6 +55,10 @@ Required change:
 
 ## 2. P3 — Remove the Accidental Reference-Version Requirement
 
+Status: Complete. The integration contract now distinguishes the v0.6.0
+reference capability from selected cache flags and the tested v0.7.0 baseline,
+without introducing a runtime gate.
+
 Location: `docs/integrations/notarius.md`, Invocation section, line 28.
 
 The documentation now says Narratio requires the Notarius v0.7.0 CLI contract