Fix Repository Diagnostics

Run a closed diagnostic loop: establish the baseline, verify each finding, fix its root cause, rerun the finding's source, and report the remaining state.

1. Establish Scope

1. Work from the repository root and read the applicable repository instructions.

2. Inspect the worktree before editing. Preserve user-owned changes and identify files already modified by others.

3. Use the requested tools, files, rules, or findings as the scope. When the request gives no narrower scope, run all three project-wide diagnostics:

   nub run lint
   nubx tsc --noEmit
   nubx react-doctor@latest
   

4. Run diagnostics separately so each exit status and output remains attributable to one tool.

5. Record findings in stable tool-output order with their tool, rule or error code, file, location, and message. Record a command failure as a blocker, not as a clean result.