SuperDiscussion v0.2.0

SuperDiscussion v0.2.0

中文

v0.2.0 将 SuperDiscussion 从“实现后的代码审核”扩展为“实现前的设计审核 + 实现后的代码审核”，同时完成原计划中的本机可观察性与外发透明度加固。

一眼看懂这次更新

• 先审设计，再写代码。 现在可以直接用自然语言发起 Design Review，检查产品逻辑、用户流程、前端交互、状态模型和技术架构。
• 联网前先看清楚。 新增 preview-request，可以预览外部 Agent 将收到的上下文、不会收到的内容、目标 Provider 和请求哈希。
• 审核进度不再是黑盒。 新增 task-status，集中显示授权、冷却时间、审核轮次、候选版本、阻塞原因和下一责任方。
• 审核结果更可信。 候选、请求、reviewer 结果、Codex 裁定与最终归档均进行一致性校验；代码一旦改变，旧 approval 不会继续算数。
• Windows 上更稳定。 改进并发状态访问、短暂文件占用和账本追加过程，降低安全软件或同时读取造成的误失败。
• 升级无需重新配置。 配置与 runtime 继续使用 v2，现有 API Key、Provider 配置和正式审核记录保持兼容。

查看完整更新日志

自然语言 Design Review

• 用户不需要输入 design-review 命令。Codex 根据“先别开发”“审一下交互逻辑”“比较架构方案”等自然语言意图选择设计审核。
• 只有用户同时明确邀请 SuperDiscussion、外部 reviewer、Kimi、ZCode 或多 Agent 时才产生外部授权；普通设计问题仍由 Codex 单独回答。
• Design Review 支持一至三轮单审或双盲双审。每轮冻结设计候选，Codex 逐条裁定并只修改设计工件，不在该阶段写实现代码。
• 设计输出必须覆盖问题定义、假设、替代方案、权衡、产品逻辑、前端交互、架构与简化机会。缺少浏览器原型时必须如实记录。

可观察性与安全

• task-status 只读显示授权、Provider 冷却、审核轮次、候选哈希、缺失 reviewer、阻塞原因和下一责任方。
• preview-request 在联网前展示精确上下文投影、排除项、Provider 目标和请求哈希，不创建授权、不访问 Provider、不输出 API Key。
• invoke 与 review-team 可绑定预览得到的请求文件 SHA-256；调用前和重试前发现漂移即关闭失败。
• 新增两轮 Design Review 假 Provider 黑盒流程，覆盖真实设计工件、目标不可切换、最终归档，以及首次发送和结构化修复重试前的请求漂移。
• Reviewer 失败原因会持久化到只读状态视图；README 引用的二维码作为显式审计二进制资源进入确定性发布包。
• Windows JSON 原子替换与读取对短暂共享冲突进行有限重试，并保留失败临时文件清理与并发回归测试。
• 只读 ledger 可区分并发追加中的短暂尾行与持续损坏；reviewer waiver 会清除对应的旧 blocker，保持 runtime 可验证。
• 三轮部署前双审补强：review 只能经状态机派发，设计候选必须提供哈希绑定的完整可见工件，预览区分授权与实际调度就绪状态，账本与发布输入使用原子/不可变快照，审核状态记录实际发送请求的快照身份，外部 HTTP 后的漂移仍留下失败审计，v2 quorum、裁决和降级语义严格校验，降级失败摘要在归档及后续加载时复核，最终来源清单必须精确导出最终候选哈希，二维码按长度与 SHA-256 固定。

配置格式与 runtime 继续使用 v2，旧 review-team 代码审核请求、授权链、候选哈希、归档和最多三轮限制保持兼容；独立 review 不再允许绕过 review-team 直接调用。

SuperDiscussion 可以显著提高设计与代码质量，但会增加 Token 消耗和完成时间，请按任务价值选择使用。

English

v0.2.0 expands SuperDiscussion from post-implementation code review into pre-implementation Design Review plus post-implementation code review, while delivering the planned local observability and outbound-context transparency improvements.

What changed at a glance

• Review the design before writing code. Natural-language Design Review now covers product logic, user flow, frontend interaction, state models, and architecture.
• See outbound context before networking. preview-request shows what an external agent will receive, what is excluded, the destination provider, and the request hash.
• Review progress is no longer a black box. task-status reports authorization, cooldowns, review rounds, candidate identity, blockers, and the next responsible actor.
• Review conclusions are harder to misrepresent. Candidates, requests, reviewer results, Codex adjudication, and final archives are consistency-checked; an old approval cannot survive a code change.
• More reliable on Windows. State access, transient file sharing, and concurrent ledger appends are handled more robustly.
• No configuration migration. Config and runtime remain at v2, preserving existing API keys, providers, and formal review records.

Read the complete changelog

Natural-language Design Review

• Users do not need a design-review command. Codex infers the design phase from ordinary requests to pause implementation, challenge an interaction, or compare architectures.
• External authorization still requires an explicit invitation to SuperDiscussion, external reviewers, Kimi, ZCode, or multiple agents. Ordinary design questions remain Codex-only.
• Design Review supports one to three single or blind-dual rounds. Each round freezes the design candidate; Codex adjudicates findings and revises design artifacts without editing implementation code during the phase.
• Structured results cover problem framing, assumptions, alternatives, trade-offs, product logic, frontend interaction, architecture, and simplification. Missing browser prototypes are reported honestly.

Observability and safety

• task-status reads local grants, provider cooldowns, review rounds, candidate hashes, missing reviewers, blockers, and next actors.
• preview-request shows the exact context projection, exclusions, destination, and request hash before networking without creating a grant, contacting a provider, or exposing an API key.
• invoke and review-team can bind the previewed request-file SHA-256 and fail closed before calls or retries when content drifts.
• Adds a two-round fake-provider Design Review black-box flow covering real design artifacts, immutable targets, final archive binding, and request drift before initial sends and structured repair retries.
• Reviewer failure reasons persist in the read-only status view, and the README-linked QR image ships as an explicitly audited binary in the deterministic archive.
• Windows atomic JSON replacement and reads now perform bounded retries for transient sharing violations while retaining temporary-file cleanup and concurrency regression coverage.
• Read-only ledger inspection distinguishes a transient append tail from persistent corruption, and reviewer waiver clears the corresponding stale blocker so runtime state remains valid.
• Three pre-deployment dual-review rounds harden state-machine-only review dispatch, hash-bound full design artifacts, authorization-versus-dispatch preview readiness, atomic ledger and immutable release snapshots, identity of the request snapshot actually sent, failed auditing after post-contact drift, strict v2 quorum/adjudication/degradation semantics, degradation-evidence revalidation, exact final-source candidate identity, and length/SHA-256 pinning for the QR asset.

Config and runtime remain v2. Existing review-team code-review requests, grants, candidate hashes, archives, and the three-round ceiling remain compatible; standalone review calls can no longer bypass review-team.

SuperDiscussion can materially improve design and code quality at the cost of additional tokens and completion time. Use it selectively.