Blank Or Stuck
A page did not render expected cards
Use runtime and container checks to see whether data, route manifest, or page wiring is the likely problem.
Diagnostics
Check page wiring, live data state, and runtime assumptions from one place.
This is a lightweight internal view for finding missing containers, stale routes, and feed/runtime drift before they turn into confusing blank sections.
Use Diagnostics When
Something feels broken, not when you are choosing content
Android App
The WebView trainer behaves differently
Check app shell markers, local storage, rail model, last URL, app version, network state, and API contract assumptions.
Large Batch
You changed many pages at once
Use release, readiness, manual QA, and fragile-area checks after big site or app batches before trusting the public route.
Runtime Health
What the current browser session can see
Product Quality
Metadata, navigation, and page coverage checks
App Contract
Android shell markers and app-facing API assumptions
Performance And Payload
Browser timing, payload estimates, cache state, and asset checks
Release Dashboard
Public launch files, sitemap readiness, and local feedback
Launch Readiness
Practical checks before adding more content or publishing changes
Manual Browser QA
What to test later on desktop and mobile
Known Fragile Areas
Places most likely to reveal regressions after large batches
Route Manifest