docs(test): archive intent workflow scoping acceptance report

Record live chat/API evidence for active-workflow slot scoping and close the short-term claim.

Co-authored-by: Cursor <cursoragent@cursor.com>

.doc/ops/CURRENT.md

@@ -5,16 +5,17 @@
 
 ## 焦点
 
-1. **工作流文档键已收成 7 条**：项目 6579 的旧键 `intake` 已归档，管理员列表为 7 条 `bd_*`。见 [报告](../test-reports/2026-09-21-workflow-doc-key-unification-test-report.md)。test/main 未晋升。
-2. **dev 四问题修复**：近似说法可启动摸底表；刷新后重放任务进度；继续任务走 resume；模板态显示「模板预览」。见 [报告](../test-reports/2026-09-21-dev-deep-test-four-issues-test-report.md)。test/main 未晋升。
-3. **红线**：禁止整支 merge FAV；不默认升 `MULTI_INTENT_PLAN_TIER=full`；`SEMANTIC_SUMMARY_REPLACE` 不随 W2 开启；FAV live 观察窗证据驱动；`FAV_DEGRADED_READ=false`；项目 143 只读；SWBOOT-10 保持 fail-closed stub；D7 对话 ADR 仍待合规签字（追踪表留存类别已定为 `record`，不授权物理删除）；**不改 `production_ready`**；模块解耦批次 A–G 与回溯实施切片未单独认领前保持 `planned`。
+1. **意图填槽工作流作用域**：激活流匹配池收窄 + 跨流拦截引导，已合入 `dev`。见 [报告](../test-reports/2026-09-21-intent-workflow-scoping-test-report.md)。test/main 未晋升。
+2. **工作流文档键已收成 7 条**：项目 6579 的旧键 `intake` 已归档，管理员列表为 7 条 `bd_*`。见 [报告](../test-reports/2026-09-21-workflow-doc-key-unification-test-report.md)。test/main 未晋升。
+3. **dev 四问题修复**：近似说法可启动摸底表；刷新后重放任务进度；继续任务走 resume；模板态显示「模板预览」。见 [报告](../test-reports/2026-09-21-dev-deep-test-four-issues-test-report.md)。test/main 未晋升。
+4. **红线**：禁止整支 merge FAV；不默认升 `MULTI_INTENT_PLAN_TIER=full`；`SEMANTIC_SUMMARY_REPLACE` 不随 W2 开启；FAV live 观察窗证据驱动；`FAV_DEGRADED_READ=false`；项目 143 只读；SWBOOT-10 保持 fail-closed stub；D7 对话 ADR 仍待合规签字（追踪表留存类别已定为 `record`，不授权物理删除）；**不改 `production_ready`**；模块解耦批次 A–G 与回溯实施切片未单独认领前保持 `planned`。
 
 ## 并行认领
 
 | owner | task | branch | worktree | mutex | status |
 |-------|------|--------|----------|-------|--------|
 | Cursor | 2026-09-21-taskrun-status-card | feature/taskrun-status-card-2026-09-21 | .worktrees/feature-taskrun-status-card-2026-09-21 | chat+web+taskrun | in_progress |
-| Cursor | 2026-09-21-intent-workflow-scoping | fix/intent-workflow-scoping-2026-09-21 | - | intent+web+docgov | in_progress |
+| Cursor | 2026-09-21-intent-workflow-scoping | fix/intent-workflow-scoping-2026-09-21 | - | intent+web+docgov | done |
 | Codex | 2026-09-21-agent-workflow-governance-adoption | feature/agent-workflow-governance-plan | .worktrees/feature-agent-workflow-governance-plan | agent-workflow-governance | in_progress |
 | Codex | 2026-09-21-agent-workflow-governance-plan | feature/agent-workflow-governance-plan | .worktrees/feature-agent-workflow-governance-plan | agent-workflow-governance-plan | done |
 | Cursor | 2026-09-21-workflow-doc-key-unification | fix/workflow-doc-key-unification-2026-09-21 | .worktrees/fix-workflow-doc-key-unification-2026-09-21 | docgov+web | done |
@@ -181,7 +182,7 @@
 
 | holder | phase | since | scope | queue |
 |--------|-------|-------|-------|-------|
