feat(agent-workspace): cover endpoint conflicts

Author: Jacobinwwey

Knowledge_Base/ragendpointconflict/endpoint conflict probe.md

@@ -0,0 +1,10 @@
+# Endpoint Conflict Probe
+Endpoint conflict probe records competing webhook endpoint values: /api/v1/hooks and /api/v2/hooks.
+
+## Webhook Routing
+The webhook endpoint is /api/v1/hooks.
+
+Context paragraph keeps the endpoint conflict inside one scoped section.
+
+The webhook endpoint is /api/v2/hooks.
+Operators must resolve which webhook endpoint is active before release.

Knowledge_Base/ragendpointqualifier/environment scoped endpoint probe.md

@@ -0,0 +1,10 @@
+# Environment Scoped Endpoint Probe
+Environment scoped endpoint probe records that the webhook endpoint is /api/staging/hooks for staging and /api/prod/hooks for production.
+
+## Environment Routes
+The webhook endpoint is /api/staging/hooks in the staging environment.
+
+Context paragraph keeps both environment-specific endpoints in one scoped section.
+
+The webhook endpoint is /api/prod/hooks in the production environment.
+Operators should not collapse staging and production endpoint records into one single route.

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

@@ -79,6 +79,7 @@ Fresh implementation evidence in this slice:
 - 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 `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 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

@@ -71,6 +71,7 @@
 - runtime probe `platform_scoped_ownership_identity_probe_en` 现在由 `Knowledge_Base/ragplatformqualifier` 支撑，把平台限定 false-positive guard 扩展到受控责任归属 identity facts：Windows `Release Ops` owner 与 Android `Rollback Team` owner 会保留为平台限定 evidence，而不是误产出 `conflict` fragment。
 - 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。
 
 后续推进：
 

docs/plans/2026-07-05-001-feat-rse-document-augmented-rag-plan.md

@@ -451,6 +451,8 @@ flowchart TB
 
 **Cross-document condition-scoped ownership increment (2026-07-07):** `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`, verify that the full-document cross-document conflict scanner preserves environment-, version-, and platform-qualified owner facts across separate scoped documents. The scanner still emits conflicts for unqualified or same-scope ownership identity contradictions; this slice only prevents false positives when the qualifying scope is explicit in the source evidence.
 
+**Endpoint conflict increment (2026-07-07):** `evidenceContextAssembler.ts` now recognizes a conservative `endpoint` comparable-fact class for explicit endpoint/url/uri/route subjects whose values are path- or URL-shaped. `conflicting_endpoint_evidence_probe_en`, backed by `Knowledge_Base/ragendpointconflict`, verifies that `/api/v1/hooks` and `/api/v2/hooks` in one scoped section produce a `conflict` fragment, `borderline/conflict` sufficiency, and `context_assembly` classification. `environment_scoped_endpoint_probe_en`, backed by `Knowledge_Base/ragendpointqualifier`, verifies the hard negative: staging and production endpoint values stay environment-qualified evidence. The endpoint extractor deliberately treats route path segments such as `/v1/` as value text rather than version scopes, while same-environment or unqualified endpoint contradictions remain comparable.
+
 **Location conflict increment (2026-07-07):** `evidenceContextAssembler.ts` now recognizes a conservative `location` comparable-fact class for explicit location/site/region/zone/room/rack/slot/bay subjects. `conflicting_location_evidence_probe_en`, backed by `Knowledge_Base/raglocationconflict`, verifies that Rack A vs Rack B placement facts in one scoped section produce a `conflict` fragment, `borderline/conflict` sufficiency, and `context_assembly` classification. `temporal_scoped_location_probe_en`, backed by `Knowledge_Base/ragtemporalqualifier`, verifies the opposite hard negative: current and historical placement facts remain condition-qualified evidence and do not produce a false conflict. This extends controlled semantic conflict coverage beyond measurement/date/state while deliberately avoiding a claim of open-domain semantic contradiction detection.
 
 **Quantity conflict increment (2026-07-07):** `evidenceContextAssembler.ts` now recognizes a conservative `quantity` comparable-fact class for explicit unitless operational subjects such as count, limit, threshold, budget, quota, capacity, size, window, attempts, and retries. `conflicting_quantity_limit_evidence_probe_en`, backed by `Knowledge_Base/ragquantityconflict`, verifies that `retry limit is 3` and `retry limit is 5` inside one scoped section produce a `conflict` fragment, `borderline/conflict` sufficiency, and `context_assembly` classification instead of publishing one stable retry limit. This extends structured conflict coverage to unitless operational limits while keeping extraction deliberately narrow.
@@ -494,6 +496,7 @@ flowchart TB
   - explicit version-qualified state false-positive guards through `version_scoped_state_status_probe_en`;
   - explicit platform-qualified state false-positive guards through `platform_scoped_state_status_probe_en`;
   - cross-document condition-scoped ownership false-positive guards through `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`;
+  - controlled endpoint/route conflict and environment-qualified endpoint false-positive coverage through `conflicting_endpoint_evidence_probe_en` and `environment_scoped_endpoint_probe_en`;
   - explicit unitless quantity/limit conflict coverage through `conflicting_quantity_limit_evidence_probe_en`;
   - cross-document plural unitless quantity conflict coverage through `conflicting_multi_document_quantity_evidence_probe_en`;
   - same-document and cross-document controlled ownership identity conflict coverage through `conflicting_ownership_identity_evidence_probe_en` and `conflicting_multi_document_ownership_identity_evidence_probe_en`;
@@ -534,6 +537,7 @@ flowchart TB
 - Runtime: `what is platform scoped state status probe?` reads `Knowledge_Base/ragplatformqualifier/platform scoped state status probe.md`, preserves Windows-enabled and Android-disabled state facts as platform-qualified evidence, keeps `forbiddenRagRoles: ['conflict']`, and returns `sufficient/none` instead of degrading as a conflict.
 - Runtime: `what is platform scoped deployment owner probe?` reads `Knowledge_Base/ragplatformqualifier/platform scoped deployment owner probe.md`, preserves Windows `Release Ops` and Android `Rollback Team` owner facts as platform-qualified identity evidence, keeps `forbiddenRagRoles: ['conflict']`, and returns `sufficient/none` instead of degrading as a conflict.
 - Runtime: the three `cross_document_*_scoped_ownership_identity_probe_en` probes read paired files under `Knowledge_Base/ragconditionownercrossscope`, preserve environment-, version-, and platform-qualified `Release Ops` / `Rollback Team` owner facts as cross-document scoped identity evidence, keep `forbiddenRagRoles: ['conflict']`, and return `sufficient/none` instead of degrading as cross-document conflicts.
+- Runtime: `what is endpoint conflict probe?` reads `Knowledge_Base/ragendpointconflict/endpoint conflict probe.md`, preserves `/api/v1/hooks` and `/api/v2/hooks` as controlled endpoint conflict evidence, keeps both route values in one public answer, and classifies the degradation under `context_assembly`. `what is environment scoped endpoint probe?` reads `Knowledge_Base/ragendpointqualifier/environment scoped endpoint probe.md`, keeps staging and production endpoint values condition-qualified, and forbids a false `conflict` fragment.
 - Runtime: `what is quantity limit conflict probe?` reads `Knowledge_Base/ragquantityconflict/quantity limit conflict probe.md`, preserves `retry limit is 3` and `retry limit is 5` as unitless quantity conflict evidence, keeps both values in one public answer, and classifies the degradation under `context_assembly`.
 - Runtime: `compare nominal retry attempts quantity conflict probe with field retry attempts quantity conflict evidence` reads two scoped files under `Knowledge_Base/ragquantitymulticonflict`, preserves plural `retry attempts are 3` and `retry attempts are 5` statements as a cross-document unitless quantity `conflict` fragment, keeps both values in one public answer, and classifies the degradation under `context_assembly`.
 - Runtime: `what is ownership conflict probe?` reads `Knowledge_Base/ragidentityconflict/ownership conflict probe.md`, preserves `deployment owner is Release Ops` and `deployment owner is Rollback Team` as a controlled ownership identity `conflict` fragment, keeps both values in one public answer, and classifies the degradation under `context_assembly`.
@@ -960,6 +964,8 @@ flowchart TB
 
 **跨文档条件限定责任归属增量（2026-07-07）：** 由 `Knowledge_Base/ragconditionownercrossscope` 支撑的 `cross_document_environment_scoped_ownership_identity_probe_en`、`cross_document_version_scoped_ownership_identity_probe_en` 与 `cross_document_platform_scoped_ownership_identity_probe_en` 验证完整文档 cross-document conflict scanner 会在两个 scoped documents 之间保留 environment / version / platform 限定 owner facts。未限定或同一 scope 内的责任归属 identity 矛盾仍会产出 conflict；该切片只防止 source evidence 中已有显式限定语时的误报。
 
+**Endpoint 事实增量（2026-07-07）：** `evidenceContextAssembler.ts` 现在加入保守的 `endpoint` comparable-fact 类，只识别显式 endpoint/url/uri/route subject，且 value 必须是 path 或 URL 形态。由 `Knowledge_Base/ragendpointconflict` 支撑的 `conflicting_endpoint_evidence_probe_en` 验证同一 scoped section 中 `/api/v1/hooks` 与 `/api/v2/hooks` 会产出 `conflict` fragment、`borderline/conflict` sufficiency 和 `context_assembly` 归因。由 `Knowledge_Base/ragendpointqualifier` 支撑的 `environment_scoped_endpoint_probe_en` 验证相反 hard negative：staging 与 production endpoint value 保持 environment-qualified evidence。endpoint 抽取会把 `/v1/` 这类 route path segment 当作 value text，而不是 version scope；同一 environment 或未限定的 endpoint 矛盾仍然会进入 conflict 路径。
+
 **位置事实增量（2026-07-07）：** `evidenceContextAssembler.ts` 现在加入保守的 `location` comparable-fact 类，只识别 subject 明确包含 location/site/region/zone/room/rack/slot/bay 的位置事实。由 `Knowledge_Base/raglocationconflict` 支撑的 `conflicting_location_evidence_probe_en` 验证同一 scoped section 中 Rack A 与 Rack B 的 control-module placement 事实会产出 `conflict` fragment、`borderline/conflict` sufficiency 和 `context_assembly` 归因。由 `Knowledge_Base/ragtemporalqualifier` 支撑的 `temporal_scoped_location_probe_en` 验证相反 hard negative：current 与 historical placement 事实保持条件限定 evidence，不会误产出 `conflict`。这把受控语义 conflict 覆盖从 measurement/date/state 扩展到 location，但不声称已经解决开放域语义矛盾检测。
 
 **数量事实增量（2026-07-07）：** `evidenceContextAssembler.ts` 现在加入保守的 `quantity` comparable-fact 类，只识别 count、limit、threshold、budget、quota、capacity、size、window、attempts、retries 等显式无单位工程数量主题。由 `Knowledge_Base/ragquantityconflict` 支撑的 `conflicting_quantity_limit_evidence_probe_en` 验证同一 scoped section 中 `retry limit is 3` 与 `retry limit is 5` 会产出 `conflict` fragment、`borderline/conflict` sufficiency 和 `context_assembly` 归因，而不是发布单一稳定 retry limit。这把 structured conflict 覆盖扩展到无单位 operational limit，但抽取口径仍保持窄范围。
@@ -1013,6 +1019,7 @@ flowchart TB
 - `what is platform scoped state status probe?` 会读取 `Knowledge_Base/ragplatformqualifier/platform scoped state status probe.md`，把 Windows-enabled 与 Android-disabled 状态事实保留为平台限定 evidence，保持 `forbiddenRagRoles: ['conflict']`，并返回 `sufficient/none`，而不是误降级为 conflict。
 - `what is platform scoped deployment owner probe?` 会读取 `Knowledge_Base/ragplatformqualifier/platform scoped deployment owner probe.md`，把 Windows `Release Ops` 与 Android `Rollback Team` owner 事实保留为平台限定 identity evidence，保持 `forbiddenRagRoles: ['conflict']`，并返回 `sufficient/none`，而不是误降级为 conflict。
 - 三个 `cross_document_*_scoped_ownership_identity_probe_en` 探针会读取 `Knowledge_Base/ragconditionownercrossscope` 下的成对文件，把 environment / version / platform 限定的 `Release Ops` / `Rollback Team` owner 事实保留为跨文档 scoped identity evidence，保持 `forbiddenRagRoles: ['conflict']`，并返回 `sufficient/none`，而不是误降级为跨文档 conflict。
+- `what is endpoint conflict probe?` 会读取 `Knowledge_Base/ragendpointconflict/endpoint conflict probe.md`，把 `/api/v1/hooks` 与 `/api/v2/hooks` 保留为受控 endpoint conflict evidence，在单条公开回答中保留两侧 route value，并把降级归类到 `context_assembly`。`what is environment scoped endpoint probe?` 会读取 `Knowledge_Base/ragendpointqualifier/environment scoped endpoint probe.md`，把 staging 与 production endpoint values 保留为条件限定 evidence，并禁止误产出 `conflict` fragment。
 - `what is quantity limit conflict probe?` 会读取 `Knowledge_Base/ragquantityconflict/quantity limit conflict probe.md`，把 `retry limit is 3` 与 `retry limit is 5` 保留为无单位数量冲突 evidence，在单条公开回答中保留两侧数值，并把降级归类到 `context_assembly`。
 - `compare handoff deployment owner conflict probe with rollback deployment owner conflict evidence` 会读取 `Knowledge_Base/ragidentitymulticonflict` 下的两个 scoped 文件，把 `deployment owner is Release Ops` 与 `deployment owner is Rollback Team` 保留为跨文档受控责任归属 `conflict` fragment，在单条公开回答中保留两侧值，并把降级归类到 `context_assembly`。
 - `why causal answer profile probe needs bounded evidence?` 会读取 `Knowledge_Base/ragcausalprofile/causal answer profile probe.md`，使用有界 causal RAG profile（`20` 个 fragment、每 fragment `1500` 字符、总计 `7600` 字符），保持 `full_document` source boundary，并在单条公开回答中返回 mechanism 与 downstream evidence。