Reconcile post-merge and peer-lane readiness truth

[YuzeJ21]

What changed

• reconcile post-merge project-status, next-stage, readiness command, and active documentation truth
• make selected Data Health readiness counts prefer evidence-backed saved readiness while preserving project-status fallback
• keep explicit saved zero authoritative and prevent incomplete saved reports from promoting synthesized zeroes
• keep source-setup counts project-status-only and align Personal, Public, and Operator peer-lane behavior
• label peer_ready accurately as mapped peer trend context, without implying a reviewed peer relationship or peer-valuation readiness
• add the approved design, implementation plan, and focused regression coverage

Why

After PR #113 merged, several status and continuation surfaces still reflected the pre-merge lifecycle. Separately, selected peer-lane answers could use a stale project-status count instead of the selected profile's evidence-backed saved readiness, and the visible “trusted peer context” label overstated the underlying mapped-price trend gate.

This PR restores fail-closed source precedence and keeps reviewed-peer and peer-valuation gates independent.

Impact

Researchers see consistent saved-readiness counts across Personal, Public, and Operator Data Health. Missing or malformed evidence falls back safely or remains unavailable, while candidate peers stay context-only. No readiness calculation, threshold, generated artifact, provider, or source-rights decision changes.

Verification

• cache-safe full suite: 6,725 passed, 1 known third-party warning
• dashboard helper suite: 1,132 passed
• affected route-render tests: 3 passed
• current-byte browser proof: 2/2 passed at desktop and phone widths
• independent review: READY, 0 Critical and 0 Important findings
• diff checks clean
• all 18 protected generated/data paths remained unstaged and byte-identical

Boundaries

• draft for human review
• research-only; no recommendation, ranking, allocation, sizing, transaction, or performance behavior
• no generated-data mutation, provider refresh, readiness materialization, deployment, publication, or release action