feat(bluetooth): retire blueman, assert the swap in VM tests

I dropped blueman from the desktop_environment bluetooth loop (bluez + bluez-utils stay) and added the VM assertions: bluetooth stack installed, blueman absent as the retirement regression guard. No new sudoers rule was needed for bt-priv, since the existing blanket grant already covers systemctl restart bluetooth.

1 files changed, 16 insertions, 0 deletions

diff --git a/scripts/testing/tests/test_packages.py b/scripts/testing/tests/test_packages.py
index f237088..f0d8ff2 100644
--- a/scripts/testing/tests/test_packages.py
+++ b/scripts/testing/tests/test_packages.py
@@ -58,3 +58,19 @@ def test_git_installed(host):
 @pytest.mark.parametrize("tool", DEV_TOOLS)
 def test_dev_tool_present(host, tool):
     assert host.exists(tool), "dev tool %s missing from PATH" % tool
+
+
+BLUETOOTH_STACK = ["bluez", "bluez-utils"]
+
+
+@pytest.mark.attribution("archsetup")
+@pytest.mark.parametrize("pkg", BLUETOOTH_STACK)
+def test_bluetooth_stack_installed(host, pkg):
+    assert host.package(pkg).is_installed
+
+
+@pytest.mark.attribution("archsetup")
+def test_blueman_not_installed(host):
+    # blueman was retired 2026-07-02 in favor of the dotfiles bt panel;
+    # its reappearance means the desktop_environment step regressed.
+    assert not host.package("blueman").is_installed