Feature/score bounds 1197

[warisu]

📝 Pull Request Summary [Wave 200pts]

Description

This PR addresses Issue #1197, hardening database integrity bounds by introducing a strict database CHECK constraint enforcing the standard 300–850 scoring index.

Key Modifications

• Idempotent Data Backfill: Added a transactional preprocessing batch script in the migration path to clean and clamp legacy database entries ahead of time.
• Database Contraband Guards: Attached the chk_score_range constraint via raw migration commands to reject stray manual modifications or query bugs trying to commit anomalous numbers.
• Service Boundary Sync: Confirmed application query scripts map to the structural constraint cleanly without disrupting operational code execution.

Target Branch: main
Closes #1197

[ogazboiz]

conflicting with main (it touches the initial-schema migration + scoresService, which have both moved), please rebase and i'll review the score-bounds logic and the requestLogger changes: git fetch origin && git rebase origin/main && git push --force-with-lease.

one thing to reconsider while you're in there: this edits backend/migrations/1771691269865_initial-schema.js, the initial migration that's already been applied in every environment. schema changes should almost always be a NEW migration rather than an edit to an applied one (editing it won't re-run anywhere it's already applied). worth splitting the score-bounds schema change into its own new migration.

if you want to keep contributing, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0