Aurora source enhancements
The separate .20-enh1 source lane has build and later hardware receipts; its old “staged but unbooted” description is historical. Check each exact build’s receipt rather than transferring acceptance between .20, enh1 and wip2. No paired energy saving is established.
Per-build hardware receipts and gates · Source and build scopeAurora .20 hardware freeze
Experimental .20 packages and their scoped boot/PMP/idle/GPU/filesystem receipts remain available. .20 is the last documented persistent boot default, while the October 21 attended boot used wip2. Actual return-to-.20 recovery, full suspend and paired energy testing remain open.
Frozen package, source and checksums · Tested scopes and release gatesAurora unified 7.2 trials
October 21 wip2 booted on J314S; all three USB-C ports produced WD22TB4 picture at 1080p/60 in that scoped trial. On October 22, one wip3 dock plug on dcpext1 produced no picture; same-port replug did not recover it, while another port restored 1080p/60. This is one observation, not sustained or all-port wip3 qualification. Current wip4 candidate PR #533 passed ARM64 candidate, unified72 and eGPU build/payload checks in run 39860520050, and M-series validation in run 39860519355. This is source/build evidence only: DCP KUnit, attended J314S boot, dock recovery/repeatability, suspend, long-run stability and paired power qualification remain open. No wip4 package was installed or armed; the persistent boot selection was not changed. Wip3 identity and qualification limits.
First-boot receipt · All-port follow-up · Source and remaining gatesAurora unified 7.2 trials
October 21 wip2 booted on J314S; all three USB-C ports produced WD22TB4 picture at 1080p/60 in that scoped trial. On October 22, one wip3 dock plug on dcpext1 produced no picture; same-port replug did not recover it, while another port restored 1080p/60. This is one observation, not sustained or all-port wip3 qualification. As of October 23, wip4 candidate PR #533 is at head 266d54af; ARM64 candidate, unified72 and eGPU build/payload checks passed in run 39944207967, and M-series validation passed in run 39944207727. The PR remains open and conflicts with current dev, so it needs a refresh before merge. This is source/build evidence only: DCP KUnit, attended J314S boot, dock recovery/repeatability, suspend, long-run stability and paired power qualification remain open. No wip4 package was installed or armed; the persistent boot selection was not changed. Wip3 identity and qualification limits.
Enhanced kernel test build
Historical Fairydust packaging work is retained separately from the current Aurora trial. A local monitor link is useful only if its service is running on your own Mac; this public page cannot tell whether that local build is active.
Local kernel monitor ↗ · Historical build recordsLocal Mac build
Native assembly finished in 16m 39s and its checksum passed. Inspection found missing live-session hardware helpers; the corrected GitHub image now passes its hardware-helper payload check. The corrected ISO also passed its independent checksum and graphical VM boot check. This public page does not poll your Mac.
Live local monitor · on this Mac ↗ · Build records and controlsRust compositor performance
The Rust compositor has since been used on the transformed desktop. Recent source and staged-package fixes have their own installed-versus-loaded boundaries. Retained October 19 performance samples remain unmatched, so they establish no CPU, power or latency advantage over Gala; Gala remains a rollback option.
Measurements, dates and limits · Current deployment recordsElementaryOS M-Series
Experimental port of elementary OS 9 (Pantheon, Ubuntu-based) to Apple Silicon Macs (M1/M2/…), informed by the maintained Apple hardware packages in omacom/omarchy-mac-pkgs.
- +Local AI on M1 Pro 32 GB: measured model comparisons, personal memory and MCP app coverage.
diff --git a/mseries/OS9-HANDOFF.md b/mseries/OS9-HANDOFF.md index 7a3cf0d53..cff922772 100644 --- a/mseries/OS9-HANDOFF.md +++ b/mseries/OS9-HANDOFF.md @@ -11837,3 +11837,21 @@ bound to the manifest hash; per-action approvals for external and privileged int shows; remembered denials, immediate revocation, content-free audit, owner-only grants file. 14 tests against the real T3 manifest, clippy clean. Library only: no service, consent dialog, Settings page or app-side dispatcher; the caller's identity is not yet taken from a connection. See `SDK-AGENT-SURFACE.md` section 8. Nothing installed. + +## GitHub Pages wip4 candidate status refresh — 2026-10-23 + +Updated `docs/index.html` and `docs/build-status.html` to link the current PR #533 head +`266d54af49ca6dede2492f11b4fe830cafa7228a` and its successful ARM64 candidate, +unified72 and eGPU build/payload run `39944207967`, plus M-series validation run +`39944207727`. Both runs use that exact head. PR #533 remains open and conflicts +with current `dev`; it must be refreshed before merge. Wip4 remains source/build +evidence only: no package was installed or armed, and hardware/recovery/suspend +acceptance is still open. + +The current `dev` Pages deployment `39954620306` succeeded for exact source +`7053069f7502cbdd2390a5ece09d825c1c1b9dd6`. Live `index.html`, +`build-status.html` and `build-status.js` returned HTTP 200 and each byte-matched +that revision. This PR updates the candidate links/status; it is not published +until merge and a new successful Pages deployment. No host, boot, panel, kernel, +audio or power state changed. Next: merge after required review/current-head +checks, then verify Pages deployment and live bytes for the merged revision. diff --git a/mseries/ROADMAP.md b/mseries/ROADMAP.md index 92e70249b..fd6894a49 100644 --- a/mseries/ROADMAP.md +++ b/mseries/ROADMAP.md @@ -4374,3 +4374,12 @@ See `upstream-audits/housekeeping/2026-10-21-machine-lab-qmp-teardown.md`. ### SDK dock anchoring — 2026-10-23 Pantheon panel protocol adapter implemented in msdk-gtk; dock builds with bottom anchor, size and hide mode. Next: live placement review and pin editing. + +### GitHub Pages current wip4 candidate status — 2026-10-23 + +The public home and build monitor now point to PR #533 head +`266d54af49ca6dede2492f11b4fe830cafa7228a` and successful same-head build/payload +run `39944207967` and validation run `39944207727`. PR #533 is still open and +conflicts with `dev`; refresh/review remains required. Wip4 hardware acceptance +remains open. The current live site byte-matches `dev` `7053069f` from Pages run +`39954620306`; this correction is prepared in a PR and awaits publication.