test(agent-workspace): guard environment scoped owners

Author: Jacobinwwey

Knowledge_Base/ragenvironmentqualifier/environment scoped deployment owner probe.md

@@ -0,0 +1,9 @@
+# Environment Scoped Deployment Owner Probe
+Environment scoped deployment owner probe validates that the deployment owner is Release Ops in the staging environment while production owner facts remain environment-qualified evidence rather than a conflict.
+
+## Deployment Owner By Environment
+The deployment owner is Release Ops in the staging environment.
+
+Operators should preserve the environment label before comparing owner records.
+
+The deployment owner is Rollback Team in the production environment.

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

@@ -5,7 +5,7 @@ It tracks what is already implemented, where the hard gaps remain, and how to ve
 
 ## 2026-07-05 RSE Document-Augmented Graph RAG Implementation Plan
 
-This slice now tracks implementation progress for richer Knowledge Workspace answers. The concrete plan remains at [RSE document-augmented graph RAG answer pipeline](../../../plans/2026-07-05-001-feat-rse-document-augmented-rag-plan.md), but the branch has moved beyond planning: the deterministic RSE/document-augmentation path, full-document graph-neighbor augmentation, query-intent graph-neighbor ranking, intent-aware graph connection-path ordering, intent-aligned graph-window ambiguity filtering, budgeted context pack, stable RAG context replay ids, provider-backed sufficiency trace, bounded one-step recovery, RAG failure-stage classification, RAG-aware one-message release review, claim-level citation-backed RAG release gating, prompt/preamble artifact filtering for public RAG clauses, answer claim-to-citation trace/export mapping, operand-aware compare answer-profile budgeting, how-to answer-profile budgeting, causal answer-profile budgeting, generic answer-profile ranking, Mermaid-label evidence extraction, runtime verifier fields, graph successor-window and graph-diagnostics verifier assertions, context-budget truncation/drop/malformed-provider/timeout-provider/graphintent probe coverage, conflicting adjacent, same-section non-adjacent, cross-document structured measurement/date/location/quantity evidence including plural unitless quantity facts, same-document and cross-document controlled ownership identity conflicts, full-document remote-scan hard-negative coverage, controlled current-vs-historical, environment-qualified, version-qualified, and platform-qualified false-positive guards, single- and multi-neighbor graph source-unavailable hard-negative coverage, localized frontend RAG status, and export RAG trace preservation are implemented. Calibrated graph-confidence thresholds, broader replay tooling over larger corpora, more natural synthesis over label-heavy evidence, further profile-specific release-budget calibration, broader semantic conflict classes, and larger runtime probes remain follow-up work.
+This slice now tracks implementation progress for richer Knowledge Workspace answers. The concrete plan remains at [RSE document-augmented graph RAG answer pipeline](../../../plans/2026-07-05-001-feat-rse-document-augmented-rag-plan.md), but the branch has moved beyond planning: the deterministic RSE/document-augmentation path, full-document graph-neighbor augmentation, query-intent graph-neighbor ranking, intent-aware graph connection-path ordering, intent-aligned graph-window ambiguity filtering, budgeted context pack, stable RAG context replay ids, provider-backed sufficiency trace, bounded one-step recovery, RAG failure-stage classification, RAG-aware one-message release review, claim-level citation-backed RAG release gating, prompt/preamble artifact filtering for public RAG clauses, answer claim-to-citation trace/export mapping, operand-aware compare answer-profile budgeting, how-to answer-profile budgeting, causal answer-profile budgeting, generic answer-profile ranking, Mermaid-label evidence extraction, runtime verifier fields, graph successor-window and graph-diagnostics verifier assertions, context-budget truncation/drop/malformed-provider/timeout-provider/graphintent probe coverage, conflicting adjacent, same-section non-adjacent, cross-document structured measurement/date/location/quantity evidence including plural unitless quantity facts, same-document and cross-document controlled ownership identity conflicts, full-document remote-scan hard-negative coverage, controlled current-vs-historical, environment-qualified, version-qualified, and platform-qualified false-positive guards including environment-scoped ownership identity, single- and multi-neighbor graph source-unavailable hard-negative coverage, localized frontend RAG status, and export RAG trace preservation are implemented. Calibrated graph-confidence thresholds, broader replay tooling over larger corpora, more natural synthesis over label-heavy evidence, further profile-specific release-budget calibration, broader semantic conflict classes, and larger runtime probes remain follow-up work.
 
 Current code-vs-plan reading:
 
