Автоматическое доказательство
Repository-native clean URLs PR #114
Состояние: merged
Что подтверждает: PR #114 moved public page identity to directory routes, cleaned internal links and SEO/feed/search outputs, and retained legacy .html as noindex compatibility entrypoints. It proves the repository-only route contract; GitHub Pages still cannot emit repository-configured HTTP 301 redirects.
Открыть доказательство ↗
Автоматическое доказательство
Portfolio 1.0 P3.1 exact-head Build #836
Состояние: green
Что подтверждает: Exact head 67d3f6593c45d1239630f71be6a3cb15a33f4519 passed 360 unit contracts, generated-site integrity, browser accessibility, Lighthouse, Firefox/WebKit, search, RU/EN, analytics, metadata, visual regression and custom-domain artifact checks. This proves repository and generated-artifact readiness, not deployment.
Открыть доказательство ↗
Автоматическое доказательство
GitHub Pages deployment #147
Состояние: published
Что подтверждает: Pages #147 published accepted squash fe1a796df37313401c07e25c0672dc32db30a1c4 through the configured GitHub Pages pipeline. This proves deployment identity and publication completion, not live browser behavior or search-engine indexing.
Открыть доказательство ↗
Автоматическое доказательство
Production Live Smoke #58
Состояние: passed
Что подтверждает: Deployment-driven Production Live Smoke #58 resolved the exact successful Pages build and verified the deployed homepage, canonical clean routes, legacy compatibility, generated search, Atom feed, favicon, analytics boundary and absence of browser/request errors. It does not prove audience growth, engagement or immediate search-index replacement.
Открыть доказательство ↗