Skip to content

Vitrallis Shell 1.0.1 — certification prerelease

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Oct 07:19

Certification prerelease of Vitrallis Shell 1.0.1 for PocketCHIP on Debian 12 or 13. Public installer and update fault certification is continuing; stable release readiness has not been declared.

This release preserves the distinct previous generation when reinstalling the active bundle, correcting the lost restore choice in 1.0.0. Applications remain in Documents/Vitrallis/Apps and persistent data in Documents/Vitrallis/AppData.

Source: b2ff6d48be33b0a70c373d56d1a8c2f354501db2, tagged v1.0.1. The tagged workflow passes canonical validation, x86-64 and ARMv7 builds, native utility packaging and legal notice checks. Build evidence.

Exact tagged installation and repeat installation pass on the physical PocketCHIP, retaining 1.0.0 as the distinct previous generation. All 93 tracked saved data/config/app/integration entries and eight saved settings remain unchanged. All five executables pass version/hash/ownership/mode checks. Shell graphics self-test and all three native utility hardware smokes pass on Mali400 with VSync and no fallback. A software reboot reaches the focused 480×272 launcher with no PocketHome or service-owned zombies across three observations. Clean public installation and official update/interruption checks follow publication. Physical keyboard and touch acceptance applies to the repaired startup integration; the final candidate still requires its final physical smoke test.

Requires glibc 2.36+ and SDL2 2.26.5+. See the repository certification ledger for remaining tests and hardware qualifications.

ARMv7 bundle SHA-256: 1ee6c8e5e4cd7184a27ce8668f252ab40ac8a339f30ba9e96e55f746910dc0e6

x86-64 bundle SHA-256: 3f4a8c74c40e61d998cf832ead89a3c2794f53d96e1d0f32d45aa4221134a804

Known rendering limitation: strict software/hardware equality fails on 73 Terminal, 41 Notepad and 90 Files pixels at 480×272, with a maximum one-colour-level difference. Hardware and automatic readbacks match exactly; repository assertions are unchanged.

Later certification found a process-lifecycle defect: Restore/relaunch can leave a background system query as a persistent zombie. Cancelling setup can also print a Python traceback. Corrections in PR #8 pass prepared-build host/device tests but are not part of published 1.0.1. The published assets remain unchanged; a fresh authorized release and final certification are required.