Fix dashboard readiness gauge and topology

[dorkalev]

What changed

• imports the deterministic verifier's signed design, technical, and operating dimension summaries
• measures observation coverage as the percentage of checks with a known verdict
• calculates the readiness gauge as the equal-weight mean of those four dimensions
• derives the dashboard subject from the signed report instead of rendering an unnamed organization
• describes the actual main-only, solo-founder workflow and marks model review as optional and off by default
• documents what a 100% machine-readiness score does and does not mean

Why

The dashboard independently reconstructed readiness from criterion credit, so a signed 100/90/100 report with no unknowns rendered as 54%. Its workflow map also described a retired staging topology and presented optional model review as a required gate.

Impact

The dashboard now presents the same bounded readiness result as the signed verifier report. The current Genesis report deterministically renders 97.5%, and the one remaining failing technical control remains visible rather than being obscured by an unrelated formula.

Validation

• cargo test --manifest-path website/app/Cargo.toml --locked (7 passed)
• rendered the current 40-check Genesis report locally and verified 97.5%, 100/90/100/100 dimensions, repository identity, and main-only topology

Closes #16