test(agent-workspace): guard dependency scopes

Author: Jacobinwwey

Knowledge_Base/ragdependencymulticonflict/field storage dependency conflict evidence.md

@@ -0,0 +1,6 @@
+# Field Storage Dependency Conflict Evidence
+Field storage dependency conflict evidence records the field storage dependency as PostgreSQL.
+
+## Field Dependency
+The storage dependency is PostgreSQL in the field deployment manifest.
+Operators must resolve the active dependency source before publishing a dependency value.

Knowledge_Base/ragdependencymulticonflict/nominal storage dependency conflict probe.md

@@ -0,0 +1,6 @@
+# Nominal Storage Dependency Conflict Probe
+Nominal storage dependency conflict probe records the nominal storage dependency as SQLite.
+
+## Nominal Dependency
+The storage dependency is SQLite in the nominal deployment manifest.
+Operators must compare this nominal dependency source against field evidence before publishing a dependency value.

Knowledge_Base/ragdependencyversionqualifier/version scoped dependency probe.md

@@ -0,0 +1,10 @@
+# Version Scoped Dependency Probe
+Version scoped dependency probe records that the storage dependency is SQLite for version 1.0 and PostgreSQL for version 2.0.
+
+## Version Dependencies
+The storage dependency is SQLite in version 1.0.
+
+Context paragraph keeps both version-specific dependencies in one scoped section.
+
+The storage dependency is PostgreSQL in version 2.0.
+Operators should not collapse version 1.0 and version 2.0 dependency records into one single storage dependency.

docs/diataxis/en/explanation/development-progress-dashboard.md

@@ -80,7 +80,7 @@ Fresh implementation evidence in this slice:
 - The runtime probe `platform_scoped_ownership_identity_probe_en`, backed by `Knowledge_Base/ragplatformqualifier`, extends that platform guard to controlled ownership identity facts: Windows `Release Ops` and Android `Rollback Team` owners remain platform-qualified evidence rather than a false conflict.
 - The runtime probes `cross_document_environment_scoped_ownership_identity_probe_en`, `cross_document_version_scoped_ownership_identity_probe_en`, and `cross_document_platform_scoped_ownership_identity_probe_en`, backed by `Knowledge_Base/ragconditionownercrossscope`, now verify that the full-document cross-document conflict scanner preserves environment-, version-, and platform-qualified owner facts across separate scoped documents instead of producing false `conflict` fragments.
 - The runtime probes `conflicting_endpoint_evidence_probe_en` and `environment_scoped_endpoint_probe_en`, backed by `Knowledge_Base/ragendpointconflict` and `Knowledge_Base/ragendpointqualifier`, now extend controlled semantic-conflict coverage to explicit endpoint/url/uri/route facts. Same-section `/api/v1/hooks` versus `/api/v2/hooks` produces a `conflict` fragment and `context_assembly` degradation, while staging and production endpoint routes stay environment-qualified evidence without a false conflict. Endpoint path segments such as `/v1/` are treated as route values, not version scopes.
-- The runtime probes `conflicting_dependency_evidence_probe_en` and `environment_scoped_dependency_probe_en`, backed by `Knowledge_Base/ragdependencyconflict` and `Knowledge_Base/ragdependencyqualifier`, now extend controlled semantic-conflict coverage to explicit dependency/package/provider/driver/runtime/library/module/plugin/adapter facts. Same-section SQLite versus PostgreSQL storage dependency statements produce a `conflict` fragment and `context_assembly` degradation, while staging and production dependency records stay environment-qualified evidence without a false conflict.
+- The runtime probes `conflicting_dependency_evidence_probe_en`, `conflicting_multi_document_dependency_evidence_probe_en`, `environment_scoped_dependency_probe_en`, and `version_scoped_dependency_probe_en`, backed by `Knowledge_Base/ragdependencyconflict`, `Knowledge_Base/ragdependencymulticonflict`, `Knowledge_Base/ragdependencyqualifier`, and `Knowledge_Base/ragdependencyversionqualifier`, now extend controlled semantic-conflict coverage to explicit dependency/package/provider/driver/runtime/library/module/plugin/adapter facts. Same-section and cross-document SQLite versus PostgreSQL storage dependency statements produce `conflict` fragments and `context_assembly` degradation, while staging/production and version-1.0/version-2.0 dependency records stay condition-qualified evidence without false conflicts.
 - The runtime probe `causal_answer_profile_budget_en`, backed by `Knowledge_Base/ragcausalprofile`, now verifies that why/cause/mechanism-style requests use a bounded causal RAG profile (`20` fragments, `1500` chars per fragment, `7600` total chars), keep the source boundary at `full_document`, and return one public answer with mechanism and downstream evidence rather than a single definition sentence.
 - The runtime probe `conflicting_multi_document_evidence_probe_en`, backed by `Knowledge_Base/ragmulticonflict`, now verifies that contradictory `+/-0.10 mm` and `+/-0.50 mm` calibration-tolerance facts across two scoped documents produce a cross-document `conflict` fragment, stay visible in the one public answer, and degrade under `context_assembly`.
 - The runtime probe `full_document_scan_remote_conflict_probe_en`, backed by `Knowledge_Base/ragfullscan`, now verifies the corrected source-boundary rule: the local paragraph window is not the maximum range. Two selected documents are read in full, remote appendix facts outside the matched opening spans are scanned for structured conflict evidence, and only the budgeted `RagContextPack` is capped before model-visible answer composition.

