From e45c5df794a405050b686e06f3d887e3d99f7f5c Mon Sep 17 00:00:00 2001 From: Codex Date: Wed, 28 Oct 2026 05:40:31 -0400 Subject: [PATCH] docs: refresh dock candidate and Pages status --- docs/build-status.html | 2 +- docs/index.html | 2 +- mseries/OS9-HANDOFF.md | 48 +++++++++++++++++++++++++++++++++++++++++ mseries/ROADMAP.md | 49 ++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 99 insertions(+), 2 deletions(-) diff --git a/docs/build-status.html b/docs/build-status.html index 61e610be0..b2676f70a 100644 --- a/docs/build-status.html +++ b/docs/build-status.html @@ -18,7 +18,7 @@

OS 9 build monitor

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 scope
Separate qualification lanes

Aurora .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 gates
Experimental fallback
-

Aurora 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.

First-boot receipt · All-port follow-up · Source and remaining gates
Wip4 build checks pass · hardware gates open
+

Aurora 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. The retained October 20–27 wip3 observations show DPTX timeouts when first plugging within about four seconds of resume; changing ports restored picture in one observed case. This suggests, but does not prove, a post-resume DCP state issue. A separate user-space monitor-profile watcher restored the saved layout in two observed same-port cycles; automatic restore was confirmed only on the later cycle after a fallback association fix. This does not qualify kernel recovery. Open wip4 revision-6 proposals #533 at f68fd1d9 and #619 at 1dfb6ecc have different patch lists; an owner decision is needed before either merges. At this audit, #619 head 1dfb6ecc had diverged from current dev 57b143c: eight commits behind and four ahead. On #619 head 1dfb6ecc, both ARM64 candidate and unified72 build/payload-inspection jobs passed in run 40605242087; see the immutable receipt. DCP KUnit, wip4 installation/arming, attended J314S boot, repeatable dock recovery, suspend, long-run stability and paired-power qualification remain open. Aurora .20 remains the documented persistent boot default. Wip3 identity and qualification limits.

First-boot receipt · All-port follow-up · Source and remaining gates
Rev-6 candidate conflict · wip4 unbooted

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 records
Local state unknown

Local 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 controls
Rebuild needed

Rust 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 records
Experimental · no measured win
diff --git a/docs/index.html b/docs/index.html index c0c3d67de..90cd52ce4 100644 --- a/docs/index.html +++ b/docs/index.html @@ -19,7 +19,7 @@

