roadmap: contribution quality & adoption wave

[JSONbored]

Continues: #127 (ecosystem adoption v1)

Goal

Make Gittensory the gittensor-native quality + planning layer that a contributor's own AI harness (Claude Code, Cursor, Codex) cannot replicate, and surface it where people already work. The wedge is a shared, deterministic "real contribution vs AI slop" definition: help miners ship real PRs and help maintainers enforce quality — the #1 maintainer complaint about Gittensor work. We deliberately do not try to be the code agent.

Pillars

• roadmap(pillar 1): anti-slop contribution quality layer #526 — Pillar 1: anti-slop contribution quality layer
• roadmap(pillar 2): surfaces — browser-extension rebuild & notifications #527 — Pillar 2: surfaces (browser-extension rebuild & notifications)
• roadmap(pillar 3): maintainer CI power-ups #528 — Pillar 3: maintainer CI power-ups
• roadmap(pillar 4): foundations & learning loop #529 — Pillar 4: foundations & learning loop
• roadmap(pillar 5): MCP miner intelligence deepening #544 — Pillar 5: MCP miner intelligence deepening
• roadmap(pillar 6): general product & non-gittensor reach #704 — Pillar 6: general product & non-gittensor reach
• roadmap(pillar 7): metagraphed ecosystem integration #705 — Pillar 7: metagraphed ecosystem integration

Related existing work (reuse, do not duplicate)

• [Feature]: Cross-repo queue health federation and comparative pressure index #479 cross-repo queue-health federation (reused under pillar 3)
• feat(agent): add repo-specific scenario simulator #271 scenario simulator, feat(agent): add replayable decision snapshots #270 replayable decisions (depth, under roadmap(phase 6): advanced contribution operating layer #269)
• MCP release due: 0.5.0 #321 / feat(mcp): expose decision-pack and doctor resources #292 / feat(mcp): add maintainer and repo-owner workflow prompts #294 / test(mcp): add resource and prompt discovery fixtures #295 MCP release + native resources/prompts
• [Bug]: Over-long focus-manifest list entries bypass both de-duplication and the MAX_LIST_ITEMS safety cap #522 / [Bug]: Pre-auth rate limits collapse to unknown-ip when cf-connecting-ip is absent, so one client can throttle everyone behind fallback proxies #477 / feat(issues): respect declined (closed) contributor-issue drafts to stop re-proposal churn #517 stability + correctness hardening

Done when

• A miner can self-check slop risk locally and receive the gittensor rubric before opening a PR.
• A maintainer can enable a slop gate + per-line check annotations and view quality trends.
• The browser extension serves both miners and maintainers, and a miner is alerted the moment a review requests changes on their PR.

Cross-cutting acceptance criteria

• npm run test:ci passes; 97%+ global coverage. No source upload from miner tooling (fail closed).
• Public output never exposes wallets, hotkeys, reward estimates, raw trust scores, public score predictions, private reviewability/scoreability, or farming language.
• Advisory-only / human-in-the-loop preserved: gates default to advisory, never auto-merge or auto-submit.

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.

---

Wave 1 — remaining after the 2026-06-17 discovery sweep → Milestone M1 (due 06-22)

Backend is largely shipped; remaining work is dashboard surfaces + write-safety bugs + email. Detail: docs/roadmap/discovery-sweep-findings.md.

• Frontend control surfaces (the bulk): feat(control-panel): add miner command center #129 feat(control-panel): add maintainer control panel #130 feat(ui): maintainer repo/org quality dashboard #539 unified miner+maintainer cockpit (dual-role home) #700 one-step maintainer activation / instant-value onboarding #701 + net-new feat(ui): audit feed / skipped-PR viewer #792 (audit feed) feat(ui): cross-cutting error/loading/empty states + retry #793 (error/loading states) feat(ui): responsive/mobile + accessibility pass #794 (responsive/a11y) feat(ui): analytics role-specific breakdowns + cohorts #795 (analytics breakdowns)
• Maintainer-CI cluster (also the Phase-1 prereq): feat(github-app): per-file/line check-run annotations #537 feat(github-app): gate appeal/override command + configurable settings #538 feat(signals): advisory reviewer routing via CODEOWNERS + load #540 feat(github-app): merge-readiness aggregate gate #551 feat(github-app): first-time-contributor-aware gating #552 feat(github-app): new maintainer @gittensory commands #553 feat(github-app): focus-manifest policy as gate input #555 feat(api): maintainer quality-dashboard service + endpoint #557
• Reliability / write-safety bugs: [Bug]: transient 403 at Gate finalize still orphans the check (P1) #785 [Bug]: webhook enqueue failure strands event as queued with no recovery (P1) #786 [Bug]: per-login batch jobs are poison-pill-prone (no per-item isolation) (P1) #787 [Bug/write-safety]: command authority conflates org MEMBER with repo maintainer (P1, agent-layer prereq) #788 (write-safety prereq) [Bug]: webhook redelivery re-runs non-idempotent side effects (P2) #789 [Bug]: fetchPublicContributorProfile has no timeout and is unauthenticated (P2) #790 [Bug]: contributor stat aggregation can split one user across two casings (P2) #791
• Wiring: [Bug]: MCP contract references /v1/local/branch-analysis route that may not exist #796 feat(config): audit repository-settings flag enforcement #797 [Bug/privacy]: focus-manifest public-safety redaction may be applied inconsistently #798 chore(mcp): add outputSchema to tools that lack it #550
• Email channel: feat(notifications): email delivery channel #570 · Priority docs: docs(launch): create miner quickstart by contribution lane #252 docs(launch): create repo-owner onboarding checklist #254 · Visual-agent epic: owner-led: visual-change PR auto-review (before/after screenshots) #577 owner-led(visual-agent): visual-change detection + affected-route mapping #579 owner-led(visual-agent): R2 image hosting + managed PR comment #583 owner-led(visual-agent): optional LLM visual review + verdict #584 (others in PR)
• Verify-and-close candidates (shipped per code audit — confirm vs acceptance): implement upstream TIME_DECAY_* scoring dimension (deferred; owner-reviewed) #703 (closing now), feat(extension): rebuild as dual-audience overlay (WXT + React) #534, feat(notifications): event-to-subscription-to-delivery service #535, feat(notifications): D1 data model + idempotency guard #567, feat(notifications): queue jobs (notify-evaluate/deliver) #568, feat(notifications): extension-badge delivery channel #569, slop expansions feat(signals): slop signal — no linked issue without rationale #562–feat(signals): slop weight tuning + golden-fixture tests #565/feat(github-app): deterministic slop gate (slopGateMode) #571/feat(github-app): opt-in LLM slop augmentation #572 (note: feat(signals): slop signal — generated/vendored/dependency/docs matchers #561 closes via PR feat(signals): add slop path matchers and non-substantive-padding signal (#561) #752)

Next wave

• Unblocks → roadmap: Wave 2 — Agent Layer (auto-maintain + auto-development) #772 Wave 2 — Agent Layer (auto-maintain + auto-development)

---

⭐ Immediate focus → #805 — PMF: non-registered → gittensor onboarding funnel (Milestone M0, due 06-20)

The prioritized front of Wave 1: prove the onboarding funnel on awesome-claude / gittensory / metagraphed before scaling. Children #799–#804.

---

🔄 Upstream sync → #814 — gittensor scoring-sync hardening + parity

Keep scoring/outcomes/planning in parity with entrius/gittensor. 2 correctness bugs to M0 (#806/#807); parity+hardening #808–#812; upstream watch #813 (incl. gitt miner advisor #1460).