[chriskearney]

Scope: This draft is for existing experimental mesa-m3 installations. Standard Omarchy images use mesa-aurora/vulkan-aurora directly; this login-hook migration is outside the broader RC requirements.

Older installations retaining the mesa-m3 session hook can keep selecting the legacy driver or software rendering even when compatible native system Mesa is installed. This draft attempts the existing strict system-provider admission automatically on J613/J615 T8122 and J516S T6030, with matching mesa-aurora/vulkan-aurora versions at or above 1:26.3.0_devel.20261025.231095.7c86130d26c-1 and package ownership of the resolved native providers. J615 is added to both the shell and C helper identity checks.

This is stacked on #213; its parser fix remains byte-identical. Retarget to integration/aurora after #213 lands. The existing manual disable-file route remains available. Explicit user software/provider choices, an experimental profile, mesa_m3=off and nomodeset retain priority. Node/display/current-boot journal, previous-attempt, strict provider and bounded helper checks remain in place. Success selects ordinary /usr Mesa without requiring a user-created flag file and clears only this hook’s own software-fallback pair. The proposed recipe increments pkgrel to 9 and refreshes source checksums.

Validation: 253 session checks under each of sh and Bash, 22 provider tests, 51 legacy detector checks and 22 C board-parser controls pass. Exact #1591 CI package layout and resolved provider ownership were additionally checked using real pacman queries against a synthetic package database, with 13 admission/explicit-choice/negative controls. These fixtures do not load ARM GPU libraries or exercise a physical login.

Keep this draft until a native package build and exact-package ordinary-login/rendering checks qualify the claimed routes, particularly J615. The helper’s successful context admission alone does not prove rendering or presentation, and this does not add native failed-login tracking. Matching boot handoff and enabled kernel backends are separate prerequisites; #230 prepares the kernel source slice. Unknown models/firmware are not newly admitted by this change. No device qualification or release-ready claim is made.

[chriskearney]

This draft targets existing experimental mesa-m3 installations. The standard image installs mesa-aurora/vulkan-aurora directly, so this login-hook migration is not required for RC. Closing this draft to keep the release work scoped to the normal packages.