|
1 | 1 | # HarmonyOS uninstall route with post-uninstall verification, 2026-11-12 |
2 | 2 |
|
3 | | -Evidence for #4292: the public `uninstall` command runs the fixed route end to |
4 | | -end on hardware. The fix at 31dfcd012 keys removal success on a second |
5 | | -`bm dump` that no longer finds the bundle record, not on the `bm uninstall` |
6 | | -answer, because `bm` prints its verdict into stdout at host exit code 0 on |
7 | | -this build (see `harmonyos-uninstall-2026-11-08.md` for the recorded shapes). |
| 3 | +Evidence for #4292: the public `uninstall` command runs the route end to end |
| 4 | +on hardware. The route at e36de175b answers bundle state twice from the |
| 5 | +`bm dump -a` inventory through the shared `parseHarmonyBundleList` (one owner |
| 6 | +with the app-lifecycle list), and removal counts only when a non-empty |
| 7 | +inventory no longer lists the bundle; the `bm uninstall` answer and any |
| 8 | +unparseable read are never proofs, because `bm` prints its verdict into stdout |
| 9 | +at host exit code 0 on this build (see `harmonyos-uninstall-2026-11-08.md` |
| 10 | +for the recorded shapes). |
8 | 11 |
|
9 | 12 | ## Device and build |
10 | 13 |
|
@@ -92,10 +95,11 @@ A second uninstall answers honestly that nothing was removed: |
92 | 95 | test `uninstall refuses to claim removal when the inventory still lists the |
93 | 96 | bundle` pins the behavior with the recorded output shapes, alongside the |
94 | 97 | unknown-read and failed-exit refusals the inventory read now carries. |
95 | | -- Local `check:affected --run --head 31dfcd012 --base old-origin/main` passes |
| 98 | +- Local `check:affected --run --base old-origin/main` at e36de175b passes |
96 | 99 | every stage except `unit`; `unit` fails only |
97 | 100 | `scripts/__tests__/eager-closure-budgets.test.ts` because this clone's |
98 | 101 | `origin` names a private fork, so the gate reads the wrong merge base. With |
99 | 102 | `refs/remotes/origin/main` pointed at the upstream head for the duration of |
100 | | - one `pnpm run check:unit`, that chain exits 0. Both receipts are local; CI on |
101 | | - the pushed head is the authoritative run. |
| 103 | + one `pnpm run check:unit`, that chain exits 0. Both receipts are local; the |
| 104 | + authoritative run is CI at a1787af (16 checks, none failing), a commit that |
| 105 | + changes only comments after this run's sources. |
0 commit comments