roadmap(phase 2): maintainer trust and browser extension

[JSONbored]

Parent roadmap: #127

Goal

Make maintainers trust Gittensory inside the GitHub review flow: private context stays private, public output is previewable/sanitized, the extension has real screenshot-backed states, and repo maintainers can see exactly what the GitHub App will do before enabling it.

Existing tracked work

• feat(control-panel): add maintainer control panel #130: maintainer control panel.
• feat(extension): scaffold GitHub overlay browser extension #145: extension scaffold.
• feat(extension): add PR sidebar Gittensory context panel #146: PR sidebar context panel.
• feat(github-agent): add repo and docs context Q&A from connected sources #142: repo/docs context Q&A from connected sources.

Completed foundation to link, not reopen

• feat(control-panel): add public-safe preview simulator #135, feat(github-agent): add @gittensory command router v2 #140, feat(github-agent): add public-safe answer cards with citations #141, feat(github-agent): add maintainer digest and queue commands #143, feat(github-agent): add command usefulness feedback loop #144, feat(extension): add public-safe packet and private blocker actions #147, feat(extension): add secure auth and session handling #148.

Done when

• Maintainers can preview public GitHub output before it is posted.
• Private review context never leaks into public GitHub surfaces.
• Extension review states include screenshots or recordings for the changed UI.
• GitHub App installation and command permissions are clear enough for repo owners to trust.

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.