Two issues found while verifying the live install:
1. pack.py produced a different zip MD5 for identical content, because zip
records file mtimes. Re-running pack.py would have rewritten the manifest
checksum while the already-published asset stayed the same, and Jellyfin
would then refuse the install with "The checksum of the received data
doesn't match." The zip entry now carries a fixed 1980-01-01 timestamp, and
--publish downloads the published asset back and compares its MD5 with the
manifest checksum before reporting success.
2. The legacy deploy.py tag lives in the on-disk index.html, so it was stripped
from every single response and logged at INFO each time (6 lines and counting
per boot on the live server). The message is now emitted once, and says what
it actually means: the tag is still on disk, run deploy.py rollback to clean
it up.
Verified: 21/21 rewrite checks pass, including a regression case built from the
tag actually present on the server.