Version 2.0.0

The public repository is now a generic Bitrix infrastructure engine: a fresh clone boots the official Bitrix demo at http://localhost with no source changes (verified independently by three AI agents following only the README). Site-specific configuration lives in a private overlay repository and re-attaches via docker-compose.override.yml, nginx include globs and map-entry files — the pattern is documented in the README ("Production overlay") and is validated in CI on every change.

Breaking changes — migration guide for forks

1. Site vhosts, redirect maps, Metrika cookie pinning, CSP snippets, four Zabbix templates, PHPStan scopes, site cron jobs, the updater task list and bin/yandex-reviews left this repository. If you customised any of them, move your versions into your own overlay following the README pattern.
2. container_name: is gone from compose: docker exec nginx ... becomes docker exec <project>-nginx-1 ..., or pin names in your own docker-compose.override.yml.
3. Values now come from .env (see .env.example); check the defaults against your deployment: MYSQL_DATABASE defaults to bitrix (was favor_group_ru), DOCKER_MTU to 1500 (was 1450 — Yandex Cloud DDoS-protected IPs need 1450), HTTP_PORT/HTTPS_PORT to 80/443, TZ to Europe/Moscow (unchanged).
4. nginx carries no TLS material: certificate paths moved out of the shared files — declare them per vhost in your overlay (ssl.conf include pattern). CSP includes are now globs that tolerate absence; hotlink protection, X-Frame-Options and admin CORS are driven by maps extendable via private.conf.d/*.map. FastCGI HTTP_HOST uses the port-preserving $bitrix_host map.
5. Scripts now read site values from env files: backup scripts need private/environment/backup.env, seo-reindex.sh needs QUOTA_HOST in its env, urls.py needs SITE_URL and writes the redirect map to the overlay path.
6. New: localhost demo vhost, AGENTS.md + llms.txt for coding agents, and a validate CI workflow guaranteeing a fresh clone always passes nginx -t and compose config.