Replace remaining console.* calls with the injected Nest Logger

[RUKAYAT-CODER]

Overview

The project ships a structured logging setup in src/logging/structured-logging.ts with correlation id propagation, yet several files bypass it. src/email-marketing/automation/automation.service.ts uses console.warn for an unknown action type; src/achievements/achievements.seed.ts uses console.log; and src/slack.service.ts contains three commented-out console.error/console.log lines where error reporting used to be. Output written through console directly does not carry the correlation id, the service name, or the structured fields the log aggregation pipeline under logging/ indexes on, so these events are invisible to log-based alerting and cannot be tied back to a request.

Specifications

Features:

• All application logging flows through the injected Logger.
• A lint rule prevents new console.* calls in src/.

Tasks:

• Replace console.warn in automation.service.ts with this.logger.warn, including the workflow and action identifiers as structured fields.
• Replace console.log in achievements.seed.ts with a logger instance appropriate to a seed script.
• Delete the commented-out console lines in slack.service.ts and implement real error logging there.
• Enable the no-console ESLint rule for src/** with a narrow exception for genuine CLI scripts.

Impacted Files:

• src/email-marketing/automation/automation.service.ts
• src/achievements/achievements.seed.ts
• src/slack.service.ts
• .eslintrc.js

Acceptance Criteria

• No console.* call remains in src/ outside explicitly-exempted CLI scripts.
• The replaced log lines carry correlation ids and structured fields.
• npm run lint:ci fails on a newly introduced console.log.

[adewaleomolara522-coder]

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

Hi Maintainer, I understand the problem and am confident I can provide a high quality fix, kindly assign this issue to me thanks

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

[DatboiCaleb]

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

Hi Good day Maintainer

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code. With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK and Soroban lets me ship real-world Web3 solutions that actually move value.

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

[nede110]

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

hi maintainer i will like to work on this issue please

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

[Chrisland58]

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

hi maintainer i will like to work on this issue please

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

[ajulaybeeb]

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

Hi Maintainer, haven reviewed the description of the issue, and well experienced with Js Library,
I would like to hop on the issue and sure to deliver at ETA 2hrs

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

[rabsqueen]

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

Hi there, I can work on this please assign

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

[drips-wave]

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

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