ElementaryOS 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 9b43cdbc3..9814bc17d 100644 --- a/mseries/OS9-HANDOFF.md +++ b/mseries/OS9-HANDOFF.md @@ -1,6 +1,54 @@ ## T3 Dock launcher and Wingpanel — 2026-10-27 The owner chose to retain the unified Wingpanel menu. The Dock launcher opens the T3 window and its taskbar status area does not add a second T3 menu. The Dock source-preparation guard checks these boundaries; the Wingpanel module is not retired. Source preparation is verified against the pinned upstream Dock, with live desktop acceptance still outstanding. +## WD22TB4 and wip4 candidate status — 2026-10-28 + +Current `dev` is `57b143c4afd78b0a4a0f9905e48e39632d1ecc3c`. Pages deployment +`40628638433` succeeded for that exact revision. The live homepage and build +monitor still showed the October 23 #533 candidate paragraph; a focused status +correction is prepared in this docs change and is not published until it merges +and a Pages deployment succeeds for the resulting `dev` revision. + +The attended October 21 wip2 trial confirmed WD22TB4 picture at 1080p/60 on all +three USB-C ports. Retained wip3 observations from October 20–27 show three DPTX +failures when the dock was first plugged within about four seconds of resume; +there were no matching failures on .20, wip2, or a wip3 boot with the dock +connected at boot. Moving to another port restored picture in one observed +incident. This pattern is consistent with, not proof of, a post-resume DCP state +problem. A separate user-space monitor-profile watcher restored the saved layout +on two observed same-port cycles; automatic restore was confirmed only on +the later cycle after a fallback association fix. This does not establish kernel +recovery or wip4 acceptance. + +Two wip4 revision-6 proposals remain open: #533 at head +`f68fd1d9833d4895607df1951726b163542c71f0` and draft #619 at head +`1dfb6ecc43400b2051bdd7c81c3408defd45e305`. Their patch lists differ, and the +#619 conversation records that the intended revision must be resolved before +either merges. PR #619 is based on older `dev` `44644d852cf70d12068ebbbba73726ffbf9a0338`; +against current `dev` `57b143c4afd78b0a4a0f9905e48e39632d1ecc3c`, its head is +eight commits behind and four ahead. Do not choose or refresh one candidate until +the owner settles the overlap. + +On exact #619 head `1dfb6ecc`, Aurora candidate run +[40605242087](https://github.com/techmore/ElementaryOS_MSeries/actions/runs/40605242087) +passed both ARM64 candidate and unified72 profile jobs: pinned-source preparation, +selected production-kernel logic checks, kernel/modules/DTB builds, payload-only +Debian package builds, and package-boundary checks. Actions uploaded +`elementary-aurora-enhancements-candidate-40605242087` (artifact 12782705133, +SHA-256 `6601d97a59fb070fc6a2b0aa4bf74711b49216ddecf151fc068b0150d69f9a94`) and +`elementary-aurora-enhancements-unified72-40605242087` (artifact 12782670058, +SHA-256 `31ffc75baec619e3e466751d890b8d483df78901a934530117e424c7a8be20c8`). +The workflow did not run DCP KUnit, and no independent post-upload artifact audit +is recorded. No wip4 package was installed or armed, and no wip4 hardware boot, +dock recovery, suspend, long-run stability, or paired-power qualification was +performed. The .20 kernel remains the documented persistent boot default; factory +image boot remains unverified. + +Next: obtain the owner’s choice between #533 and #619, then review the chosen +current-head patch interactions and required KUnit/build evidence before any +owner-authorized attended hardware trial. Reuse the existing dock/VRR results; +do not repeat the completed trials. After the docs change merges, verify the new +Pages run and live status separately. ## T3 panel menu HIG audit — 2026-10-27 diff --git a/mseries/ROADMAP.md b/mseries/ROADMAP.md index 95e325900..bffda679e 100644 --- a/mseries/ROADMAP.md +++ b/mseries/ROADMAP.md @@ -1,3 +1,52 @@ +## WD22TB4 and wip4 candidate status — 2026-10-28 + +Current `dev` is `57b143c4afd78b0a4a0f9905e48e39632d1ecc3c`. Pages deployment +`40628638433` succeeded for that exact revision. The live homepage and build +monitor still showed the October 23 #533 candidate paragraph; a focused status +correction is prepared in this docs change and is not published until it merges +and a Pages deployment succeeds for the resulting `dev` revision. + +The attended October 21 wip2 trial confirmed WD22TB4 picture at 1080p/60 on all +three USB-C ports. Retained wip3 observations from October 20–27 show three DPTX +failures when the dock was first plugged within about four seconds of resume; +there were no matching failures on .20, wip2, or a wip3 boot with the dock +connected at boot. Moving to another port restored picture in one observed +incident. This pattern is consistent with, not proof of, a post-resume DCP state +problem. A separate user-space monitor-profile watcher restored the saved layout +on two observed same-port cycles; automatic restore was confirmed only on +the later cycle after a fallback association fix. This does not establish kernel +recovery or wip4 acceptance. + +Two wip4 revision-6 proposals remain open: #533 at head +`f68fd1d9833d4895607df1951726b163542c71f0` and draft #619 at head +`1dfb6ecc43400b2051bdd7c81c3408defd45e305`. Their patch lists differ, and the +#619 conversation records that the intended revision must be resolved before +either merges. PR #619 is based on older `dev` `44644d852cf70d12068ebbbba73726ffbf9a0338`; +against current `dev` `57b143c4afd78b0a4a0f9905e48e39632d1ecc3c`, its head is +eight commits behind and four ahead. Do not choose or refresh one candidate until +the owner settles the overlap. + +On exact #619 head `1dfb6ecc`, Aurora candidate run +[40605242087](https://github.com/techmore/ElementaryOS_MSeries/actions/runs/40605242087) +passed both ARM64 candidate and unified72 profile jobs: pinned-source preparation, +selected production-kernel logic checks, kernel/modules/DTB builds, payload-only +Debian package builds, and package-boundary checks. Actions uploaded +`elementary-aurora-enhancements-candidate-40605242087` (artifact 12782705133, +SHA-256 `6601d97a59fb070fc6a2b0aa4bf74711b49216ddecf151fc068b0150d69f9a94`) and +`elementary-aurora-enhancements-unified72-40605242087` (artifact 12782670058, +SHA-256 `31ffc75baec619e3e466751d890b8d483df78901a934530117e424c7a8be20c8`). +The workflow did not run DCP KUnit, and no independent post-upload artifact audit +is recorded. No wip4 package was installed or armed, and no wip4 hardware boot, +dock recovery, suspend, long-run stability, or paired-power qualification was +performed. The .20 kernel remains the documented persistent boot default; factory +image boot remains unverified. + +Next: obtain the owner’s choice between #533 and #619, then review the chosen +current-head patch interactions and required KUnit/build evidence before any +owner-authorized attended hardware trial. Reuse the existing dock/VRR results; +do not repeat the completed trials. After the docs change merges, verify the new +Pages run and live status separately. + ## Public messaging status — 2026-10-27 The public homepage and support matrix now distinguish the scoped October 20 BlueFerry texting observation from the owner’s October 22 decision that the Messages and Signal experience is incomplete and deferred. See [MESSAGING-STATUS.md](MESSAGING-STATUS.md). This documentation update does not change or qualify the apps, phone pairing or hardware.