feat(conversation): add dag-aware reply context

Author: Jacobinwwey

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

@@ -14,7 +14,8 @@ The key result is that the current code has moved further than the old plan word
 - reply rendering now has a typed structured-answer path,
 - workflow-artifact review follow-up is part of the runtime surface,
 - graph focus can render original markdown with matched-span highlighting,
-- a dedicated evidence pane now carries grounding inspection plus durable `knowledge_run` and `flashcard_batch` inspection.
+- a dedicated evidence pane now carries grounding inspection plus durable `knowledge_run` and `flashcard_batch` inspection,
+- grouped conversation knowledge points now retain relation-path and temporal-validity signals, and the composer uses them in structured explanation/next-action text.
 
 At the same time, the product surface is still behind the intended final behavior:
 
@@ -33,11 +34,11 @@ Code-vs-plan reconciliation for this slice:
 | Answer area contraction to a single targeted answer | `agent_workspace.js` now keeps the full conversation result in runtime state while only rendering user-facing answer blocks (`structured_answer`, `main_markdown`, `html_artifact`) in the main chat surface. | Implemented current slice |
 | Hide developer-heavy evidence from the primary hit list | `workspace_panes.js` no longer renders inline knowledge previews or visible typed capability buttons in the left-side hit list; those flows now route into graph focus or the dedicated evidence pane. | Implemented current slice |
 | Durable evidence/claim inspector | `workspace_panes.js` now exposes a dedicated evidence pane for grounding metadata, `knowledge_run`, `knowledge_run_history`, `knowledge_run_compare`, and `flashcard_batch`; `agent_workspace.js` wires the API status strip into grounding inspection. | Implemented current slice |
-| DAG-native answer planning | The system already has `KnowledgeAtom`, `RelationEdge`, `TemporalEdge`, path queries, mastery-path logic, and `KnowledgeQueryItem.relationPath`, but conversation synthesis still does not have a dedicated graph-conditioned context-assembly layer. | Not complete |
+| DAG-native answer planning | `AgentConversationKnowledgePoint` now carries grouped `relationPath`, `relationKinds`, `relationPathAtomIds`, and `temporalValidity`, and `conversationComposer.ts` now uses those signals in overview, explanation, and next-action guidance. | Implemented partial slice |
 
 Immediate next direction from this point:
 
-1. Insert a graph-conditioned context-assembly layer between retrieval and answer synthesis so the current DAG becomes a first-class answer-planning substrate.
+1. Extend the new DAG-aware conversation slice into a dedicated graph-conditioned context-assembly layer instead of relying on grouped relation hints alone.
 2. Preserve the new primary answer / right-pane-first interaction contract while growing the evidence pane toward a broader durable evidence ledger.
 3. Continue ownership reduction across `src/server.ts`, `KnowledgeLearningPlatform.ts`, `agent_workspace.js`, and `workspace_panes.js`.
 
@@ -48,6 +49,7 @@ Verification for the current code-backed alignment:
 - `node --check src/frontend/workspace_panes.js`
 - `npm.cmd exec -- jest src/learning/conversationComposer.test.ts src/learning/KnowledgeLearningPlatform.test.ts src/learning/KnowledgeLearningPlatform.persistence.test.ts src/learning/KnowledgeLearningPlatform.program-f.test.ts src/agent_workspace.frontend.test.ts src/knowledge.api.contract.test.ts src/routes/registry.contract.test.ts src/pathbridge.handshake.contract.test.ts src/server.port.fallback.contract.test.ts src/workflows/WorkflowArtifactStore.test.ts --runInBand --no-cache`
 - `npm.cmd exec -- jest src/agent_workspace.frontend.test.ts src/agent_workspace.locale.contract.test.ts src/agent_workspace.contract.parity.test.ts src/agent_workspace.runtime.behavior.test.ts --runInBand --no-cache`
+- `npm.cmd exec -- jest src/export/WorkspaceExportBundle.test.ts --runInBand --no-cache`
 - `npm.cmd run test:agent-workspace:contracts`
 - `npm.cmd run build`
 

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

