[Infra] Stricter tsconfig flags (noUnusedLocals/Parameters/ImplicitReturns/Fallthrough/ImplicitOverride) are commented out

[grantfox-oss]

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

Why this matters

backend/tsconfig.json:25-30 leaves noImplicitReturns, noImplicitOverride, noUnusedLocals, noUnusedParameters, and noFallthroughCasesInSwitch disabled. Enabling them surfaces dead code, missing returns, and switch fallthrough at build/typecheck time - the class of defects already being filed manually (e.g. dead route registrations).

Acceptance criteria

• Enable noUnusedLocals, noUnusedParameters, noImplicitReturns, and noFallthroughCasesInSwitch (at minimum)
• Fix or annotate resulting errors so npm run typecheck stays green
• Keep the eslint no-unused-vars argsIgnorePattern aligned

Files to touch

• backend/tsconfig.json

Out of scope

• exactOptionalPropertyTypes / noUncheckedIndexedAccess (already enabled)

[Banx17]

Hello Team I'd love to be assigned this issue. As a backend developer, I've experience across different frameworks, and I'm confident I'll be able to resolve this. Looking forward to it. Thanks

[thewealthyplace]

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

Hi maintainer, I’d like to work on this issue.

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

[Windowlight]

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

Hi, I'm interested in this issue and have experience with contracts, backend systems, and frontend implementation.
I've reviewed the issue requirements and my plan is to:
• Understand the existing implementation.
Implement the requested changes.
•Add tests where applicable.
•Submit a clean, well-documented PR.
I can start immediately and will provide regular progress updates as I work through the task.
Thanks for considering my application.

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

[drips-wave]

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

🧑‍💻 @thewealthyplace: 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 — @thewealthyplace has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.