ultra-builder-pro-cli 5.0.0 → 5.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [5.0.1] — 2026-08-26
11
+
12
+ ### Fixed
13
+
14
+ - Corrected Codex Doctor's Hook-trust observation. Codex owns persisted Hook trust but
15
+ does not expose the live decision through its plugin CLI, so Doctor now reports
16
+ `hook_activation: host_managed` with `observable: false` instead of permanently
17
+ claiming `user_review_required` and instructing already-trusted users to review again.
18
+ This changes no Hook registration, ACP transport, installation, or permission behavior.
19
+
10
20
  ## [5.0.0] — 2026-08-26
11
21
 
12
22
  ### Added
package/README.md CHANGED
@@ -21,7 +21,7 @@ writing authority to a different Agent requires an explicit verified transfer
21
21
 
22
22
  ## Ultra Builder Pro 5.0
23
23
 
24
- Version `5.0.0` is the current implementation of Ultra as a cognitive-alignment harness
24
+ Version `5.0.1` is the current implementation of Ultra as a cognitive-alignment harness
25
25
  for real software engineering. It preserves the accepted 3.0 file-first and model-agency
26
26
  constitution, then makes workflow position, recovery, and cross-Agent execution directly
27
27
  observable. It is not a decentralized multi-agent platform and it does not prescribe one
@@ -123,7 +123,7 @@ map, evidence convergence, owner checkpoints, and baseline promotion.
123
123
 
124
124
  ### What happened to the original Agents
125
125
 
126
- Version 5.0.0 does not install a custom `agents/` projection. The old review workers became the
126
+ Version 5.0.1 does not install a custom `agents/` projection. The old review workers became the
127
127
  six focused files under `ultra-review/references/`; review coordination and synthesis
128
128
  belong to the parent `ultra-review` Skill. The old debugger procedure lives under
129
129
  `ultra-dev/references/debugging.md`, and test execution lives under
@@ -204,17 +204,17 @@ Node.js 22 or newer is required.
204
204
 
205
205
  ```bash
206
206
  # Current project, one host
207
- npx ultra-builder-pro-cli@5.0.0 --claude --local
208
- npx ultra-builder-pro-cli@5.0.0 --codex --local
207
+ npx ultra-builder-pro-cli@5.0.1 --claude --local
208
+ npx ultra-builder-pro-cli@5.0.1 --codex --local
209
209
 
210
210
  # Global installation
211
- npx ultra-builder-pro-cli@5.0.0 --opencode --global
212
- npx ultra-builder-pro-cli@5.0.0 --kimi --global
213
- npx ultra-builder-pro-cli@5.0.0 --grok --global
214
- npx ultra-builder-pro-cli@5.0.0 --zcode --global
211
+ npx ultra-builder-pro-cli@5.0.1 --opencode --global
212
+ npx ultra-builder-pro-cli@5.0.1 --kimi --global
213
+ npx ultra-builder-pro-cli@5.0.1 --grok --global
214
+ npx ultra-builder-pro-cli@5.0.1 --zcode --global
215
215
 
216
216
  # All supported hosts
217
- npx ultra-builder-pro-cli@5.0.0 --all --global
217
+ npx ultra-builder-pro-cli@5.0.1 --all --global
218
218
  ```
219
219
 
220
220
  ZCode ACP delegation additionally requires the independently built bridge and an
@@ -261,13 +261,13 @@ Installation is managed, atomic, and provenance-checked.
261
261
 
262
262
  ```bash
263
263
  # Re-running install updates the managed artifact
264
- npx ultra-builder-pro-cli@5.0.0 --codex --global
264
+ npx ultra-builder-pro-cli@5.0.1 --codex --global
265
265
 
266
266
  # Read-only diagnosis
267
- npx ultra-builder-pro-cli@5.0.0 --all --global --doctor --json
267
+ npx ultra-builder-pro-cli@5.0.1 --all --global --doctor --json
268
268
 
269
269
  # Remove only managed Ultra assets
270
- npx ultra-builder-pro-cli@5.0.0 --all --global --uninstall
270
+ npx ultra-builder-pro-cli@5.0.1 --all --global --uninstall
271
271
  ```
