@seanyao/roll 4.703.2 → 4.706.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 +43 -0
- package/README.md +12 -1
- package/dist/postinstall.mjs +731 -0
- package/dist/roll.mjs +6419 -3869
- package/docs/verification.md +20 -0
- package/guide/en/acceptance-evidence.md +18 -0
- package/guide/en/configuration.md +1 -0
- package/guide/en/installation.md +16 -1
- package/guide/zh/acceptance-evidence.md +14 -1
- package/guide/zh/configuration.md +1 -0
- package/guide/zh/installation.md +13 -1
- package/lib/i18n/init.sh +2 -2
- package/package.json +3 -1
- package/scripts/postinstall-roll-capture.mjs +9 -0
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,49 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
## v4.706.1 — 2026-07-06
|
|
6
|
+
|
|
7
|
+
### 稳定性(48 小时长跑冲刺:9 个真实故障全部根治)
|
|
8
|
+
- 修掉一类让循环静默停摆数小时的身份错认:建造残留会让后续周期认错自己在哪,现在开工前自动检查并纠正,漂移时大声报警而不是带病硬跑(FIX-1209)`[loop-engine]`
|
|
9
|
+
- 一轮周期产生的坏配置收工时立刻清掉、写入当场被拦,不再留下"机器带病运转"的时间窗(FIX-1210)`[loop-engine]`
|
|
10
|
+
- owner 把卡标成"进行中"抢占后循环真的会让路,不再人机同做一张卡产出两份重复实现;死掉周期留下的卡仍会被正常回收(FIX-1211)`[loop-engine]`
|
|
11
|
+
- 一次发布失败留下的内部标记不再永久挡路,待办卡不会因此被晾几个小时没人领;实战复发的残余路径也已堵上(FIX-1212、FIX-1215)`[loop-engine]`
|
|
12
|
+
- agent 供应商抽风、一个字没输出就超时的情况不再算到卡头上把无辜卡打入冷宫,失败统计不再被污染(FIX-1213)`[loop-engine]`
|
|
13
|
+
- GitHub 偶尔抽风时建 PR 会自动重试,不再一击不中就把整轮成功建造全部作废(FIX-1214)`[loop-engine]`
|
|
14
|
+
- 长寿 PR 分支掉进 CI 事件黑洞(push/sync 事件 GitHub 不投递、零 check-run、合并永远被保护规则卡死)时,pr-loop 自动检测并通过 workflow_dispatch 定向拉起 CI,同时以 ALERT 记录静默场景(FIX-1217)`[loop-engine]`
|
|
15
|
+
- `roll release --yes` 不再在 bump/changelog 提交步被自己的 60 秒测试新鲜度闸拦下:提交前自动重写 `.roll/last-test-pass` 证明并校验树匹配,一键发版全程无需人工垫步;测试后改文件的恶意场景仍会被拒绝(FIX-1207)`[release-management]`
|
|
16
|
+
|
|
17
|
+
- 发版自动生成的记录性提交(changelog、建卡)不再被当成卡的正式交付,已完成卡的状态不会发版后莫名漂移,卡也不会没做就被标完成(FIX-1206、FIX-1208)`[release-management]`
|
|
18
|
+
- 主仓被弄脏拦下发布时会列出到底哪些文件脏(含暂存区的),不再"说脏又不说哪脏"(FIX-1218)`[loop-engine]`
|
|
19
|
+
|
|
20
|
+
### 验收与观测
|
|
21
|
+
- 发版前的验收检查能认出现行格式的验收标准清单,不再因"看不见清单"全部豁免放行——验收闸从装饰变回真闸,豁免会留痕(FIX-1216)`[loop-engine]`
|
|
22
|
+
- 协调交付时的判断、验证结论和救场动作会记成日志,终端里能回看,不再只活在聊天窗口(US-OBS-048)`[loop-observability]`
|
|
23
|
+
|
|
24
|
+
### 物理截图与隐私
|
|
25
|
+
- 截图证据默认只拍被测应用的窗口(测终端拍终端、测网页拍浏览器),不再默认全屏,屏幕上的聊天邮件等隐私不会夹带进证据;全屏须显式声明,找不到窗口的回落会留明确记录(US-PHYSICAL-006)`[capture-tool]`
|
|
26
|
+
- 物理截图拍完先过隐私闸:`roll attest` 在把 PNG 收进证据前校验像素尺寸与声明目标一致——窗口目标误拍成全屏、或未声明的全屏拍摄会被拒绝并记录原因,避免误把敏感桌面内容落库;通过校验的证据附带拍摄目标、请求来源、拍摄时间、是否声明全屏等元数据(US-PHYSICAL-007)`[capture-tool]`
|
|
27
|
+
- 截图证据不再误提交到公开仓库:入库前自动校验 remote 可见性,public/不可判定仓一律拒绝并告警,私有仓正常放行;owner 可显式豁免(US-PHYSICAL-008)`[capture-tool]`
|
|
28
|
+
|
|
29
|
+
### 护栏
|
|
30
|
+
- 赦免名单(`loop pardon-skip-list`)收编进 `roll doctor pardon` 诊断子命令,旧命令保留为过渡别名(REFACTOR-073)`[loop-engine]`
|
|
31
|
+
|
|
32
|
+
### 内部工程(护栏审计签字批次落地)
|
|
33
|
+
- 依据护栏大盘点的裁定,十一项整并一次落地:删净退役死代码、重复实现合一(git 环境处理、评审派发、验收清单自愈)、失败归因全系统统一词表与单一判定(外部故障分类、纠错归因、重复失败熔断、失败类别与根因键铺满全部终态记录、终态词表 17 收敛 15)、全局安装陈旧度进 roll doctor 读数、视觉证据校验前移为建卡软提醒(REFACTOR-062、REFACTOR-063、REFACTOR-065、REFACTOR-066、REFACTOR-067、REFACTOR-068、REFACTOR-069、REFACTOR-070、REFACTOR-071、REFACTOR-072、REFACTOR-076)`[loop-engine]`
|
|
34
|
+
|
|
35
|
+
|
|
36
|
+
## v4.704.2 — 2026-07-04
|
|
37
|
+
|
|
38
|
+
### 易用性
|
|
39
|
+
- 安装 roll 时顺手装好 Roll Capture:`npm i -g` 的 postinstall 会自动从 GitHub Release 下载 Roll Capture.app 装到 ~/Applications(macOS;CI/无网/sudo 场景优雅跳过,失败给手动指引绝不让安装失败);`roll setup` 可随时修复重装(US-PHYSICAL-005)`[capture-tool]`
|
|
40
|
+
|
|
41
|
+
## v4.704.1 — 2026-07-04
|
|
42
|
+
|
|
43
|
+
### 稳定性(今晚 roll-capture 实战暴露的三个自愈缺口)
|
|
44
|
+
- 构建过程中产生的文件不再留在工作区等人:验收证据随交付进 PR 分支、审计流水自动入库、agent 会话目录自动忽略,bootstrap 检查只拦真正来路不明的文件(FIX-1203)`[loop-engine]`
|
|
45
|
+
- PR 卡在"缺证据"时 pr-loop 会自己修:找到/生成本地证据、附进 PR 分支、重新校验后合并,修不了才发一条告警,不再每五分钟留字条等人(FIX-1204)`[loop-engine]`
|
|
46
|
+
- 选卡不再重做已经在等合并的卡:能从 PR 正文的证据锚点认出自家在途 PR,等合并的卡会显示"awaiting merge of PR #N"并跳过(FIX-1205)`[loop-engine]`
|
|
47
|
+
|
|
5
48
|
## v4.703.2 — 2026-07-03
|
|
6
49
|
|
|
7
50
|
### 稳定性(backlog 清仓批次 · 2026-07-03)
|
package/README.md
CHANGED
|
@@ -27,6 +27,17 @@ npm install -g @seanyao/roll
|
|
|
27
27
|
```
|
|
28
28
|
|
|
29
29
|
Requirements: Node.js ≥ 22. Roll is a self-contained TypeScript CLI — no runtime engine beyond node.
|
|
30
|
+
On macOS, npm installation also tries to install `Roll Capture.app` from the
|
|
31
|
+
latest `seanyao/roll-capture` GitHub Release into `~/Applications` so physical
|
|
32
|
+
screenshots can run. If the release is private, the installer first tries
|
|
33
|
+
anonymous GitHub access, then retries with `GITHUB_TOKEN`/`GH_TOKEN` or
|
|
34
|
+
`gh auth token` when available; credentials are used only in request headers.
|
|
35
|
+
GitHub requests respect `HTTP_PROXY`/`HTTPS_PROXY`/`NO_PROXY` when Node exposes
|
|
36
|
+
the matching fetch dispatcher. CI, headless sessions, non-macOS hosts,
|
|
37
|
+
sudo/root shells, offline downloads, or `ROLL_SKIP_CAPTURE_INSTALL=1` skip this
|
|
38
|
+
step without failing install; when skipped under sudo/root, re-run `roll setup`
|
|
39
|
+
as a regular user so the app installs into that user's `~/Applications`.
|
|
40
|
+
`roll setup` and `roll doctor tools` report the same readiness and repair path.
|
|
30
41
|
|
|
31
42
|
## Use
|
|
32
43
|
|
|
@@ -210,7 +221,7 @@ with `roll loop resume` when ready.
|
|
|
210
221
|
| `roll next` | Continue init/onboard with one best next command |
|
|
211
222
|
| `roll north [--json] [--no-color]` | North-star terminal panel for autonomy, delivery rate, fix tax, and attribution errors |
|
|
212
223
|
| `roll release [--dry-run\|--showcase]` | Release planning/flow plus golden-path showcase support |
|
|
213
|
-
| `roll setup [-f\|--force] [--reselect]` / `roll setup skills\|offboard` | Install/sync conventions or remove Roll-owned project artifacts |
|
|
224
|
+
| `roll setup [-f\|--force] [--reselect] [--no-capture-install]` / `roll setup skills\|offboard` | Install/sync conventions, repair Roll Capture.app readiness, or remove Roll-owned project artifacts |
|
|
214
225
|
| `roll status [ci\|pulse] [--json]` | Project health, CI state, and delivery pulse |
|
|
215
226
|
| `roll test [--where] [--reset]` | Run tests through the isolation adapter |
|
|
216
227
|
| `roll update` | Upgrade the global Roll install and re-sync conventions |
|