01
Start with the artifact
Run route discovery, doctor, build, checks, and analyzer before guessing. Compare source boundaries with emitted HTML, manifest, runtimes, and chunks.
02
Diagnose boundary failures
For non-working interaction, inspect data-nx-on-* and data-nx-scope, chunk paths, serializability diagnostics, and the browser network request triggered by first intent.
03
Keep operational failures separate
Route resolution, missing public assets, sitemap/feed origins, edge adapter differences, test ports, stale processes, and performance regressions each need their own evidence path.
PRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Start at the artifact
Shellpnpm exec nexis doctor
pnpm exec nexis routes
pnpm build
pnpm analyze- OUTPUT
- Diagnostics separate route discovery, build output, and delivery assets before browser debugging.
- BOUNDARY
- Do not hide flaky behavior by rerunning tests until green.
- PROVE IT
- Capture the route, command, generated file, server log, network trace, and minimum reproduction.
VERIFICATION
Prove the contract.
Capture the route, command, generated file, server log, browser network trace, and minimal reproduction before filing a framework issue.