272
272
 
273
273
  `--config-dir <path>` isolates both the primary config and host-owned sidecars. It is
@@ -458,7 +458,7 @@ conformance rather than semantic acceptance.
458
458
 
459
459
  - [5.0 design and acceptance contract](docs/ULTRA-BUILDER-PRO-5.0.zh-CN.md) —
460
460
  Route, Skill ownership, continuation, ACP/CLI execution, migration, and journey
461
- boundaries implemented by 5.0.0.
461
+ boundaries implemented by 5.0.1.
462
462
  - [5.0 journey results](docs/evals/ultra-5-0-journey-results.md) — observable source,
463
463
  isolated-runtime, real-provider, real-HOME, and cross-platform outcomes plus the
464
464
  deliberately excluded service-deployment boundary.
package/README.zh-CN.md CHANGED
@@ -17,7 +17,7 @@ Host 模型仍然是工程师。Ultra 提供可复用的方法和可检查的产
17
17
 
18
18
  ## Ultra Builder Pro 5.0
19
19
 
20
- `5.0.0` 是 Ultra 作为真实软件工程认知对齐 Harness 的当前实现。它保留已接受的
20
+ `5.0.1` 是 Ultra 作为真实软件工程认知对齐 Harness 的当前实现。它保留已接受的
21
21
  3.0 file-first 与 model-agency 宪法,再让工作流位置、恢复和跨 Agent 执行变得可直接
22
22
  观察。它不是去中心化多 Agent 平台,也不规定唯一的 Agent 拓扑。它只承诺五件事:
23
23
 
@@ -108,7 +108,7 @@ subagent 的 Host 可以并行运行 Review lens;其他 Host 则顺序运行
108
108
 
109
109
  ### 原来的 Agents 去哪里了
110
110
 
111
- `5.0.0` 不安装自定义 `agents/` 投影。原来的 Review workers 变成
111
+ `5.0.1` 不安装自定义 `agents/` 投影。原来的 Review workers 变成
112
112
  `ultra-review/references/` 下六个聚焦文件;Review 协调和综合归属于父级
113
113
  `ultra-review` Skill。原来的 debugger 流程位于
114
114
  `ultra-dev/references/debugging.md`,测试执行流程位于
@@ -185,17 +185,17 @@ receipts 都是派生证据,不是额外语义文档。
185
185
 
186
186
  ```bash
187
187
  # 当前项目,单个 Host
188
- npx ultra-builder-pro-cli@5.0.0 --claude --local
189
- npx ultra-builder-pro-cli@5.0.0 --codex --local
188
+ npx ultra-builder-pro-cli@5.0.1 --claude --local
189
+ npx ultra-builder-pro-cli@5.0.1 --codex --local
190
190
 
191
191
  # 全局安装
192
- npx ultra-builder-pro-cli@5.0.0 --opencode --global
193
- npx ultra-builder-pro-cli@5.0.0 --kimi --global
194
- npx ultra-builder-pro-cli@5.0.0 --grok --global
195
- npx ultra-builder-pro-cli@5.0.0 --zcode --global
192
+ npx ultra-builder-pro-cli@5.0.1 --opencode --global
193
+ npx ultra-builder-pro-cli@5.0.1 --kimi --global
194
+ npx ultra-builder-pro-cli@5.0.1 --grok --global
195
+ npx ultra-builder-pro-cli@5.0.1 --zcode --global
196
196
 
197
197
  # 所有受支持 Host
198
- npx ultra-builder-pro-cli@5.0.0 --all --global
198
+ npx ultra-builder-pro-cli@5.0.1 --all --global
199
199
  ```
200
200
 
201
201
  把任务通过 ACP 派给 ZCode 还需要独立构建的 bridge 和已安装的 ZCode Desktop。
@@ -239,13 +239,13 @@ ZCode uninstall 与 reinstall。
239
239
 
