Packaging plan: ffmpeg-v4l2-request via marfrit-packages (fermi+feynman)

README.md

@@ -181,6 +181,32 @@ HEVC once the stretch goal is viable.
 Patches upstreamed along the way (v4l2-request to FFmpeg, VDPU346 to
 linux-media) count double — they benefit the whole fleet.
 
+## Packaging — marfrit-packages
+
+New fleet hosts should get Fourier userspace via `pacman -S` / `apt install`,
+not per-device AUR rebuilds. Mirror plan in `marfrit-packages` (layout:
+`arch/<pkg>/PKGBUILD`, `debian/<pkg>/build-deb.sh + debian/`):
+
+| Package                      | Source                                  | CI runner | Target  |
+|------------------------------|-----------------------------------------|-----------|---------|
+| `ffmpeg-v4l2-request-git`    | fork of AUR (Jernej's patchset on ffmpeg tip) | **fermi** (Arch ARM aarch64) | Path A: ohm, fresnel, ampere |
+| `ffmpeg-v4l2-request`        | same patches against Debian ffmpeg src  | **feynman** (Debian aarch64) | Path A Debian hosts |
+| `gst-plugins-bad-fourier`    | only if stock distro package is <1.28   | fermi / feynman | 1.28 HEVC UAPI uplift |
+| `libva-v4l2-request`         | upstream tag                            | fermi / feynman | VA-API bridge |
+
+The Arch package is the priority (ohm + fresnel are Arch-based). Debian
+package comes second (relevant if a fleet host ever runs Debian — kepler or
+similar). Both are `provides=(ffmpeg) conflicts=(ffmpeg)`, so install
+deliberately replaces the distro ffmpeg on a given host.
+
+CI trigger on each push. Artifacts land in packages.reauktion.de
+(`reference_marfrit_repo_bootstrap.md` in noether memory has the client
+bootstrap).
+
+Out of scope: rkmpp-based FFmpeg (Path B). Boltzmann stays on rkr* until
+Neutron migrates; that host doesn't need a marfrit-packages entry until
+migration.
+
 ## Working agreements
 
 Standing rules for how we run this project — inherited from the broader