Skip to content

docs(release): state exactly how the 0.2.0 release packages were verified #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HanZijie merged 1 commit into from
Oct 9, 2026
Merged

docs(release): state exactly how the 0.2.0 release packages were verified #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/m1-acceptance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ M1 的目标：一个 zip 跑通对话。代码项已经全部进 main。**现
- **界面是脚本点的，不是人手点的**：授权提示、确认通知、面板的每个按钮都是 `uiautomator` 坐标点击或调试接收器应答，没有人在真机上用手点过一遍。
- **提示词框里用中文输入法打字没有验证**：adb 的文字输入经过输入法被改写成乱码（光标也落在中间），所以只验证了数字输入；编辑后保存并被模型执行这条链路，用 `ask_agent --es instructions` 的一次性覆盖验证了（见上表），界面里“编辑 → 开始 → 保存”也走通了一次（数字）。
- **短信是用 root 写进系统短信库的**：没有收过真实来信，也没有用真实 SIM；`READ_SMS` 读到的内容与真实来信一样（同一张表），但来信的广播路径没有走。
- **覆盖安装**：短信 App 用同一把调试证书覆盖旧构建，保留了设置；换成项目发布证书之后的覆盖安装在发布后单独验证（见发布说明）。
- **覆盖安装**：真机上短信 App 用同一把调试证书覆盖旧构建（versionCode 1 → 2），保留了一项非默认设置。**发布证书签名的 0.2.0 包没有装进这台真机**：它装的是 debug 证书的构建，换成发布证书要先卸载、模型配置和授权会一起丢。发布包改在干净的 API 36 模拟器（Pixel_8a，只读无快照）上验证：下载的 0.1.0 短信 APK（校验和与它自己的 `SHA256SUMS` 一致）→ 改一项设置 → `install -r` 0.2.0 发布 APK：覆盖成功、设置保留、不再弹第一次的对话框；AgentOS App 和五个示例的发布 APK 都装上、版本 0.2.0；发布版短信 App 里按钮 → 预览面板 → 开始 → “等你在 AgentOS 里允许”。证书指纹与 0.1.0 相同（`42:2C:E2:7F…`），每个 APK 的 `apksigner verify` 指纹一致，`SHA256SUMS` 全部 OK。**没有做**：真机上用发布证书重刷模块 zip（`install.sh`）、AgentOS 本体 0.1.0 → 0.2.0、授权记录是否随覆盖保留。
- **模型的随机性**：验收按“多种合理结果都算对”判断（例如起床既可以是闹钟也可以是 06:30 的日程）；每次运行的创建项数量可能略有不同。
- **这轮脚本给手机留下的**：脚本清理时对日历做了一次 `reset`（日历 App 的调试接收器只能整库清理）：它清掉了手机上**之前备忘录演示留下的一个日程**（“和王总开会”）。之后脚本改成日历里有非本次创建的数据时拒绝运行，除非显式加 `--allow-calendar-reset`。其余（待办、闹钟、授权、审批设置）按原样还原。

Expand Down
10 changes: 8 additions & 2 deletions docs/release-notes/0.2.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,10 @@

## 升级

覆盖安装即可：同一发布证书下，插件身份（包名 + 签名摘要）不变，按设计保留用户策略、无需重新确认签名。**从 0.1.0 的发布包覆盖到 0.2.0 的发布包，这条路径在发布前没有做完整验证**：开发中只在 Pixel 8 上用同一把（debug）证书把短信 App 的测试构建覆盖到了手机上已有的旧构建上，应用自己的设置保留（一项非默认的设置覆盖前后一致）；AgentOS 里的授权记录是否随覆盖保留没有单独验证；换成项目发布证书之后的覆盖、AgentOS 本体和模块 zip 重刷的升级路径，**发布后再用从 GitHub 下载的文件在测试机上验证**，结果见本版的验收记录（docs/m1-acceptance.md 三之五）。
覆盖安装即可：同一发布证书下，插件身份（包名 + 签名摘要）不变，按设计保留用户策略、无需重新确认签名。证书指纹与 0.1.0 相同（`42:2C:E2:7F:…`，完整值见 Release 页）。

- **已验证（干净的 API 36 模拟器）**：用从 GitHub 下载的 0.1.0 短信 APK（校验和与它自己的 `SHA256SUMS` 一致），在设置页改了一项非默认设置，再 `install -r` 这一版的短信 APK：覆盖成功、设置保留、**不会再弹第一次的对话框**（所以 0.1.0 升级上来的用户看不到新的数据去向对话框，新说明在设置页和状态页，见上面的已知限制）。这一版发布的 AgentOS App 和五个示例 APK 也在同一台干净模拟器上装好、版本号是 0.2.0；短信发布包里：会话页按钮、预览面板、点“开始”后进入“等你在 AgentOS 里允许”。
- **没有验证**：用**发布证书**签名的包装进那台 Pixel 8 测试机（那台机器装的是 debug 证书的构建，换成发布证书要先卸载、数据和模型配置会一起删，所以没有做）；在真机上重刷模块 zip（`install.sh`）；AgentOS 本体从 0.1.0 升到 0.2.0（这一版 AgentOS 本体代码没有改动，只有版本号）；AgentOS 里的授权记录是否随覆盖保留。

# English

Expand Down Expand Up @@ -74,4 +77,7 @@

## Upgrading

Install over the previous version. Under the same release certificate the plugin identity (package + signing digest) is unchanged, so by design user policy is kept and no signature re-confirmation is needed. **Going from the 0.1.0 release package to the 0.2.0 release package was not fully verified before publishing**: during development only a test build of the Messages app, signed with the same (debug) certificate, was installed over the older build already on a Pixel 8 (the app's own settings were kept: a non-default setting was the same before and after; whether AgentOS's authorization record survives was not checked separately). The upgrade with the project release certificate, and the AgentOS app and module-zip re-flash path, **are verified after publishing with the files downloaded from GitHub** on the test phone; the result is in this release's acceptance record (docs/m1-acceptance.md, 三之五).
Install over the previous version. Under the same release certificate the plugin identity (package + signing digest) is unchanged, so by design user policy is kept and no signature re-confirmation is needed. The certificate fingerprint is the same as in 0.1.0 (`42:2C:E2:7F:…`, full value on the Release page).

- **Verified (clean API 36 emulator)**: with the 0.1.0 Messages APK downloaded from GitHub (its checksum matches its own `SHA256SUMS`), one non-default setting was changed, then this release's Messages APK was installed over it with `install -r`: the install succeeded, the setting was kept, and **the first-run dialog is not shown again** (so users coming from 0.1.0 do not see the new data-flow dialog; the new wording is on the Settings and Status pages, see the known limitations above). The AgentOS app and the five sample APKs of this release were also installed on the same clean emulator at version 0.2.0; with the published Messages package the button on the conversation page, the preview panel, and, after Start, the "waiting for your approval in AgentOS" stage were seen.
- **Not verified**: installing packages signed with the **release certificate** on the Pixel 8 test phone (it carries builds signed with the debug certificate; switching means uninstalling first, which deletes its data and model configuration, so it was not done); re-flashing the module zip on a real phone (`install.sh`); the AgentOS app going from 0.1.0 to 0.2.0 (its code is unchanged in this release, only the version number); whether AgentOS's authorization record survives the upgrade.
Loading