Evidence driver for [issue #38057](https://github.com/pingdotgg/t3code/issues/38057).

This is a real Debian packaging/install comparison, not a unit test or web scenario.
The web scenario runner does not exercise Debian dependency resolution.

1. Install dependencies with `vp i` in isolated checkouts of [10784e01f8](https://github.com/pingdotgg/t3code/commit/10784e01f8b5158ef0f6d61ebd19a8963c45579d) and [60561d584b](https://github.com/pingdotgg/t3code/commit/60561d584bb7dbc3ebad377e6ca018f105d4893e).
2. Download [0.1.9 amd64](https://github.com/pingdotgg/t3code/releases/download/v0.1.9/T3-Code-0.1.9-amd64.deb) as `previous.deb` and [0.1.10 amd64](https://github.com/pingdotgg/t3code/releases/download/v0.1.10/T3-Code-0.1.10-amd64.deb) as `release.deb` in a scratch directory.
3. Run `python3 prove.py SCRATCH BASE_CHECKOUT HEAD_CHECKOUT` (requires Node with TypeScript support, Docker, readelf, dpkg-deb).
4. The driver extracts the release, runs each checkout's actual `linux-after-pack.ts`, writes its resolved dependencies into the original Debian control file, and builds a real package with `dpkg-deb`. It retains the released application binaries and package scripts. Compile-cache generation is skipped with the packaging hook's untrusted-bundle flag.
5. For each side, a fresh `ubuntu:22.04` container installs the other declared dependencies, installs 0.1.9, then upgrades to that side's 0.1.10 package with `dpkg -i`. Its output and installed package status are captured. No dependency is force-ignored.

The PNGs render the captured command transcript for inspection; they are not desktop screenshots. They show the installation portion, and the TXT files contain the full output. The first driver's supplementary KDE-helper invocation used a path without `(Beta)`; it was corrected separately and both helpers reached D-Bus after only a weak-version warning. This typo did not affect either installation run. The uploaded driver corrects the path.

Scope: this proves the changed packaging hook on the exact released payload and real Ubuntu 22.04 dpkg upgrades. It does not rebuild all Electron/frontend/native application components from source, launch the desktop GUI, or exercise the in-app updater. All 133 regular payload files had identical SHA-256 hashes between sides. No application data was seeded.
