fix: release TypeType 1.7.2

[Priveetee]

Summary

• publish the TypeType 1.7.2 hotfix notes
• advance the TypeType-Token pin to the reviewed 1.7.2 merge revision
• keep every other component pinned to its existing release revision

Production behavior

• rejected anonymous YouTube playback identities are discarded
• fresh BotGuard and PO-token material is generated before retrying
• SABR session creation remains bounded to one identity rotation

Deployment requirements

No frontend change or manual database migration is required. The stable Token image is ghcr.io/typetype-video/typetype-token@sha256:05d7323290cc7b0354b4f4e7d5f8e3123aed31fc78e4a480b856cc92655da253.

The public instance also stopped routing YouTube traffic through the rejected IPv6 egress path.

Runtime verification

• the public instance runs Token 1.7.2 at revision 888e91d1c26b
• repeated public SABR bootstrap checks returned complete sessions for the three affected videos and the control video
• Chromium playback advanced continuously for two affected videos with readyState 4, growing buffered ranges, no media error and no failed SABR request
• Token and Server remained healthy, with no LOGIN_REQUIRED, failure or exception in their post-rollout logs

Tests

• Token PR fix: use preopened iOS tab for download prompt #16: 99 tests, lint, type checks, build and dependency audit
• isolated real-network Token probes for four public VODs
• stable multi-architecture image publication
• git diff --check

Rollback

• restore the TypeType-Token pointer to 87c6e7e4a3d8
• restore the previous stable Token image digest sha256:18e425d86ca299be89c80fbff3e4d7bd0ae549d3bbc092347bc6d76ca0202a28
• restore the previous production environment from the recorded deployment backup
• no database rollback is required