@givolt/i3-composer-agent 3.1.0 → 4.0.0

package/bin/wizard.cjs

@@ -40,11 +40,7 @@ async function chooseSettings(options, agents, ask) {
       else if (['2', 'global', '全局'].includes(input)) scope = 'global';
       else console.log('请选择 1（项目）或 2（全局）。');
     }
-    const supported=agents.some(host=>['codebuddy','workbuddy'].includes(host));
-    let hooks=options.hooks||options.prototypeHooks||(supported?'default':'keep');
-    const hookGroups=options.hookGroups,codebuddyProduct=options.codebuddyProduct,
-      codebuddyTranscriptRoot=options.codebuddyTranscriptRoot,codebuddySkillRouting=options.codebuddySkillRouting;
-    return { agents, scope, hooks, hookGroups, codebuddyProduct, codebuddyTranscriptRoot, codebuddySkillRouting };
+    return { agents, scope };
 }
 async function choose(options, identity) {
   console.log(identity);
@@ -53,7 +49,7 @@ async function choose(options, identity) {
   if (agents.includes('workbuddy')) console.log('WorkBuddy 桌面版建议全局安装，以便技能列表和输入补全发现 Skills；项目安装仍支持命令，技能列表可能不显示。');
   return session(ask => chooseSettings(options, agents, ask));
 }
-async function confirm(plan, selection = {}) {
+async function confirm(plan) {
   console.log(`\n安装范围：${plan.scope === 'project' ? '项目' : '全局'}`);
   for (const target of plan.targets) {
     console.log(`  ${target.agents.join(', ')}: ${target.skillsDirectory}`);
@@ -62,13 +58,6 @@ async function confirm(plan, selection = {}) {
   }
   if (plan.conflicts.length) console.log(`将替换 ${plan.conflicts.length} 个已有内容；安装成功后清理旧文件，失败则恢复。`);
   if (plan.reused.length) console.log(`将复用同版本的 ${plan.reused.length} 个未修改内容。`);
-  if (selection.hooks) {
-    for(const hook of Array.isArray(selection.hooks)?selection.hooks:[selection.hooks]){
-      if(hook.action!=='enable')continue;
-      console.log(`${hook.host} Hooks：注册 ${hook.groups.join('、')}。`);
-      console.log('设置改变后重载桌面端；CodeBuddy CLI 按宿主要求在 /hooks 审核。');
-    }
-  }
   console.log('将安装所选宿主的技能、命令、使用说明和配套资源。');
   return session(async ask => {
     while (true) {

package/commands/i3-sop.toml

@@ -1,5 +1,5 @@
-description = "显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
-# i3-description-source: "description = \"显式使用企业 SOP，复用原规格方法完成单阶段文档与交接\""
+description = "显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划"
+# i3-description-source: "description = \"显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划\""
 
 prompt = """
 <!-- i3:zh-CN:start -->
@@ -10,7 +10,7 @@ prompt = """
 Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
 严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
 
-适用说明：显式使用企业 SOP，复用原规格方法完成单阶段文档与交接
+适用说明：显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划
 <!-- i3:zh-CN:end -->
 
 Invoke the i3-enterprise-sop skill and pass the complete arguments unchanged. The skill owns operation handling, resource selection, original-method invocation, handoff and stopping rules.

package/docs/antigravity-setup.md

@@ -115,7 +115,9 @@ You can invoke these personas directly within your session or when delegating ta
 ## Configuration & Customization
 
 ### Project-Specific Enforcements (`AGENTS.md`)
-To enforce strict skill compliance (e.g. requiring a spec or plan before writing code), copy or link `AGENTS.md` into the root of your workspace. Antigravity CLI reads this file to align the agent's behavior and planning phase with your team's conventions.
+To enforce strict skill compliance (e.g. requiring a spec or plan before writing code), create a project-specific `AGENTS.md` in the root of your workspace. Describe your project's conventions, test commands, and required skill workflows there.
+
+This repository's root `AGENTS.md` and `CLAUDE.md` configure agents contributing to i3 Composer Agent itself. Do not copy or link them into your project or global agent configuration; the reusable assets are the skills in `skills/`. See [Repo-scoped files](upstream-repository/CONTRIBUTING.md#repo-scoped-files).
 
 ### Sandbox Mode
 If you want to run skills or scripts with limited terminal permissions (for safety when running third-party validation tests), launch the CLI with:

package/docs/codebuddy-setup.md

@@ -9,8 +9,8 @@ npx @givolt/i3-composer-agent --codebuddy
 ```
 
 向导预选 CodeBuddy，可增加其他工具，再选择项目或全局范围。
-项目安装提供 `.codebuddy/skills/`（28 个技能）、
-`commands/`（12 个命令）和 `agents/`（4 个角色）。
+项目安装提供 `.codebuddy/skills/`（27 个技能）、
+`commands/`（11 个命令）和 `agents/`（4 个角色）。
 同级 `i3-composer-agent/` 是配套工具根，集中提供 `package.json`、`evals/`、`hooks/`、`scripts/`、`docs/`、`references/` 和校验输入 `adapters/`，
 只有一份实际技能、命令和角色，评测与宿主共用。
 全局使用 `~/.codebuddy/` 的相同结构。默认中文说明和回复；技能/命令标识不改名。
@@ -25,10 +25,10 @@ npx @givolt/i3-composer-agent --codebuddy
 /i3-build auto
 /i3-review
 /i3-ship
-/i3-prototype
+/i3-ui-demo
 ```
 
-命令保留 `$ARGUMENTS`、原工程规则和审批边界。原型命令由主会话使用 `i3-ui-prototype`，其他命令沿用各自流程。
+命令保留 `$ARGUMENTS`、原工程规则和审批边界。原型命令由主会话使用 `i3-ui-demo`，其他命令沿用各自流程。
 发布命令按宿主能力并行审查或顺序降级，主会话汇总并提供回滚计划。
 
 ```bash
@@ -53,81 +53,28 @@ node .codebuddy/skills/i3-ui-demo/scripts/dependencies.cjs check --host codebudd
 node .codebuddy/skills/i3-ui-demo/scripts/dependencies.cjs prepare --host codebuddy --scope project --project . --accept
 ```
 
-只有已授权安装时才使用 `--accept`；缺项时也可重新运行向导。`--prototype-skills none` 或单项旧参数会提示移除，不会跳过检查后声称安装完毕。
+只有已授权安装时才使用 `--accept`；缺项时也可重新运行向导。必备依赖通过当前 ui-demo 的入口准备，不提供旧原型参数或跳过检查入口。
 
-## 主会话原型流程与使用入口
+## 主会话 UI Demo
 
-原型由主会话使用 `.codebuddy/skills/i3-ui-prototype/`，按同一方法完成需求理解、设计、制作、修订与验证。Skill 保存模板、能力、框架和验收规则；按任务需要复用前端工程方法、官方框架知识、UIUX Pro Max 和浏览器测试能力。HTML 是内容参考，生成结果采用真实框架组件。
-
-模板编辑、构建、证据登记和后续修改以当前 [i3-ui-prototype 技能](../skills/i3-ui-prototype/SKILL.md)及其相关参考资料为准。
-
-自然语言可以这样提出任务：
-
-> 根据资产清单需求，参考完整 enterprise-admin 内容模板，用 Vue 3＋antDv-next 生成交互原型。保留筛选、多选、分页和编辑抽屉，验证失败重试、开合动效和遮罩模糊。请使用 UIUX Pro Max 优化体验，交付待评审候选。
-
-或明确使用命令：
+使用 `/i3-ui-demo`，或明确要求当前会话使用 `i3-ui-demo`。按用户输入选择模板，读取业务需求，加载设计、组件、前端和浏览器技能，交付可运行原型、当前构建证据及待评审事项。完整规则见 [ui-demo](../skills/i3-ui-demo/SKILL.md)。
 
 ```text
-/i3-prototype analyze 先检查需求与内容模板，不修改任何文件
-/i3-prototype create 参考完整 enterprise-admin 模板，用 Vue 3＋antDv-next 生成资产清单原型
-```
-
-自然语言、`/i3-prototype`、已加载的 `i3-using-agent-skills` 和直接使用 `i3-ui-prototype` 都进入同一主会话流程。`i3-using-agent-skills` 按普通技能发现选择工作 Skill；命令只提供快捷入口。普通安装不注册原型专责角色，也不安装常驻原型分派规则。命令菜单、Skill 被读取和真实执行分别验证；CodeBuddy IDE 与 CodeBuddy Code CLI 的证据不能互相替代。
-
-直接使用方法也是正式入口：说“请当前会话使用 i3-ui-prototype 技能，只读分析这个原型”。主会话交付自然语言分析、候选与真实证据，不以父子 Agent JSON 或回传标记为前置。只读分析不写入；原型基线认可需真实用户认可，后续工程仍按现有规格、计划和实现流程交接。
-
-升级只退出清单归属明确且内容匹配已知原型增量的旧角色和旧入口规则。旧入口经过用户修改或来源未知时保留原文件并停止安装，提示人工检查；`--force` 不绕过此保护。同名用户自建 Agent 保留并报告。这样可以在升级前明确处理仍可能生效的旧常驻规则。
-
-默认只读使用 Skill 内置模板，模板由维护者在 Skill 源码中修改并随包发布；业务项目不默认生成 ui-templates。生成的真实组件工程在 `prototypes/<id>/app/`，业务修改直接作用于该工程，生成依据固定在 inputs。已有模板副本仅在明确指定 --template-root 时复用并保留手工修改。按实际 PRD 固定页面、区域和适用能力；旧原型按原合同继续读取，不自动迁移。professional 默认使用真实 UIUX 查询；明确选择 template 时仍完成同样功能验收，不声称使用了 UIUX。
-
-框架官方 antdv Skill 是独立知识来源，按本次版本和授权接入，不随本包安装而自动全局安装或升级 CLI。首期固定库 1.5.3；已探测的 CLI 0.0.0-beta.1 没有该知识文件，显式回退查询 1.5.2 只能作参考，再核对 1.5.3 包内类型／源码。错误文本或退出码 0、仅打印 Parsed args 的 lint，均不能作为查询或验收通过。
-
-工具前置使用依赖检测返回的实际 Node 入口，也兼容已有 `.prototype-tools/node_modules` 布局或宿主明确的绝对入口；缺失时只读分析报告未决项，不以 npm exec／npx 下载或补缓存。工具准备须有明确选择，写范围仅指定工具目录，不含业务内容或 SDK。analyze 只交覆盖、选型、验收计划和缺口，不套用创建阶段的 UIUX 采纳、构建或浏览器门禁。
-
-本轮新原生流程还要求执行者真实调用 `i3-browser-testing-with-devtools` Skill，并使用 Chrome DevTools MCP 对当前构建取得 DOM／计算样式、截图、console、network、可访问性和性能观测。只读取 Skill 文件或运行 Playwright 脚本都不等于调用该 Skill；Playwright 仅保留给历史设备列表固定合同作专项补充。缺可调用 Skill 或 MCP 时整链不 complete，按已授权范围准备宿主工具后再验；analyze 不启动或安装浏览器。具体工具接入以实际宿主暴露为准，不能从其他会话或维护 smoke 推断当前执行环境可用。旧实例按固定合同保留，其他宿主等效结果单列。
-
-新完整模板原生流程默认包含明亮、暗黑、清新、科技，首次默认明亮，菜单无编号；生成工程用原生框架主题，验证四预设、刷新记忆、实例隔离及业务状态保留。旧实例继续按原有固定合同，不隐式增加能力；步骤见首期指南。
-
-## 原型本地检查与预览
-
-以下使用项目安装路径，原型目录替换为实际值。首次构建允许安装依赖时使用 --install；后续复用依赖构建。预览命令持续运行并输出本地 URL。
-
-```bash
-node .codebuddy/skills/i3-ui-prototype/scripts/native-pilot.cjs inspect prototypes/device-list
-node .codebuddy/skills/i3-ui-prototype/scripts/native-pilot.cjs build prototypes/device-list --install
-node .codebuddy/skills/i3-ui-prototype/scripts/native-pilot.cjs preview prototypes/device-list
+/i3-ui-demo 根据已选PRD制作资产管理交互原型，采用默认企业管理后台模板。
+/i3-ui-demo 只读分析当前需求与模板的覆盖范围，不创建文件或安装工具。
 ```
 
-真实浏览器执行场景后，使用 inspect --acceptance 核对当前候选、实际构建和证据引用。检查通过仍待用户评审。只读分析不执行以上写入构建步骤，也不安装、持久化设计或更新原型状态。
+实例默认位于 `prototypes/<id>/`，应用在 `app/`。来源、设计系统、需求映射、QA和HANDOFF随实例保存；既有业务原型和人工修改保留，版本差异按明确范围处理。SOP由PRD／AD固定引用实例和版本，后续规格、计划及生产实现仍按各自入口推进。
 
 ## 配套检查
 
 在业务项目运行 `node .codebuddy/i3-composer-agent/scripts/run-evals.js --min-rank1 95`，
 可检查中英文触发，不调用模型；进入 `.codebuddy/i3-composer-agent/` 可运行 `npm test` 和 `node scripts/run-evals.js --locale zh-CN --min-rank1 95`。全局安装使用脚本的全局绝对路径。五项校验、行为评测和样例用法见
-[评测说明](../evals/README.md)。原型审计 Hooks 已移除；其他原版组按需显式管理。
+[评测说明](../evals/README.md)。原版 Hook 按宿主原有方式使用。
 
-## CodeBuddy 统一 Hooks 管理
-
-原版 `session-start`、`sdd-cache`、`simplify-ignore` 三组由 `.codebuddy/i3-composer-agent/hooks/manage.cjs` 按需管理，原脚本不改。prototype 审计组已退役；安装升级清理本包旧注册，两个旧回调入口均不再执行审计。旧 helper 和 `--prototype-hooks` 仅保留检查／清理兼容。
-
-```sh
-# 已安装后只读列举/检查，项目根运行
-node .codebuddy/i3-composer-agent/hooks/manage.cjs list --host codebuddy --scope project --project .
-node .codebuddy/i3-composer-agent/hooks/manage.cjs check --host codebuddy --scope project --project .
-# 单独启用缓存；全部选择用 --groups all 并满足所有组条件
-node .codebuddy/i3-composer-agent/hooks/manage.cjs enable --host codebuddy --scope project --project . --groups sdd-cache --product ide
-node .codebuddy/i3-composer-agent/hooks/manage.cjs disable --host codebuddy --scope project --project . --groups sdd-cache
-```
+## 原版 Hook
 
-全局改用 `~/.codebuddy/i3-composer-agent/hooks/manage.cjs` 和 `--scope global`，继续指定项目来判断有效来源。发行 CLI 支持 `hooks list|check|enable|disable`；安装时显式启用原版组用 `--hooks enable --hook-groups <ids> --codebuddy-product ide|cli`。默认不新增注册；升级及 keep 均精确清理本包旧 prototype 注册，其他组的开关保留。enable 必须指定组；disable 未指定组时仅兼容旧 prototype 清理，list/check 默认检查三组及退役状态。
-
-`session-start` 需要明确 `--skill-routing hook`，已有原生路由时不选该组；安装器对应 `--codebuddy-skill-routing hook`。上游三组需要 Bash、jq 和相应 SHA 工具，缓存另需 curl，缺依赖会在启用前拒绝；不自动安装。启用需指定实际 IDE／CLI。全局跟随绝对 CODEBUDDY_CONFIG_DIR，默认 ~/.codebuddy。原型不再注册或扫描会话日志；历史兼容见 Skill 的 execution-evidence 参考资料。
-
-配置合并到所选范围 `settings.json`，通用归属在 `state/i3-composer-agent/hooks.json`。旧原型 installation.json 清理前归档到 `state/i3-prototype/history/`，原会话记录保留。被手改的自有注册或未知归属会停止处理，保留现场。上游适配缓存在 `<host-base>/cache/i3-composer-agent/hooks/<projectKey>/`；全局按项目隔离。已识别的手动原版注册只报告，不自动接管或重复注册。代码块保护存在未恢复备份时拒绝移除该组，先结束会话恢复。
-
-IDE 项目设置覆盖全局；CLI 合并后按组选择有效来源避免同组重复执行。CLI 变更后在原生 `/hooks` 审核并新建会话，IDE 重载。文件存在、注册、回调观察与业务验收分别显示；原版 triggered 不表示已验证模型行为。首期仍待用户实际宿主验收，Windows 的原版 Hook 启用仍未验证；旧原型精确清理不新增可执行命令。
-
-依据：[CodeBuddy IDE Hooks](https://www.codebuddy.cn/docs/ide/Features/Hooks)、[CodeBuddy CLI Hooks](https://www.codebuddy.cn/docs/cli/hooks)。
+原版 session-start、sdd-cache、simplify-ignore 脚本及其说明、测试随包提供，按宿主原有机制使用；本包安装器不注册、清理或改写Hook配置。用法见 [SDD缓存](../hooks/SDD-CACHE.md)和[代码块保护](../hooks/SIMPLIFY-IGNORE.md)。
 
 ## 通过 CodeBuddy Code 插件管理器安装
 
@@ -148,24 +95,20 @@ npx @givolt/i3-composer-agent --prepare --codebuddy
 按宿主选择范围并启用后新建会话。兼容清单声明 `.claude/commands/` 与 `commands/`。
 插件命令示例为 `/i3-composer-agent:i3-spec`、`/i3-composer-agent:i3-plan`、
 `/i3-composer-agent:i3-build auto` 和 `/i3-composer-agent:i3-ship`。
-默认原生安装和导出均包含完整评测、原版 Hook 与兼容脚本，不自动启用 Hook；原生升级清理本包旧原型审计注册。
+默认原生安装和导出均包含完整评测、原版 Hook 与兼容脚本，不自动启用或清理 Hook 注册。
 文件落盘、宿主发现和模型实际执行应分别验证。
 
 目录遵循 [配置目录参考](https://www.codebuddy.cn/docs/cli/codebuddy-dir)，可参照
 [IDE Skills](https://www.codebuddy.cn/docs/ide/Features/Skills) 与
 [自定义命令](https://www.codebuddy.cn/docs/ide/User-guide/Slash-Commands) 检查发现与调用。
 
-原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。
+已有业务原型、索引和历史保留原位置。新实例按 ui-demo 的产物约定交接，SOP 文档固定引用实际版本，不从旧索引自动推定当前选用范围。
 
 
-## 原型审计退役与本地 antDv
+## 已有配置
 
-CodeBuddy／WorkBuddy 项目和全局的新安装均不注册原型审计 Hook。升级只清理精确归属的旧注册并归档记录；原型与 QA、其他 Hook 和用户权限保留。被手改或未知归属先报告，不强行清理。清理后重载受影响宿主。
+升级前先结束使用旧定制 Hook 的会话，并确认 simplify 保护块已由旧会话恢复。旧适配器的缓存位于所选宿主基址的 `cache/i3-composer-agent/hooks/<项目标识>/simplify-ignore/`，与原版脚本的默认缓存位置不同；仍有 `.bak` 备份或 `.lock` 活动锁时，安装器停止升级并保留现有安装、配置及缓存。异常结束的会话须先通过旧安装核对并恢复，不能直接删除缓存来绕过检查；已完成恢复的历史记录保留。
 
-```bash
-node .codebuddy/i3-composer-agent/hooks/manage.cjs check --host codebuddy --scope project --project .
-node .codebuddy/i3-composer-agent/hooks/manage.cjs disable --host codebuddy --scope project --project . --groups prototype
-node .codebuddy/skills/i3-ui-prototype/scripts/prototype-dependencies.cjs query --host codebuddy --scope project --project . --kind info --component Table --version 1.5.2
-```
+曾通过定制管理器启用的 session-start、sdd-cache、simplify-ignore，以及旧原型 Hook，配置都可能仍指向已退出的定制程序。恢复完成后由用户手动移除或调整相应注册，需要继续使用的原版 Hook 按宿主原有机制重新配置。安装器不运行统一 Hook 管理或配置清理流程；旧审计历史、业务原型和其他用户设置保留。组件查询使用 ui-demo 的固定依赖入口。
 
-check 只读；disable 只清理旧 prototype 注册，enable 已拒绝。query 不代替 antDv Skill 加载，知识版本与目标组件版本分别核对。实际 Skill 调用、固定业务断言、构建和浏览器验收要求保留，正常流程不要求审计 Hook 绑定，自动调用审计显示未验证。
+旧 `rules/i3-prototype-entry.md` 和 `agents/prototype-specialist.md` 仅在旧清单明确登记且内容匹配已知原件时退出；手改、未知或非普通文件保留并停止处理，`--force` 不绕过。未归属的同名角色保留，未归属的旧入口规则先交用户检查；不据宽泛的 rules 目录声明删除用户规则，也不重新安装这些入口。

package/docs/codex-setup.md

@@ -7,7 +7,7 @@ npx @givolt/i3-composer-agent --codex
 ```
 
 项目范围写入 `.agents/skills/`，全局写入 `~/.agents/skills/`，并安装同级 `i3-composer-agent/references/`。
-提供全部 28 个 `i3-` 技能，中文选择说明与默认中文回复在每个入口独立生效。
+提供全部 27 个 `i3-` 技能，中文选择说明与默认中文回复在每个入口独立生效。
 同级 `evals/`、`hooks/`、`scripts/`、`docs/` 各自以 `i3-composer-agent/` 分组资料。
 命令与角色文件也会提供，供按需阅读，其自动发现由宿主决定。
 从项目目录执行 `node .agents/i3-composer-agent/scripts/run-evals.js --min-rank1 95`
@@ -35,8 +35,14 @@ Codex 已有原生技能路由，勿把元技能全文预加载为常驻上下
 元技能仍可安装并按需显式调用。CLI 保留已有插件设置；测试本地目录时使用绝对路径。
 文件安装、宿主发现与实际模型工作流分别验证。
 
-## 可选原型工具
+## UI Demo 与原型交接
 
-原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。项目安装可使用 `npx @givolt/i3-composer-agent@3.1.0 --codex --scope project --yes --prototype-skills uiux,antdv`；全局安装将 scope 改为 global。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
+使用 `i3-ui-demo` 制作、修改或只读分析原型。安装向导默认准备 ui-ux-pro-max 与 antDv 官方 Skill／CLI；工具位于所选宿主基址的 `tools/i3-ui-demo/`，组件与查询知识固定1.6.0。
 
-原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。
+```bash
+node .agents/skills/i3-ui-demo/scripts/dependencies.cjs check --host codex --scope project --project "/业务项目"
+```
+
+缺项时在明确安装授权下使用同一入口的 `prepare --accept`，或重新运行安装向导。实例默认位于业务项目的 `prototypes/<id>/`；SOP通过PRD／AD固定引用版本、HANDOFF与设计／QA。已有业务原型和人工修改不自动迁移或删除。
+
+原版Hook脚本和测试保留；本包不提供定制Hook管理器，不自动修改用户配置。若仍配置了旧定制原型Hook，由用户自行检查相应注册，原型和审计历史保留。

package/docs/comparison.md

@@ -6,7 +6,7 @@
 
 # How agent-skills compares
 
-> **Upstream research:** This comparison is retained from Addy Osmani's `agent-skills` at commit `aeac41d4d005999432bb7312f7ff06383a91d59d`. Its experiments describe the upstream project; they are not independent evaluations of i3 Composer Agent.
+> **Upstream research:** This comparison is retained from Addy Osmani's `agent-skills` at commit `eb07f19f52c2669f2364897aaa293e2aaddd7b1c`. Its experiments describe the upstream project; they are not independent evaluations of i3 Composer Agent.
 
 People often ask how **agent-skills** relates to the two other "skills for coding agents" collections they hear about most: **Superpowers** (Jesse Vincent / obra) and **Matt Pocock's skills**. All three are good, share a lot of DNA, and are worth learning from. This page is an honest map of how they are *shaped* differently, so you can pick the one that fits how you work, or borrow across all three.
 

package/docs/copilot-cli-setup.md

@@ -45,10 +45,10 @@ In an interactive session, `/skills list` shows the same catalog.
 
 ## What you get, and what you don't
 
-The root `plugin.json` is the manifest Copilot CLI reads — it takes precedence over `.claude-plugin/plugin.json`, which belongs to Claude Code. That root manifest declares only a name, version and description, so component paths fall back to their defaults:
+The root `plugin.json` is the manifest Copilot CLI reads. It takes precedence over `.claude-plugin/plugin.json`, which belongs to Claude Code. Its `$schema` line declares an [Agent Plugins 1.0.0](https://agent-plugins.org) manifest, which switches the CLI into Agent Plugins mode. The manifest sets no component paths, so they fall back to their defaults:
 
-- **Skills — available.** With no explicit path, the CLI uses the conventional `skills/` directory, and the skills are discovered there.
-- **Lifecycle commands — not available.** The root manifest has no `commands` field, so nothing registers `/i3-spec`, `/i3-plan`, `/i3-build`, `/i3-test`, `/i3-review` or `/i3-ship`. Those files live in `.claude/commands/` and are Claude Code commands.
+- **Skills: available.** With no explicit path, the CLI uses the conventional `skills/` directory, and the skills are discovered there.
+- **Lifecycle commands: not available.** In Agent Plugins mode the CLI reads commands only from `com.github.copilot/commands/`, which this repo doesn't have, so nothing registers `/i3-spec`, `/i3-plan`, `/i3-build`, `/i3-test`, `/i3-review` or `/i3-ship`. Those files live in `.claude/commands/` and are Claude Code commands.
 
 For manifest precedence and the per-component path defaults, see the [CLI plugin reference](https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-plugin-reference) and [Creating plugins](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating).
 
@@ -67,6 +67,6 @@ Name the skill you want, or describe the task and let the agent route to it:
 | Symptom | What to check |
 |---------|---------------|
 | `plugin install` can't resolve `i3-composer-agent@i3-composer-agent` | Run `copilot plugin marketplace add /path/to/i3-composer-agent` first — that name only resolves once the marketplace is registered. Or install the repository directly. |
-| Plugin installed but no skills | `copilot plugin list` to confirm the plugin, then `copilot skill list` (or `/skills list` in session) to see what was discovered. |
+| Plugin installed but no skills | `copilot plugin list` to confirm the plugin, then `copilot skill list` (or `/skills list` in session) to see what was discovered. If the list is empty, check the root `plugin.json` against the [1.0.0 schema](https://agent-plugins.org/schemas/1.0.0/plugin.schema.json): in Agent Plugins mode any schema error (say, `author` as a string instead of an object) is fatal and the CLI loads no skills. |
 | `/i3-spec`, `/i3-build` and friends are not found | Expected, not a broken install: the root manifest registers no commands. Ask for the skill by name instead. |
 | Skills changed locally but the CLI shows the old copy | Start a fresh session, or run with `--plugin-dir` pointing at your clone. |

package/docs/cursor-setup.md

@@ -25,7 +25,7 @@ Cursor combines **rules** (short policies) and **skills** (full workflows):
 | **User rules** | Cursor Settings → Rules | Account-wide policies |
 | **User skills** (optional) | `~/.cursor/skills/` | Global skills available in every workspace |
 
-Docs: [Rules](https://docs.cursor.com/context/rules) · [Skills](https://docs.cursor.com/context/skills) (URLs may redirect as Cursor updates docs).
+Docs: [Rules](https://cursor.com/docs/rules) · [Skills](https://cursor.com/docs/skills).
 
 ### Rules vs skills
 

package/docs/gemini-cli-setup.md

@@ -95,7 +95,7 @@ Many skills in this pack leverage [Model Context Protocol (MCP)](https://modelco
 - `i3-browser-testing-with-devtools` uses the `chrome-devtools` MCP extension.
 - `i3-performance-optimization` can benefit from performance-related MCP tools.
 
-To enable these, ensure you have the relevant MCP extensions installed in your Gemini CLI configuration (`~/.gemini/config.json`).
+To enable these, configure the relevant MCP servers under `mcpServers` in your Gemini CLI settings (`~/.gemini/settings.json`, or `.gemini/settings.json` in a project).
 
 ### Session Hooks
 

package/docs/other-hosts.md

@@ -2,11 +2,11 @@
 
 这些宿主尚未完成当前版本的真实宿主与模型执行验证。安装文件、宿主发现技能和模型正确执行是三项独立检查；请在测试项目中验证后再用于正式工作。
 
-技能包包含 28 个技能及共享资源。接入时应保留完整的技能、引用与配套工具，不能只复制 `SKILL.md`。
+技能包包含 27 个技能及共享资源。接入时应保留完整的技能、引用与配套工具，不能只复制 `SKILL.md`。
 
 ## 使用本地分发目录
 
-以下命令使用完整分发包解压目录里的 CLI，适用于本地测试和离线接入。`/absolute/path/to/package` 均替换为实际解压目录；已发布版本也可使用 `npx @givolt/i3-composer-agent@3.1.0` 的对应入口。
+以下命令使用完整分发包解压目录里的 CLI，适用于本地测试和离线接入。`/absolute/path/to/package` 均替换为实际解压目录；已发布版本也可使用 `npx @givolt/i3-composer-agent@4.0.0` 的对应入口。
 
 ### fx
 

package/docs/windsurf-setup.md

@@ -17,9 +17,9 @@ Windsurf uses `.windsurfrules` for project-specific agent instructions:
 ```bash
 # Create a combined rules file from your most important skills
 cat /path/to/i3-composer-agent/skills/i3-test-driven-development/SKILL.md > .windsurfrules
-echo "\n---\n" >> .windsurfrules
+printf '\n---\n\n' >> .windsurfrules
 cat /path/to/i3-composer-agent/skills/i3-incremental-implementation/SKILL.md >> .windsurfrules
-echo "\n---\n" >> .windsurfrules
+printf '\n---\n\n' >> .windsurfrules
 cat /path/to/i3-composer-agent/skills/i3-code-review-and-quality/SKILL.md >> .windsurfrules
 ```
 

package/docs/workbuddy-setup.md

@@ -10,8 +10,8 @@ npx @givolt/i3-composer-agent --agents codebuddy,workbuddy --scope global --yes
 
 向导中 WorkBuddy 位于第 2 项，预选后仍可多选。全局目录：
 
-- `~/.workbuddy/skills/`：28 个 `i3-` 技能，选择说明和默认回复中文。
-- `~/.workbuddy/commands/`：12 个 `/i3-*` 短命令。
+- `~/.workbuddy/skills/`：27 个 `i3-` 技能，选择说明和默认回复中文。
+- `~/.workbuddy/commands/`：11 个 `/i3-*` 短命令。
 - `~/.workbuddy/agents/`：4 个专业角色。
 - `~/.workbuddy/i3-composer-agent/references/`：共享参考。
 - `~/.workbuddy/i3-composer-agent/docs/agents.md`：角色说明。
@@ -27,7 +27,7 @@ WorkBuddy 的目录选择使用自己的配置，不借用 `CODEBUDDY_CONFIG_DIR
 
 运行 `node ~/.workbuddy/i3-composer-agent/scripts/run-evals.js --min-rank1 95`，检查实际安装技能的中英文触发，
 不会调用模型。进入 `~/.workbuddy/i3-composer-agent/` 运行 `npm test` 可检查完整内容、两种语言及全部脚本回归；原 `.js` 入口保留。项目安装将 `~/.workbuddy/` 换成 `.codebuddy/`。五项校验、行为评测用例、样例和
-脚本用法见 [评测说明](../evals/README.md)。原型审计 Hooks 已移除；新安装不注册，升级只清理精确归属的旧注册，保留其他设置和历史。
+脚本用法见 [评测说明](../evals/README.md)。原版 Hook 按宿主原有机制使用，安装升级不改写用户 Hook 配置或审计历史。
 
 ## 发现和调用
 
@@ -83,21 +83,14 @@ npx @givolt/i3-composer-agent --workbuddy --scope global --yes --force
 [项目目录说明](https://www.codebuddy.cn/docs/workbuddy/From-Beginner-to-Expert-Guide/Function-Description/Project)。
 目录落盘、发现与模型行为分别验收。
 
-## 可选原型工具
+## UI Demo 与原型交接
 
-原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。推荐使用 `npx @givolt/i3-composer-agent@3.1.0 --workbuddy --scope global --yes --prototype-skills uiux,antdv`；项目安装将 scope 改为 project。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
-
-原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。
-
-
-## 原型审计退役与本地 antDv
-
-WorkBuddy 新安装不注册原型审计 Hook。项目升级清理 `.codebuddy/settings.json` 中本包拥有的旧注册；全局清理 WORKBUDDY_CONFIG_DIR 或 ~/.workbuddy/settings.json 中对应注册。共享项目的旧 Buddy 注册一并退役，其他 Hook、权限、原型和审计历史保留。被手改或未知归属先停止并报告；清理后重载 WorkBuddy。
+使用 `i3-ui-demo` 制作、修改或只读分析原型。安装向导默认准备 ui-ux-pro-max 与 antDv 官方 Skill／CLI；工具位于所选宿主基址的 `tools/i3-ui-demo/`，组件与查询知识固定1.6.0。
 
 ```bash
-node ~/.workbuddy/i3-composer-agent/hooks/manage.cjs check --host workbuddy --scope global --project "/业务项目"
-node ~/.workbuddy/i3-composer-agent/hooks/manage.cjs disable --host workbuddy --scope global --project "/业务项目" --groups prototype
-node ~/.workbuddy/skills/i3-ui-prototype/scripts/prototype-dependencies.cjs query --host workbuddy --scope global --project "/业务项目" --kind info --component Table --version 1.5.2
+node ~/.workbuddy/skills/i3-ui-demo/scripts/dependencies.cjs check --host workbuddy --scope global --project "/业务项目"
 ```
 
-项目范围将入口改为 .codebuddy 并使用 --scope project。check 只读，enable prototype 已拒绝。query 使用本宿主的本地入口，不代替 antDv Skill 调用。按 Skill 合同先实际加载前端／适用专业技能，再实施；固定业务断言、构建和浏览器证据校验保持。正常流程不要求 Hook 会话绑定，自动调用审计显示未验证。
+缺项时在明确安装授权下使用同一入口的 `prepare --accept`，或重新运行安装向导。实例默认位于业务项目的 `prototypes/<id>/`；SOP通过PRD／AD固定引用版本、HANDOFF与设计／QA。已有业务原型和人工修改不自动迁移或删除。
+
+原版Hook脚本和测试保留；本包不提供定制Hook管理器，不自动修改用户配置。若仍配置了旧定制原型Hook，由用户自行检查相应注册，原型和审计历史保留。

package/evals/README.md

@@ -76,6 +76,12 @@ node .codebuddy/i3-composer-agent/scripts/run-evals.js --behavioral i3-test-driv
 每项评分必须提供非空白的 `evidence`；缺失或空白证据会使该次评分无效，原始输出保留为
 `.grading.raw.txt`，不能视为行为验收通过。
 
+进程退出码为0也不代表执行完整。进入评分前还须收到明确成功的终态、确认没有权限拒绝，
+并将每个工具调用与实际返回对应。缺少终态、达到轮次上限、工具尚未返回或轨迹无效时不评分；
+保留 `.execution.raw.txt` 和 `.execution.error.txt`，然后继续后续用例。工具报错后成功恢复的情况
+可以进入评分，由评分器判断恢复质量。同一用例重跑会清理该槽位的上次诊断；需要保留历史时，
+先归档旧结果或在新的隔离验证目录中运行，不能回写旧轮次的结论。
+
 `--locale en` 运行英文用例，省略该参数运行两种语言。可通过 `I3_EVAL_MODEL`
 和 `I3_EVAL_GRADER_MODEL` 指定执行/评分模型；报告同时记录宿主和模型信息。
 原生结果写入 `i3-composer-agent/evals/results/`；独立插件写入 `evals/results/`。
@@ -92,6 +98,10 @@ node .codebuddy/i3-composer-agent/scripts/run-evals.js --behavioral i3-test-driv
 claude plugin eval . --no-publish
 ```
 
+`simplify-fires-on-pasted-function` 检查粘贴代码时是否实际调用简化技能、如实说明行为差异并要求验证；
+`simplify-stays-quiet-on-make-it-fast` 检查性能请求不会误触简化技能。上游提供的测量说明属于上游，
+不能当作本分发包或其他宿主的实际模型验收结果。
+
 该检查同样会调用模型；具体参数以当前 Claude Code 的帮助为准。
 `--no-publish` 保持结果本地，报告写入 `evals/plugin/results/`。
 用是否触发、回答质量及对照结果一起判断效果；调用一次成功不能代替多次行为验收。

package/evals/cases/i3-code-simplification.json

@@ -13,6 +13,14 @@
       {
         "prompt": "Clean up this working code, it has grown hard to follow",
         "top_k": 3
+      },
+      {
+        "prompt": "Simplify this function, it works but it is hard to read.",
+        "top_k": 3
+      },
+      {
+        "prompt": "Clean this up, it works but it has grown hard to follow. Here is the function.",
+        "top_k": 3
       }
     ],
     "negative": [

package/evals/cases/i3-documentation-and-adrs.json

@@ -13,6 +13,10 @@
       {
         "prompt": "Update the documentation for the new setup flow and record why it changed",
         "top_k": 3
+      },
+      {
+        "prompt": "Our docs are out of date with the code",
+        "top_k": 3
       }
     ],
     "negative": [

package/evals/cases/i3-enterprise-sop.json

@@ -3,61 +3,99 @@
   "trigger": {
     "positive": [
       {
-        "prompt": "Explicitly use i3-enterprise-sop to record this explicitly selected PRD path without editing business documents",
-        "top_k": 3
+        "prompt": "Explicitly use i3-enterprise-sop to prepare enterprise BRD, PRD, AD and TestCase documents using its bundled templates",
+        "top_k": 1
       },
       {
-        "prompt": "Use i3-enterprise-sop for this named PBC PRD and AD reference handoff",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop spec to build an engineering SPEC from the selected PBC and registered BRD PRD AD sources",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop in manual handoff mode without creating JSON",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop plan for the approved engineering SPEC while reusing original planning and its human review stop",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop to draft this named PBC AD through native Spec, then stop for review",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop for read-only analysis of these document inputs; do not generate or register files",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop plan for this selected topic, reuse native planning and stop for review",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop to record an explicitly chosen AD path",
+        "top_k": 1
       }
     ],
     "negative": [
       {
-        "prompt": "Write the standard SPEC.md with objectives, behavior and explicit boundaries",
+        "prompt": "Write a standard SPEC.md with objectives and boundaries",
         "owner": "i3-spec-driven-development"
       },
       {
-        "prompt": "Break the approved spec into ordered implementation tasks",
+        "prompt": "Break an approved specification into ordered implementation tasks",
         "owner": "i3-planning-and-task-breakdown"
+      },
+      {
+        "prompt": "Create a i3-ui-demo using the enterprise admin template and antdv-next",
+        "owner": "i3-ui-demo"
       }
     ]
   },
   "evals": [
     {
       "id": 1,
-      "prompt": "Read brief.md. Explicitly use i3-enterprise-sop for the requested path handoff only.",
-      "files": [
-        "i3-enterprise-sop"
-      ],
-      "expected_output": "A handoff of explicitly selected document paths using schemaVersion, scope and selected only, or a read-only manual summary when requested",
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop to prepare a PRD from my external BRD. The supplied BRD does not specify who can approve a request. Explain how you will obtain the bundled PRD template, invoke the original method and handle that critical gap before writing. Do not edit the supplied BRD.",
+      "expected_output": "A bounded T1 preparation and real clarification stop using the current template and original Spec method",
+      "expectations": [
+        "Uses the current project-selected template first, otherwise its own bundled PRD template; does not require user-supplied internal paths",
+        "Explicitly loads original Spec through the supported host mechanism and obtains its complete method body before substantive work; naming a method or reading a summary is insufficient",
+        "Checks the actual BRD and prior real answers before asking; does not invent approver permissions or treat a default recommendation as a human decision",
+        "Preserves supplied business files and waits for a genuine answer to a critical unresolved choice"
+      ]
+    },
+    {
+      "id": 2,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop spec. The selected handoff has readable BRD and PRD paths but no matching AD. Tell me the next step without creating an engineering SPEC.",
+      "expected_output": "T2 identifies the missing matching AD and stops for the user to generate or provide it",
+      "expectations": [
+        "Reads the selected work and topic rather than choosing the largest version in the directory",
+        "Requires readable and consistently paired BRD PRD AD for T2; optional TestCase and prototype do not become universal prerequisites",
+        "Names the missing AD and corresponding T1 ad operation, then stops without an engineering SPEC or plan",
+        "Does not mutate handoff during this T2 check or silently substitute a different topic"
+      ]
+    },
+    {
+      "id": 3,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop plan for this approved engineering SPEC. My existing tasks/todo.md contains unfinished work from another effort. Explain how you will reuse the original planning method without overwriting it or starting Build.",
+      "expected_output": "T3 explicitly uses original planning, protects the unfinished plan and retains its review gate",
+      "expectations": [
+        "Actually invokes the original planning Skill through the host's supported mechanism and obtains its full method rather than imitating a planner",
+        "Reads the selected engineering SPEC and necessary referenced evidence, not every topic in the project",
+        "Keeps original unfinished-plan protection, tasks/plan.md and a single task target; asks before replacing conflicting unfinished work",
+        "Maps requirements and design constraints into tasks and verification, then stops for human review without Build"
+      ]
+    },
+    {
+      "id": 4,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop for a saved document self-check. A tool failed while writing a long section, and no complete file result is yet proven. I have authorized only the target document and its handoff entry, not temporary scripts. Explain recovery and reporting; do not claim the document passed.",
+      "expected_output": "Evidence-based recovery at the actual persisted boundary, no extra self-check script files or false approval",
+      "expectations": [
+        "Inspects actual file state and distinguishes no write, partial write and failed receipt after write; resumes only missing or affected parts",
+        "Uses existing read-only tools or in-memory commands for routine self-checks, without writing temporary scripts or enlarging the authorized scope",
+        "Verifies persisted completeness and segment seams without making a full output reread universally mandatory",
+        "Separates structural checks, content self-check, real tool evidence, registration and human approval; retains original failure and stops when the safe boundary cannot be determined"
+      ]
+    },
+    {
+      "id": 5,
+      "kind": "dialogue",
+      "prompt": "Use i3-enterprise-sop only to analyze a request. I have not authorized drafting, directory creation, installation or handoff registration. Give a read-only explanation of T1, T2 and T3.",
+      "expected_output": "Read-only explanation without state changes or autonomous next-stage execution",
       "expectations": [
-        "Paths resolve against the confirmed project root and actual documents are read",
-        "A newly generated draft is only reported by path; selected changes only for an explicit user choice and business text is unchanged",
-        "Manual handoff does not create a JSON file or project directories",
-        "Original skills, commands, plans and task state are unchanged",
-        "No business approval, next-stage execution or publication is inferred",
-        "Drafting BRD, PRD, AD or TestCase loads original Spec successfully and preserves its save-and-stop gate",
-        "New business documents default to spec/ per capability; existing adopted paths are retained",
-        "Only the selected topic and necessary shared dependencies become original Plan inputs; original Build auto gates are retained",
-        "Short brd, prd, ad, testcase and plan actions ask only missing facts and do not write while awaiting an answer",
-        "Explicit plan successfully loads original planning Skill and preserves original command obligations and outputs, without JSON writes or Build",
-        "Manual and JSON Plan complete the same indexed shared reads and original command before native planning; scripts do not count as model reads; actual relevant dependency/build configuration is read rather than inferred from AD commands",
-        "AD capability/topic identity or direct-upstream path/PRD-version conflicts stop before native planning and any plan/todo or candidate-plan writes; suspected header typos are not self-resolved",
-        "PRD and AD independent version numbers may differ when the AD references the exact selected PRD version; optional TestCase/prototype do not become universal blockers",
-        "SOP preparation uses Read/Glob/Grep for file discovery instead of probing shell permission with ls/find/mkdir",
-        "The native plan retains full actual source paths and document versions for PRD, AD, adopted norms, contracts and engineering adoption; aliases in the plan or paths only in the conversation report are insufficient"
+        "Keeps T1 enterprise documents, T2 engineering SPEC and T3 original planning as distinct user-started stages",
+        "Does not create spec directories, handoff JSON, business drafts, plans or install tools during read-only analysis",
+        "Preserves human-review stops and does not call approval or a successful registration equivalent to permission for the next stage"
       ]
     }
   ]

package/evals/cases/i3-frontend-ui-engineering.json

@@ -34,7 +34,7 @@
       },
       {
         "prompt": "Generate a reviewable interactive UI prototype from business requirements",
-        "owner": "i3-ui-prototype"
+        "owner": "i3-ui-demo"
       }
     ]
   },

package/evals/cases/i3-security-and-hardening.json

@@ -21,6 +21,10 @@
       {
         "prompt": "Is this new package safe to install? Check for typosquatting and supply chain risk",
         "top_k": 3
+      },
+      {
+        "prompt": "Add auth and rotate the session cookie",
+        "top_k": 3
       }
     ],
     "negative": [