@@ -72,6 +72,7 @@ Fresh implementation evidence in this slice:
 - The runtime probe `conflicting_multi_document_ownership_identity_evidence_probe_en`, backed by `Knowledge_Base/ragidentitymulticonflict`, verifies the same ownership identity fact class across two scoped documents: the handoff-side `Release Ops` owner and rollback-side `Rollback Team` owner produce one cross-document `conflict` fragment and preserve both values in the public answer.
 - The runtime probe `temporal_scoped_location_probe_en`, backed by `Knowledge_Base/ragtemporalqualifier`, verifies the paired hard negative: current and historical placement facts stay in separate comparable scopes, the public answer can use the current Rack A fact, and the RAG pack does not emit a false `conflict` fragment.
 - The runtime probe `environment_scoped_state_status_probe_en`, backed by `Knowledge_Base/ragenvironmentqualifier`, now verifies the next condition-qualified guard: staging-enabled and production-disabled status facts stay in explicit environment scopes, the RAG pack forbids `conflict`, and sufficiency remains `sufficient/none` instead of degrading a cross-environment state difference.
+- The runtime probe `environment_scoped_ownership_identity_probe_en`, backed by `Knowledge_Base/ragenvironmentqualifier`, extends the same environment guard to controlled ownership identity facts: staging `Release Ops` and production `Rollback Team` owners stay environment-qualified evidence rather than a false conflict.
 - The runtime probe `version_scoped_state_status_probe_en`, backed by `Knowledge_Base/ragversionqualifier`, now verifies the next condition-qualified guard: version-1.0-enabled and version-2.0-disabled status facts stay in explicit version scopes, the RAG pack forbids `conflict`, and sufficiency remains `sufficient/none` instead of degrading a cross-version state difference.
 - The runtime probe `platform_scoped_state_status_probe_en`, backed by `Knowledge_Base/ragplatformqualifier`, now verifies the next condition-qualified guard: Windows-enabled and Android-disabled status facts stay in explicit platform scopes, the RAG pack forbids `conflict`, and sufficiency remains `sufficient/none` instead of degrading a cross-platform state difference.
 - 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.

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

@@ -66,6 +66,7 @@
 - runtime probe `conflicting_multi_document_quantity_evidence_probe_en` 现在由 `Knowledge_Base/ragquantitymulticonflict` 支撑，验证跨文档复数无单位数量事实：`retry attempts are 3` 与 `retry attempts are 5` 会产出跨文档 `conflict` fragment，在单条公开回答中保留两侧数值，并在 `context_assembly` 下显式降级；该切片只扩大显式 quantity subject 的语法覆盖，不把开放域数量语义冲突纳入已完成范围。
 - runtime probe `conflicting_ownership_identity_evidence_probe_en` 现在由 `Knowledge_Base/ragidentityconflict` 支撑，验证受控责任归属事实：显式 owner/assignee/contact/maintainer/team/group subject 中 `Release Ops` 与 `Rollback Team` 会产出 `conflict` fragment，在单条公开回答中保留两侧证据，并在 `context_assembly` 下显式降级；该切片只覆盖责任归属 identity 类，不把开放域身份或语义矛盾纳入已完成范围。
 - runtime probe `conflicting_multi_document_ownership_identity_evidence_probe_en` 现在由 `Knowledge_Base/ragidentitymulticonflict` 支撑，把同一受控责任归属 identity fact class 扩展到两个 scoped documents：handoff 侧 `Release Ops` owner 与 rollback 侧 `Rollback Team` owner 会产出一个 cross-document `conflict` fragment，并在公开回答中保留两侧值。
+- runtime probe `environment_scoped_ownership_identity_probe_en` 现在由 `Knowledge_Base/ragenvironmentqualifier` 支撑，把环境限定 false-positive guard 扩展到受控责任归属 identity facts：staging `Release Ops` owner 与 production `Rollback Team` owner 会保留为环境限定 evidence，而不是误产出 `conflict` fragment。
 
 后续推进：