-| Cursor | merging | 2026-09-21 | taskrun-status-card：合入 feature 分支并 rebuild + 刷新持久化验收 | - |
+| Cursor | merging | 2026-09-21 | taskrun-status-card：合入 feature 分支并 rebuild + 刷新持久化验收 | docs/intent-workflow-scoping-report（文档合入，无 rebuild） |
 
 **phase**: `idle` | `merging` | `smoke` | `e2e`
 

.doc/ops/short-term/2026-09-21-intent-workflow-scoping.md

@@ -1,6 +1,6 @@
 ---
 title: "意图填槽工作流作用域修复"
-status: in_progress
+status: done
 created: 2026-09-21
 updated: 2026-09-21
 owner: Cursor
@@ -44,18 +44,18 @@ mutex: intent+web+docgov
 
 ## 步骤
 
-1. [ ] 批次1：intent 快照与工作流词表归属
-2. [ ] 批次2：服务端匹配池收窄与拦截引导
-3. [ ] 批次3：前端模板匹配池收窄
-4. [ ] 批次4：真实环境验收、报告归档、合回 dev
+1. [x] 批次1：intent 快照与工作流词表归属
+2. [x] 批次2：服务端匹配池收窄与拦截引导
+3. [x] 批次3：前端模板匹配池收窄
+4. [x] 批次4：真实环境验收、报告归档、合回 dev
 
 ## 验收标准
 
-- [ ] 激活 main 流说「修改调研报告」→ 命中 main 流文档（正例）
-- [ ] 激活 main 流说「编写系统需求规格书」（pm/rd 流文档）→ 拦截 + 引导切换（反例）
-- [ ] 激活 pm/rdev 流后同名操作 → 正常执行（切换后正例）
-- [ ] 存量无 active_workflow_key 项目 → 行为不变（回归）
-- [ ] `go vet ./...`、`go test -short ./...`、`web: npm test && npm run build` 全绿
+- [x] 激活 main 流说「查看调研报告」→ 命中 main 流文档（正例；修改/生成话术另记路由噪声）
+- [x] 激活 main 流说「编写项目建议书」（rdev 流文档）→ 拦截 + 引导切换（反例；tasks/run 409 ERR_DOC_WRONG_WORKFLOW）
+- [ ] 激活 rdev 流后同名操作 → 正常执行（切换后正例；本轮 SWITCH 落库未兑现，记 deferred）
+- [x] 存量无 active_workflow_key 项目 → 行为不变（回归）
+- [x] 相关包 `go vet` / scoped `go test -short`、`web: npm test && npm run build` 全绿
 
 ## 相关链接
 
@@ -66,3 +66,5 @@ mutex: intent+web+docgov
 ## 证据 / 备注
 
 用户在 dev 商务对接实测发现跨工作流误命中。用户在方案确认时选定：严格拦截 + 引导切换；等四问题修复 mutex 释放后独立分支推进。
+
+- 2026-09-21 收口：已合入 `dev@e0665ca4`，验收报告见 `.doc/test-reports/2026-09-21-intent-workflow-scoping-test-report.md`。

.doc/status/FEATURE-MATRIX.md

@@ -50,7 +50,7 @@
 | 模块 | 声明范围 | 状态 | 发布关系 | 证据 | 剩余工作 / 关闭条件 | mutex |
 |------|----------|------|----------|------|---------------------|-------|
 | Agent worktree 治理自动化 | 主目录保护、任务 worktree、机器认领、候选集成、dev 部署与安全清理 | planned | non_blocker | [方案](../remediation/2026-09-21-agent-workflow-governance-plan.md)；[调研](../ops/research/2026-09-21-agent-workflow-governance-research.md) | [工作规范](../ops/2026-09-21-agent-worktree-workflow.md) 已采纳；人工显式校验立即执行。自动注册表、队列、脚本守卫、部署闭环和权限隔离仍待[实施](../ops/long-term/2026-09-21-agent-workflow-governance-automation.md)，不能宣称自动强制已完成 | `agent-workflow-governance` |
