roadmap(phase 5): ecosystem distribution

[JSONbored]

Parent roadmap: #127

Goal

Make adoption easy across the Gittensor ecosystem: lane-specific launch docs, Raycast/PWA distribution where useful, maintainer queue notifications after the PWA research decision, and onboarding that explains why Gittensory is a contribution operating layer rather than another dashboard.

Existing tracked work

• feat(raycast): scaffold Gittensory Raycast extension #113, feat(raycast): add miner command center #114, feat(raycast): add maintainer queue commands #115: Raycast extension path.
• research(mobile): validate native mobile vs PWA for maintainer digests #150: mobile/PWA research.

Done when

• Miners have quickstarts by contribution lane.
• Maintainers have install/trust docs that explain public/private boundaries and review control.
• Repo owners have an onboarding checklist that clarifies readiness and expected maintenance burden.
• PWA/digest notifications are implemented only after the research decision supports them.

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.

MCP/CLI acceptance criteria

• Machine-readable JSON output is available where automation needs it.
• Token, wallet/hotkey, and local absolute-path redaction are covered by tests.
• Source-upload behavior remains explicit and fails closed where upload is unsupported.

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.