Install the Mac battery mirror through VM integrations

[NimbleAINinja]

What changed and why

Existing VMs keep their disk across app updates, so after #220 they get the battery port but not the guest module and bridge. The only way to add them has been to stage eight repo files through the shared folder and run install-battery-into-existing-guest.sh by hand. The VM integrations manager from #193 already delivers reviewed guest features to existing VMs, so this delivers the battery through it. VM integrations → Review… now installs the Mac battery mirror along with sudo Touch ID support.

• Bundle: adds the retrofit script, the three DKMS sources and the five bridge/udev/module-load/UPower files. The updater runs the script with --source pointing at the staged, verified bundle.
• Already installed: the managed files include the DKMS sources at the factory package's path (/usr/src/try-omarchy-battery-1.0.0/), so a guest built with the battery reports current. When the files are current and dkms status shows the module built for the running kernel, installation records the component without rerunning the script, leaving the package-owned files untouched.
• Can't build here: the module needs DKMS and headers for the running kernel. Images before v0.3.0 have neither, and after a kernel update the headers match the new kernel until a restart. In those cases the battery reports disabled instead of repair, the review names the reason, and installation skips it without failing Touch ID.
• Mac side: GuestIntegrationReport rejected any report naming a component outside its allowed list, and treated anything beyond bootstrap/sudo as "use matching app". It now accepts battery as a supported component, so a guest with the earlier sudo-only bundle is offered the update and a guest with the battery reports up to date.
• Docs: docs/host-battery.md now points to VM integrations for retrofitting, keeping the shared-folder route as a fallback; docs/integration-updates.md and the README list the battery.

Testing

• make test: passed. New Python tests cover: the bundle carrying every file the installer stages; the version and path matching the factory DKMS package; disabled versus repair status; each unavailable reason; the installer running from the staged bundle; skipping an unbuildable battery; and keeping an installed one without rerunning the script. New Swift tests cover decoding and summarising reports that include battery, and offering the update to a sudo-only guest.
• git diff --check: clean.
• Built the full app with make build from this commit (fresh guest image; the guest build needed a local-only package-lock refresh because Arch Linux ARM has moved past several pins on main, which is not part of this PR).
• Manual, on an M1 Max MacBook Pro, with an existing VM created before VM integrations whose battery had been installed by hand with the retrofit script:
  • The launcher's Review VM integrations offered the setup command. Running it in an Omarchy terminal opened the review, which listed Touch ID support and the Mac battery as installed.
  • Install/update integration support completed with "Integrations installed and checked.", and the battery meter stayed in the bar. A second run reported sudo: already verified; retained. and battery: already verified; retained.
  • The launcher's VM integrations status then showed "Last check: Up to date. Checked again after each VM launch."
• Not checked on a real VM: a first battery install on a VM without it, the disabled path (image before v0.3.0, or a kernel update without a restart), and a fresh image reporting up to date without setup. These are covered by the unit tests above.
• The updated dialog wording ("…sudo Touch ID support and the Mac battery mirror…") compiles and passes the tests, but the build tested above had the previous wording.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HTMdXGJ5j4UcAVdNtQLW4y