Deployments failing with "Failure during content distribution" — zero correlation with repo content, tested extensively

The blocker: deployments are currently broken, unrelated to any of this.
Since yesterday's last successful deploy, every single push to main has failed at Azure's "content distribution" step — tested exhaustively:

Full Telegram feature added → failed
Symlinks removed (unrelated pre-existing issue) → failed
Everything fully reverted to the last known-good state → failed
A single-line trivial comment change → failed
Pushed from a second computer → failed
Waited 15 min between attempts → failed
Regenerated the deployment token → failed
Service Health shows no incidents

This rules out repo content, dependencies, size, symlinks, timing, and the deployment token as causes. It's a stuck/broken state on Azure's side for this specific resource.

Start with the Azure deployment's "content distribution" failure and compare it with the last known-good deployment. Review the issue's reproduction attempts, including the reverted state and regenerated token; done means deployments succeed again or the Azure-side resource failure is confirmed and actionable.

Written by the indexing model from the issue text.