Clarify Doctor readiness states

[fly1d]

Decision

Doctor should say that a failure is ready to reduce only after its fresh-copy baseline passes. A successful scan without a command is useful preflight evidence, but it is not reproduction evidence.

Context

repomin doctor SOURCE previously mapped every result with no failed checks to ready, even when baseline.status was not_run. That can send a first-time user into reduction before they have configured or verified the target failure.

Changes

• text output distinguishes static checks passed; failure not verified, ready to reduce, and needs attention;
• Markdown uses static_checks_passed, ready_to_reduce, or needs_attention;
• next-step guidance follows the overall readiness, so a passing baseline cannot hide another failed check;
• the Doctor guide and changelog document the distinction and Markdown value change.

Verification

• python -m unittest tests.test_doctor -v (44 passed)
• python scripts/check_contribution.py --skip-tests
• complete local suite before the final narrow review correction (767 passed, 4 skipped)
• offline benchmark suite (16 passed)
• manual CLI checks for static-only and 2/2 passing-baseline output

GitHub CI will run the complete suite on this exact commit.