Skip to content

Remove scoring engine and close superseded issues #89

@rigomart

Description

@rigomart

Part of #82

Depends on: #88 + future dimension and verdict issues (TBD)

Summary

Once the three-layer system (verdict + dimensions + red flags) is fully in place and no code paths reference the scoring system, remove the scoring engine from the codebase. This is the final cleanup step.

What gets removed

  • Scoring enginesrc/core/scoring/engine.ts (main calculation), quality.ts (weighted signal scoring), freshness.ts (freshness multiplier and hard caps), profiles.ts (score-to-category mapping and thresholds)
  • Maintenance scoring APIsrc/core/maintenance/maintenance.ts and maintenance-config.ts (public scoring interface and category config)
  • Score-related UI componentsscore.tsx, category-info-popover.tsx, confidence-indicator.tsx
  • Score-related types — scoring types that are no longer referenced anywhere
  • Tests — scoring engine tests, maintenance score tests, any test fixtures that only exist to test scoring

What gets kept

  • Activity tier detection (src/core/scoring/signals.ts) — still used for contextualizing red flags
  • All data collection code — GitHub API queries, metrics extraction, Convex storage
  • Domain types for metrics snapshots — the data model is unchanged

Superseded issues

Close #61 ("idea: incorporate commit activity trend into score") and #70 ("feat: integrate commit activity into scoring engine and confidence penalties") as superseded — the scoring engine they aimed to improve no longer exists.

Acceptance Criteria

Metadata

Metadata

Assignees

No one assigned

    Labels

    signals-redesignMigration from score-based to signals-based analysis

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions