feat: add structured logger and replace server-side console usage

[chavanGaneshDatta]

Description

Fixes #4915

Summary

Implemented a structured logging system for server-side runtime services.

Changes Made

• Added lib/logger.ts with:

  • debug()
  • info()
  • warn()
  • error()

• Added environment-aware logging behavior:

  • Development: human-readable console output
  • Production: structured JSON logging

• Suppressed debug and info logs in production.

• Replaced server-side console.warn() and console.error() usages with structured logger methods across:

  • Dashboard pages
  • API routes
  • Cache utilities
  • GitHub integration utilities
  • Contributors page

• Added lib/logger.test.ts covering:

  • Debug logs are silent in production
  • Info logs are silent in production
  • Error logs are emitted in production
  • Production log output is valid JSON

• Updated affected tests to match the new logging implementation.

Example Production Output

{
  "level": "error",
  "msg": "Failed to fetch notification preferences",
  "route": "/api/notify",
  "timestamp": "2026-06-09T12:00:00.000Z"
}

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

N/A (logging infrastructure change)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run format and npm run lint locally and resolved all errors.
• My commits follow the Conventional Commits format.
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that I have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard.
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@chavanGaneshDatta is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🚨 Hey @chavanGaneshDatta, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod-Dev]

Great initiative! A structured logger is much more scalable and easier to index in production environments than raw console usage. Approving!

[Aamod-Dev]

Excellent telemetry refactor! I went through the changes and replacing raw console logs with a structured JSON logger provides massive observability improvements for production monitoring.
Labels applied:

• level:advanced: Custom structured logger implementation.
• quality:clean: Perfect environment fallbacks.
• ype:feature, ype:refactor: Modernizes the architecture.