[Backend] Reputation engine: make scoring weights and thresholds config-driven, not hardcoded

[Baskarayelu]

Description

The reputation engine hardcodes scoring constants — BOND_SCORE_MAX = 50, DURATION_SCORE_MAX = 20, ATTESTATION_SCORE_MAX = 30, ONE_ETH_WEI, the 365-day cap, and the 5-attestation cap — directly in src/services/reputationService.ts and src/services/reputation/. Tuning the trust model requires a code change and redeploy, and there is no audit trail of weight changes. We should externalize these into versioned configuration so the model can be tuned and snapshotted.

Requirements and context

• Move weights/caps into src/config/index.ts (validated with Zod) with sane defaults preserving current behavior.
• Include a scoringModelVersion so src/jobs/scoreSnapshot.ts can record which model produced a score.
• Keep computeBondScore/computeDurationScore/computeAttestationScore pure but parameterized.
• Document the model in src/services/reputation/README.md.

Suggested execution

Create branch feature/config-driven-reputation.

• Refactor src/services/reputationService.ts and src/services/reputation/score.ts.
• Add config schema + validation in src/config/.
• Update src/services/reputation/score.test.ts and add config tests.
• Update docs/ reputation/model docs.

Test and commit

Run npm run test. Edge cases: default config == current scores (regression), invalid config rejected at boot, total capped at 100. Security: config from env validated, no eval.

Example commit message

feat: externalize reputation scoring weights into versioned config

Guidelines

• Minimum 95% test coverage
• Clear documentation in src/services/reputation/README.md
• Timeframe: 96 hours

[charliechinedu19-netizen]

@charliechinedu19-netizen has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hey gm, i'd love to take on this task real quick

ℹ️ Repo Maintainers: To accept this application, review their application or assign @charliechinedu19-netizen to this issue.

[drips-wave]

Congratulations, @charliechinedu19-netizen! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @charliechinedu19-netizen: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