docs: reorganize MVP interview documentation

mvp/demo/payment-timeout-acceptance.md

@@ -1,24 +1,24 @@
-# Payment Timeout Acceptance Case
+# 支付超时诊断验收用例
 
-## Goal
+## 1. 目标
 
-Validate that the MVP can diagnose a payment timeout incident and expose the complete trace for replay.
+验证 MVP 能诊断支付超时问题，并暴露完整 Trace 供回放。
 
-## Input
+## 2. 输入
 
-- Session id: `mvp-demo-payment-timeout-001`
-- Question: `支付接口最近出现超时，请结合知识库、日志和指标判断可能原因，并给出修复建议。`
-- Profile: `mvp-demo`
+- Session id：`mvp-demo-payment-timeout-001`
+- 问题：`支付接口最近出现超时，请结合知识库、日志和指标判断可能原因，并给出修复建议。`
+- Profile：`mvp-demo`
 
-## Acceptance Criteria
+## 3. 验收标准
 
-1. Chat returns a successful answer with the same session id.
-2. Trace API returns session metadata, final answer, ordered agent steps, and ordered tool invocations.
-3. Trace contains enough evidence to explain which tools were used and whether verifier/self-evaluation was persisted.
-4. Feedback can be submitted for the same session id.
-5. A follow-up trace query shows the persisted feedback value.
+1. Chat 返回成功答复，且 session id 与请求一致。
+2. Trace API 返回 session 元数据、最终答案、按顺序排列的 agent steps 和 tool invocations。
+3. Trace 中有足够证据说明用了哪些工具，以及 verifier / self-evaluation 是否已持久化。
+4. 可以使用同一个 session id 提交反馈。
+5. 后续 Trace 查询能看到已持久化的 feedback 值。
 
-## Trace Fields To Inspect
+## 4. 需要检查的 Trace 字段
 
 - `data.session.query`
 - `data.session.answer`
@@ -32,8 +32,9 @@ Validate that the MVP can diagnose a payment timeout incident and expose the com
 - `data.toolInvocations[*].retrievalDetails`
 - `data.summary`
 
-## Known Limits
+## 5. 已知边界
+
+- 这不是完整离线测试，仍需要有效的 chat、持久化、向量检索和模型调用环境。
+- `mvp-demo` profile 启用 mock 日志和指标，让证据工具返回更稳定。
+- 敏感配置清理不属于当前 MVP 优先级。
 
-- This case is not a full offline test. It still requires valid infrastructure for chat, persistence, vector search, and model calls.
-- Mock logs and metrics are enabled by the `mvp-demo` profile to make those evidence tools repeatable.
-- Sensitive configuration cleanup is deferred by current MVP priority.