Skip to content

feat(scoring): pull + model upstream constants not currently fetched #809

Description

@JSONbored

Found in the 2026-06-17 scoring-sync audit.

Problem

Scoring-relevant upstream constants are dropped by the knownOnly parser (absent from SCORING_CONSTANT_NAMES, model.ts:46): MAX_OPEN_PR_REVIEW_COLLATERAL_MULTIPLIER=2.0, MAX_LINES_SCORED_FOR_NON_CODE_EXT=300, DEFAULT_ISSUE_DISCOVERY_SHARE=0.5. The first two directly affect score/density (open-PR review collateral, non-code line cap).

Deliverable

  • Add to SCORING_CONSTANT_NAMES; model open-PR review-collateral multiplier + non-code line cap in preview.ts
  • Use DEFAULT_ISSUE_DISCOVERY_SHARE as the upstream default for issue-discovery share

Outcome

Scoring matches upstream for review-collateral and non-code line handling. Milestone M1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)upstream-syncParity/sync with upstream entrius/gittensor scoring model

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions