feat(app): turn registration readiness into a guided owner workflow

[JSONbored]

Parent phase: #236
Parent roadmap: #127

Problem

Repo owners need a guided workflow that turns registration readiness into concrete actions: policy, labels, issue quality, PR queue pressure, maintainer burden, and docs readiness.

Acceptance criteria

• Owner workflow groups readiness into policy, data quality, queue health, docs/onboarding, and maintainer capacity.
• Each blocker has a concrete remediation action or reason it must remain manual.
• The workflow distinguishes accepted, needs cleanup, and not ready states.

Validation expected

• API tests cover readiness buckets and blocked/ready states.
• Screenshots show ready, partial, and blocked workflows.

UI evidence gate

Any visible web, browser-extension, or GitHub-overlay change must include maintainer-reviewable screenshots or a short recording covering the changed states. A checked template box without actual visual evidence is not enough.

Cross-cutting acceptance criteria

• Preserve the repo quality gate: npm run test:ci, 97%+ global coverage, and the local branch coverage target for touched code.
• Keep public/private boundaries explicit. Public GitHub output must not expose wallets, hotkeys, reward estimates, raw trust scores, public score predictions, private reviewability, private scoreability context, or farming language.
• Add/update focused tests for the changed behavior instead of relying on green checks alone.