Repository navigation
CI: inventory all stale public growth routes after failed live smoke - #121
Merged
appdevelopsk merged 3 commits intoNov 13, 2026
Merged
Conversation
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Observed problem
Latest app-site live CI fails on the first stale VPS route (catalog five-language selector). The first failure is valid, but it stops before checking whether five press locales and additional support pages have been deployed. This creates serial release triage work while
mainis demonstrably ahead of the public VPS.Changes
continue-on-error.diagnose_growth_routes.py(catalog aliases and five press locales) anddiagnose_growth_deploy.py(12 source/live pages), without campaign query parameters.Safety
Verification
GitHub source readback confirms two existing diagnostic commands, failure-only execution, artifact retention, 4 source test cases, QA references and no main divergence. Await native PR runner validation before merge.
Follow-up
Use the reported route inventory to execute the existing authorized
publish to VPSmanual release and verify live pages. Do not count code merge as a deployment.