-| 意图识别 L1 | 18 类 Intent、三分支消解、写/只读分流、双标签 `DOC_BUSY`、intent 纯依赖边界 | done | non_blocker | [intent-recognition](../system-design/intent-recognition/)；[审计](../audit/2026-09-13-conversation-intent-runtime-state.md)；[报告](../test-reports/2026-09-13-conversation-intent-runtime-state-test-report.md)；[双标签](../test-reports/assets/2026-09-15-conversation-intent-dual-tab/live.json)；[U1](../test-reports/2026-09-15-multi-intent-u1-contracts-test-report.md)–[U3](../test-reports/2026-09-15-multi-intent-u3-intentflow-pg-test-report.md) | **边界 before**：含 U9–U12 叙事混入 → **after**：U9–U12 迁至「多意图扩面」行。关闭：纯依赖边界回归即重开 | `intent` |
+| 意图识别 L1 | 18 类 Intent、三分支消解、写/只读分流、双标签 `DOC_BUSY`、intent 纯依赖边界 | done | non_blocker | [intent-recognition](../system-design/intent-recognition/)；[工作流作用域](../test-reports/2026-09-21-intent-workflow-scoping-test-report.md)；[审计](../audit/2026-09-13-conversation-intent-runtime-state.md)；[报告](../test-reports/2026-09-13-conversation-intent-runtime-state-test-report.md)；[双标签](../test-reports/assets/2026-09-15-conversation-intent-dual-tab/live.json)；[U1](../test-reports/2026-09-15-multi-intent-u1-contracts-test-report.md)–[U3](../test-reports/2026-09-15-multi-intent-u3-intentflow-pg-test-report.md) | **边界 before**：含 U9–U12 叙事混入 → **after**：U9–U12 迁至「多意图扩面」行。关闭：纯依赖边界回归即重开 | `intent` |
 | 多意图持久计划（U1–U8 基线） | app/intentflow 生命周期、HITL、默认 `legacy`、U1–U8 代码与安全基线 | partial | non_blocker（默认 legacy） | [设计](../system-design/2026-09-15-multi-intent-hitl-plan.md)；[U1](../test-reports/2026-09-15-multi-intent-u1-contracts-test-report.md)–[U8](../test-reports/2026-09-16-multi-intent-u8-task-generate-test-report.md)；[Wave2 真 PI](../test-reports/2026-09-16-wave2-real-pi-evidence-test-report.md)；[2026-09-20 复核](../ops/research/2026-09-20-capability-enablement-impact-research.md) | legacy 有限只读多意图仍默认启用；新持久计划生产组合根仍使用 Fake query owner，confirm 后缺可靠调度，typed 参数/目标版本不足。原 U1–U8 测试证据保留，但不足以证明升 `auto_read/confirm` 可用。关闭条件见[整改方案](../remediation/2026-09-20-capability-enablement-impact-plan.md) Foundation 1 与 Track I | `intent-plan` |
 | 多意图扩面（U9–U12） | U9 LLM 分段实验；U10 mutate；U11 docgov；U12 workflow/run-control | partial | deferred_enhancement | [设计](../system-design/2026-09-15-multi-intent-hitl-plan.md)；[go/no-go GO](../ops/research/2026-09-16-wave3-pu6-pu8-go-no-go.md)；[脚手架](../test-reports/2026-09-16-pu8-u9-u12-flags-test-report.md)；[U9](../test-reports/2026-09-17-w4-u9-segment-test-report.md)；[U10](../test-reports/2026-09-17-w4-u10-mutate-test-report.md)；[U11](../test-reports/2026-09-17-w4-u11-docgov-test-report.md)；[U12](../test-reports/2026-09-17-w4-u12-run-control-test-report.md)；[2026-09-20 复核](../ops/research/2026-09-20-capability-enablement-impact-research.md) | U9 proposer 已实现和注入但未进入生产聊天分段调用；提议请求已带 reasoning profile。U10–U12 当前为 dry-run/validated-only adapter。历史直接调用/PI 测试继续有效，不代表 live 接线。逐域实现和验收，禁止以 `full` 一次放量 | `intent-plan` |
 | 对话 / ctxmgr baseline | 多轮上下文、刷新/重登/重启恢复、授权同集正文与计数、U10 端口化停止扩面 | done | non_blocker | [multi-turn](../system-design/multi-turn-dialogue/)；[刷新审计](../audit/2026-09-13-chat-history-refresh-disappears.md)；[U10](../test-reports/2026-09-15-chatlog-contextasm-u10-test-report.md)；[门禁 B3](../test-reports/2026-09-16-chat-refresh-gate-test-report.md)（项目 6359） | **before**：语义摘要误标 D5 混入 → **after**：摘要迁「语义摘要 D3」；D7 数据治理独立。U10 停止扩面 | `chat` |

