#632 Replace console.log statements with structured logger

[vic-Gray]

Replace all console.log calls with the application's structured logging service.\n\nWhy: Unstructured logs are unsearchable in production log aggregators.\n\nHints:\n- Search for console.log across backend/src/\n- Use the existing NestJS Logger or pino instance

[iGEORGE17]

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

Objective: Replace all unstructured console.log calls across backend/src/ with NestJS’s structured Logger system to ensure logs are traceable, categorized by severity, and fully searchable in production log aggregators.

Key Execution Steps:

Audit: Scan the source directory using regex to find and isolate all active console.log statements.

Refactor Components: Instantiate a class-scoped private readonly logger = new Logger(ClassName.name) within NestJS services, controllers, and providers.

Level Alignment: Convert basic console prints to explicitly leveled calls: standard info to .log(), system warnings to .warn(), and runtime catches to .error() along with their error stacks.

Standalone Fallbacks: Apply static Logger.log('message', 'Context') syntax inside global middleware, pipes, or bootstrap functions.

Validation: Run npm run lint to confirm all naked console logs are eliminated, verify structured formatting (timestamps, contexts, log levels) in the local console, and ensure the project passes npm run build.

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

[raphael-01-visual]

@raphael-01-visual has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Can I work on this issue ? ETA - 12hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @raphael-01-visual to this issue.

[drips-wave]

Congratulations, @raphael-01-visual! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @raphael-01-visual: 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 🌊