[alexey-igrychev]

Summary

Website deployment, registry cleanup and content validation use werf from group 3 alpha instead of group 3 dev.

What

• All six CI setup-app invocations select group 3 and channel alpha.
• Repair the obsolete Habr URL and replace the unavailable VPA article with upstream documentation.
• Local development tasks retain their existing fallback version.

Why

Use the alpha promotion channel for operational CI instead of consuming every dev release.

[alexey-igrychev]

Verification

• All checks passed for head 7be1fb7b21acf83671d6f6f9561c7d388ddf281b: broken links, English and Russian spelling, DCO.
• Repaired the obsolete Habr URL and replaced the unavailable VPA article with upstream documentation; the replacement targets return HTTP 200.
• The initial content-validation run selected the v3.12.1 installation path after a 3/alpha cache miss. This proves the selected binary path, not an independently logged runtime werf version.
• Independent review found no issues. No link-check exclusions or TLS checks were weakened.