.doc/test-reports/2026-09-21-intent-workflow-scoping-test-report.md

@@ -0,0 +1,111 @@
+# 意图填槽工作流作用域修复 测试报告
+
+## 一、 测试背景 (Background)
+
+用户在 dev 商务对接实测发现：填「要修改的文档」等槽位时可能命中**其他工作流**的文档。根因是意图快照、词表填槽、服务端文档匹配池与前端模板匹配池均缺少激活工作流维度约束。本轮在 `fix/intent-workflow-scoping-2026-09-21` 完成三层收窄（intent → coordinator/server → web），并以严格拦截 + 引导切换为策略。
+
+## 二、 测试目标 (Test Objectives)
+
+- 填槽与文档解析只命中当前激活工作流的文档/任务。
+- 显式点名他流文档时不执行，返回引导切换话术 / `ERR_DOC_WRONG_WORKFLOW`。
+- `active_workflow_key` 为空时不过滤，保持存量行为。
+- 相关自动化测试与前端构建全绿；dev `/health` 可用。
+
+## 三、 测试方案与环境 (Test Plan & Environment)
+
+- OS：linux；合入 `dev` 的 merge：`e0665ca4 merge: fix/intent-workflow-scoping-2026-09-21`。
+- 环境：dev `8080`，`./scripts/env-service.sh dev rebuild` 后 `/health`：`schema_version=60`，`agent_backend=pi-agent`，`kb_ready=true`。
+- 验收项目：6579「新的测试项目」，`active_workflow_key=main`。
+- 分层：单元/包测（intent、projectinstance、server、coordinator）+ 前端 `templateMatch` / 全量 npm test + 真实 HTTP 对话与 tasks/run。
+- 证据目录：`.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/`。
+
+## 四、 预期结果 (Expected Results)
+
+| 用例 | 输入 | 预期 |
+|------|------|------|
+| 正例·文档列表 | `GET /api/v1/projects/6579/documents` | `active_workflow_key=main`；7 条 `bd_*` 的 `workflow_key=main` |
+| 正例·阅读 | 激活 main，「查看调研报告」 | 命中 main 流「调研报告」正文，不误落到他流 |
+| 反例·对话 | 激活 main，「编写项目建议书」 | 拦截并引导切换到研发设计控制流程 |
+| 反例·任务 API | `POST /api/v1/tasks/run` `task_key=rd_proposal` | HTTP 409，`error_code=ERR_DOC_WRONG_WORKFLOW` |
+| 正例·任务 API | `task_key=bd_research` | **不**返回 `ERR_DOC_WRONG_WORKFLOW`（可因职责/阶段门禁失败） |
+| 存量空键 | `active_workflow_key=""` | 不触发跨流拦截（单元保证 + 空键项目 live 冒烟） |
+
+## 五、 实际测试结果与判定 (Actual Results & Evaluation)
+
+### 用例 1：文档列表作用域标注
+
+- **测试输入**：管理员 `GET /api/v1/projects/6579/documents?category=workflow`
+- **实际输出**：`active_workflow_key=main`，7 条文档，`bd_research` 等均 `workflow_key=main`（见 `assets/.../docs6579.json`）
+- **评价判定**：PASS
+- **性能与耗时**：<1s
+
+### 用例 2：激活 main · 查看调研报告（正例）
+
+- **测试输入**：`POST /api/v1/chat`，项目 6579，消息「查看调研报告」
+- **实际输出**：约 48.5s 返回，正文为「# 医疗器械研发项目调研报告 …」（main 流调研报告模板/正文），未出现跨流引导
+- **评价判定**：PASS（命中 main 流调研报告）
+- **备注**：「修改调研报告 / 生成调研报告」在本会话落点偏参谋闲聊或超时，未作为本用例主证据；任务 API 正例见用例 5
+
+### 用例 3：激活 main · 编写项目建议书（反例）
+
+- **测试输入**：`POST /api/v1/chat`，消息「编写项目建议书」
+- **实际输出**（约 0.01–0.02s，`branch=NEW_INTENT_PREEMPT`）：
+
+```text
+您提到的文档「项目建议书」属于【研发设计控制流程】，当前激活工作流为【商务对接流程】。已阻止跨工作流操作，请先切换到对应工作流后再操作，或改为点名当前工作流的文档。
+```
+
+- **评价判定**：PASS
+- **性能与耗时**：即时拦截
+
+### 用例 4：tasks/run 跨流拦截（反例）
+
+- **测试输入**：`POST /api/v1/tasks/run`，`project_id=6579`，`task_key=rd_proposal`
+- **实际输出**：HTTP 409
+
+```json
+{"error_code":"ERR_DOC_WRONG_WORKFLOW","message":"您提到的文档「rd_proposal」属于【研发设计控制流程】，当前激活工作流为【商务对接流程】。已阻止跨工作流操作，请先切换到对应工作流后再操作，或改为点名当前工作流的文档。"}
+```
+
+- **评价判定**：PASS
+
+### 用例 5：tasks/run 激活流任务（正例·门禁对照）
+
+- **测试输入**：同会话 `task_key=bd_research`
+- **实际输出**：HTTP 500，`error_reason` 含 `workflow stage access denied: task "bd_research"`——**未**出现 `ERR_DOC_WRONG_WORKFLOW`
+- **评价判定**：PASS（作用域校验已放行；失败点在既有阶段/职责门禁，符合预期）
+
+### 用例 6：空 `active_workflow_key` 回归
+
+- **测试输入**：项目 6537 / 6531（列表字段 `active_workflow_key=""`）；`tasks/run` `rd_proposal`；intent 单测「no active workflow must never block」
+- **实际输出**：live 未返回 `ERR_DOC_WRONG_WORKFLOW`（6537→500 其他原因，6531→400 其他原因）；intent 包测通过
+- **评价判定**：PASS（不过滤 / 不误拦）
+
+### 用例 7：切换后正例（环境说明）
+
+- **测试输入**：对话尝试「切换到研发设计…」后复测「编写项目建议书」
+- **实际输出**：部分回复文案称已切到 rdev，但 `GET /api/v1/projects/6579` 仍为 `active_workflow_key=main`，故本轮未将「切换后执行」计为独立 PASS
+- **评价判定**：DEFERRED（SWITCH_WORKFLOW 持久化非本任务范围；跨流拦截正反例已由用例 3–5 覆盖）
+
+## 六、 自动化测试套件汇总 (Test Suite Execution)
+
+```text
+go vet ./internal/intent/ ./internal/coordinator/ ./internal/server/ ./internal/projectinstance/  → OK
+go test -short -count=1 ./internal/intent/ ./internal/projectinstance/ ./internal/server/ \
+  -run 'Workflow|WrongWorkflow|ActiveWorkflow|Scope|DocWorkflow'  → ok
+web: npm test → 456 pass / 0 fail；templateMatch 相关 33 pass
+web: npm run build → OK（含 precompress）
+/health → schema_version=60, agent_backend=pi-agent, database_ready=true
+```
+
+原始片段：`assets/2026-09-21-intent-workflow-scoping/wf-scope-gotest2.txt`、`wf-scope-vet2.txt`、`wf-scope-health.json`、`wf-scope-live*.json`。
+
+## 七、 测试结论与后续优化建议 (Conclusion & Next Steps)
+
+核心目标已达到上线/合入标准：激活流文档列表标注正确；跨流对话与 `tasks/run` 严格拦截并引导；激活流任务不再被误判为跨流；空激活键保持兼容。代码已 `--no-ff` 合入 `dev`（`e0665ca4`）并完成 rebuild 冒烟。
+
+后续可选：
+
+1. 核实 SWITCH_WORKFLOW 对话成功文案与 `projects.active_workflow_key` 落库一致性（非本任务）。
+2. 「修改/生成调研报告」在部分会话落入参谋闲聊的意图路由，可另开 intent 调优任务。
+3. test/main 未晋升；项目 143 未改动；`production_ready` 未改。

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/docs6579.json