docs/diataxis/zh/explanation/development-progress-dashboard.md

@@ -72,7 +72,7 @@
 - runtime probe `temporal_scoped_ownership_identity_probe_en` 现在由 `Knowledge_Base/ragtemporalqualifier` 支撑，把 current-vs-historical false-positive guard 扩展到受控责任归属 identity facts：current `Release Ops` owner 与 historical `Rollback Team` owner 会保留为条件限定 evidence，而不是误产出 `conflict` fragment。
 - runtime probe `cross_document_environment_scoped_ownership_identity_probe_en`、`cross_document_version_scoped_ownership_identity_probe_en` 与 `cross_document_platform_scoped_ownership_identity_probe_en` 现在由 `Knowledge_Base/ragconditionownercrossscope` 支撑，验证完整文档 cross-document conflict scanner 会在两个 scoped documents 之间保留 environment / version / platform 限定 owner facts，而不是误产出 `conflict` fragment。
 - runtime probe `conflicting_endpoint_evidence_probe_en` 与 `environment_scoped_endpoint_probe_en` 现在由 `Knowledge_Base/ragendpointconflict` 和 `Knowledge_Base/ragendpointqualifier` 支撑，把受控语义冲突覆盖扩展到显式 endpoint/url/uri/route facts。同一 section 中 `/api/v1/hooks` 与 `/api/v2/hooks` 会产出 `conflict` fragment 并在 `context_assembly` 下降级；staging 与 production endpoint routes 会保留为 environment-qualified evidence，不会误产出 conflict。`/v1/` 这类 endpoint path segment 会被视为 route value，而不是 version scope。
-- runtime probe `conflicting_dependency_evidence_probe_en` 与 `environment_scoped_dependency_probe_en` 现在由 `Knowledge_Base/ragdependencyconflict` 和 `Knowledge_Base/ragdependencyqualifier` 支撑，把受控语义冲突覆盖扩展到显式 dependency/package/provider/driver/runtime/library/module/plugin/adapter facts。同一 section 中 SQLite 与 PostgreSQL storage dependency 会产出 `conflict` fragment 并在 `context_assembly` 下降级；staging 与 production dependency records 会保留为 environment-qualified evidence，不会误产出 conflict。
+- runtime probe `conflicting_dependency_evidence_probe_en`、`conflicting_multi_document_dependency_evidence_probe_en`、`environment_scoped_dependency_probe_en` 与 `version_scoped_dependency_probe_en` 现在由 `Knowledge_Base/ragdependencyconflict`、`Knowledge_Base/ragdependencymulticonflict`、`Knowledge_Base/ragdependencyqualifier` 和 `Knowledge_Base/ragdependencyversionqualifier` 支撑，把受控语义冲突覆盖扩展到显式 dependency/package/provider/driver/runtime/library/module/plugin/adapter facts。同一 section 与跨文档的 SQLite / PostgreSQL storage dependency 会产出 `conflict` fragment 并在 `context_assembly` 下降级；staging / production 与 version 1.0 / version 2.0 dependency records 会保留为条件限定 evidence，不会误产出 conflict。
 
 后续推进：