240
240
  ```bash
241
241
  # 重新执行安装会更新受管理产物
242
- npx ultra-builder-pro-cli@5.0.0 --codex --global
242
+ npx ultra-builder-pro-cli@5.0.1 --codex --global
243
243
 
244
244
  # 只读诊断
245
- npx ultra-builder-pro-cli@5.0.0 --all --global --doctor --json
245
+ npx ultra-builder-pro-cli@5.0.1 --all --global --doctor --json
246
246
 
247
247
  # 只移除受管理的 Ultra 资产
248
- npx ultra-builder-pro-cli@5.0.0 --all --global --uninstall
248
+ npx ultra-builder-pro-cli@5.0.1 --all --global --uninstall
249
249
  ```
250
250
 
251
251
  `--config-dir <path>` 会同时隔离主配置和 Host 自有 sidecar。它是测试时的安全选择,
@@ -413,7 +413,7 @@ effect;validator 成功只证明结构符合要求,不代表语义已被接
413
413
 
414
414
  ## 文档
415
415
 
416
- - [5.0 设计与验收合同](docs/ULTRA-BUILDER-PRO-5.0.zh-CN.md) — 5.0.0 已实现的
416
+ - [5.0 设计与验收合同](docs/ULTRA-BUILDER-PRO-5.0.zh-CN.md) — 5.0.1 已实现的
417
417
  Route、Skill 职责、continuation、ACP/CLI execution、migration 与 journey 边界。
418
418
  - [5.0 journey 结果](docs/evals/ultra-5-0-journey-results.md) — 可观察的 source、
419
419
  isolated-runtime、real-provider、real-HOME 与跨平台结果,以及明确排除的服务部署边界。
package/adapters/codex.js CHANGED
@@ -370,13 +370,10 @@ function doctor(ctx = {}) {
370
370
  if (!discovered) report.issues.push({ code: 'HOST_PLUGIN_NOT_DISCOVERED' });
371
371
  }
372
372
  report.checks.hook_activation = {
373
- status: 'user_review_required',
374
- reason: 'Codex does not trust non-managed plugin hooks merely because the plugin is installed or enabled.',
373
+ status: 'host_managed',
374
+ observable: false,
375
+ reason: 'Codex owns persisted Hook trust, and its CLI does not expose the live trust decision to plugins.',
375
376
  };
376
- report.actions = [{
377
- code: 'REVIEW_CODEX_HOOK_TRUST',
378
- message: 'Open a new Codex session, review the current Ultra hook definition, and trust it before relying on hook acceleration.',
379
- }];
380
377
  report.status = report.issues.length === 0 ? 'healthy' : 'degraded';
381
378
  return report;
382
379
  }
@@ -81,9 +81,10 @@ descriptions and runtime guard rather than a fabricated routing flag.
81
81
 
82
82
  All hooks share the same `.ultra/` idle guard. Wire adapters normalize payload and
83
83
  output fields only; they do not change semantic policy. Codex installation health and
84
- hook activation are distinct: Codex skips newly installed non-managed plugin hooks
85
- until the user reviews and trusts the current definition, so Doctor reports
86
- `hook_activation: user_review_required` without pretending the hook already ran.
84
+ Hook trust are distinct. Codex owns the persisted trust decision, while its plugin CLI
85
+ does not expose that live decision to Ultra. Doctor therefore reports
86
+ `hook_activation: host_managed` with `observable: false`; it claims neither trusted nor
87
+ untrusted and emits no remediation action without an authoritative Host observation.
87
88
 
88
89
  ## Agent execution driver selection
89
90
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ultra-builder-pro-cli",
3
- "version": "5.0.0",
3
+ "version": "5.0.1",
4
4
  "description": "File-first Ultra Builder Pro workflows for Claude Code, OpenCode, Codex CLI, Kimi Code, Grok Build, and ZCode.",
5
5
  "bin": {
6
6
  "ultra-builder-pro-cli": "bin/install.js",