Skip to content

chore(roadmap): triage stale v1 PR queue into land/replace/close buckets #239

Description

@JSONbored

Parent phase: #233
Parent roadmap: #127

Problem

The v1 PR queue has a mix of useful work, stale/conflicting branches, missing UI evidence, and deterministic CI blockers. Maintainers need one explicit land/replace/close pass so the roadmap stops being blocked by ambiguous PR state.

This is the immediate roadmap hygiene gate before advanced Phase 6 work becomes active.

Acceptance criteria

  • Every open v1 PR is assigned to land, replace, or close with a concrete reason.
  • UI/frontend/extension PRs without actual screenshot or recording evidence are marked as not acceptable until evidence is supplied.
  • Mechanical blockers are separated from product/design blockers.
  • Replacement work is linked to the relevant roadmap phase instead of leaving stale PRs as the active path.
  • Current review-required PRs are separated from stale dirty/changes-requested PRs.
  • New Phase 6 issues stay future-facing and do not distract from clearing the active queue.

Validation expected

  • Open PR list reviewed against current checks, merge state, and review state.
  • Maintainer queue summary updated with no code/repo file mutation required.
  • Branch protection/check-state notes are kept separate from reviewer/mergeability state.

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.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions