Repository navigation
Closed
Milestone
Description
Result: 2.0.1 published on 11 Nov 2026
Stable 2.0.1 went live on 11 Nov at 17:16 UTC from tag v2.0.1, the same source and build as the signed test version 2.0.1-rc.2. The release page is v2.0.1; what changed is in CHANGELOG [2.0.1].
Done means
- All scope PRs merged to develop with CI green and reviews recorded.
- Release prechecks: the linux-arm64 Browser image is checked; the local AI engine archives equal 2.0.0's.
- Test version signed and published: rc.1 on 7 Nov, then rc.2 on 11 Nov (rc.2 added the missing [2.0.1] notes and the Browser internet permission fixes).
- Installed checks on rc.2 passed:
- fresh install, update and Undo on Linux x86-64 and ARM64;
- System update, Stop, Start, Undo and a second update on Anders's own Mac Home with Browser set up;
- a Mac with local AI updating through System;
- CLI install, update and Undo on the Jetson.
- Not met: Browser on the Jetson was not tried on the final build. Anders deferred it to G5 Private Browser: Jetson support #90 on 11 Nov.
- Stable signed and published from the same build, with the GitHub release page. The live check passed on fresh Linux x86-64 and ARM64: install gives 2.0.1, Undo gives 2.0.0, update gives 2.0.1. Root independently confirmed the served files are the signed ones.
Known issues shipped
- Browser permission gaps: Browser internet permission: five robustness gaps shipped in 2.0.1 (fix in 2.0.2) #566.
- The hickory-proto advisories: Update hickory crates to 0.26.2 (RUSTSEC-2026-0487 to 0491, 0506 to 0520) #569, fixed by After 2.0.1: update-hop pin names 2.0.1, and hickory-proto 0.26.2 (RUSTSEC-2026-0487 to 0491) #573.
- Direct messages across home networks: Carrier: any Home reaches any Home by DID on any network (seed relay) #345.
- Browser on the Jetson untested on the final build: G5 Private Browser: Jetson support #90.
All are in milestone 2.0.2.
Not in 2.0.1
- Update fails on Homes with the local AI engine: sealed llama.cpp tree cannot be replaced (2.0.1) #515: local AI update with a changed engine archive.
- Browser image admission trusts digests in the installed image directory #534: Browser image admission. Its hold was scoped out for 2.0.1, and the issue is in 2.1.0.
Earlier planning notes, candidate checkpoints and receipts are in this description's edit history.
Metadata
Metadata
Assignees
Labels
No labels
Activity
andersalm commentedon Nov 5, 2026
#534 has a scoped no-hold disposition for 2.0.1: the reported attack requires prior host-account write access. Its signed-digest repair stays open, and the decision changes if the path crosses confinement, account or privilege boundaries.
Keep #406’s signed helper-byte gate and the existing #90 installed/media/manual/human acceptance. Anders’s Jetson/channel steering changes the release scope; it grants the existing owners their work and preserves the signing/publication approvals.
Main owns the exact candidate, current reviews/checks, unchanged 2.0.0 engine-archive check and installed qualification before release. Earlier #515 work remains open under the new release order.
andersalm commentedon Nov 5, 2026
Room-session PR #536 has bounded independent source PASS, with grant-bound expiry and legacy-record refusal traced through its use paths. The exact completed full Linux receipt was read; execution remains owner evidence.
Main owns current checks/reviews and integration, followed by the installed sign-out/reconnect and release qualification in #86 and this issue. Private advisory contents remain private.
andersalm commentedon Nov 5, 2026
For the Linux opt-in scope, verify the complete fresh-install path: install.sh and opening an unprepared Browser show the explicit setup command while leaving acquisition and administrator setup to that command. Runtime’s current local-engine preparation happens before the readiness probe, so changing install.sh alone does not establish this behavior.
The explicit command still needs #406’s signed-byte binding for the privileged helper. Preserve existing prepared installations and Browser profiles, then qualify first setup, Open, Close/reopen, update and Undo on the release candidate under #90.
Anders’s Marketplace request is confirmed at origin; the terminal command for 2.0.1 and #333 Marketplace work are Main’s recorded implementation stages. Source review waits for their frozen candidate and completed checks.
andersalm commentedon Nov 5, 2026
The push queue reports that the Linux Browser opt-in candidate
ac38aa17eis waiting for its required full Linux check. This is a missing completed receipt, rather than a reported test failure.Main owns the next action: use the existing remote-check queue and an available owned slot, preserve any failed attempt, then supply the completed full-check receipt with the full commit, tree and base. Main continues the normal review and integration gates; Root reviews the frozen source and completed evidence when supplied. The fresh-install refusal, explicit setup/Open/Close, profile and update/Undo acceptance checks remain in scope.
andersalm commentedon Nov 6, 2026
Main reports that the old 2.0.0 Cargo build cache was removed after its final process/open-file check, and both lifecycle inventory rows were marked removed. Reported free space is 63,920,976 KiB, above the reported 52,468,949 KiB stop line. The channel chooser’s previously refused Clippy and all-target checks are resuming. This is completed owner evidence; Root’s earlier independent check established zero tracked paths and zero open files before releasing cache protection.
The queue now reports one untriaged late failure and Browser opt-in candidate
10dec7c60waiting for its required full Linux receipt. Main owns failure triage from the actual error, any repair and check scheduling in the existing lane. The changed candidate needs its own completed receipt and frozen review. These source/check steps remain separate from installed release acceptance.andersalm commentedon Nov 6, 2026
Root SOURCE REVIEW: CHANGES REQUIRED on
f1232e148f2b1d0ab8ab9ee03d63e9c3e366aab2/ tree3de15aca32bce6ea2c4f63ea0809a521f2539270, base527a193cca91dcf8cce37e0d721f436071f580c7(17 changed files). Independent Browser status 17/17 and four focused installer cases pass, zero skipped; candidate-attribute diff check passes. The first narrow installer invocation used unsupported test arguments and ran zero tests; the corrected module invocation passed. The completed full Linux receipt matches this head/tree/base and reports PASS; execution remains owner evidence. Root ran zero Rust builds/tests or target operations.P1, #406:
setup/browser_linux.rs:37–53,158–185still leaves the privileged helper handoff without an exact binding to the admitted bytes. Main must complete #406’s replacement regression and repair that handoff before claiming this manual setup meets the existing release gate. Details stay with Main’s private review delivery.P2,
api/gateway_browser.rs:618–623/setup/browser_config.rs:191–224: an already open Browser viewer whose native supervisor is missing or stale receives setup guidance before it reaches the helper repair path. The new helper-refresh tests call the producer directly and miss this consumer ordering. Main should keep the early fresh-Home refusal, allow admitted helper repair for an already configured Home before the host probe, and test actual Browser Open with missing/stale helpers after the viewer is loaded. Installed setup/Open/Close/profile/update/Undo acceptance remains open.andersalm commentedon Nov 6, 2026
Root bounded SOURCE PASS for Browser opt-in candidate
bc39a939a7b319223b65ac667fbbc777dccf68b3/ tree1569fb28bb1cd64a5a33be13bbd4773133f4c436, base95a2896deb7a8b0c4f14561c12cd60aae39475bf. The eight affected task files were re-reviewed; the earlier unchanged task files reuse their review. Both findings onf1232e148are resolved in source: #406 now binds the captured admitted payload to the root read-back bytes and memory execution; configured Homes repair helpers before the Open host probe, while fresh Homes retain refusal before acquisition. Actual Open regressions cover missing/stale helpers and fresh refusal, including a padded adapter ID.Independent bootstrap tests: 8 PASS, 0 skipped; candidate-attribute diff check PASS. The prior unchanged Browser status/installer checks remain 21 PASS, 0 skipped, with the original unsupported installer invocation preserved. The new completed full Linux receipt binds this exact head/tree/base and reports PASS; Root read it and the completed log tail, while execution remains owner evidence. Root ran zero Rust builds/tests, privileged or target operations. Main owns compatibility with the current integration base, current reviews and checks after any merge. Signed installed setup/removal/Open/Close/profile/update/Undo and media/manual/human acceptance remain open.
andersalm commentedon Nov 6, 2026
Release notes for 2.0.1: the Unreleased section on develop has no bullet yet for Browser on Linux ARM64 with KVM (#531, Added) or the Assistant fix (#533/#545: a finished answer stays in view, also while a longer question is typed). Both go into the rc.1 section when it is named, so the notes match what the team sees.
andersalm commentedon Nov 6, 2026
All planned 2.0.1 changes are on develop (c6adf60): #532, #531, #526, #533, #536, #542, #543, #544, #545, #546, #551, #556, plus test fixes #547 to #549 and #553. Naming 2.0.1-rc.1 now (version bump and release notes section), then the full check, CI, package run and qualification. Signing gates still open: Irzhy's review of #536 (his #551 security review passed, comment 6685844716); installed checks on Mac, Linux and the Jetson after rc.1 is published to the test channel.
andersalm commentedon Nov 6, 2026
2.0.1-rc.1 package run 42287807786 failed in both Linux musl builds:
libc::getentropyis not declared for musl in libc 0.2.189 (elastos-common owned_removal.rs:161). The module became Linux-compiled with #531; every Linux gate builds glibc, so the release build was the first musl build. Develop CI on d88efd1 is green. Fix (portable random bytes) plus a musl compile check in a pre-release gate are being written on release/2.0.1-rc.1; then the package run is dispatched again. Nothing was published; the name 2.0.1-rc.1 stays.andersalm commentedon Nov 7, 2026
2.0.1-rc.1 is READY TO SIGN from 30b166b (version bump, release notes, and the musl fix 43cf06d + 30b166b that a musl check in CI now guards). Develop CI and the package run (both musl builds) are green; the universal-asset check found 0 conflicts in 296 entries; the seed is upgraded. After signing: verify, Community node, publish to the test channel, then installed checks (update from 2.0.0 on Mac, Linux and the Jetson, fresh installs, the Jetson's one-time Browser setup, Undo). Irzhy's review of #536 remains a gate before 2.0.1 stable.
andersalm commentedon Nov 7, 2026
Correction: Irzhy's security review of #536 passed on 5 Nov (PR #536 comment 6665818315, tree 344284e); the reviewed files are unchanged in 30b166b, so that signing gate is met. Signing of 2.0.1-rc.1 waits for Anders to try the build first (his request, 7 Nov): Main is staging a private test Home from the exact rc.1 files. Note for the plan: publishing rc.1 makes it the seed's single release head, so fresh installs during the test window get 2.0.1-rc.1 (stable Homes are not offered it).
andersalm commentedon Nov 7, 2026
Trial before signing, 2.0.1-rc.1 (source 30b166b, package run 42337367672, signing input sha256 c79cb0fd586e755665ada39c3ab97e0898fe560834a96be3f7d5284c45c84ed6). Unsigned, nothing published.
Anders's private trial Home (Jetson, linux-arm64, port 8097, his own test account, separate from his own Home):
elastos --version2.0.1-rc.1; Home 200; Browser readiness ready; a separate harness Home with the same payloads opened and closed Browser (202/200) with crosvm--cpus 4on the 6-core host.elastos setup --browserrefuses an unsigned installation, as designed).Linux tester: GO on a Linux x86_64 source Home built from 30b166b (first-run passkey, unlock after restart, Library document across restart, People, Marketplace and Chat UI). Not a channel install.
Found during the trial, both present in 2.0.0: #558 (operator-drive-adapter never starts) and #559 (Browser reaches the internet with no owner grant). #559 is a release decision for Anders: ship 2.0.1 with the gap stated in its notes, or wait.
Signing is not requested until Anders has tried the build and decided on #559.
andersalm commentedon Nov 8, 2026
Anders's rc.1 trial on the Jetson (8 Nov): Chat stable overnight; Browser works but scrolls slowly (recorded on #90); the Stable or Test choice (#546) is not visible in System.
Cause of the last one: the trial Home on port 8097 was staged from a source build and then given the rc.1 package files, so it has no
sources.json(no update source). System hides the channel choice when Home has no update source (capsules/system/browser/system.js:3721) and shows Update channel "Off". This is a gap in how the trial Home was staged, not an rc.1 fault; a Home installed with the install command always has an update source. I did not add one by hand: this Home has no~/.local/bin/elastos, so an update applied there would go to the wrong place.Proof so far for #546 is automated only (server tests and
scripts/system-channel-choice.test.mjs). The first check by a person happens on an installed Home after rc.1 is signed and published to Test versions: install rc.1, switch Test to Stable and back with the passkey, and confirm it never offers 2.0.0. Added to the post-signing installed checks.19 remaining items
andersalm commentedon Nov 10, 2026
Independent source review passed for rc.2 candidate
ff3edb3670d29313616f4c1f9b21ee6f3e56061b(tree155598fe110dd6abcfef011b8f9ef26ff0a1fb83, base30b166b05e1e4e29e97597aad25a688a19380ad1). The five-file delta fromca52fbb56resolves both preflight findings. Target refresh requires and installsbrowser-python.mjswith the preflight scripts. The readiness cache tracks the module and the selected Node executable. Four checks against the exact cache-key function with mock file metadata failed on the parent and passed on the candidate. They covered replacement of bundled Node, fallback to PATH, replacement of PATH Node, and removal of the module. Candidate whitespace and syntax checks passed. Both release sections passed the notes rules and signed text bounds (20 bullets / 2,234 bytes for 2.0.1, 22 / 2,686 for rc.2).I verified the completed full Linux PASS receipt and successful log tail for
ca52fbb568cb68cde26ed72b285482d8fe0a234a(tree5f4f1b187287cb42fafc9d9e97d196eff1bd8cec, same base). The receipt names that ancestor. The later three commits change only Browser scripts, their tests, and release notes. Main reports 93 passing focused tests and peer review on the preflight changes, plus Mac tests on the ancestor. The current candidate's queued Mac gate and package qualification remain open. Main owns triage of the late failure reported at queue admission if it still blocks that gate.The rc.2 notes retain the manual repair requirement for rc.1 Homes whose journal reference copy is gone. Main owns the exact packaged trial before signing and the signed Mac Update, Stop, Start, Undo, and update-again journey before Stable. Recovery review
GitHub confirms that the published release branch points to the reviewed commit and tree. The completed-run snapshot had no CI or package result for this commit. Main owns the Mac gate receipt and package qualification, followed by the real-machine trial before signing. Published rc.2 source
andersalm commentedon Nov 10, 2026
Independent source review passed for
42cda65a226733e81c5342cf4f89cddc9c6f3b32(treed28c80f6793b7a553efecc182d7168b36851a2ae, parentff3edb3670d29313616f4c1f9b21ee6f3e56061b). The only change is the previous-release test pin. I verified both Ed25519 signatures on the public 2.0.1-rc.1 Test head and release manifest against the existing publisher key. Both CIDs, the manifest digest, version, and signer match the new pin. The actual prepare check refused the prior 2.0.0 pin against these public bytes and accepted the new pin. The oldest System-update pin remains in place. Candidate whitespace check passed. Prepare checkMain reports that the first committed Mac gate on
ff3edb367failed in the harness when an early-exit grep ran under pipefail. Main triaged that attempt and reports the rerun passed on the same commit. The pin change has its own queued gate and package qualification. Main owns the exact package trial before signing. The signed Mac update and Undo from 2.0.0 remain required before Stable.GitHub confirms the rc.2 release branch now points to this reviewed pin commit and tree. Package qualification and the real-machine trial remain open. Published rc.2 source
andersalm commentedon Nov 10, 2026
rc.2 candidate 42cda65: develop CI run 42759688970 failed. Packaging (run 42759695489) keeps running, only to catch packaging-only failures early; this SHA will not be qualified.
scripts/system-window-policy-browser-smoke.mjsfixture does not serve/api/apps/browser/internet, which Browser uses this computer's internet only after the owner grants it, as a revocable capability #559 made System call (capsules/system/browser/system.js:394-412). Test fixture gap;just product-ui-browserruns only in GitHub CI. Lesson 1483.scripts/browser-vm-target-refresh.test.mjs:87(new in 165f84b) expectspreparation_required, but the Linux runner returnshost_unsupported: a host-dependent test that was run only on the Mac. Lesson 1484.scripts/chat-online-behavior.test.mjs:140"the poll actually reached the fault": first failure in the ledger; it passed on three full Linux checks of this train. It is being measured under load to tell a test race from a product bug.Fix:
fix/rc2-ci-linuxfrom 42cda65 (tests and fixtures only, unless the Chat measurement shows a product bug), proven on Linux including the wholejust product-ui-browserlist, then Grok review, the Mac gate and a new qualification. No rerun of the failed run.andersalm commentedon Nov 10, 2026
CI attempt 1 failed on rc.2 commit
42cda65a226733e81c5342cf4f89cddc9c6f3b32(treed28c80f6793b7a553efecc182d7168b36851a2ae). Ten jobs passed, three failed, and three were skipped. The Linux and Mac installed CI update-hop jobs both passed and retained their receipts. The packaged trial and signed Mac Update and Undo journey are separate gates. CI attempt 1preparation_requiredfor a Darwin ARM64 request on Linux, where the preflight correctly returnedhost_unsupported. Main should make the fixture expect the result for the actual host while retaining the exit, JSON schema and installed module checks. My earlier fixture check covered the preparation-required path. JavaScript behavior jobMain owns the fixture fixes, targeted regressions, and CI and package qualification for the resulting commit. The first log read was refused by the terminal-escape filter. The corrected bounded read supplied the results above.
Release package attempt 1 completed successfully on the same commit. All 11 jobs passed, including the three native N/N+1 builds, Jetson compatibility, and the four seed and platform attestations. The workflow used pinned engine inputs and skipped both engine rebuilds. GitHub lists 11 artifacts. This verifies the completed packaging run; installed behavior still needs a real-machine trial. The failed CI result above still blocks this commit. Main confirmed the fixture repair plan and will run the gates on the resulting commit.
andersalm commentedon Nov 10, 2026
Independent source review passed for rc.2 fixture repair
8ce6d25836ac9ef80e59d89577a6494f862f9ac5(tree0192039ac512331c3db6e629bc3be45976765c70). The three commits above42cda65a226733e81c5342cf4f89cddc9c6f3b32change three test files. The earlier pin review carries because those pin inputs are byte-identical. GitHub still points the rc.2 release branch to42cda65a2at this snapshot.The refresh fixture checks the installed module, exit status, and readiness schema for the actual host, then checks that removing the module fails. The System window fixture serves the existing Browser internet off response and still rejects unknown API paths. Chat waits up to five seconds for the fixture socket to close or the response to finish before clearing the fault. Recovery, draft, cursor and history assertions still run. I checked syntax and whitespace and ran five cases against the exact Chat fixture handler with mock events. All five passed.
Main reports 73 focused tests passing on Linux and Mac, all 16 Linux Browser UI commands passing, and 2,235 Linux behavior cases passing with a complete test-name comparison. Main also reports two earlier exit-zero runs with incomplete output, preserved in lesson 1497. The 51 affected cases passed separately and the blocking stdout preload restored the complete report. The Mac gate and Grok review remain pending in the handoff.
Main owns qualification on this commit, including fresh CI and packaging after the Mac gate and Grok review. Packaging passed on the parent. The exact packaged trial precedes signing, and the signed Mac Update, Stop, Start, Undo, and update-again journey remains due before Stable. Prior CI failure and package result
GitHub now shows both
release/2.0.1-rc.2anddevelopat the reviewed commit and tree. Completed CI and package results for that commit are pending. Published sourceCI attempt 1 finished successfully on
8ce6d25836ac9ef80e59d89577a6494f862f9ac5at 09:21 UTC. Fourteen jobs passed and two were skipped. The completed logs show the Browser refresh and Community Chat network cases passing, and the Browser layout smoke step passed after running the System window fixture. The AMD64 job installed its tools and verified the cached pinned engine archive. Both engine rebuilds were skipped. Linux and Mac update hops passed with disposable signed fixtures and uploaded receipts. Completed CIMain owns package qualification and the real-machine trial of the resulting artifacts before signing. The signed installed journeys remain due before Stable.
Release package attempt 1 passed all 11 jobs on the reviewed commit. The three native N/N+1 builds, Jetson compatibility, and all four attestation jobs passed. The package used pinned engine archives and skipped both rebuilds. I checked the four small GitHub proof archives. The six native input receipts and the seed input receipt each contain the reviewed commit and tree. This check covers the receipts and workflow results. Main reports that assembly produced 300 entries from six inputs with zero conflicts, and that the committed Mac gate and Grok review passed. Package run Main's qualification record
After the seed upgrade, Main reports a fresh non-root Ubuntu 24.04 install of the currently published rc.1 with 30 components installed and zero skipped. Its update check exited 0. Main is preparing the exact unsigned rc.2 package for the Mac trial before signing. The signed Mac Update, Stop, Start, Undo, and update-again journey remains due before Stable.
The Mac trial report supersedes the signing preparation for
8ce6d2583. Main reports that Runtime Close completed and all 13 cleanup checks passed. The subsequent Browser internetendcall returned HTTP 409, so the Browser window stayed open. The same trial recorded one timing failure in the full behavior suite, followed by a pass for that case in isolation. Trial evidenceI independently traced the failure in the reviewed source. Home signs the projection with Browser as the executable actor and Home as the authority actor. The token validator already checks the executable actor, origin and session. The extra
endcheck compares the authority actor, which is why the direct-token test passed while Close from Home failed. Keep the repair local toend. A regression through Home launch should prove that ending one Browser launch stops that launch's dispatch, leaves a second launch usable under the same grant, and still refuses a System projection. The signed token's launch ID remains the only retirement target. Main owns the frozen fix, applicable checks and a repeat of the packaged Mac Close journey before any signing request. Main's repair record #559Browser Close repair source review
Source review passed for the six-file delta from
8ce6d25836ac9ef80e59d89577a6494f862f9ac5to975b2524d8249721cdd87f4ed038b7c61668b3f2, tree8cc9cb3fc720fa7d19c0410c9948863f5df1f841. Runtime validates the launch token, checks that Browser is its executable actor and ends only its signed launch ID. The route test uses the Home launch handler and checks that a second Browser stays usable under the same consent. It covers repeated End, refusal for other actors and invalid tokens, and System Stop for the remaining launch. The public Home launch route still selects the host platform internally. The UI smoke fixture holds the End response to check that Home keeps the window open until End succeeds.Candidate whitespace and JavaScript syntax checks passed. The first syntax-check invocation failed to resolve the source blob, and the corrected command checked the candidate blob. I verified Main’s completed full Linux PASS receipt against the exact commit, tree and base. Main ran the Linux checks and reported the Mac checks and separate security review. The first Linux attempt failed because the fixture assumed Darwin arm64, as Main reported. At review, the clean release worktree was three commits ahead of the fetched and public release refs.
Main owns the Mac gate, CI and package qualification for this commit. Repeat the exact unsigned Mac trial with consent active. Record artifact parity, Runtime Close and cleanup, successful End and window removal before any signing request. The signed installed journeys and release acceptance stay open. Prior trial Browser consent scope
GitHub CI attempt 1 passed on
975b2524d8249721cdd87f4ed038b7c61668b3f2with 14 successful jobs and two skipped jobs. Behavior, Runtime and capsule tests, the macOS and both Linux source Home jobs, and the Linux update hop passed. The failure cancellation and release upstream asset jobs were skipped. Pinned engine rebuilds, release packaging and Jetson compatibility were among the skipped steps. Main owns package qualification and the unsigned Mac Close trial before signing. Completed CI runI verified both completed package attempts for
975b2524d8249721cdd87f4ed038b7c61668b3f2. Attempt 1 failed in the x86_64 Linux prerequisite step. Main reports that apt reached the step’s 15-minute limit. The failed-job retry stopped at the pinned AMD64 engine download. The workflow gives both the producer and consumer artifact names the current attempt number, so a retry that reuses the earlier producer cannot find its artifact. Both attempts stopped before the x86_64 Runtime build and skipped platform receipt attestation. Attempt 1 Attempt 2Main started a full rerun on the same commit. The package and unsigned Mac Close trial remain the next release checks. Main’s correction
The full package rerun passed on
975b2524d8249721cdd87f4ed038b7c61668b3f2in attempt 3, with all 11 jobs successful. Apple silicon and both Linux architectures passed N and N+1 builds. Jetson compatibility passed on ARM64, and GitHub recorded successful provenance attestation for all three platforms and the matching seed package. The run reused the pinned engines and skipped their rebuilds. Completed package runI matched the downloaded Mac and seed proof ZIPs to their GitHub SHA-256 digests. This verifies the proof archives used for preparation. Main owns the package and installed file comparison, the engine archive equality check against 2.0.0, and the unsigned Mac trial of Browser Close with consent active before any signing request.
Main's unsigned Mac trial on
975b2524d8249721cdd87f4ed038b7c61668b3f2passed Browser Close. Main reports HTTP 200 for Close and End, all 13 cleanup effects, window removal, and a second Browser opening under the same consent. The verified attempt 3 Mac N receipt contains the reported Runtime and Browser image hashes for this commit and tree. The assembled components manifest and installed journey results are Main's evidence. The trial report retains the staging and harness corrections and the two Linux-only skips. Main’s trial reportAfter trying that package, Anders held signing for the Browser permission screens. Main owns the clickable mock for Anders and will freeze a new candidate after design acceptance, keeping the rc.2 name. The next commit needs its own applicable review, checks, package and trial. Main reports fixing the separate signing preflight false refusal. The signed install, update, Undo and setup checks remain open. Release decision Mock review and checks
andersalm commentedon Nov 10, 2026
2.0.1-rc.2 QUALIFIED from
8ce6d25836ac9ef80e59d89577a6494f862f9ac5(tree 0192039ac512331c3db6e629bc3be45976765c70):Now: release preparation (approval, seed node upgrade, prepare). Then a private trial Home on Anders's Mac from the exact unsigned package (port 8096) before he is asked to sign. After signing and before Stable: the signed Mac 2.0.0 to rc.2 Update, Stop, Start, Undo and update-again journey with Browser set up.
andersalm commentedon Nov 10, 2026
Private trial on macOS 26.6.2 ARM64 uses exact unsigned
2.0.1-rc.2from8ce6d25836ac9ef80e59d89577a6494f862f9ac5, package run 42781179180. All 72 package input hashes and 4,173 payload files per Home passed before and after. Browser image was an APFS clone after byte verification. Runtime SHA-25675108e4e962e1edb2fd478f386b5b6cb60149f8cda001e241731f187a52a4c10. Components manifest SHA-2565140d03067f2be621b3f91d00650d72588fe47725665ee19f20493049b10bc25. Browser image archive SHA-2566894608add893a9b5791da9cd141ab9ce756f3d6d16e710c114373384e4bcb66.Version, health, Browser readiness, Community join, virtual-passkey Inbox approval and native Browser open passed. Browser UI Close FAILED. Runtime Close returned HTTP 200 with
closed=true, cleanup success and all 13 absence effects proved, then internetendreturned 409Browser launch requiredand left the window open. The end guard checks authority actor, while the Home projection retains Home authority. Browser waits for end before confirming window close. Source gate passed. Behavior ran 2,235 cases with one timing failure, and that case passed alone in 2.01 seconds under the lease. Lessons 1506–1512 record the timing failure, harness repairs and installed Close failure. Trial remains running with no account. Harness is stopped. Install, update from 2.0.0, Undo and first administrator Browser setup await signing. Push and CI were excluded by this local-only task.All 72 verified package input SHA-256 values
4328697c968e614dd45715bfe893747ae4bf3f338d576b8c3f325d09cefb57a5e1c5bb2d8d5dd416c5b3b4b276826a8b421cf4af04131c1a3e5c951b60b81fdaaa76e795d85520d0f0532068a078ddbbfb0cefc51fd6e6c8745290943b2d4304c92e71843d1e307587b66a7c20c5253be05236cd4faed4d5b1d82cfe07ca1eae969517090c23995496f39a3c346734c0bfb7d51afa900fcbeddf481167b8f6cc6445c6e79c65df3a37f7e7ac57f16e2caf2aaaf5bdd385b37484136682da01aa580b1fe074af3a7b72f1cef95fd71b95c775602a8c4938069ff694283d2cce6c2dd00cb4e9ed21082ea607f04672093894ac952e8435067bf24df041c8315c23c5bbbc0e0cfe4da2114999eaaed22f68485152acb712fab43e5ef16adc41ecbb24f16e504c9bfce81665e5b93684e3195e7473ed49f04ba1f13613de3133bb1ac5bbbc0e0cfe4da2114999eaaed22f68485152acb712fab43e5ef16adc41ecbb5451bfa7566136cb3473549dc702e5c61153afee7be4ede7d93da3546af9690a6894608add893a9b5791da9cd141ab9ce756f3d6d16e710c114373384e4bcb661901313788901843e80944ae38b56a49865973ee51202881d390e9a803ddfb468b48641cbcedbbf9ebfe4e21c5cc202f2b45eaebea95884c9a0cada4257f1c47beaa60bba735c569aa58cfe50655824232da6bd6a9d28fd50ae15139b39ee4f95b2a06789f0f37282ec87b7c2b88ac6a29bdaa2d5d500ac2a376914c647460c56743912b1550d52452218f051b55538186f67829ce6d42284f52a10dce6d29385b90fcf804aa79636d020a50d032e63ec1260f204f5b2ec3c8ddfc015efff7065140d03067f2be621b3f91d00650d72588fe47725665ee19f20493049b10bc25cd50f0153fd591333f61607bf7840127b4b1ea7124eed22101360a756ad739b97eb96b88db27e035446201a2e9dea06bb9f82f8a2160457e7c466abb127529b656acbc96c456e8aae08994936e5a2eb33bcf0c5b779cd6017478176a6455b594e501fbc3504ca5a5870a9ce06b848dc95f0b1f5efd9f4d95a6332ede0f4f8a0384359c31fb6ddf2a195ff649393c01814f1e1662e3bc42d79123a56d706184f67146502fecb1bf3a7941ffa88819b64da6af37be5da7273dae0525dba248f3cb5bbe65206a2721050af9231269e65a046e85bc05bd001da576da51b6b74307f044e8755cd1ea5422ea203886497bb7367a0ff32030d31258b5906de8aa38852375108e4e962e1edb2fd478f386b5b6cb60149f8cda001e241731f187a52a4c104a207d86cb75f7e455a0aede6c7782410fb495683960057094001c2c941c1de1b41d1a45aaa528d01bc915cbde2c5b8bdf26b184860cb38049b9f6de9a0c407d2f7536be0735ab008f667725237bed0962217a5f73b0bca98a82fa59d9834ed1c4e849146c9e6fddb9b06d625e8b788f09581b5c8713c5a30b1d57ecb9ed9b580204397f323b1e81f91fefd423f9a377f24b83631bb4b7466e13e1c8aa371ff6df4893a293694298abbc88df1f0800986472e2176c7c28e49d11bf280acc2e67d3bdfd4d9b521686db2f5034c72fd7d7ae482f56ee9c07384f27ead72e8909f298f04ef8e90a6ff0b3a724de857dc9830be37622e992ecc207ae476732e6e135938565c1a48d2e92d7a530220498ef9d9d4fda11454605da1ab80a76a9acd0bb6f03fd125eb0b285e3ae7f032dcf7252a5ea4777cb3cf4ce16becf28c4230ce41e21953d0831b909ac7ec36049d5e53cc5dcdf43767cdf49adc4ede4f190b41320892eeb6377e0e8bcbed19a4962f21422b4027105c7371f9c4b1e42dabb0086bd58236c9a2ba9c2098f317d9863a7083a15dbc4969b10c0101d66a7ff7f9d1ea3ba8ae214c761a6f96b34e2c3ee6a87fde4716063a130df07bb906ba05c28761264f35cd09557c3b0952d58b48635b27192c6ca9537835cc002db0e0b75f917b79735803807a2f86116013ddd80f43113ac5916de59ca4b2334da6af753d43bcfd377cd87619b9152d90e540944663583c3c070bcdba85efbee6edb78d187a0aa8bde75f2ca802c05907e5577492fe24a66b0be6341a018c4800608751f1f2fa8bc69202ea91ac0fd6db8acd6b29efcdf94be82f3eec281677abf600c149b777d58b5d03f95dc2ddffa96de7791c83229e0d6cfb4b146a05934e11319a1bfcf8926d7303cd2df8fdc41e508668ffbad0f184693e2eccef5d38e20f5b0baeec2eefa8f0d500bad074fd5faf1a629c5763802ce394f97581d495c4c06adaecf0023c797b49f7de93eaf248b9982b7b1353b74c39d96587a60deb0781d0086fccf8c9e6bf11d23d96f04931cee55f342d55741e278cbacd50cb419dc837d9f2b15402b261afef75b7e4a3e77a79082a39a24cae2803833b3004cd37d20fd00ef3afa7a40a08677f8a020be3040d165f8c1ee5f206b3a2d781c5a03a7ece87a6d4535295a73cebe957ce124cf18fe931b759ff1ea7673d12abdc8d24917f32e20f97cb67e09817450ad72d7b09dd42d934f11a24ad1bd469bc99664d0710eb181b4add12651906b1578f30564b81cc8c246dffb3d623c3e975fd93711018ad07f3831bf0512b508f661d57f6505b9dc3717a18fa2abc2dc3d37d7d2772628584c164a98cfab3aa17cdc079d0632a08cbc57afa10b4440defcf08e0ab66467242e767123a536a662b200b9cc1c51fed49866fb9e6417eb0130bbe81bb0cb270530b18d837e5aa0595cf431b31fab443ce078bd82875159d3b3facbdfca16106a4d040dccaac84ec38db2d3e42ade5ab90e761a83e44b6d6a04b2a8ce6ecd34a979c9b378752b67c62a3b2d9f4f54a2ca356b28df58a0cc7db87fbe382e230c37c4c544386ae7491b9482f36bae09d7294443dcffd5869309143b62d808c3905aa6606bd5b16e5189d57056b8877a70f1ae19454583ddd35db7ff38f9e08950ba842ffcd0c776ddd68e6a49c426b2e5952bd1d6e7b76f59f1acd3b08f361fcd59397c15da9394d5be56e7bfe775b0604d82560da2820bead209af17cf6b8109ae4e0b08eb1a98bea2e46c98c2928e0f7f1ea5231ec16becce269eb50c0a5b20209f640835847bbc9366dd7bb7e5e48cb1fff618dd2b1e6959b6b5f75d2784ee75b67a73b0a215f85988269ffedb8ebec2bf5b81cb24fc7fcf8394cc48c816f2c94916ae8a1cf80842de7941c3464b22947eb94c4e5a052c36e19f40a67845b4b6119candersalm commentedon Nov 10, 2026
rc.2 blocker found in the pre-signing trial (8ce6d25, not signed). In the private Mac trial Home, closing Browser from the Home window fails every time:
POST /api/apps/browser/internet {"action":"end"}returns 409 "Browser launch required", and the window stays open.Cause:
endguard (gateway_browser_internet.rs~669, new in Browser uses this computer's internet only after the owner grants it, as a revocable capability #559) requiresauthority_actor == browser./api/apps/home/launch, which issues projection tokens:authority_actoris Home,executable_actoris the app.app_token_for_authority), so they never took the real launch path.Fix in progress on
fix/rc2-browser-end-launchfrom 8ce6d25:endaccepts the Browser frame's own launch, projection or direct, and still refuses System, Home and other apps.home_launchpath.Then the full Linux check, a Grok security review, Root's review, the Mac gate, a new qualification and prepare, and the trial again. The unsigned 8ce6d25 preparation is superseded and will be removed before the next prepare.
andersalm commentedon Nov 10, 2026
rc.2 candidate 975b252: develop CI 42829303178 green. Package run 42829315495 attempt 1 failed only in
x86_64-linux N and N+1, stepinstall host prerequisites, which hit its 15-minute limit while apt downloaded slowly from the Ubuntu mirror (single 4 MB packages took about 30 s); Apple silicon, aarch64-linux and the engine jobs passed. Infrastructure, not the candidate: reran the failed job once (attempt 2). Qualification resumes on the same recorded run.andersalm commentedon Nov 10, 2026
Correction to my last comment: rerunning only the failed package job cannot work, because release-package.yml names every artifact with
github.run_attempt; attempt 2 failed at once looking forrelease-llama-amd64-975b2524d…-2. Started a full rerun of all jobs (attempt 3) of package run 42829315495 on the same source; qualification resumes on it. Lesson recorded.andersalm commentedon Nov 10, 2026
Private Mac trial passed on macOS 26.6.2 ARM64 (
aarch64-darwin), exact unsigned2.0.1-rc.2from975b2524d8249721cdd87f4ed038b7c61668b3f2, package run 42829315495 attempt 3. Runtime SHA-2561b578051f43e472f1271d6a4cfc693fc79681e158b13cefc2e3630be343aad31. Components manifest SHA-256e75f2792a47e9b7e8eb5bbdbdbd5f61101ba0dd97dc74758e74d709a57d48f6d. Browser image archive SHA-2566894608add893a9b5791da9cd141ab9ce756f3d6d16e710c114373384e4bcb66.All 72 package hashes and 4,174 payload files per Home passed before and after, with zero new Python caches. Verified image bytes were APFS-cloned. Version, health, Browser readiness, Community gossip join and one-Profile readiness passed. Fresh virtual-passkey Inbox approval returned 200. From Home with consent active, Browser loaded Example Domain, Runtime Close returned 200 with closed=true and all 13 cleanup effects true at 4662 ms, End returned 200 {"status":"ended"} at 4674 ms, and the window was removed at 4881 ms. A second Browser loaded Example Domain under the same consent digest, with zero new consent or passkey requests, and also closed successfully. Behavior passed 2235/2235. Source gate passed with two Linux-only pidfd cases skipped. Both premortems passed after correcting the initial working directory. Local staging omissions and the harness's missing after-approval button click were fixed and recorded in lessons 1531–1534. The model-catalog presence guard failed before the staging fix and passed after it. Trial 8096 is running with no account, harness 8098 is stopped. Full receipts are local in rc2-trial/final-evidence.json, the note is ~/omp-inbox/rc2-mac-test-home.md.
Coverage awaits signing for the install command, update from 2.0.0, Undo and one-time Browser setup. This was local only, with no push or CI.
All 72 verified package input SHA-256 values
4328697c968e614dd45715bfe893747ae4bf3f338d576b8c3f325d09cefb57a5e1c5bb2d8d5dd416c5b3b4b276826a8b421cf4af04131c1a3e5c951b60b81fdaaa76e795d85520d0f0532068a078ddbbfb0cefc51fd6e6c8745290943b2d4304c92e71843d1e307587b66a7c20c5253be05236cd4faed4d5b1d82cfe07ca1eae969517090c23995496f39a3c346734c0bfb7d51afa900fcbeddf481167b8f6cc6445c6e79c65df3a37f7e7ac57f16e2caf2aaaf5bdd385b37484136682da01aa580b1fe074af3a7b72f1cef95fd71b95c775602a8c4938069ff694283d2cce6c2dd00cb4e9ed21082ea607f04672093894ac952e8435067bf24df041c8315c23c5bbbc0e0cfe4da2114999eaaed22f68485152acb712fab43e5ef16adc41ecbb24f16e504c9bfce81665e5b93684e3195e7473ed49f04ba1f13613de3133bb1ac5bbbc0e0cfe4da2114999eaaed22f68485152acb712fab43e5ef16adc41ecbb5451bfa7566136cb3473549dc702e5c61153afee7be4ede7d93da3546af9690a6894608add893a9b5791da9cd141ab9ce756f3d6d16e710c114373384e4bcb661901313788901843e80944ae38b56a49865973ee51202881d390e9a803ddfb468b48641cbcedbbf9ebfe4e21c5cc202f2b45eaebea95884c9a0cada4257f1c47beaa60bba735c569aa58cfe50655824232da6bd6a9d28fd50ae15139b39ee4f95b2a06789f0f37282ec87b7c2b88ac6a29bdaa2d5d500ac2a376914c647460c56743912b1550d52452218f051b55538186f67829ce6d42284f52a10dce6d29385b90fcf804aa79636d020a50d032e63ec1260f204f5b2ec3c8ddfc015efff706e75f2792a47e9b7e8eb5bbdbdbd5f61101ba0dd97dc74758e74d709a57d48f6dcd50f0153fd591333f61607bf7840127b4b1ea7124eed22101360a756ad739b97eb96b88db27e035446201a2e9dea06bb9f82f8a2160457e7c466abb127529b656acbc96c456e8aae08994936e5a2eb33bcf0c5b779cd6017478176a6455b594e501fbc3504ca5a5870a9ce06b848dc95f0b1f5efd9f4d95a6332ede0f4f8a0384359c31fb6ddf2a195ff649393c01814f1e1662e3bc42d79123a56d706184f67146502fecb1bf3a7941ffa88819b64da6af37be5da7273dae0525dba248f3cb5bbe65206a2721050af9231269e65a046e85bc05bd001da576da51b6b74307f044e8755cd1ea5422ea203886497bb7367a0ff32030d31258b5906de8aa3885231b578051f43e472f1271d6a4cfc693fc79681e158b13cefc2e3630be343aad314a207d86cb75f7e455a0aede6c7782410fb495683960057094001c2c941c1de1b41d1a45aaa528d01bc915cbde2c5b8bdf26b184860cb38049b9f6de9a0c407d2f7536be0735ab008f667725237bed0962217a5f73b0bca98a82fa59d9834ed1c4e849146c9e6fddb9b06d625e8b788f09581b5c8713c5a30b1d57ecb9ed9b580204397f323b1e81f91fefd423f9a377f24b83631bb4b7466e13e1c8aa371ff6df4893a293694298abbc88df1f0800986472e2176c7c28e49d11bf280acc2e67d3bdfd4d9b521686db2f5034c72fd7d7ae482f56ee9c07384f27ead72e8909f298f04ef8e90a6ff0b3a724de857dc9830be37622e992ecc207ae476732e6e135938565c1a48d2e92d7a530220498ef9d9d4fda11454605da1ab80a76a9acd0bb6f03fd125eb0b285e3ae7f032dcf7252a5ea4777cb3cf4ce16becf28c4230ce41e21953d0831b909ac7ec36049d5e53cc5dcdf43767cdf49adc4ede4f190b41320892eeb6377e0e8bcbed19a4962f21422b4027105c7371f9c4b1e42dabb0086bd58236c9a2ba9c2098f317d9863a7083a15dbc4969b10c0101d66a7ff7f9d1ea3ba8ae214c761a6f96b34e2c3ee6a87fde4716063a130df07bb906ba05c28761264f35cd09557c3b0952d58b48635b27192c6ca9537835cc002db0e0b75f917b79735803807a2f86116013ddd80f43113ac5916de59ca4b2334da6af753d43bcfd377cd87619b9152d90e540944663583c3c070bcdba85efbee6edb78d187a0aa8bde75f2ca802c05907e5577492fe24a66b0be6341a018c4800608751f1f2fa8bc69202ea91ac0fd6db8acd6b29efcdf94be82f3eec281677abf600c149b777d58b5d03f95dc2ddffa96de7791c83229e0d6cfb4b146a05934e11319a1bfcf8926d7303cd2df8fdc41e508668ffbad0f184693e2eccef5d38e20f5b0baeec2eefa8f0d500bad074fd5faf1a629c5763802ce394f97581d495c4c06adaecf0023c797b49f7de93eaf248b9982b7b1353b74c39d96587a60deb0781d0086fccf8c9e6bf11d23d96f04931cee55f342d55741e278cbacd50cb419dc837d9f2b15402b261afef75b7e4a3e77a79082a39a24cae2803833b3004cd37d20fd00ef3afa7a40a08677f8a020be3040d165f8c1ee5f206b3a2d781c5a03a7ece87a6d45c28a1787a6c49d8c32170b7eb5453fb1a55c76bc9a3b0c1950216bd3fb4afe9e7cb67e09817450ad72d7b09dd42d934f11a24ad1bd469bc99664d0710eb181b4add12651906b1578f30564b81cc8c246dffb3d623c3e975fd93711018ad07f3831bf0512b508f661d57f6505b9dc3717a18fa2abc2dc3d37d7d2772628584c164a98cfab3aa17cdc079d0632a08cbc57afa10b4440defcf08e0ab66467242e767123a536a662b200b9cc1c51fed49866fb9e6417eb0130bbe81bb0cb270530b18d837e5aa0595cf431b31fab443ce078bd82875159d3b3facbdfca16106a4d040dccaac84ec38db2d3e42ade5ab90e761a83e44b6d6a04b2a8ce6ecd34a979c976dfe20b7baa75aa6eef56fe51a5860d2f4e3e1fadeece8a51d7e9e5127d2ee744386ae7491b9482f36bae09d7294443dcffd5869309143b62d808c3905aa6606bd5b16e5189d57056b8877a70f1ae19454583ddd35db7ff38f9e08950ba842ffcd0c776ddd68e6a49c426b2e5952bd1d6e7b76f59f1acd3b08f361fcd59397c15da9394d5be56e7bfe775b0604d82560da2820bead209af17cf6b8109ae4e0b08eb1a98bea2e46c98c2928e0f7f1ea5231ec16becce269eb50c0a5b20209f640835847bbc9366dd7bb7e5e48cb1fff618dd2b1e6959b6b5f75d2784ee75b67a73b0a215f85988269ffedb8ebec2bf5b81cb24fc7fcf8394cc48c816f2c94916ae8a1cf80842de7941c3464b22947eb94c4e5a052c36e19f40a67845b4b6119candersalm commentedon Nov 10, 2026
Anders, after trying 975b252 in the private Mac trial (10 Nov): not signed. The Browser internet permission works but its screens are too rough to ship. Redo rc.2 with the fix (the name stays 2.0.1-rc.2 because nothing was signed or published). Problems are listed on #559 (comment 6776426102), plus two more:
gateway_browser_stream.rs1077 and 1150), but the text says 'this computer's internet connection', which is wrong when a remote Exit is chosen.Next: a clickable mock for Anders (
~/omp-inbox/browser-internet/mock/index.html); after his yes, the build, review, full check, gate, packaging and trial. Separately:sign-release.shfalsely refused rc.2 ('no CHANGELOG [2.0.1] section') because of a SIGPIPE under pipefail in Main's own check; fixed and proven (lesson 1535). The 975b252 preparation is superseded and is removed before the next prepare.andersalm commentedon Nov 11, 2026
Decision (Anders, 11 Nov): publish Stable 2.0.1 from the signed rc.2 source, without an rc.3. Accepted known issues: #566 (a) to (d), the hickory-proto advisories (#569), and Browser on the Jetson untested on the final build (#90).
andersalm commentedon Nov 11, 2026
2.0.1 is live (17:16 UTC) with its release page; the result and checks are in the description. Closing.