The e2e image built 0.19.19 while PLAN decision 19 and every task doc name 0.19.20 as the target and strictness ceiling — and the behaviours tasks 13, 14, 15 and 17 were written against were read from 0.19.20's source. So the suite was proving compatibility with a version we had not studied, and the studied version was never exercised. Either half alone is defensible; the pair is not. Suite green on the bump: tests/e2e ok in 267s, no other change required. One note for whoever runs this next: the first attempt failed with Postgres connection-refused from both tidepool-migrate and lemmy, immediately after the Rust rebuild. That is a startup race under a saturated machine, not a version incompatibility — a re-run against the cached image passed untouched. A full Lemmy build from source and `docker compose up` should not be judged on the same pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>