[Backend] scoreDecayJob is never scheduled or invoked, so inactivity score decay never runs in production

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

src/cron/scoreDecayJob.ts:33 exports runScoreDecayJob as default, but a repo-wide grep shows it is referenced only by its own test. src/index.ts wires every other scheduler (startIndexer, startDefaultCheckerScheduler, startWebhookRetryScheduler, startScoreReconciliationScheduler, startNotificationCleanupScheduler, startLoanDueCheckCron at lines 59-74) but never imports or calls runScoreDecayJob. The decay job has no cron.schedule/setInterval wrapper at all, so it executes nowhere. This is distinct from the borrowers-table bug: even with that table fixed, decay still never runs because nothing calls the job.

Acceptance criteria

• Wire score decay on a recurring schedule (e.g., daily cron) in index.ts startup, mirroring the other schedulers
• Add a matching stop on SIGTERM/SIGINT in the index.ts shutdown path
• Guard against overlapping runs and skip in NODE_ENV=test like the other schedulers
• Record jobMetricsService success/failure (the job already calls it) so a missing run is visible in /metrics

Files to touch

• backend/src/cron/scoreDecayJob.ts
• backend/src/index.ts

Out of scope

• Fixing the non-existent borrowers table
• Changing decay formula

[warisu]

@warisu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to handle this in less than 12hrs

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

[dikachim060-wq]

@dikachim060-wq has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hello i would like to work on this issue please

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

[damzempire]

@damzempire has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would like to work on this issues as a full stack developer

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

[drips-wave]

Congratulations, @warisu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @warisu: 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 🌊

[grantfox-oss]

🦊 GrantFox — @warisu has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1199)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@warisu's PR #1276 was approved and merged by @ogazboiz.

🏆 @warisu: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (328 total points). Track your full progress on GrantFox.

👏 Great work, @warisu! Keep contributing to LabsCrypt.