Two readiness gaps surfaced after the end-to-end install verification on
ohm 2026-05-08:
(1) The "Building" section was a one-liner ("makepkg -s ... pacman -U
... reboot") with no actual install commands. Replaced with proper
Building / Installing / Verifying / Rolling back sections, using
the exact commands that worked end-to-end on ohm:
- sudo pacman -U <pkg.tar.zst>
- The new conflicts/provides metadata means no --overwrite needed
- PineTab2 U-Boot script update via /boot/boot.txt + mkscr
- Off-device backup (boot.scr.pre-besser) for trivial rollback
- Post-reboot checks: uname -r, lsmod, /sys/module/bes2600/srcversion
(2) The "What's in the patchset" table listed Patch G / Patch B / etc.
without linking to the actual commits. Added a preamble pointer to
the cleanups branch on marfrit/bes2600-dkms gitea, which is the
source-of-truth for individual commits + Phase-7 verification logs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>