Build log
ChaseOS Studio V1.0.7: requiring rendered evidence before release
How V1.0.7 changed packaged QA from a screenshot exercise into a rendered-page gate and proved the signed clean-install and updater path.
Source: Public ChaseOS V1.0.7 changelog, signed release manifest, Windows Sandbox report and updater evidence
- Signed build accepted
- Public release
- Build identity
20260823-043952-18975c27
Technical bibliography record
The build, in five parts.
- 01 Built
- A signed Studio release whose nine native pages, clean install, updater notification and uninstall path were accepted as one bounded release contract.
- 02 Process
- Packaged QA waited for route-specific ready states, rejected repeated captures, and then ran a 26-check clean Windows Sandbox lifecycle.
- 03 Learned
- A screenshot is not page evidence until the requested route has rendered, and source work begun after publication belongs to the next signed release.
- 04 Skills
- packaged visual QAWindows Sandboxupdater acceptancerelease manifestsapproval-bound UX
- 05 Saved
- Distinct page captures, Sandbox results, immutable installer identity, updater evidence and the exact boundary between V1.0.7 and later repairs.
The release gap#
Earlier packaged checks could capture the shell before the requested Studio page had finished rendering, producing repeated or incomplete images that looked like separate evidence. V1.0.7 made the requested route, page-ready state and distinct capture part of the acceptance contract.
Rendered-page acceptance#
The release lane waited for all nine native panels to render and rejected repeated or incomplete captures. Passive UI acceptance also stopped runtime probes from starting Hermes or OpenClaw while the package itself was under inspection.
Cloud, Chat and approvals#
Cloud state was reconciled across Chat, Terminal, Connect and runtime setup, and disabling Cloud restored the saved pre-Cloud harness configuration. Chat gained safe rich links and media presentation, while file and terminal proposals remained exact and approval-bound with readable expiry, session-grant and receipt states.
Signed Windows proof#
A clean Windows Sandbox run covered signed installation, native first launch, exact installed hashes, signed uninstall and preservation of the user's workspace. The accepted public manifest then exposed V1.0.7 to an existing V1.0.6 installation through the in-app update notification and Update now action.
What shipped later#
Persistent notification ages, duplicate suppression, the Pulse decision desk, restored workspace manager and proposed graph destinations were post-release source work. They are intentionally recorded under V1.0.8 instead of being backfilled into this release.