Repository navigation
CI: monitor deployed BrainBurst and bilingual debate guides; activate source diagnostics tests - #128
Merged
appdevelopsk merged 4 commits intoNov 14, 2026
Conversation
…e-vs-live inventory
…nd workflow changes
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.
Actual production defects being monitored
The main-branch VPS smoke is red and the app-site VPS is still behind source. A previous owner-readonly source-vs-public deployment inventory checked only 12 URLs, omitted
/support/brain-burst/even though sync-pages #43539163983 identifies that route as STALE, and omitted both newly released sitemapped AI debate practice guides (English and Japanese). Thediagnose_growth_deploy.pyunit tests existed but had never been invoked in app-discovery CI. They also imported as bare modules which failed under rootpython3 -m unittest scripts.test_....Change
Validation and guardrails
Exactly five source/CI files (zero behind main when authored). Native PR QA must succeed before merge. The existing public post-merge smoke will intentionally fail until an owner-approved VPS release publishes the current 46-file verified ZIP. This PR performs NO deployment, DNS change, IndexNow request, store release, social post or GA4 event. The diagnostic report shows public source mismatch and must not be read as a verified live release SHA or as user growth.