roadmap(phase 3): repo owner intake console

[JSONbored]

Parent roadmap: #127

Goal

Turn repo onboarding from a one-off config exercise into a guided owner workflow: intake readiness, focus manifests, issue-draft quality, direct-PR vs issue-discovery tradeoffs, and an onboarding pack for accepted Gittensory repos.

Existing tracked work

• feat(registration): create Gittensory self-dogfood registration pack #117: self-dogfood registration pack.
• feat(config): add Gittensory repo focus manifest #118: repo focus manifest.
• feat(issues): generate recommended contributor issue drafts from repo policy #119: contributor issue drafts.
• feat(control-panel): add repo owner registration workspace #131: repo owner registration workspace.

Done when

• A repo owner can see what is ready, what is risky, and what still needs policy/config cleanup.
• Maintainer burden tradeoffs are visible before inviting more miner traffic.
• Accepted repos can export an onboarding pack that gives miners clear, repo-specific contribution lanes.

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.

Public-output safety criteria

• Public text is sanitized before reaching GitHub comments, issue bodies, PR bodies, extension-visible public panels, or copied public snippets.
• Tests cover forbidden wallet/hotkey, reward-estimate, trust-score, public-score-prediction, private-reviewability, private-scoreability, and farming-language leakage.

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.