perf(cli): isolate leaderboard calculation

[rexdotsh]

Summary

• Split leaderboard calculation from database query and hydration logic.
• Extract score-provider initialization into a narrow module.
• Extract shared challenge query predicates from the broader challenge service.

Part of #190.

Motivation

The seed command only needs leaderboard calculation and score-provider functionality, but its imports previously traversed broad API service and provider barrels. This pulled unrelated provider SDKs and services into the seed dependency graph, preventing Bun from tree-shaking them.

The new module boundaries allow the seed entry point to import only what it uses.

Bundle impact

Measured from apps/cli with:

bun build src/commands/seed/index.ts --target bun --minify

	Before	After
Seed entry bundle	3,174,547 bytes	941,101 bytes

This is a reduction of approximately 70%. AWS SDK, Nodemailer, and Google Cloud dependencies are no longer included in the seed graph.

This PR does not materially reduce the complete CLI bundle yet. Other CLI entry points still import the full provider barrel; those will be handled separately.

Behavior

Leaderboard query and calculation logic is unchanged; this is a module-boundary refactor.

Score-provider configuration is now validated when the scoring module is loaded rather than whenever the general provider barrel is imported. The API server continues to load it during startup through the leaderboard workers.

Verification

• Workspace typecheck passes.
• oxlint --deny-warnings passes.
• Server suite passes: 630 tests across 54 files.
• No stale imports of the removed leaderboard service remain.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[rexdotsh]

also - this is just a start, have some other changes lined up that would shrink the entire CLI, but thought i'd split em up to make it easier for you to review

[es3n1n]

since you moved the score provider to score.ts, maybe it would make sense to split all of them like this? probably in a new subfolder in providers though

[es3n1n]

sorry for the delays in my response, i was out of office this entire time 🙃

i will do a more thorough review later on this week

[rexdotsh]

since you moved the score provider to score.ts, maybe it would make sense to split all of them like this? probably in a new subfolder in providers though

yeah agreed, that's where the rest of the changes were also headed. i was thinking in providers/instances/? i think a followup PR for this might be better, or lmk, i can do it directly in this PR as well.

sorry for the delays in my response, i was out of office this entire time 🙃

i will do a more thorough review later on this week

no worries! hope you had fun at defcon :) (so much fomo lol)

[es3n1n]

yeah agreed, that's where the rest of the changes were also headed. i was thinking in providers/instances/? i think a followup PR for this might be better, or lmk, i can do it directly in this PR as well.

do you want to try these new github stacked prs for this?

[rexdotsh]

yeah agreed, that's where the rest of the changes were also headed. i was thinking in providers/instances/? i think a followup PR for this might be better, or lmk, i can do it directly in this PR as well.

do you want to try these new github stacked prs for this?

that'd be great but seems like it's not possible to do stacked PRs across different repos... since i’m sending these PRs from my fork, i think we could only use that if i had collaborator access here.

https://docs.github.com/en/pull-requests/get-started/about-stacked-prs#where-can-you-use-stacked-pull-requests

[es3n1n]

oof yeah, i see. makes sense.

you can just add these changes to this pr then i think

[rexdotsh]

oof yeah, i see. makes sense.

you can just add these changes to this pr then i think

yeah, all done

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[es3n1n]

Thank you!