docs(launch): add role-based beta onboarding journeys

[JSONbored]

Background

The docs should support beta activation by role. They should explain how to get useful output, not just describe APIs.

Goal

Update docs/site content around role-based onboarding journeys.

Current Behavior

Docs explain installation and concepts, but adoption will need clearer role-first paths as the control panel and GitHub agent evolve.

Desired Behavior

A miner, maintainer, repo owner, or operator can quickly find the right setup path and first useful action.

Implementation Requirements

• Document miner MCP flow.
• Document maintainer GitHub App setup and command usage.
• Document repo owner readiness/config workflow.
• Document operator usage/value/drift reporting.
• Keep Gittensory positioned as a base-agent/control-plane product, not an official Gittensor frontend.

Public/Private Output Boundaries

Public GitHub output must never include wallets, hotkeys, payout/reward estimates, raw trust scores, public score estimates, private reviewability, private scoreability context, or farming language. Private API/MCP/control-panel surfaces may show authenticated scoreability, blockers, projections, and evidence, but must not claim guaranteed payout outcomes.

Acceptance Criteria

• Miner journey: install MCP, login, doctor, agent plan, preflight, packet.
• Maintainer journey: install GitHub App, configure settings, preview public surface, use commands.
• Repo owner journey: readiness report and config guidance.
• Operator journey: usage/value report and drift status.
• Docs do not present Gittensory as an official Gittensor frontend.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, source-upload safety, public/private boundaries, or telemetry privacy.
• MCP/local tooling must prove source contents are not uploaded when local metadata is involved.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.