feat: release TypeType 1.8.1

[Priveetee]

Summary

• Release TypeType 1.8.1 across the Frontend, Server, Token, Downloader, Player and documentation repositories.
• Improve playback reliability across YouTube, BiliBili and NicoNico, including MSE buffering, seeks, resume and mobile controls.
• Add profile-aware state, service-aware search and recommendations, and the multilingual Lemmy announcement.
• Simplify stack initialization and keep the verified component revisions pinned below.

Production behavior

• Frontend, Server, Token and Downloader are aligned with the 1.8.1 release line.
• TypeType-Player is aligned with MSE 0.1.60.
• BiliBili and NicoNico media remain behind the Server proxy and expiring opaque handles.
• Stack initialization uses one short-lived typetype-init service and preserves existing data volumes during updates.

Deployment requirements

• Publish and record immutable image digests for Frontend, Server, Token and Downloader.
• Deploy the verified image references to watch.typetype.video and watch.eltux.fr through the stable installer path.
• Run Garage and Downloader initialization without removing existing PostgreSQL, secret or artifact volumes.
• Keep the previous component SHAs, image digests and stack configuration as the rollback point.

Component revisions

• TypeType-Server: 945d59a25bb8c4ee9a979cd435c21cecb23af40c
• TypeType-Frontend: f19386cb44f2cda189e66659afcd9428e76587e0
• TypeType-Player: 8eb0027f5270b78d9cb17657662868e66b71738d
• TypeType-Token: b91a2a7683a8d3839abf4f4aa4f4031189d5cb29
• TypeType-Downloader: 321a4870673313643d531eee4faf44e1820d5d3e
• Docs-TypeType: e8183d0dc1227737b9c191167f9d4a3195543cf9

Runtime verification

• Check health, API instance metadata and the watch route on both production domains.
• Verify YouTube, BiliBili and NicoNico playback, exact resume positions, provider changes, mobile controls and bounded buffering.
• Confirm profile switching, service-aware recommendations, notifications and search after deployment.
• Record container health, image digests, logs, volumes and failed requests before declaring the rollout complete.

Tests

• Component PR checks passed for Server, Frontend, Token, Player and Downloader, including coverage and image builds where applicable.
• Central stack validation passed on the dev candidate, including Compose and installer checks.
• Full post-deployment runtime checks are required before treating this release as complete.

Rollback

• Restore the previous component image digests and gitlinks, then rerun the rollback procedure from the maintenance documentation.
• Keep PostgreSQL, secret, Garage and Downloader artifact volumes intact during rollback; do not use docker compose down -v.