investigate: release failure across 9 apps caused by python base image bump to 3.14 / ubuntu resolute

[Copilot]

Triage-only PR. The release-failure issue lists 9 apps, but they share an upstream root cause and split into fixes that violate this agent's "one app = one PR" rule against the environment's "cannot open new PRs" constraint. Stopped before committing any code change to get direction.

Root cause

All 9 apps FROM ghcr.io/trueforge-org/python:3.14.4, which was rebuilt on Ubuntu 26.04 (resolute) + Python 3.14. That single bump explains every failure.

Per-app classification

App	Failure	Class
apprise-api	uwsgi link: ld: cannot find -lcrypt (missing libxcrypt-dev)	trivial per-app
babybuddy	apt: libxml2 has no installation candidate (resolute rename, likely libxml2t64)	trivial per-app
bazarr	same libxml2 rename	trivial per-app
calibre-web	lxml wheel: missing libxml2-dev / libxslt1-dev in build deps	trivial per-app
home-assistant	apt install fails on resolute (binutils/bluez/cups/udev set) — needs deeper triage	medium
sickgear	upstream tarball 404	medium (upstream URL change)
deluge	pip install libtorrent → no distribution for py3.14	upstream blocker
pyload-ng	pydantic-core 2.27.2 → PyO3 0.22 rejects Python 3.14	upstream blocker
znc	modpython SWIG bindings don't compile against Python 3.14 (SWIG_Python_str_AsChar undeclared)	upstream blocker

Why no commits yet

• Agent contract: one app = one branch = one PR.
• Environment: cannot open new PRs from this session, only push to this one.
• 3–4 failures are real Python-3.14 incompatibilities and won't be fixable in apps/<app>/ without bumping (or waiting on) upstream releases — or reverting the base.

Decision needed

1. Bundle the trivial fixes (apprise-api, babybuddy, bazarr, calibre-web, home-assistant) here and report the rest on the issue.
2. Fix one app only, comment the rest back on the issue.
3. Treat as an apps/python regression and pin the base image back to Python 3.13 / Ubuntu 25.x — likely resolves most failures at once.