Repository navigation
docs(release): record the v0.9.0-alpha runtime, migration and platform limits - #204
qiyuanhuakai wants to merge 4 commits into
Conversation
|
AI 辅助源码/文档审查（dot；中文顶层评论，非 APPROVE / REQUEST_CHANGES）。 审查 head：f003d0a8f0119bf8f177d525e56dc104007d3e98 [P2] 发布文档仍称“App.vue 尚未接入 runtime”，与当前代码不符。 迁移状态 与 RoadMap 仍把主界面接线列为未完成，但同一head的App.vue已经：
继续以“运行时客户端尚未成为生产传输”描述整个版本，会误导迁移和功能可达性的判断。建议同步核对migration、README、CHANGELOG、RoadMap等相关表述，明确区分“已经接线”“有条件回退”和“尚未完成端到端验证”；保留实际条件：没有合适Bridge endpoint时不创建客户端，目标尚未attached时使用旧路径。已有接线不代表所有原生能力已完成验收，也不代表上游已报告发送契约问题不存在。 性能口径不另报虚假缺陷。 验证说明：本次独立重新读取精确SHA文档与源码进行对照，没有新执行UI、真实后端或性能测试，没有把作者测试陈述视作我的执行结果。主CI与Live QA均completed/failure；Validate的六项TS7016和Live QA故障都继承自基底，不归因为本次文档改动。本次确认的是上述文档一致性缺陷，未确认本PR新增运行时代码问题，也不保证不存在其他缺陷。 |
…laims The release docs still said "App.vue 尚未接入新运行时 wire" / "App.vue 未接入" / "运行时客户端尚未成为生产传输", which the code at this head contradicts: app/App.vue:9854-9900 creates a real /runtime connection (createRuntimeConnection over a real WebSocket) and a real runtime client (createRuntimeClient), calls connection.connect(), and publishes the hello's target identity; :9931-9949 builds useRuntimeSessionTree over that client and starts it once the client and the target both exist (the sidebar renders the unified five-source tree); :10442-10468 hands the client to useRuntimeSessionActions, useRuntimeMessageSend and useRuntimeInteractions. The wiring order is itself regression-guarded (app/appScopeRegressions.integration.test.ts: the runtime-client-wiring-order and runtimeSessionRuntime-binding suites). Changed sentences, and why each new sentence is accurate at this head: - docs/migration-v090.md 迁移状态 paragraph: now states the wiring that exists (connection + client + connect + hello target + unified tree start + the three consumer modules) and keeps the qualifiers that remain true — no live /runtime connection means the per-backend fallback path, and the login page's per-backend selection and direct addresses still exist and work (§3). - docs/migration-v090.md §3 "为什么仍可用": the per-backend selection and direct addresses are one usable connection path, and the fallback when no /runtime connection is live (a bare OpenCode server is not a runtime wire endpoint); they are no longer described as the only path. - docs/migration-v090.md §11: the five UI-TREE render metrics are graded at the store-substrate layer because the performance harness drives the store substrate and never mounts App.vue — the real reason, not "App.vue is not wired"; the doc still claims no running-app rendering numbers. - docs/migration-v090.md §12 and RoadMap: the wiring row is checked with its residual stated (the legacy fallback path is not removed), and the RoadMap worktree row keeps the substrate-layer reason. Not overclaimed: 迁移状态 stays 部分完成, the deprecated-login-path section and its "仍可用于本 alpha" framing stay, and the task-47 owned-doc checkers still pass (the worktree-count sentences all carry the seeded-and-graded disclosure and the store-substrate configuration; the migration-status literal is unchanged).
|
AI 辅助增量源码/文档复核（dot；中文顶层评论，非 APPROVE / REQUEST_CHANGES）。 审查 head：6ee3b7d702a2e0039735bb359f71d1418d13137f。 原 P2 部分修复，尚未完整关闭。 已确认修正：
[P2，原问题残留] README 与 CHANGELOG 仍明确宣称主界面未接入，发布入口继续互相矛盾。
同时收窄新写入的 fallback 声明。 验证与 CI 边界 PR 元数据返回的历史 base_sha 为 8c5cb23，但本轮 Validate 日志明确检出测试合并提交 a417367，即本 head 合入实时基底 #203 e2517a5。因此下面是该合并树的外部 CI 证据，不是本分支 head 已回补所有上游代码：
本轮结论是文档一致性部分修复、入口残留及 fallback 条件需同步；不保证其他继承问题已解决。 |
…he fallback claims README (zh L94/L97, en L509/L512) and CHANGELOG (L19/L38) still stated the main app was not wired to the new runtime, contradicting the already-fixed migration/RoadMap notes and the real App.vue wiring. Correct the stale claims and keep every qualifier that is still true (store-substrate grading with no running-app rendering claimed; login and direct-connection paths remain usable in this alpha). Narrow the fallback description in migration-v090.md (L7/L46/L159) and RoadMap.md (L15) to the code-exact conditions: session actions keep the per-backend path until a usable runtime target is attached (no bridge URL bound, or the bridge has not answered hello); the sidebar keeps its legacy tree until the unified tree is built (unifiedSessionTree === null); the connection listener handles hello only, so a disconnect does not clear the target or the unified tree and cannot be read as a whole-UI fallback.
|
AI 辅助增量文档复核（dot；中文顶层评论，非 APPROVE / REQUEST_CHANGES）。 审查 head：5b95ef766e3eae38ba37da48cbe6cb14379d75c9。 原文档 P2 的主要问题已修复。
仍有一处非阻塞措辞需精确化： 验证与 CI |
This branch's App.vue composes the landed Thread / Handoff / collaboration services through app/runtime/threadPorts.ts and app/runtime/collaborationPorts.ts, but only the .js modules were inherited: the six sibling .d.ts files and the node:crypto seam existed solely on #205's head, so `vue-tsc --noEmit` failed here with 6x TS7016 ("Could not find a declaration file for module '../../bridge/runtime/{threads,collaboration}/<service>.js'"). Bring the actual bytes from #205's head 32ca6b7 rather than re-deriving them: - bridge/runtime/threads/checkpointService.d.ts, handoffService.d.ts - bridge/runtime/collaboration/coordinator.d.ts, delegationService.d.ts, fanoutService.d.ts, mailbox.d.ts - app/utils/nodeCrypto.ts (+ its test) and the vite.config.ts alias that maps `node:crypto` onto it, so a browser realm gets the browser primitives while a Node realm (bridge, SEA, workers, tests) keeps the real builtin RED: 6 TS7016 at app/runtime/{threadPorts,collaborationPorts}.ts. GREEN: vue-tsc --noEmit exit 0, vite build exit 0, nodeCrypto.test.ts 4 green.
|
AI 辅助增量复核（dot，2026-10-19 08:18 UTC；非 APPROVE / REQUEST_CHANGES） head： 上轮六处继承 TS7016 的缺失声明已补入本分支，不再只是下游 #205 上的修复。 node:crypto 浏览器接线也已明确回补。 独立定向验证：Node v24.19.0 对精确 head 的原始 adapter 与 shared/context 源码进行类型擦除，在无 process/require 的隔离 VM realm 和 Node realm 执行，共 20 个断言通过：空串、ASCII、中文/emoji、长串的 SHA-256 hex/base64/base64url 与 Node 对照；多次 update 字符串拼接；UUID 正常及 getRandomValues 回退；Node SHA-512 路径；浏览器不支持的算法明确拒绝。没有用假的 hash 算法替代产品实现。此为 realm 模型，未运行实际浏览器、Vite dev/生产页面、完整 Vitest、原生安装或 live SSH/Slurm；不能将有限调用面的测试升级为完整 node:crypto 兼容性保证。 本次增量未发现新的确定缺陷。上轮文档主要 P2 已修结论保持；migration L7仍未精确区分 client attached targets 与 App 保存的 UI identity/统一树对象，这一非阻塞措辞尾项本次没有修改，不再另报新缺陷。 CI 终态补记（2026-10-19 08:24 UTC，head 再核对未变）：
|
CI 修复：把 #200 已落地的声明文件同步到本分支结论： 失败原因（已从 check-run 注解核实）
根因同上： 修法（cherry-pick 已验证字节，不重新推导）
字节同一性证明（
|
Task 47 — v0.9.0-alpha docs + version bump.
package.jsonbumps0.8.20-alpha.3→0.9.0-alpha;README.md,RoadMap.md(including the App.vue runtime wiring rows that were stale relative to the delivered code) andCHANGELOG.mdrecord the alpha;docs/{API,desktop-integration,projects,testing}.mdare updated anddocs/{collaboration,migration-v090,remote,runtime}.mdare new.Verification: the four version-sensitive suites (
desktopController,updateRelease,updateVersion,bridgeUpdateCli) 61/61 green — their version strings are synthetic fixtures, not the repo version;vue-tsc --noEmitexit 0; oxlint warnings-only.