feat(home-assistant): add alexa_media_player custom component

Package the Alexa Media Player HACS component declaratively (v5.15.7),
so HA can drive the Echo devices (TTS/announce, media, sensors). Needs
dictor 0.1.12 (absent from nixpkgs) and an alexapy 1.29.22 -> 1.29.25
bump to satisfy the manifest's exact requirement pins; both build
against HA's interpreter. Config-flow based: add via the HA UI and sign
in with the Amazon account after rebuild.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RCn8YgGQMGpauatdeTdQYf

docs/superpowers/plans/2026-07-26-jellyfin-hw-transcoding.md

@@ -0,0 +1,154 @@
+# Jellyfin Hardware Transcoding (jupiter) Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Give jupiter's Jellyfin service access to the Intel iGPU's VAAPI render node so Quick Sync hardware transcoding can be enabled, instead of every transcode falling back to CPU.
+
+**Architecture:** One NixOS module change (`modules/environments/jellyfin/default.nix`) grants the `jellyfin` systemd service supplementary access to the `video`/`render` groups and installs `libva-utils` for verification. This is declarative and build-verifiable from the Mac. Enabling Quick Sync inside Jellyfin's own dashboard, and the on-machine verification, is a manual step run by the user on jupiter after deploy — the NixOS module has no option for it and this environment's convention is that the assistant never SSHes into jupiter directly (see `docs/superpowers/specs/2026-07-26-jellyfin-hw-transcoding.md`).
+
+**Tech Stack:** NixOS (flake-parts), nixpkgs `services.jellyfin` module, VAAPI/`intel-media-driver`, `libva-utils`.
+
+## Global Constraints
+
+- No SSH from the assistant into jupiter — all on-machine commands are given to the user to run and paste back.
+- Follow the existing profile pattern in `modules/environments/jellyfin/default.nix` (`config = lib.mkIf cfg.enable { ... }`); don't introduce a new toggle option — hardcode the hardware-acceleration wiring on, per the approved spec.
+- Verify locally via `nix eval` / `nix build` before asking the user to deploy.
+
+---
+
+### Task 1: Grant Jellyfin access to the iGPU and verify the build
+
+**Files:**
+- Modify: `modules/environments/jellyfin/default.nix`
+
+**Interfaces:**
+- Produces: `systemd.services.jellyfin.serviceConfig.SupplementaryGroups = [ "video" "render" ];` — verified via `nix eval` in Step 2.
+
+- [ ] **Step 1: Add the device-access config and `libva-utils` package**
+
+Read the current file first (`modules/environments/jellyfin/default.nix`), then edit the `config = lib.mkIf cfg.enable { ... }` block so it reads:
+
+```nix
+  config = lib.mkIf cfg.enable {
+    services.jellyfin = {
+      enable = true;
+      openFirewall = true;
+    };
+
+    environment.systemPackages = [ pkgs.libva-utils ];
+
+    my.homepage.services = [
+      {
+        group = "Media";
+        name = "Jellyfin";
+        description = "Media server";
+        href = "http://${hostName}:${toString port}";
+        icon = "jellyfin.png";
+      }
+    ];
+
+    systemd.services.jellyfin = {
+      after = [ "network-online.target" ];
+      serviceConfig.SupplementaryGroups = [
+        "video"
+        "render"
+      ];
+    };
+  };
+```
+
+Note the two existing `systemd.services.jellyfin` keys (`after`) and the new `serviceConfig.SupplementaryGroups` now live in the same attrset — don't create a second `systemd.services.jellyfin = { ... }` block, it would overwrite the first.
+
+- [ ] **Step 2: Verify the rendered config with `nix eval`**
+
+Run (from the repo root on the Mac):
+
+```bash
+nix eval '.#nixosConfigurations.jupiter.config.systemd.services.jellyfin.serviceConfig.SupplementaryGroups' \
+  --extra-experimental-features 'nix-command flakes'
+```
+
+Expected output: `[ "video" "render" ]`
+
+- [ ] **Step 3: Verify the machine still builds**
+
+Run:
+
+```bash
+nix build '.#nixosConfigurations.jupiter.config.system.build.toplevel' \
+  --extra-experimental-features 'nix-command flakes' --no-link
+```
+
+Expected: build succeeds with no errors (may take a while; watch for any evaluation error mentioning `jellyfin` or `libva-utils`).
+
+- [ ] **Step 4: Format and commit**
+
+```bash
+nixfmt-rfc-style modules/environments/jellyfin/default.nix
+git add modules/environments/jellyfin/default.nix
+git commit -m "feat(jellyfin): grant iGPU access for Quick Sync hardware transcoding"
+```
+
+---
+
+### Task 2: Deploy on jupiter and enable Quick Sync (user-executed)
+
+**Files:** none (on-machine deploy + Jellyfin dashboard UI)
+
+**Interfaces:**
+- Consumes: the `SupplementaryGroups` change from Task 1, already merged into the flake.
+
+These steps run **on jupiter**, by the user — paste the output back so we can confirm each one before moving to the next.
+
+- [ ] **Step 1: Deploy**
+
+```bash
+sudo nixos-rebuild switch --flake '.#jupiter'
+```
+
+Expected: switch succeeds, no errors mentioning `jellyfin`.
+
+- [ ] **Step 2: Confirm the service picked up the new groups**
+
+```bash
+systemctl show jellyfin -p SupplementaryGroups
+systemctl status jellyfin --no-pager
+```
+
+Expected: `SupplementaryGroups=video render` (order may vary) and the service is `active (running)`.
+
+- [ ] **Step 3: Confirm VAAPI driver loads**
+
+```bash
+vainfo
+```
+
+Expected: output starts with something like `vainfo: VA-API version: 1.x` and `Driver version: Intel iHD driver`, followed by a list of supported VAProfiles/VAEntrypoints (e.g. `VAProfileH264Main : VAEntrypointVLD`, `VAEntrypointEncSlice`).
+
+If this instead prints a permissions or "no VA display" error, paste it back — that means the group grant isn't reaching the process and Task 1 needs a follow-up fix (e.g. the jellyfin service may be more sandboxed than expected, requiring an explicit `DeviceAllow=char-drm rw` in `serviceConfig` as well).
+
+- [ ] **Step 4: Enable Quick Sync in the Jellyfin dashboard**
+
+In the Jellyfin web UI:
+1. **Dashboard → Playback**.
+2. Hardware acceleration: **Intel QuickSync (QSV)**.
+3. VA-API device: `/dev/dri/renderD128`.
+4. Enable hardware decoding for the codecs your library uses (H264 at minimum).
+5. If the library has HDR content, enable tone-mapping.
+6. Save.
+
+- [ ] **Step 5: Functional check**
+
+Play a file that requires transcoding (or force a lower quality in the client's playback settings to trigger one), then:
+
+```bash
+journalctl -u jellyfin -n 50 --no-pager
+```
+
+Look for a line referencing `qsv` or `vaapi` in the transcode command. Separately, watch CPU usage (`htop`) during playback — it should stay low on the core doing the transcode, rather than pegging at 100%, since the iGPU is now doing the encode/decode work.
+
+## Self-Review Notes
+
+- Spec coverage: NixOS change (Task 1) ✓, manual dashboard step (Task 2 Step 4) ✓, verification via `vainfo`/build (Task 1 Step 2-3, Task 2 Step 3) ✓, functional check (Task 2 Step 5) ✓. Toggle option explicitly excluded per approved spec — not present, correctly.
+- No placeholders — every step has literal commands/code.
+- `SupplementaryGroups` key/value matches exactly between Task 1 (produced) and Task 2 (consumed/checked).

docs/superpowers/plans/2026-07-29-alexa-media-player.md

@@ -0,0 +1,189 @@
+# Alexa Media Player Integration — Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Package the `alexa_media_player` HACS component declaratively on jupiter's Home Assistant so HA can drive the household Echo devices (TTS/announce, media, sensors).
+
+**Architecture:** Add one `buildHomeAssistantComponent` entry to `services.home-assistant.customComponents` (same pattern as the existing `ha-sourdough`). The component has real Python deps, so the module's `let` block also defines two supporting derivations built against HA's own interpreter: a new `dictor` package and an `alexapy` version bump. No HACS runtime, no YAML config — the integration is added through the HA UI after the rebuild.
+
+**Tech Stack:** NixOS, `pkgs.buildHomeAssistantComponent`, `buildPythonPackage`, `fetchFromGitHub`/`fetchFromGitLab`/`fetchPypi`.
+
+## Global Constraints
+
+- Target machine: **jupiter** only. All edits live in `modules/environments/home-assistant/default.nix`.
+- Python dep derivations MUST build against Home Assistant's interpreter set — `pkgs.home-assistant.python3Packages` — the same set `buildHomeAssistantComponent` uses. Do not use top-level `pkgs.python3Packages`.
+- Manifest requirements are enforced at build time by `manifestCheckPhase` and again by HA at runtime. Every requirement must resolve to an installed dist satisfying its specifier. Exact pins (verbatim from `alexa_media_player` v5.15.7 `manifest.json`):
+  - `alexapy==1.29.25`
+  - `dictor>=0.1.12,<0.2`
+  - `wrapt>=1.14.0`  (nixpkgs 1.17.2 — already satisfied)
+  - `packaging>=20.3`  (nixpkgs 26.1 — already satisfied)
+- Pinned artifacts (all three hashes verified to build during planning):
+
+  | Artifact           | Fetcher          | Ref / version | Hash                                              |
+  | ------------------ | ---------------- | ------------- | ------------------------------------------------- |
+  | alexa_media_player | fetchFromGitHub  | `v5.15.7`     | `sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI=` |
+  | alexapy            | fetchFromGitLab  | `v1.29.25`    | `sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4=` |
+  | dictor             | fetchPypi (sdist)| `0.1.12`      | `sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs=` |
+
+---
+
+## File Structure
+
+Single file touched: `modules/environments/home-assistant/default.nix`.
+- Its `let` block gains `haPython`, `dictor`, and `alexapy` bindings.
+- Its `services.home-assistant.customComponents` list gains a second entry (`alexa_media`) alongside the existing `sourdough` entry.
+
+No new files. The two supporting derivations are small and specific to this component, so they live inline in the module's `let` block next to their only consumer (files that change together live together).
+
+---
+
+### Task 1: Package `alexa_media_player` with its Python dependencies
+
+**Files:**
+- Modify: `modules/environments/home-assistant/default.nix` (the `let` block, currently lines 9-12; and the `customComponents` list, currently lines 29-41)
+
+**Interfaces:**
+- Consumes: `pkgs.home-assistant.python3Packages` (HA interpreter set), `pkgs.buildHomeAssistantComponent`, `pkgs.fetchFromGitHub`, `pkgs.fetchFromGitLab`.
+- Produces: a second `customComponents` entry with `domain = "alexa_media"`. No other module consumes these `let` bindings.
+
+- [ ] **Step 1: Add the supporting derivations to the `let` block**
+
+Edit the `let` block so it reads exactly:
+
+```nix
+let
+  cfg = config.my.profiles.home-assistant;
+  hostName = config.networking.hostName;
+
+  # Python deps for the alexa_media_player custom component (Task: Alexa).
+  # Built against Home Assistant's own interpreter — the same set
+  # buildHomeAssistantComponent uses — so HA's build-time and runtime
+  # manifest-requirement checks are satisfied.
+  haPython = pkgs.home-assistant.python3Packages;
+
+  # dictor is not in nixpkgs; alexa_media_player needs dictor>=0.1.12,<0.2.
+  # Pure-Python, no runtime deps, legacy setup.py.
+  dictor = haPython.buildPythonPackage {
+    pname = "dictor";
+    version = "0.1.12";
+    format = "setuptools";
+    src = haPython.fetchPypi {
+      pname = "dictor";
+      version = "0.1.12";
+      hash = "sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs=";
+    };
+    build-system = [ haPython.setuptools ];
+    doCheck = false;
+    pythonImportsCheck = [ "dictor" ];
+  };
+
+  # nixpkgs ships alexapy 1.29.22; the manifest pins ==1.29.25. Patch bump.
+  # nixpkgs fetches alexapy from GitLab (keatontaylor/alexapy), tag v<version>.
+  alexapy = haPython.alexapy.overridePythonAttrs (old: {
+    version = "1.29.25";
+    src = pkgs.fetchFromGitLab {
+      owner = "keatontaylor";
+      repo = "alexapy";
+      tag = "v1.29.25";
+      hash = "sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4=";
+    };
+  });
+in
+```
+
+- [ ] **Step 2: Add the `alexa_media` entry to `customComponents`**
+
+In `services.home-assistant.customComponents`, immediately after the closing `)` of the existing `sourdough` entry (current line 40) and before the list's closing `]` (current line 41), add:
+
+```nix
+        (pkgs.buildHomeAssistantComponent {
+          owner = "Alandtse";
+          domain = "alexa_media";
+          version = "5.15.7";
+          src = pkgs.fetchFromGitHub {
+            owner = "Alandtse";
+            repo = "alexa_media_player";
+            rev = "v5.15.7";
+            hash = "sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI=";
+          };
+          # Every manifest requirement must be importable at a satisfying
+          # version or manifestCheckPhase fails the build.
+          dependencies = [
+            alexapy
+            dictor
+            haPython.wrapt
+            haPython.packaging
+          ];
+        })
+```
+
+- [ ] **Step 3: Format the file**
+
+Run: `nixfmt-rfc-style modules/environments/home-assistant/default.nix`
+Expected: exits 0, no diff surprises (re-read the file if unsure).
+
+- [ ] **Step 4: Build the component in isolation first (fast feedback)**
+
+This is the real test: it runs `manifestCheckPhase`, which fails loudly if any of the four requirements is unmet. It was verified to succeed during planning.
+
+Run:
+```bash
+nix build --impure --no-link --print-out-paths --expr '
+  let
+    pkgs = (builtins.getFlake (toString ./.)).nixosConfigurations.jupiter.pkgs;
+    py = pkgs.home-assistant.python3Packages;
+    dictor = py.buildPythonPackage {
+      pname = "dictor"; version = "0.1.12"; format = "setuptools";
+      src = py.fetchPypi { pname = "dictor"; version = "0.1.12"; hash = "sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs="; };
+      build-system = [ py.setuptools ]; doCheck = false; pythonImportsCheck = [ "dictor" ];
+    };
+    alexapy = py.alexapy.overridePythonAttrs (old: {
+      version = "1.29.25";
+      src = pkgs.fetchFromGitLab { owner = "keatontaylor"; repo = "alexapy"; tag = "v1.29.25"; hash = "sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4="; };
+    });
+  in pkgs.buildHomeAssistantComponent {
+    owner = "Alandtse"; domain = "alexa_media"; version = "5.15.7";
+    src = pkgs.fetchFromGitHub { owner = "Alandtse"; repo = "alexa_media_player"; rev = "v5.15.7"; hash = "sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI="; };
+    dependencies = [ alexapy dictor py.wrapt py.packaging ];
+  }'
+```
+Expected: prints a `/nix/store/...-Alandtse-alexa_media-5.15.7` path, exit 0. If it fails with `<pkg><specifier> not satisfied by version ...`, a dependency version drifted — re-check the manifest pin against the provided dep.
+
+- [ ] **Step 5: Build the whole jupiter system (integration gate)**
+
+Run: `nix build '.#nixosConfigurations.jupiter.config.system.build.toplevel'`
+Expected: builds to completion, exit 0. This confirms the module edits evaluate and the component is wired into HA's package.
+
+- [ ] **Step 6: Commit**
+
+```bash
+git add modules/environments/home-assistant/default.nix
+git commit -m "$(cat <<'EOF'
+feat(home-assistant): add alexa_media_player custom component
+
+Package the Alexa Media Player HACS component declaratively (v5.15.7),
+so HA can drive the Echo devices (TTS/announce, media, sensors). Needs
+dictor 0.1.12 (absent from nixpkgs) and an alexapy 1.29.22 -> 1.29.25
+bump to satisfy the manifest's exact requirement pins; both build
+against HA's interpreter. Config-flow based: add via the HA UI and sign
+in with the Amazon account after rebuild.
+
+Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
+EOF
+)"
+```
+
+---
+
+## Post-implementation (manual, by the user — not an automatable step)
+
+After `sudo nixos-rebuild switch --flake '.#jupiter'`:
+1. Settings → Devices & Services → Add Integration → **Alexa Media Player**.
+2. Sign in with the Amazon account; complete any 2FA / app-password prompt in the UI flow.
+3. Confirm media_player entities and sensors appear; test a TTS/announce service call to an Echo.
+
+## Self-Review
+
+- **Spec coverage:** goal (alexa_media_player packaging) → Task 1; alexapy bump → Step 1; dictor packaging → Step 1; component entry → Step 2; wrapt/packaging already-satisfied → included as deps in Step 2; build-time manifest check → Steps 4-5; runtime config-flow → Post-implementation. Deferred Alexa→HA scope: intentionally absent. No gaps.
+- **Placeholder scan:** none — every step has concrete code/commands and the verified hashes.
+- **Type/name consistency:** `haPython`, `dictor`, `alexapy` defined in Step 1 and referenced by those exact names in Step 2; domain `alexa_media` consistent throughout; hashes identical across plan, spec, and the verified build.

docs/superpowers/specs/2026-07-26-jellyfin-hw-transcoding.md

@@ -0,0 +1,145 @@
+# Intel Quick Sync hardware transcoding for Jellyfin on jupiter
+
+## Problem
+
+Jellyfin streams stutter on jupiter whenever a client needs a transcode
+(unsupported codec/container, bitrate cap, or a client that can't
+direct-play). Transcoding currently runs entirely on CPU.
+
+jupiter's Intel iGPU is already usable at the OS level:
+
+- `hardware.graphics.enable = true` with `intel-media-driver` (the `iHD`
+  VAAPI driver) is configured in
+  `machines/jupiter/hardware-configuration.nix:20-27`.
+- The commented-out `i915.force_probe = "9a49"` kernel param there
+  corresponds to a Quick-Sync-capable Intel UHD iGPU, confirming the
+  hardware supports it.
+
+But `modules/environments/jellyfin/default.nix` never grants the
+`jellyfin` systemd service access to `/dev/dri`, so Jellyfin has no path
+to the GPU and silently falls back to software transcoding.
+
+## Goal
+
+Give the Jellyfin service access to the iGPU's VAAPI render node, so
+Quick Sync can be enabled in Jellyfin's own dashboard and transcodes are
+offloaded from the CPU.
+
+## Non-goals
+
+- Remote/external access or reverse-proxy tuning.
+- General CPU/RAM headroom review of jupiter.
+- A toggle option (`my.profiles.jellyfin.hardwareAcceleration.enable`) —
+  jupiter only has the one iGPU, so this is hardcoded on rather than
+  made configurable.
+
+## Design
+
+### NixOS change (declarative)
+
+In `modules/environments/jellyfin/default.nix`, inside the existing
+`config = lib.mkIf cfg.enable { ... }` block, grant the systemd service
+supplementary access to the `video` and `render` groups (the groups that
+own `/dev/dri/card*` and `/dev/dri/renderD*`):
+
+```nix
+systemd.services.jellyfin.serviceConfig.SupplementaryGroups = [
+  "video"
+  "render"
+];
+```
+
+This is additive to the existing `systemd.services.jellyfin.after = [
+"network-online.target" ];` block already in the file — both apply to
+the same service.
+
+Also add `libva-utils` to `environment.systemPackages` (or scoped to
+this module) so `vainfo` is available on jupiter to verify the driver
+loads correctly.
+
+### Manual step (not declarative)
+
+Jellyfin stores its transcoding/hardware-acceleration choice in its own
+internal `encoding.xml`, which the NixOS module does not expose as an
+option. After deploying the Nix change, one-time manual configuration in
+the Jellyfin dashboard is required:
+
+1. **Dashboard → Playback**.
+2. Hardware acceleration: **Intel QuickSync (QSV)**.
+3. VA-API device: `/dev/dri/renderD128`.
+4. Enable hardware decoding for the codecs your library actually uses
+   (H264 at minimum; HEVC/VP9 depending on iGPU generation).
+5. If any HDR content exists in the library, enable tone-mapping — this
+   is one of the more CPU-expensive operations Quick Sync can offload.
+
+## Verification
+
+Build-time (from the Mac, no SSH needed):
+
+```
+nix eval '.#nixosConfigurations.jupiter.config.systemd.services.jellyfin.serviceConfig.SupplementaryGroups' \
+  --extra-experimental-features 'nix-command flakes'
+```
+
+Expect `[ "video" "render" ]`.
+
+On jupiter after `sudo nixos-rebuild switch --flake '.#jupiter'`:
+
+```
+systemctl status jellyfin
+journalctl -u jellyfin -n 50 --no-pager
+vainfo
+```
+
+`vainfo` should list the `iHD` driver and print supported VAEntrypoints
+(VLD decode / encode profiles for H264/HEVC).
+
+Functional check: play a file on a client that forces transcoding (or
+force it manually via Jellyfin's playback quality setting), then in
+Jellyfin's dashboard **Activity/Now Playing** panel confirm the
+transcode reason and check that CPU usage on jupiter (`htop`) stays low
+during playback rather than pegging a core — Quick Sync offload should
+show up as low CPU, some GPU (`intel_gpu_top`) activity instead.
+
+## Open items
+
+- Exact supported codec list depends on the iGPU generation (device ID
+  `9a49`) — confirm via `vainfo` output once run, and enable only the
+  hardware decode paths it actually reports.
+
+## Post-deploy fix: two additional runtime packages required
+
+After the initial deploy (Task 1's `SupplementaryGroups` grant) and
+enabling QSV in the dashboard, HEVC HDR playback hung indefinitely
+(Direct Play worked for some titles; titles that needed a real
+transcode+tonemap never produced output). Root-caused via
+`journalctl -u jellyfin` and the per-session ffmpeg transcode log
+(`find / -xdev -iname '*ffmpeg-transcode*'`) — two separate runtimes
+were missing beyond `intel-media-driver` (which only provides VAAPI):
+
+1. **QSV session creation failed:** `Error creating a MFX session: -9`
+   / `Error initializing an MFX session: -3` on
+   `-init_hw_device qsv=qs@va`. VAAPI and QSV are separate runtimes on
+   Linux — QSV needs the oneVPL/MFX GPU implementation. Fix: added
+   `pkgs.vpl-gpu-rt` ("oneAPI Video Processing Library Intel GPU
+   implementation"; note `onevpl-intel-gpu` is the old, renamed
+   attribute) to `hardware.graphics.extraPackages` in
+   `machines/jupiter/hardware-configuration.nix`.
+
+2. **OpenCL device creation failed:** `Failed to get number of OpenCL
+   platforms: -1001` (`CL_PLATFORM_NOT_FOUND_KHR`) on
+   `-init_hw_device opencl=ocl@va`. The `tonemap_opencl` filter jellyfin
+   uses for HDR→SDR tone-mapping needs a working OpenCL ICD, which
+   nothing installed so far provides. Fix: added
+   `pkgs.intel-compute-runtime` ("Intel Graphics Compute Runtime oneAPI
+   Level Zero and OpenCL, supporting 12th Gen and newer" — matches
+   jupiter's Tiger Lake/Xe iGPU) to the same `extraPackages` list.
+
+Confirmed working end-to-end: HEVC HDR transcode with QSV encode +
+OpenCL tone-map runs at `speed=2.68x` realtime on jupiter's iGPU, and
+plays smoothly on Apple TV (JellyTV app).
+
+Both packages live in `machines/jupiter/hardware-configuration.nix`
+(`hardware.graphics.extraPackages`), alongside `intel-media-driver`,
+rather than in the jellyfin module itself — they're iGPU runtime
+capabilities, not something specific to the jellyfin service.

docs/superpowers/specs/2026-07-27-mibook-boot-desktop-choice-design.md

@@ -1,61 +0,0 @@
-# mibook: choose terminal-only vs desktop at boot
-
-## Goal
-
-Let mibook boot to a text console by default, with KDE fully installed and
-launchable on demand. The user decides after boot whether they need the
-graphical desktop, without rebuilding the system.
-
-## Behavior
-
-- mibook boots to a text console (`multi-user.target`). SDDM and Plasma do
-  **not** start automatically.
-- KDE (SDDM + Plasma 6) remains fully installed.
-- Running `desktop` in the terminal starts the SDDM display manager, which
-  presents the graphical login screen; logging in there enters a Plasma 6
-  session.
-- No reverse command. To return to a text console, stop the display manager
-  (`sudo systemctl stop display-manager`) or reboot.
-- Other machines that enable the `kde-desktop` profile are unaffected; their
-  desktop still starts on boot.
-
-## Implementation
-
-### `modules/environments/kde-desktop/default.nix`
-
-Add an opt-out option to the existing profile:
-
-- New option `my.profiles.kde-desktop.startOnBoot`, a boolean defaulting to
-  `true`. The default preserves the current behavior for every consumer.
-- The existing `config` block (SDDM, Plasma 6, user packages) stays enabled
-  whenever the profile is enabled, regardless of `startOnBoot`.
-- When `startOnBoot = false`, additionally apply:
-  - `systemd.services.display-manager.wantedBy = lib.mkForce [ ];` so SDDM is
-    defined but not pulled in by any boot target.
-  - `systemd.defaultUnit = "multi-user.target";` so the boot target is the
-    text console.
-  - A `desktop` command provided via
-    `pkgs.writeShellScriptBin "desktop" "exec sudo systemctl start display-manager.service"`,
-    added to `environment.systemPackages`.
-
-### `machines/mibook/environments.nix`
-
-Set `kde-desktop.startOnBoot = false;` alongside the existing
-`kde-desktop.enable = true;`.
-
-## Testing / verification
-
-- `nix build '.#nixosConfigurations.mibook.config.system.build.toplevel'`
-  builds without error.
-- After `nixos-rebuild switch` on mibook: system boots to a TTY, no SDDM;
-  running `desktop` brings up the SDDM login and a working Plasma session.
-- Confirm jupiter (or any non-mibook consumer) is unchanged: its evaluated
-  `systemd.defaultUnit` / display-manager wantedBy are not altered.
-
-## Trade-offs
-
-- `desktop` relies on `sudo`; the user has sudo access, so no extra
-  configuration is required.
-- Chose "boot to terminal, launch on demand" over a GRUB boot-menu entry
-  because it is more robust across NixOS generations and needs no fragile
-  static kernel entries.

docs/superpowers/specs/2026-07-29-alexa-media-player-design.md

@@ -0,0 +1,152 @@
+# Amazon Alexa integration for Home Assistant (jupiter) — design
+
+**Date:** 2026-07-29
+**Machine:** jupiter
+**Status:** approved, ready for implementation plan
+
+## Goal
+
+Let Home Assistant control and read the household Amazon Echo devices via the
+unofficial [`alexa_media_player`](https://github.com/Alandtse/alexa_media_player)
+integration: text-to-speech / announcements, media control, and per-device
+sensors (last-called device, next alarm/timer, DND state, etc.).
+
+This uses the user's Amazon account through an unofficial API. It is a
+config-flow integration: after the rebuild it is added through the HA UI, not
+via YAML.
+
+## Non-goals (deferred)
+
+Alexa → HA voice control ("Alexa, turn on the light") is **out of scope**. It
+would need either `emulated_hue` bound to port 80 on the LAN, or a public HTTPS
+endpoint plus the AWS-Lambda Smart Home Skill. The user chose to decide on that
+later. Nothing in this change touches the firewall, port 80, systemd unit
+capabilities, or network exposure.
+
+## Approach
+
+Package the integration declaratively, following the existing `ha-sourdough`
+pattern in `modules/environments/home-assistant/default.nix` (a
+`buildHomeAssistantComponent` entry in `services.home-assistant.customComponents`).
+No HACS runtime.
+
+Unlike sourdough, `alexa_media_player` has real Python dependencies. Its
+`manifest.json` (v5.15.7) declares:
+
+```
+alexapy==1.29.25
+packaging>=20.3
+wrapt>=1.14.0
+dictor>=0.1.12,<0.2
+```
+
+`buildHomeAssistantComponent` runs `manifestCheckPhase` at build time
+(`check_manifest.py`): every requirement must resolve to an installed
+distribution **whose version satisfies the specifier**, or the build fails.
+Home Assistant repeats this check at runtime. Therefore each requirement must be
+satisfied exactly — the exact `==1.29.25` pin in particular.
+
+Dependency status in the pinned nixpkgs (`nixos-25.11`):
+
+| Requirement            | nixpkgs today | Action                                  |
+| ---------------------- | ------------- | --------------------------------------- |
+| `alexapy==1.29.25`     | 1.29.22       | **Bump** to 1.29.25 via override        |
+| `dictor>=0.1.12,<0.2`  | *absent*      | **Package** dictor 0.1.12 (new)         |
+| `wrapt>=1.14.0`        | 1.17.2        | none — already satisfied                |
+| `packaging>=20.3`      | 26.1          | none — already satisfied                |
+
+`authcaptureproxy` (in nixpkgs at 1.3.7) is a transitive dependency of
+`alexapy`, not listed in the manifest, so it needs no direct handling.
+
+## Components
+
+All changes live in `modules/environments/home-assistant/default.nix` (plus the
+hashes below). Three small pieces, wired together in the module's `let` block:
+
+### 1. `dictor` package (new)
+
+Not in nixpkgs. Pure-Python, no runtime dependencies (`requires_dist: null`),
+ships a `setup.py`. A minimal `pkgs.python3Packages.buildPythonPackage`:
+
+- pname `dictor`, version `0.1.12`
+- `src = fetchPypi { pname = "dictor"; version = "0.1.12"; hash = "sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs="; }`
+- setuptools format (legacy `setup.py`); `build-system = [ setuptools ]`
+- `doCheck = false` (no meaningful test suite); `pythonImportsCheck = [ "dictor" ]`
+
+Build against the HA Python set so the version lands in HA's venv — i.e. use
+`config.services.home-assistant.package.python.pkgs` (the same interpreter the
+component check and HA runtime use), not the top-level `pkgs.python3Packages`.
+
+### 2. `alexapy` 1.29.25 (override)
+
+nixpkgs `alexapy` is fetched from **GitLab** (`keatontaylor/alexapy`, tag
+`v<version>`), not PyPI. Override just the version + src via
+`overridePythonAttrs`, reusing the existing build-system and dependency list:
+
+- `version = "1.29.25"`
+- `src = fetchFromGitLab { owner = "keatontaylor"; repo = "alexapy"; tag = "v1.29.25"; hash = "sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4="; }`
+
+This is a patch bump (1.29.22 → 1.29.25); the dependency set is expected to be
+unchanged. Override the HA-Python-set `alexapy` so it shares the interpreter
+with dictor and the component.
+
+### 3. `alexa_media_player` component (new `customComponents` entry)
+
+```
+buildHomeAssistantComponent {
+  owner = "Alandtse";
+  domain = "alexa_media";
+  version = "5.15.7";
+  src = fetchFromGitHub {
+    owner = "Alandtse";
+    repo  = "alexa_media_player";
+    rev   = "v5.15.7";
+    hash  = "sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI=";
+  };
+  dependencies = [ alexapy' dictor' wrapt packaging ];  # HA-python-set packages
+}
+```
+
+`dependencies` must make every manifest requirement importable at the required
+version for `manifestCheckPhase` to pass. Include all four (the two custom ones
+plus `wrapt` and `packaging` from the HA Python set) to be explicit.
+
+## Data flow
+
+1. `nixos-rebuild switch` builds the component; `manifestCheckPhase` validates
+   the four requirements against the provided `dependencies`.
+2. HA starts; the custom component is present but not configured.
+3. User adds **Alexa Media Player** in Settings → Devices & Services, signs in
+   with the Amazon account (email/password; 2FA or app-password handled in the
+   UI flow at runtime).
+4. HA creates media_player entities and per-device sensors; TTS/announce
+   services become available for automations.
+
+## Error handling / risks
+
+- **Version-pin drift.** If a future `alexa_media_player` bump changes the
+  `alexapy==` pin, `alexapy` must be re-bumped in lockstep, or the build fails
+  loudly at `manifestCheckPhase` (fail-safe, not silent).
+- **Amazon login fragility.** The unofficial API can break on Amazon's side
+  (captcha/2FA changes). This is a runtime concern, independent of packaging;
+  not addressed here.
+- **`dictor` upper bound `<0.2`.** 0.1.12 is the current release and satisfies
+  it. If nixpkgs later gains a `dictor` ≥ 0.2, prefer our pinned 0.1.12 for
+  this component.
+
+## Verification
+
+- `nix build '.#nixosConfigurations.jupiter.config.system.build.toplevel'`
+  succeeds — this exercises the build-time manifest-requirements check for all
+  three new/overridden derivations.
+- `nixfmt-rfc-style` clean on the edited module.
+- Post-deploy (manual, by the user): the integration appears under Add
+  Integration, and a TTS/announce call reaches an Echo.
+
+## Pinned artifacts
+
+| Artifact                    | Source     | Ref / version | Hash                                              |
+| --------------------------- | ---------- | ------------- | ------------------------------------------------- |
+| alexa_media_player          | GitHub     | v5.15.7       | sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI= |
+| alexapy                     | GitLab     | v1.29.25      | sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4= |
+| dictor                      | PyPI sdist | 0.1.12        | sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs= |

machines/jupiter/hardware-configuration.nix

@@ -35,6 +35,8 @@
       #vaapiIntel         # LIBVA_DRIVER_NAME=i965 (older but works better for Firefox/Chromium)
       libva-vdpau-driver
       libvdpau-va-gl
+      vpl-gpu-rt # oneVPL/MFX runtime, required for QSV (h264_qsv/hevc_qsv) session creation
+      intel-compute-runtime # OpenCL runtime, required for tonemap_opencl (HDR tone-mapping)
     ];
   };
 

machines/mibook/environments.nix

@@ -6,7 +6,6 @@ in
 {
   my.profiles = {
     kde-desktop.enable = true;
-    kde-desktop.startOnBoot = false;
     zsh.enable = true;
     apps = {
       desktop_apps = true;

modules/environments/home-assistant/default.nix

@@ -9,6 +9,39 @@
 let
   cfg = config.my.profiles.home-assistant;
   hostName = config.networking.hostName;
+
+  # Python deps for the alexa_media_player custom component. Built against
+  # Home Assistant's own interpreter — the same set buildHomeAssistantComponent
+  # uses — so HA's build-time and runtime manifest-requirement checks pass.
+  haPython = pkgs.home-assistant.python3Packages;
+
+  # dictor is not in nixpkgs; alexa_media_player needs dictor>=0.1.12,<0.2.
+  # Pure-Python, no runtime deps, legacy setup.py.
+  dictor = haPython.buildPythonPackage {
+    pname = "dictor";
+    version = "0.1.12";
+    format = "setuptools";
+    src = haPython.fetchPypi {
+      pname = "dictor";
+      version = "0.1.12";
+      hash = "sha256-bbSDda4eU9ye2EToWzj04/v79qTmC+yjd1Fa0URTuRs=";
+    };
+    build-system = [ haPython.setuptools ];
+    doCheck = false;
+    pythonImportsCheck = [ "dictor" ];
+  };
+
+  # nixpkgs ships alexapy 1.29.22; the manifest pins ==1.29.25. Patch bump.
+  # nixpkgs fetches alexapy from GitLab (keatontaylor/alexapy), tag v<version>.
+  alexapy = haPython.alexapy.overridePythonAttrs (old: {
+    version = "1.29.25";
+    src = pkgs.fetchFromGitLab {
+      owner = "keatontaylor";
+      repo = "alexapy";
+      tag = "v1.29.25";
+      hash = "sha256-P/hvgqZVaBJF5dbmHrDjQMC+pwV3EEhKyFIS5KmhgD4=";
+    };
+  });
 in
 {
 
@@ -23,6 +56,42 @@ in
     services.home-assistant = {
       enable = true;
       openFirewall = true;
+
+      # HACS-style custom components, packaged declaratively (no HACS runtime).
+      # Config-flow based: add via Settings > Devices & Services after rebuild.
+      customComponents = [
+        (pkgs.buildHomeAssistantComponent {
+          owner = "Matts-Baps";
+          domain = "sourdough";
+          version = "1.1.3";
+          src = pkgs.fetchFromGitHub {
+            owner = "Matts-Baps";
+            repo = "ha-sourdough";
+            rev = "v1.1.3";
+            hash = "sha256-Uoid/2f6GxZMuE5Keu2VjHPYuOxnYG8hsCD6BYcaTvM=";
+          };
+        })
+        (pkgs.buildHomeAssistantComponent {
+          owner = "Alandtse";
+          domain = "alexa_media";
+          version = "5.15.7";
+          src = pkgs.fetchFromGitHub {
+            owner = "Alandtse";
+            repo = "alexa_media_player";
+            rev = "v5.15.7";
+            hash = "sha256-1rcZVSX1xA1Lc4qSu39MOitVEciZFhoPQy2y5+PpoAI=";
+          };
+          # Every manifest requirement must be importable at a satisfying
+          # version or manifestCheckPhase fails the build.
+          dependencies = [
+            alexapy
+            dictor
+            haPython.wrapt
+            haPython.packaging
+          ];
+        })
+      ];
+
       extraComponents = [
         "matter"
         "mobile_app"

modules/environments/jellyfin/default.nix

@@ -22,6 +22,8 @@ in
       openFirewall = true;
     };
 
+    environment.systemPackages = [ pkgs.libva-utils ];
+
     my.homepage.services = [
       {
         group = "Media";
@@ -34,6 +36,10 @@ in
 
     systemd.services.jellyfin = {
       after = [ "network-online.target" ];
+      serviceConfig.SupplementaryGroups = [
+        "video"
+        "render"
+      ];
     };
   };
 }

modules/environments/kde-desktop/default.nix

@@ -11,19 +11,9 @@ in
 {
   options.my.profiles.kde-desktop = with lib; {
     enable = mkEnableOption "KDE Desktop Environment";
-    startOnBoot = mkOption {
-      type = types.bool;
-      default = true;
-      description = ''
-        Whether the display manager (SDDM) starts automatically at boot.
-        When false, the system boots to a text console and KDE can be
-        launched on demand with the `desktop` command.
-      '';
-    };
   };
 
-  config = lib.mkIf cfg.enable (lib.mkMerge [
-    {
+  config = lib.mkIf cfg.enable {
     services = {
       displayManager.sddm.enable = true;
       displayManager.sddm.wayland.enable = true;
@@ -33,15 +23,5 @@ in
       # Programms can be added here...
       numix-icon-theme
     ];
-    }
-    (lib.mkIf (!cfg.startOnBoot) {
-      # Boot to a text console; SDDM stays installed but is not pulled in
-      # by any boot target. Launch KDE on demand with `desktop`.
-      systemd.services.display-manager.wantedBy = lib.mkForce [ ];
-      systemd.defaultUnit = lib.mkForce "multi-user.target";
-      environment.systemPackages = [
-        (pkgs.writeShellScriptBin "desktop" "exec sudo systemctl start display-manager.service")
-      ];
-    })
-  ]);
+  };
 }