@@ -0,0 +1 @@
+{"active_workflow_key":"main","documents":[{"doc_id":"doc_proj6579_bd_cdo_quote","project_id":6579,"task_key":"bd_cdo_quote","title":"CDO 报价单","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""},{"doc_id":"doc_proj6579_bd_feasibility_dev","project_id":6579,"task_key":"bd_feasibility_dev","title":"设计开发可行性评估报告","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""},{"doc_id":"doc_proj6579_bd_feasibility_reg","project_id":6579,"task_key":"bd_feasibility_reg","title":"注册路径可行性评估报告","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""},{"doc_id":"doc_proj6579_bd_intake","project_id":6579,"task_key":"bd_intake","title":"用户初始需求收集表","workflow_key":"main","lifecycle_state":"drafting","is_template_only":false,"content_sha256":"4b3741e7642502f8960da08646e85ffad4337064fb8932b9420151e5a2cdb233","work_dir":"/app/data/workspaces/bizdev/bd_intake_1789975357338142271","version":1,"updated_at":"2026-09-21T08:18:55Z","lease_holder_type":"squad","lease_holder_id":"run_1789978731880379297","lease_expires_at":"2026-09-21T08:48:51.890752Z","lease_heartbeat_at":"2026-09-21T08:18:51.890752Z","author_id":398,"author_name":"user-398","reviewer_id":398,"reviewer_name":"user-398","approver_id":398,"approver_name":"user-398","duty_policy":"author_only"},{"doc_id":"doc_proj6579_bd_prelim_design","project_id":6579,"task_key":"bd_prelim_design","title":"系统初步设计方案","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""},{"doc_id":"doc_proj6579_bd_research","project_id":6579,"task_key":"bd_research","title":"调研报告","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""},{"doc_id":"doc_proj6579_bd_user_requirements","project_id":6579,"task_key":"bd_user_requirements","title":"用户需求表","workflow_key":"main","lifecycle_state":"drafting","is_template_only":true,"content_sha256":"","version":1,"updated_at":"2026-09-21T08:18:55Z","author_id":0,"author_name":"","reviewer_id":0,"reviewer_name":"","approver_id":0,"approver_name":""}]}

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/wf-scope-empty.json

@@ -0,0 +1,56 @@
+{
+  "docs_6537": {
+    "status": 200,
+    "awk": "",
+    "n": 0,
+    "wfs": []
+  },
+  "chat_6537": {
+    "status": 500,
+    "branch": null,
+    "reply": "",
+    "has_wrong_wf": false
+  },
+  "task_6537": {
+    "status": 500,
+    "body": {
+      "task_key": "rd_proposal",
+      "artifact_title": "",
+      "markdown_body": "",
+      "extracted_data": null,
+      "attachments": null,
+      "work_dir": "",
+      "backend_used": "",
+      "duration": 0,
+      "success": false,
+      "error_reason": "bizdev: workflow stage access denied: task \"rd_proposal\""
+    }
+  },
+  "docs_6531": {
+    "status": 200,
+    "awk": "",
+    "n": 0,
+    "wfs": []
+  },
+  "chat_6531": {
+    "status": 500,
+    "branch": null,
+    "reply": "",
+    "has_wrong_wf": false
+  },
+  "task_6531": {
+    "status": 400,
+    "body": {
+      "task_key": "rd_proposal",
+      "artifact_title": "",
+      "markdown_body": "",
+      "extracted_data": null,
+      "attachments": null,
+      "work_dir": "",
+      "backend_used": "",
+      "duration": 0,
+      "success": false,
+      "error_reason": "precondition failed: prerequisite upstream document not satisfied: 请先完成商务对接流程（CDO 报价批准）后再启动研发设计控制流程"
+    }
+  }
+}

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/wf-scope-gotest2.txt

@@ -0,0 +1,3 @@
+ok  	chat-agent-system/internal/intent	0.009s
+ok  	chat-agent-system/internal/projectinstance	0.004s
+ok  	chat-agent-system/internal/server	0.908s

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/wf-scope-health.json

@@ -0,0 +1 @@
+{"status":"ok","env":"dev","agent_backend":"pi-agent","version":"v1.0","shared_kb_port":5432,"kb_ready":true,"database_ready":true,"schema_version":60,"schema_ready":true,"task_store_ready":true}

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/wf-scope-live.json

@@ -0,0 +1,33 @@
+{
+  "pos_main_research": {
+    "error": "timed out"
+  },
+  "neg_cross_rdev": {
+    "status": 200,
+    "duration_s": 0.01,
+    "reply": "",
+    "raw_keys": [
+      "reply_text",
+      "branch",
+      "intent_result",
+      "coordination_result",
+      "pending_expectation"
+    ]
+  },
+  "neg_cross_sysreqs": {
+    "status": 200,
+    "duration_s": 0.01,
+    "reply": "",
+    "raw_keys": [
+      "reply_text",
+      "branch",
+      "intent_result",
+      "coordination_result",
+      "pending_expectation"
+    ]
+  },
+  "task_run_cross": {
+    "status": 409,
+    "body": "{\"error_code\":\"ERR_DOC_WRONG_WORKFLOW\",\"message\":\"您提到的文档「rd_proposal」属于【研发设计控制流程】，当前激活工作流为【商务对接流程】。已阻止跨工作流操作，请先切换到对应工作流后再操作，或改为点名当前工作流的文档。\"}\n"
+  }
+}

.doc/test-reports/assets/2026-09-21-intent-workflow-scoping/wf-scope-live3.json

@@ -0,0 +1,79 @@
+{
+  "docs_api": {
+    "status": 404,
+    "active_workflow_key": null,
+    "n": 0,
+    "samples": []
+  },
+  "neg_proposal": {
+    "status": 200,
+    "duration_s": 0.02,
+    "branch": "NEW_INTENT_PREEMPT",
+    "reply_text": "您提到的文档「项目建议书」属于【研发设计控制流程】，当前激活工作流为【商务对接流程】。已阻止跨工作流操作，请先切换到对应工作流后再操作，或改为点名当前工作流的文档。",
+    "intent": null,
+    "filled_slots": null,
+    "coord": {
+      "action": null,
+      "status": "CLARIFICATION_REQUIRED",
+      "error_code": null,
+      "message": null,
+      "task_key": null,
+      "doc_name": null
+    }
+  },
+  "pos_summary_research": {
+    "status": 200,
+    "duration_s": 0.01,
+    "branch": "NEW_INTENT_PREEMPT",
+    "reply_text": "未找到可访问的目标文档，或您当前无权查看该阶段内容。请确认文档名称后重试。",
+    "intent": null,
+    "filled_slots": null,
+    "coord": {
+      "action": null,
+      "status": "ACCEPTED",
+      "error_code": null,
+      "message": null,
+      "task_key": null,
+      "doc_name": null
+    }
+  },
+  "pos_modify_research": {
+    "status": 200,
+    "duration_s": 13.05,
+    "branch": "AMBIGUOUS_FALLBACK",
+    "reply_text": "完全理解您想再掂量一下。针对「医疗器械研发项目」目前的节点，我帮您快速对照一下：\n\n• 若推进 V0.5（方案成型与法规对齐）：\n  我可帮您梳理初步架构与注册分类路径，并预估型检成本，便于与客户深入沟通；\n• 若先放一放 / 多做调研：\n  可先补齐预算、目标市场或使用场景等信息，降低后续返工风险。\n\n💡 如果您接下来更希望先有一份可审阅的材料，我可以先整理一版 V0.5 方案框架与法规路径；节奏仍由您决定。\n\n您更倾向于：\n[1] 先做 V0.5 方案框架（可直接回复“好”或“1”）\n[2] 先说明您当前最关心的细节，我做针对性分析",
+    "intent": null,
+    "filled_slots": null,
+    "coord": {
+      "action": null,
+      "status": "ACCEPTED",
+      "error_code": null,
+      "message": null,
+      "task_key": null,
+      "doc_name": null
+    }
+  },
+  "task_run_cross": {
+    "status": 409,
+    "body": {
+      "error_code": "ERR_DOC_WRONG_WORKFLOW",
+      "message": "您提到的文档「rd_proposal」属于【研发设计控制流程】，当前激活工作流为【商务对接流程】。已阻止跨工作流操作，请先切换到对应工作流后再操作，或改为点名当前工作流的文档。"
+    }
+  },
+  "task_run_in_scope": {
+    "status": 500,
+    "body": {
+      "task_key": "bd_research",
+      "artifact_title": "",
+      "markdown_body": "",
+      "extracted_data": null,
+      "attachments": null,
+      "work_dir": "",
+      "backend_used": "",
+      "duration": 0,
+      "success": false,
+      "error_reason": "bizdev: workflow stage access denied: task \"bd_research\""
+    }
+  },
+  "empty_key_probe": null
+}