@zq-silk/yui 1.0.0-alpha → 1.0.0-alpha.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/README.md
CHANGED
|
@@ -34,7 +34,7 @@ not from terminal windows you juggle or details you have to remember.
|
|
|
34
34
|
- **Isolated by default** — repository work happens in managed Git worktrees;
|
|
35
35
|
the stable checkout stays read-only.
|
|
36
36
|
|
|
37
|
-
> **Status:** 1.0.0-alpha, with a clean storage 1.0 baseline. Default updates
|
|
37
|
+
> **Status:** 1.0.0-alpha.1, with a clean storage 1.0 baseline. Default updates
|
|
38
38
|
> support only declared minor upgrades within one storage major. Existing v37
|
|
39
39
|
> Homes require the separate [one-time conversion](docs/storage-baseline.md).
|
|
40
40
|
|
package/docs/release-workflow.md
CHANGED
|
@@ -27,7 +27,15 @@ system sits behind `ReleaseWorkflowPorts`
|
|
|
27
27
|
external ports exercise recovery without real GitHub, npm, git, Controller,
|
|
28
28
|
or model effects.
|
|
29
29
|
|
|
30
|
-
## Clean baseline
|
|
30
|
+
## Clean baseline prereleases: 1.0.0-alpha series
|
|
31
|
+
|
|
32
|
+
`1.0.0-alpha.1` fixes the independent converter's rejection of equivalent
|
|
33
|
+
`home_meta` indentation. It archives the original DDL and recreates the exact
|
|
34
|
+
target table while preserving every row. The runtime storage 1.0 definition
|
|
35
|
+
and checksum are unchanged; already-converted Homes need no new conversion.
|
|
36
|
+
Each alpha version has a new immutable package/tag and its own verified
|
|
37
|
+
converter attachments. Continue using npm `next`; never replace an existing tag
|
|
38
|
+
or overwrite a previously published package or attachment.
|
|
31
39
|
|
|
32
40
|
0.16.2 remains the frozen historical bridge. The 1.0.0-alpha runtime starts the
|
|
33
41
|
distinct storage **1.0** baseline and carries no old migration chain or
|
|
@@ -43,13 +51,13 @@ minor transition; published schema definitions must not be silently replaced.
|
|
|
43
51
|
Current bounded automatic recovery, lock waiting, transactions, replay
|
|
44
52
|
protection and valid exact-identity caches remain normal runtime behavior.
|
|
45
53
|
|
|
46
|
-
Use the exact package version `1.0.0-alpha` to opt into this baseline. Stable
|
|
54
|
+
Use the exact package version `1.0.0-alpha.1` to opt into this baseline. Stable
|
|
47
55
|
releases use npm `latest`; prereleases use `next`, never the stable default.
|
|
48
56
|
|
|
49
57
|
The old-v37 converter is a separate archive. Its source/target verification,
|
|
50
58
|
offline boundary, full backup, original-payload audit, cold startup and rollback
|
|
51
59
|
are specified in [Storage baseline 1.0](./storage-baseline.md).
|
|
52
|
-
Publish its archive and checksum as durable
|
|
60
|
+
Publish its archive and checksum as durable attachments to each alpha release alongside
|
|
53
61
|
the exact tested runtime package. Expiring CI artifacts alone are insufficient.
|
|
54
62
|
The alpha-only `baseline-release` job runs after npm publication, uploads missing
|
|
55
63
|
attachments to a draft without overwriting existing files, downloads and compares
|
|
@@ -72,8 +80,8 @@ protocol and both storage-version bounds against status and live identity.
|
|
|
72
80
|
Missing contract fields are errors, not an older-Controller exception.
|
|
73
81
|
|
|
74
82
|
The converter source, frozen endpoint fixture and converter-specific tests are
|
|
75
|
-
release-only deliverables for
|
|
76
|
-
only after the
|
|
83
|
+
release-only deliverables for the alpha series. Remove them from the 1.0.0 development line
|
|
84
|
+
only after the final corrected alpha release attachments and checksums are durably available
|
|
77
85
|
and verified. Do not delete the only conversion path before publication.
|
|
78
86
|
|
|
79
87
|
## Authorization model
|
|
@@ -22,6 +22,11 @@ Agent 选择一个预先声明的计划，设施从持久状态驱动该计划
|
|
|
22
22
|
|
|
23
23
|
## 纯净基线版本：1.0.0-alpha
|
|
24
24
|
|
|
25
|
+
`1.0.0-alpha.1` 修复独立转换器对 `home_meta` 等价缩进的误判，保留原 DDL，
|
|
26
|
+
按目标定义重建该表并验证所有行不变。运行时存储 1.0 定义及校验和不变，
|
|
27
|
+
已转换的 Home 无需再次转换。alpha 系列每次使用新的不可变版本／标签和
|
|
28
|
+
独立转换器附件，继续发布到 npm `next`，不覆盖已发布版本、标签或附件。
|
|
29
|
+
|
|
25
30
|
0.16.2 保留为冻结历史桥接版。1.0.0-alpha 运行包启用独立的存储 **1.0**，
|
|
26
31
|
不携带旧迁移链或一次性转换工具；之后的 1.0.0 复用最终已验证的预发布存储契约，
|
|
27
32
|
不再重置。
|
|
@@ -33,7 +38,7 @@ alpha 发布后如需改变持久化契约，必须声明新的小版本迁移
|
|
|
33
38
|
已发布基线。有界自动恢复、锁等待、事务、重放保护和精确身份匹配的有效缓存
|
|
34
39
|
都是当前运行能力，不作为历史兼容删除。
|
|
35
40
|
|
|
36
|
-
使用精确软件版本 `1.0.0-alpha` 主动选择新基线。正式版使用 npm `latest`，
|
|
41
|
+
使用精确软件版本 `1.0.0-alpha.1` 主动选择新基线。正式版使用 npm `latest`，
|
|
37
42
|
预发布版使用 `next`，不能覆盖默认稳定版本。
|
|
38
43
|
|
|
39
44
|
恢复 Controller 时，status 和 live identity 都必须匹配此前捕获的执行文件、
|
|
@@ -42,7 +47,7 @@ alpha 发布后如需改变持久化契约，必须声明新的小版本迁移
|
|
|
42
47
|
|
|
43
48
|
旧 v37 转换器独立分发；来源与目标校验、离线边界、完整备份、原始负载审计、
|
|
44
49
|
冷启动和回滚见[存储基线 1.0](./storage-baseline.zh-CN.md)。
|
|
45
|
-
|
|
50
|
+
发布时将转换包及校验和作为每个 alpha 版本的长期附件，与确切测试过的运行包一同保留；
|
|
46
51
|
不能只依赖会过期的 CI artifact。运行 tarball 不得包含 tools/ 或旧迁移目录。
|
|
47
52
|
alpha 专用 `baseline-release` 在 npm 发布成功后向草稿上传缺少的附件，不覆盖
|
|
48
53
|
已有文件；逐个下载并与经过测试的产物比较后，才公开预发布 Release。
|
|
@@ -50,8 +55,8 @@ alpha 专用 `baseline-release` 在 npm 发布成功后向草稿上传缺少的
|
|
|
50
55
|
不自动覆盖发布证据。若 npm 已发布而此步骤失败，只用同一批保留产物重跑该
|
|
51
56
|
job，不重新构建或再次发布 npm 包。
|
|
52
57
|
|
|
53
|
-
转换器源码、冻结终点样本及专用测试只服务于
|
|
54
|
-
|
|
58
|
+
转换器源码、冻结终点样本及专用测试只服务于 alpha 系列的独立交付。
|
|
59
|
+
必须先确认最终修正版 alpha 的长期发布附件和校验和可取得且验证通过，才能在 1.0.0
|
|
55
60
|
开发线上移除它们；不能在发布前删掉唯一转换入口。
|
|
56
61
|
|
|
57
62
|
`yui update --version <exact-version>` 选择精确发布包，实际暂存版本必须匹配。
|
package/docs/storage-baseline.md
CHANGED
|
@@ -42,7 +42,14 @@ Admission is based on this exact storage contract, not an installed package
|
|
|
42
42
|
version: an already-valid v37 Home does not need a cosmetic rewrite.
|
|
43
43
|
It never runs the old migration chain itself.
|
|
44
44
|
|
|
45
|
-
|
|
45
|
+
Use the corrected converter attached to `1.0.0-alpha.1`. The initial alpha
|
|
46
|
+
converter rejected equivalent indentation in `home_meta`. The corrected tool
|
|
47
|
+
allows only that table's per-line indentation differences, archives the old
|
|
48
|
+
DDL and recreates the canonical target table without changing its rows.
|
|
49
|
+
Columns, constraints, all other objects and all ledger entries still match
|
|
50
|
+
exactly. The published runtime storage 1.0 definition is unchanged.
|
|
51
|
+
|
|
52
|
+
The v37 → 1.0 transition preserves Runs with missing optional Snapshot
|
|
46
53
|
references, including their original references and results. A retained record
|
|
47
54
|
need not be ready to execute: missing evidence must not block Home conversion.
|
|
48
55
|
The Leader/Operator can inspect and retire the affected Run; an explicit ordinary
|
|
@@ -55,7 +62,7 @@ effects remain separate conversion blockers.
|
|
|
55
62
|
retries and unconfirmed effects. Preserve queued intent rather than marking
|
|
56
63
|
it completed. Stop managed Sessions and the Controller. `session stop --all`
|
|
57
64
|
refuses busy Sessions; it is not authority to force-stop or discard work.
|
|
58
|
-
2. Stage the published 1.0.0-alpha package in a separate installation prefix, with
|
|
65
|
+
2. Stage the published 1.0.0-alpha.1 package in a separate installation prefix, with
|
|
59
66
|
its native dependencies installed. Do not overwrite the global CLI or try to
|
|
60
67
|
run the new Controller against the old Home.
|
|
61
68
|
3. Verify the converter archive checksum, unpack it, then use its entrypoint.
|
|
@@ -101,7 +108,7 @@ runtime inventory paths, retaining their originals and recomputing only the
|
|
|
101
108
|
format-dependent fingerprint. Resource paths, namespace and port allocations
|
|
102
109
|
do not change. Unknown markers or links remain blockers. The tool
|
|
103
110
|
does not resume old Hosts, update the global installation, start a Controller,
|
|
104
|
-
or submit model input. After a successful conversion, use the staged 1.0.0-alpha CLI
|
|
111
|
+
or submit model input. After a successful conversion, use the staged 1.0.0-alpha.1 CLI
|
|
105
112
|
to install the exact package and start only the new runtime. Start new managed
|
|
106
113
|
Sessions through the ordinary explicit lifecycle; history is not live authority.
|
|
107
114
|
|
|
@@ -35,7 +35,12 @@ Yui 1.0.0-alpha 是纯净运行基线。软件版本 `1.0.0-alpha`、Home 存储
|
|
|
35
35
|
准入依据是精确的存储结构与账本，不是当前安装的软件版本号；
|
|
36
36
|
已经满足该 v37 契约的 Home 不需要为了改软件编号而重写数据。
|
|
37
37
|
|
|
38
|
-
|
|
38
|
+
使用 `1.0.0-alpha.1` 附带的修正版转换器。初始 alpha 转换器会把 `home_meta`
|
|
39
|
+
的等价缩进误判为不支持；修正版仅允许该表逐行缩进不同，保留原 DDL 并按目标定义
|
|
40
|
+
重建该表，验证所有行不变。字段、约束、其他结构对象和完整账本仍严格匹配。
|
|
41
|
+
已发布的运行时存储 1.0 定义没有改变。
|
|
42
|
+
|
|
43
|
+
v37 → 1.0 转换保留缺少可选 Snapshot 引用的 Run、原始引用和结果。
|
|
39
44
|
记录可以读取不代表它必须能执行：证据缺失不应阻断整个 Home 转换。
|
|
40
45
|
Leader／Operator 可以查看、废弃异常 Run；显式普通重试根据当前授权事实创建
|
|
41
46
|
新的 Run 和 Snapshot，不改写旧证据。Review／结果汇总若要复用确切冻结证据，
|
|
@@ -44,7 +49,7 @@ Leader／Operator 可以查看、废弃异常 Run；显式普通重试根据当
|
|
|
44
49
|
1. 使用 0.16.2 结算活动 Run、Job、已认领通知、在途重试和未知外部效果。
|
|
45
50
|
保留排队意图，不伪造完成。停止受管 Session 和 Controller。
|
|
46
51
|
`session stop --all` 会拒绝忙碌 Session，不是强停或丢弃工作的授权。
|
|
47
|
-
2. 将已发布的 1.0.0-alpha 暂存在独立安装前缀中，安装所需原生依赖。
|
|
52
|
+
2. 将已发布的 1.0.0-alpha.1 暂存在独立安装前缀中，安装所需原生依赖。
|
|
48
53
|
不先覆盖全局 CLI，不让新 Controller 打开旧 Home。
|
|
49
54
|
3. 核验转换包校验和并解压，调用入口。以下路径均为**占位示例**：
|
|
50
55
|
|
|
@@ -78,7 +83,7 @@ Yui 记录封装及活动类型化验证计划，将每个改写前的原始负
|
|
|
78
83
|
|
|
79
84
|
旧 `active-release.json` 和 `runtime-identity.json` 归档到
|
|
80
85
|
`retired-runtime/`，不改写成新运行事实。工具不恢复旧 Host、不改全局安装、
|
|
81
|
-
不启动 Controller、不提交模型输入。转换成功后，再由暂存的 1.0.0-alpha CLI
|
|
86
|
+
不启动 Controller、不提交模型输入。转换成功后，再由暂存的 1.0.0-alpha.1 CLI
|
|
82
87
|
安装精确版本并启动新运行环境；通过正常显式生命周期创建新 Session，
|
|
83
88
|
历史记录不代表活动授权。
|
|
84
89
|
|
package/i18n/README.zh-CN.md
CHANGED
|
@@ -30,7 +30,7 @@ Yui 是面向编程 Agent 的本地控制面。你只需用自然语言把目标
|
|
|
30
30
|
Web 仅本地回环，包含只读视图和经认证的用户控制。
|
|
31
31
|
- **默认隔离** —— 仓库改动发生在受管 Git worktree 中，稳定 checkout 保持只读。
|
|
32
32
|
|
|
33
|
-
> **状态：** 1.0.0-alpha，采用纯净的存储 1.0 基线。默认更新只执行同一存储
|
|
33
|
+
> **状态：** 1.0.0-alpha.1，采用纯净的存储 1.0 基线。默认更新只执行同一存储
|
|
34
34
|
> 主版本内已声明的小版本升级。旧 v37 Home 需要独立的
|
|
35
35
|
> [一次性转换](../docs/storage-baseline.zh-CN.md)。
|
|
36
36
|
|