@@ -16,7 +16,8 @@
 - reply rendering 已具备 typed structured-answer 路径；
 - workflow-artifact review follow-up 已进入运行时表面；
 - graph focus 已能渲染原始 markdown 并高亮 matched span；
-- 独立 evidence pane 现已承接 grounding inspection 以及 durable `knowledge_run` / `flashcard_batch` 检查。
+- 独立 evidence pane 现已承接 grounding inspection 以及 durable `knowledge_run` / `flashcard_batch` 检查；
+- grouped conversation knowledge point 现已保留 relation-path 与 temporal-validity 信号，composer 也开始把这些 DAG 信号写进结构化 explanation / next actions。
 
 但当前产品面仍未完全达到目标行为：
 
@@ -35,11 +36,11 @@
 | 主回答区收缩为单一 targeted answer | `agent_workspace.js` 现在会保留完整 conversation result 到 runtime state，但主聊天面仅渲染用户面的回答块（`structured_answer`、`main_markdown`、`html_artifact`）。 | 当前切片已实现 |
 | 主命中列表不暴露开发者导向 evidence / action | `workspace_panes.js` 已不再在左侧命中列表中渲染 inline preview 或可见 typed capability button；这些流程现在会路由到 graph focus 或专门的 evidence pane。 | 当前切片已实现 |
 | durable evidence / claim inspector | `workspace_panes.js` 现已提供专门的 evidence pane，用于承接 grounding metadata、`knowledge_run`、`knowledge_run_history`、`knowledge_run_compare` 与 `flashcard_batch`；`agent_workspace.js` 也已把 API 状态条接成 grounding inspection 入口。 | 当前切片已实现 |
-| DAG-native answer planning | 系统已具备 `KnowledgeAtom`、`RelationEdge`、`TemporalEdge`、path query、mastery-path 逻辑与 `KnowledgeQueryItem.relationPath`，但 conversation synthesis 仍缺 dedicated graph-conditioned context-assembly layer。 | 尚未完成 |
+| DAG-native answer planning | `AgentConversationKnowledgePoint` 现已保留 grouped `relationPath`、`relationKinds`、`relationPathAtomIds` 与 `temporalValidity`，`conversationComposer.ts` 也已在 overview / explanation / next actions 中消费这些信号。 | 当前切片已部分实现 |
 
 从这里出发的即时推进方向：
 
-1. 在 retrieval 与 answer synthesis 之间补一个 graph-conditioned context-assembly layer，让当前 DAG 真正进入 answer planning。
+1. 把当前 DAG-aware 对话切片继续扩展成专门的 graph-conditioned context-assembly layer，而不是停留在 grouped relation hint 层。
 2. 在保持新的主回答区与 right-pane-first 主交互契约稳定的前提下，把 evidence pane 继续扩展成更广义的 durable evidence ledger。
 3. 继续缩减 `src/server.ts`、`KnowledgeLearningPlatform.ts`、`agent_workspace.js`、`workspace_panes.js` 的所有权压力。
 
@@ -50,6 +51,7 @@
 - `node --check src/frontend/workspace_panes.js`
 - `npm.cmd exec -- jest src/learning/conversationComposer.test.ts src/learning/KnowledgeLearningPlatform.test.ts src/learning/KnowledgeLearningPlatform.persistence.test.ts src/learning/KnowledgeLearningPlatform.program-f.test.ts src/agent_workspace.frontend.test.ts src/knowledge.api.contract.test.ts src/routes/registry.contract.test.ts src/pathbridge.handshake.contract.test.ts src/server.port.fallback.contract.test.ts src/workflows/WorkflowArtifactStore.test.ts --runInBand --no-cache`
 - `npm.cmd exec -- jest src/agent_workspace.frontend.test.ts src/agent_workspace.locale.contract.test.ts src/agent_workspace.contract.parity.test.ts src/agent_workspace.runtime.behavior.test.ts --runInBand --no-cache`
+- `npm.cmd exec -- jest src/export/WorkspaceExportBundle.test.ts --runInBand --no-cache`
 - `npm.cmd run test:agent-workspace:contracts`
 - `npm.cmd run build`