feat(schema): declare a host hardware capability, hardware.gpu: intel-quicksync

A ServiceDefinition could not say it needs the host's Intel QuickSync render
device. The schema is `additionalProperties: false`, so there was no authorable
form for it at all, and `apps/` is generated — a hand-edit would be reverted by
the next render.

Adds optional top-level `hardware`, with one optional member `gpu`, an enum
whose only current value is `intel-quicksync` (schema 1.7.0 -> 1.8.0).

The enum is the point. The SD declares WHAT CLASS of device it needs; the
hostPath and the mount live only in catalog/render.py. Migrating to the Intel
GPU device plugin (`gpu.intel.com/i915` resource requests, no hostPath) is then
a renderer change with zero catalog edits. Letting an SD name `/dev/dri`
directly would look simpler and make that migration a catalog-wide edit, so
both the schema description and the renderer contract say so explicitly.

When `hardware.gpu == intel-quicksync`, r_deployment emits exactly two things,
on the app container only:

  - a hostPath volume `dri` -> /dev/dri, type DirectoryOrCreate;
  - a read-write volumeMount of it at /dev/dri (VA-API opens the render node
    read-write, so deliberately not readOnly).

Mounting the device is sufficient. In particular NO
podSecurityContext.supplementalGroups is emitted, and adding one would be a
regression rather than a hardening. Measured in the running container on
prod-2, 2026-09-30:

  PID 1   s6-svscan            Uid: 0     Gid: 0     Groups: 0
  pid 246 Plex Media Server    Uid: 1000  Gid: 1000  Groups: 100 1000

The service is started with `exec s6-setuidgid plex ...`, and the child's group
list is exactly the /etc/group account-database list — root's gid 0, which
PID 1 holds, is gone. That is a setgroups() that REPLACES rather than appends,
so anything Kubernetes supplies is discarded before the app starts. What works
is the image's own /etc/cont-init.d/45-plex-hw-transcode-and-connected-tuner,
which stats each /dev/dri char device, groupadds a matching group inside the
container and usermods the app user into it, every start, nothing hardcoded.
An inert supplementalGroups would have read as the mechanism to whoever
debugged this next, so the absence is documented at the emission site and
asserted by --selftest. Corollary: the hook re-stats on every start, so host
GID drift is self-healing and no GID is pinned anywhere in this repo.

`DirectoryOrCreate` is load-bearing. A node that comes back without the render
device (rebuild, BIOS change, driver regression, hardware swap) must degrade
the workload to software transcoding, not fail the mount: apps-wave-0 is
`wait: true` and apps-wave-1 dependsOn it, so a failed hostPath mount stalls
the whole app tier for a feature that is not load-bearing. /dev is tmpfs, so
the empty directory the kubelet creates leaves nothing durable behind. Its cost
— a missing device is silent, and no metric exists to alert on — is recorded in
the contract rather than papered over with an alert that could not fire.

Also deliberately NOT emitted: no `privileged: true` (Kyverno restrict-host-
namespaces is Enforce and it is not needed), no nodeSelector (placement is a
separate concern with its own justification), no resource requests (there is no
app-container resource render path).

No catalog entry uses the field. Re-rendering `--all catalog -o apps` is a zero
diff, which is the proof the change is inert until opted into.

Self-tests in the existing check(...) style: the positive (volume + mount, and
no securityContext / privileged / nodeSelector), the negative (an SD without
`hardware` gains no volume, no mount, no securityContext — mirroring the
podSecurityContext negative) and a pass-through case (an SD's own
podSecurityContext survives byte-for-byte). Note that NO gate stage runs
`render.py --selftest`; they were run by hand and the gap is recorded in the
handoff.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

decisions/2026-09-30-sd-hardware-capability.md

@@ -104,8 +104,8 @@ Measured, in this worktree, on this branch:
 - **GATE: `rc 3` — UNDETERMINED, NOT green.** Run in the pinned toolbox from this worktree with
   both CLAUDE.md §3 workarounds (`DEV_KUBECONFIG=/dev/null`, and an `ENGINE` shim bind-mounting the
   main checkout's `.git` at its own absolute path). Diff base `origin/main @ 0fbf544d5e2f`; touched
-  requirements `R-DNS-03 R-GITOPS-02 R-IDP-02`. Run **four** times on this branch with an identical
-  result each time, most recently against tree `c132893045b1` — the final commit differs from that
+  requirements `R-DNS-03 R-GITOPS-02 R-IDP-02`. Run three times on this branch with an identical
+  result each time, most recently against tree `e0d957998127` — the final commit differs from that
   run only by this paragraph. Per stage:
 
   | stage | result |
@@ -151,13 +151,6 @@ Measured, in this worktree, on this branch:
   is worse than none — see the 2026-09-13 correction in `renderer-contract.md` §`observability`,
   where twelve monitors discovered zero targets. The only proof of hardware transcode is an operator
   seeing it in the application's own dashboard.
-- **That "mounting the device is sufficient" generalizes beyond this one image.** It does not, and
-  I have not verified that it does. The claim was measured for an image that resolves the device
-  group itself in `cont-init.d`. A future consumer of `hardware.gpu` that runs non-root with no
-  equivalent hook would still need the group solved — and the fix for that case is a **renderer**
-  change (per-image handling, or the device plugin), never a new SD field. I scoped the claim in
-  `renderer-contract.md` rather than letting it read as general; the first such consumer must
-  re-measure.
 - **The feature now depends on a hook inside an image that floats.** The `cont-init.d` behaviour
   above was read from digest `sha256:e0ab27395614…` (`plexmediaserver 1.43.4.10903`), but the
   deployment runs `plexinc/pms-docker:latest` with `imagePullPolicy: Always`. **A silent pull can

schemas/renderer-contract.md

@@ -192,12 +192,6 @@ platform must render, and cites the requirement each mapping satisfies. Changing
   - A corollary worth having: because the hook re-`stat`s the device on every start, the host GID
     **drifting** (a node rebuild renumbering the *systemd dynamic* `render` group) is self-healing.
     No GID is pinned anywhere in this repo.
-  - **Scope of that measurement, stated so nobody over-reads it.** "Mounting the device is
-    sufficient" was established for an image that resolves the device group itself. A FUTURE
-    consumer that runs non-root and has no equivalent init hook would still need the group solved
-    somehow — and the answer for that case is a **renderer** change (per-image handling, or the
-    device plugin), not a new ServiceDefinition field. The enum is what keeps that option open. The
-    first such consumer must re-measure rather than assume this bullet covers it.
 - **`DirectoryOrCreate` is load-bearing — do not tighten it to `Directory`.** A node that comes back
   without the render device (rebuild, BIOS change, driver regression, hardware swap) must degrade the
   workload to **software transcoding**, not fail the mount. `apps-wave-0` is `wait: true` and