Skip to content

feat: 完成插件安装配置验证与消息诊断闭环 - #12

Merged
lc-cn merged 1 commit into
mainfrom
codex/issue-702-console-completion
Oct 14, 2026
Merged

lc-cn merged 1 commit into
mainfrom
codex/issue-702-console-completion

Conversation

@lc-cn

@lc-cn lc-cn commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

补齐插件安装后的配置、应用与功能验证路径,避免把包已安装或当前代已加载显示为业务成功;同时修复会话历史使用内部数据库字段导致日期/发送者错误的问题。

  • 安装先核对 registry 实际版本,确认精确包版本和修订;回执丢失先只读检查,仅在相同包已安装但未挂载时生成新的补全计划,不自动重放旧操作。
  • 表单支持嵌套对象/数组、默认值和环境引用。表单、通用配置与全量源码草稿绑定首次编辑的修订,刷新后仍保留草稿并由 Host 执行 CAS;不支持的 Schema 整体进入源码编辑。
  • 分别显示安装、声明、缺配置、等待应用、当前代、平台就绪和业务验证;检查先披露副作用再批准。旧代验证失效;执行结果未知时刷新状态不能解锁重复执行,必须先核对外部结果。
  • 组件按 canonical Endpoint、会话、父频道和线程预览,展示图片/原生/文本及降级原因;预览不发送消息、不注册按钮、不执行出站中间件。
  • 实际出站和 Inbox 历史显示平台消息 ID、方向及最终投递诊断。历史方向未记录时明确提示,Host/凭据切换拒绝旧缓存和异步结果。

验证:184 项 Node 回归、typecheck 与 Farm 构建通过。配置冲突回归直接串联页面的真实保存 handler;未知验证回归执行页面的提交和刷新 handler,确认刷新不会证明外部检查未执行。

本地浏览器已验收插件安装与最小配置、显式应用、当前代证据、持久提醒的本地检查、按 ICQQ 目标的图片预览,以及真实私聊按钮/提醒的出站诊断。接收者已确认按钮回调与提醒收到。候选 Host 与真实 npm 插件包混合联调的证据不等同于新项目全 npm 安装成功。

Host 配套实现见 zhinjs/zhin#710,第三阶段验收跟踪于 Issue #702。本 PR 仅推功能分支,未部署生产站点。

Copilot AI balanced review requested due to automatic review settings October 13, 2026 08:55

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying zhin-demo-console with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0ee868d
Status: ✅  Deploy successful!
Preview URL: https://6a82614c.console-axj.pages.dev
Branch Preview URL: https://codex-issue-702-console-comp.console-axj.pages.dev

View logs

@lc-cn
lc-cn merged commit f173a94 into main Oct 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants