Skip to content

revert(issues-board): 移除 Issues 看板，相关上游文件恢复原样 - #68

Merged
Fartown merged 9 commits into
fork/integrationfrom
feat/remove-issues-board
Oct 23, 2026
Merged

revert(issues-board): 移除 Issues 看板，相关上游文件恢复原样#68
Fartown merged 9 commits into
fork/integrationfrom
feat/remove-issues-board

Conversation

@Fartown

@Fartown Fartown commented Oct 23, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Owner
Files Added Deleted Net
Test 91 $\color{#1a7f37}{\Huge{\mathbf{+}}}$​21 $\color{#cf222e}{\Huge{\mathbf{−}}}$​11902 $\color{#cf222e}{\Huge{\mathbf{−}}}$​11881
Prod 229 $\color{#1a7f37}{\Huge{\mathbf{+}}}$​216 $\color{#cf222e}{\Huge{\mathbf{−}}}$​24103 $\color{#cf222e}{\Huge{\mathbf{−}}}$​23887

背景

Issues 看板（issues-board）的设计不再保留，这个 PR 把它从 fork 里整体移除，与它相关的上游文件尽量恢复成上游原样。

改了什么

删除 Issues 本身

  • main/shared/renderer 下的 Issues 代码、issues.* 与 conversations.* RPC、orca-issues.v1 运行时能力、Issues 数据库在 WSL 迁移清单里的登记。
  • Issues 的 e2e 测试、需求与设计文档（docs/issue/Issues看板与会话、docs/requirements/Issues-*.md、.docs/并行任务看板）、112 条只给 Issues 用的中英文文案。
  • 功能登记 issues-board 和架构策略 issues-existing-capability-reuse。

恢复成上游

  • 左侧栏（不再有 Workspaces/Issues 切换）、主界面 Issues 页面入口、AI Vault Session History 的恢复动作、launchToken 透传、侧栏激活返回值、宿主列表、协议能力与共享控制的订阅清理。
  • 上游改动预算白名单相应去掉 17 个已与上游一致的文件。

保留（其他功能在用）

  • 会话命名（session-names，独立需求）的全部能力、AI Vault「跳回原窗格」修复、Goals 需要的插件存储读取、afterTerminalRuntimeStartup 启动钩子。

连带调整，行为不变，各自单独提交

  • session-names：三个测试从 Issues 目录移到 session-names/，文件链测试去掉 issues- 前缀。
  • terminal-launch-diagnostics：历史续接改由上游 launchAiVaultSessionAndReveal 记录来源。
  • integration-builds：orcad 只启动 Goals 与局域网分享；发布说明去掉 issues 别名。
  • goals：启动钩子登记为 Goal 的接缝，注释不再以 Issues 为参照。

对其他功能的影响

  • 在 Issues 里手动起的会话名不再参与会话命名，回落到 Provider 名或提示词派生名；Provider 改名、标签上直接改的名称不受影响。
  • Session History 恢复失败时的提示改回上游文案；诊断日志里该入口的来源标签变为 ai-vault-reveal-resume，与原生聊天「在 CLI 中打开」同名，靠记录里的调用栈帧区分。
  • 历史上 fix(issues) 提交在发布说明里归到「其他」。

代码评审

/code-review high 未发现正确性问题。已按评审删除诊断里无调用方的 launchAiVaultSessionInNewTab / ai-vault-resume，并更正一个测试名。未在本 PR 处理的：

  • 会话命名排序里「已有 Orca 会话人工名」这一档是兼容回退，唯一来源原是 Issues 保存的旧会话名；移除后这一档暂无输入，接口按会话命名的设计保留，其余各档不变。会话命名需求文档已同步更新。
  • 发布说明会把本 PR 列在「其他 / 回退」下，不再有 Issues 分组。
  • 各主机上的 orca-issues.db 有意保留不删。

兼容性

  • 旧客户端在访问远程主机的 Issues 前先检查 orca-issues.v1；新主机不再发布它，旧客户端把 Issues 视为不支持，不会反复请求。
  • 本机已有的 orca-issues.db 不删除，只是不再读取。

验证

  • pnpm tc、改动区域单测（1125 个文件 / 10156 个用例）、全部 fork 功能 checks、check:architecture-policies、check:fork-features、check:fork-docs、本地化与 RPC 目录校验、改动代码质量门禁均通过；合入最新 fork/integration 后复跑通过。
  • 隐藏 Electron 真机验收 5/5 通过：
    • 本机：侧栏无 Issues 切换、控制台无相关报错；issues.* 返回 method_not_found，能力列表不含 orca-issues.v1，goals.status 为 ready；Session History 用桩 agent 恢复会话，新开终端标签。
    • SSH（127.0.0.1:2222 上的 orcad 托管主机）：远程工作区与终端可用；远端无 orca-issues.v1、issues.* 返回 method_not_found，goals.status 为 ready。
  • 证据在本机 .docs/issues-board-removal-ui-validation/2026-10-23/（不入库）。

🤖 Generated with Claude Code

https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf

zhangchao.zc and others added 9 commits October 23, 2026 18:15
zhangchao.zc @claude
refactor(session-names): move name-chain tests out of the Issues tree
e25ff81 
The Issues board is being removed. Three session-name tests lived under
src/renderer/src/issues and the file-chain test carried an issues- prefix;
move them under session-names, drop the two checks that only covered Issue
conversation presentation, and stop naming Issues in comments and fixtures.
Naming behavior is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
refactor(terminal-launch-diagnostics): follow history resume through …
8a5ef9f 
…the upstream reveal launcher

The Issues-owned session-terminal-launch module goes away with the Issues
board, and AI Vault panel resume returns to upstream launchAiVaultSessionAndReveal,
which already records the ai-vault-reveal-resume origin. Point the coverage
contract there and drop the two seams that named Issues code.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
fix(integration-builds): stop starting Issues on orcad and drop its r…
12ed6e9 
…elease-note alias

orcad fork services now start Goals and the local network share only. Release
notes no longer fold issues-scoped commits into the removed issues-board
feature, and the update probe contract stops reading the deleted packaged
Issues journey fixture.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
refactor(goals): register the terminal-startup hook as a Goal seam
51ee64b 
With Issues gone, afterTerminalRuntimeStartup only starts the Goal host, so
Goals registers that seam. Comments that described Goal modules by comparison
with Issues now stand on their own. Behavior is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
revert(issues-board): remove the Issues board and restore upstream seams
9b2108c 
The Issues board design is withdrawn. Remove the feature completely:

- delete its main/shared/renderer code, issues.* and conversations.* RPC,
  the orca-issues.v1 capability, its SQLite census entries, e2e specs,
  docs and Issues-only localization keys;
- restore the files it changed to upstream: sidebar, workspace shell,
  AI Vault resume actions, launch-token plumbing, sidebar activation,
  host inventory, protocol capabilities and shared-control cleanup;
- keep what other features depend on: shared session titles, the AI Vault
  original-pane fix, plugin storage reads for Goals, and the
  afterTerminalRuntimeStartup hook;
- unregister issues-board, drop its architecture policy, and shrink the
  upstream diff budget to the files the fork still changes.

Older clients check orca-issues.v1 before calling a remote host, so they
see Issues as unsupported instead of retrying. Existing Issues databases on
disk are left untouched and no longer read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc
Merge remote-tracking branch 'Fartown/fork/integration' into feat/rem…
f73c16a 
…ove-issues-board

# Conflicts:
#	docs/issue/README.md
zhangchao.zc @claude
refactor(terminal-launch-diagnostics): drop the history resume wrappe…
a71baf5 
…r nothing calls

Review of the Issues removal found launchAiVaultSessionInNewTab and its
ai-vault-resume origin had no production caller left. Session History resume
and the native-chat CLI fork share ai-vault-reveal-resume; the recorded
callsite frames still tell them apart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
test(session-names): name the manual-title override case for what it …
948bf92 
…checks

The earlier rename implied a Session History rename feeds this title; it
does not. The case checks that a manual override outranks the Provider slot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
zhangchao.zc @claude
docs(session-names): drop the removed Issues board from the naming re…
11b3194 
…quirement

Issues is no longer a consumer, and the link to its deleted requirement is
gone. Record that the existing-Orca-manual-name tier has no source after the
removal; the ordering and every other tier are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019y33Sh5JqVpTrXQvSXcAVf
@Fartown
Fartown merged commit 343fa4f into fork/integration Oct 23, 2026
69 checks passed
@Fartown Fartown mentioned this pull request Oct 24, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Fartown