Support manual RFC completion and reversible roadmap groups

Author: tzhouam

.github/workflows/rfc-portability.yml

@@ -25,4 +25,4 @@ jobs:
         with:
           node-version: '22'
       - run: python -m pip install -e '.[dev]'
-      - run: python -m pytest test/test_rfc_application.py test/test_rfc_providers.py test/test_rfc_http.py test/test_rfc_integration.py test/test_rfc_security.py test/test_rfc_migration.py test/test_rfc_graph.py test/test_rfc_markdown.py test/test_rfc_components.py test/test_rfc_translations.py test/test_rfc_chat.py test/test_rfc_chat_web.py test/test_rfc_chat_integration.py test/test_rfc_source_updates.py
+      - run: python -m pytest test/test_rfc_application.py test/test_rfc_providers.py test/test_rfc_http.py test/test_rfc_integration.py test/test_rfc_security.py test/test_rfc_migration.py test/test_rfc_graph.py test/test_rfc_markdown.py test/test_rfc_components.py test/test_rfc_translations.py test/test_rfc_chat.py test/test_rfc_chat_web.py test/test_rfc_chat_integration.py test/test_rfc_source_updates.py test/test_rfc_work_controls.py

doc/architecture/SPEC/rfc_service.md

@@ -86,6 +86,12 @@
   工作会反映在图中，不固定轨道数量。
   源指令与回调不执行。节点提供受角色限制的工作/验收操作、键盘访问；支持
   缩放与下载，SVG 中的工作链接返回受保护的 RFC 页面。
+  贡献者通过 `rfcs.work` 的 `mark_done` / `clear_done` 及状态更新记录有身份与原因的
+  人工实现状态；人工记录优先于 PR 观察，不能改变验收结论。解析、同步和聊天编辑
+  保留人工事实与历史。`rfcs.graph` 的 merge / rename / unmerge 保存 RFC 级视图分组，
+  使用稳定特性 ID，不合并源正文、任务、验收或证据。分组可跨轨道，投影保留边界依赖、
+  隐藏内部边，全部成员实现才呈绿色。分组读取受当前权限过滤，写入重查贡献者权限，
+  可用 expected_revision 拒绝过期操作。分组与任务深链保留操作能力，状态变化复用 SVG。
 
 - **组件工作台。** 详情按成果、目标与范围、路线图与工作、设计、验收、风险与参考
   组织。共享浏览器投影使用 Markdown 标题 token 与原始行号，保留层级；中英文规则

doc/architecture/SPEC/sdk.md

@@ -1,6 +1,6 @@
 # sdk/ —— 规范
 
-<!-- verified-against: 2026-10-02 -->
+<!-- verified-against: 2026-10-05 -->
 
 
 `Python SDK v1 · 跨仓库唯一 typed 边界 · refactor-status: ok`
@@ -17,6 +17,11 @@
 
 ## 公开契约
 
+- RFC：`RFCClient` 选择显式本地或托管工作区，统一通过 `dispatch(action, payload)`
+  调用 RFC 服务并校验 API 版本。`work()` 支持人工实现记录和清除，`graph()` 支持
+  可逆节点分组；`chat_*` 提供私有会话、异步任务、分页事件和完整候选差异确认。
+  Bearer 身份来自宿主配置，权限、版本与事实校验由共享应用执行；远端故障不改写
+  另一套本地状态。验证见 `test_rfc_work_controls.py`、`test_rfc_chat_integration.py`。
 - `get_capabilities()` / `DirectClient.capabilities()` 返回 typed
   `Capabilities`：distribution/SDK/Direct/Strict/Quality/Knowledge 版本、resource revision、支持仓库、
   expected-head/structured-result/post-false/file-lock/idempotency 能力与 worker 上限。

doc/architecture/SPEC/thin_mcp_server.md

@@ -1,6 +1,6 @@
 # thin_mcp_server.py —— 规范
 
-<!-- verified-against: 2026-10-02 -->
+<!-- verified-against: 2026-10-05 -->
 
 `LOC ~490 · 默认 MCP：Direct 门面 + Strict 入口 · refactor-status: ok`
 
@@ -19,6 +19,9 @@
 上述十个工具；`build_mcp(...)`；`main()`。
 RFC 工具签名为 `rfc_request(action, payload=None)`、`rfc_capabilities()`、
 `rfc_status(rfc_id)`；后者调用 `rfcs.status`，返回不含源正文和候选列表的紧凑视图。
+`rfc_request` 同样转发 `chat.*`、`rfcs.work` 的人工实现记录，以及 `rfcs.graph` 的
+可逆节点分组。聊天调用先返回任务 ID，完整候选需通过 preview/apply 明确确认；
+本门面不执行模型工具循环，也不能自行通过验收或修改授权。
 
 ## 不变量（**C1**、**C2**、**D1**）
 - **Direct 在这个 server 里不跑任何模型。** 它返回知识路由和一份治理契约；阅读由

doc/features/rfc-service.md

@@ -102,6 +102,41 @@ zoom, reset, and SVG download controls; downloaded work nodes link back to the
 authorized RFC task view. Green implementation nodes still show pending
 acceptance until evidence or an explicit waiver satisfies its criteria.
 
+Contributors can use **Mark implementation done** in a node's details or work
+item, with a reason. This records the authenticated user and turns the node
+green even when linked PRs are still open. It records implementation only;
+acceptance and evidence keep their independent verdicts. **Clear manual status**
+restores source-derived tracking. The work-state selector also records a manual
+override, so source refreshes do not silently replace the user's chosen state.
+The reason and previous records remain in task history and audit; Agent prose
+edits cannot invent or erase these manual facts.
+
+Use **Merge nodes** on a roadmap to choose at least two tasks by stable ID and
+give the merged node a name. Groups are saved per RFC and shared with its
+authorized users. They can span tracks; boundary dependencies stay visible and
+internal edges are omitted. Tasks, evidence, acceptance and the original source
+remain separate. Clicking the group opens its member tasks, with **Rename merged
+node** and **Split nodes** controls. A group is green only when all its members
+are implemented; acceptance is still separate. Individual task links and SVG
+group links continue to open their authorized details.
+
+The same operations are available through SDK, CLI and MCP:
+
+```json
+{"rfc_id":"RFC_ID","op":"mark_done","feature_id":"F1","reason":"Implementation verified by the owner","expected_revision":"CURRENT_REVISION"}
+```
+
+Send this to `rfcs.work`. Use `clear_done` to remove the manual override. A supplied
+`expected_revision` rejects a stale preview instead of overwriting another update.
+
+```json
+{"rfc_id":"RFC_ID","op":"merge","feature_ids":["F1","F2"],"title":"Core integration","expected_revision":"CURRENT_REVISION"}
+```
+
+Send this to `rfcs.graph`. Use `rename` with `group_id` and `title`, or `unmerge`
+with `group_id`. `RFCClient.work()` and `RFCClient.graph()` reuse these actions.
+These are tracking and view changes, so they do not publish changes upstream.
+
 The same-origin Mermaid 11.12.0 bundle is shipped with licenses and its pinned
 dependency lockfile. It is built with esbuild from `mermaid/dist/mermaid.core.mjs`
 using `--bundle --format=esm --minify --target=es2020 --legal-comments=linked`.