chore(logger): consolidate console.* behind a leveled logger

[jSydorowicz21]

@

Summary

Routes all console.* calls through a single leveled logger (src/core/logger.ts) with a configurable LOG_LEVEL (debug/info/warn/error, default info). error always appends to logs/errors.log; console output for every level is gated by LOG_LEVEL. The logger sanitizes CRLF from context/detail to prevent log injection, and no secrets/tokens are logged.

Changes

• src/core/logger.ts: leveled logger with file append for errors.
• Migrated console.* call sites across api.ts, attachments.ts, maestro.ts, providers.ts, transcription.ts, index.ts, and the Discord adapters/commands - including the 3 leftover calls in the Discord disconnect handler.
• src/core/config.ts: logLevel getter + clarified JSDoc (console output is level-gated; only the error file append is unconditional).
• .gitignore: add logs/ so runtime error logs are never committed.
• .env.example: document LOG_LEVEL.

Merge order

Independent of #47. Best merged after #46 (Windows path test fixes) so CI is fully green; the only failures on this branch are those 4 pre-existing path tests, which #46 resolves.

Test plan

• npm test -> 215 pass (4 failures are the pre-existing Windows path tests fixed by test: make auto-run-command and attachments tests OS-agnostic #46)
• New logger.test.ts suite green (level gating, file append, sanitization)
• Build clean (tsc)
• Verified no secrets/tokens flow into log output
  @

[coderabbitai]

Warning

Review limit reached

@jSydorowicz21, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 36 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 975885fa-07f6-4d93-8347-603c1c0c7158

📥 Commits

Reviewing files that changed from the base of the PR and between 86aa703 and a8cccc9.

📒 Files selected for processing (18)

• .env.example
• .gitignore
• src/__tests__/logger.test.ts
• src/__tests__/mockProvider.test.ts
• src/__tests__/queue.test.ts
• src/__tests__/server.test.ts
• src/core/api.ts
• src/core/attachments.ts
• src/core/config.ts
• src/core/logger.ts
• src/core/maestro.ts
• src/core/providers.ts
• src/core/transcription.ts
• src/core/types.ts
• src/index.ts
• src/providers/discord/adapter.ts
• src/providers/discord/commands/agents.ts
• src/providers/discord/messageCreate.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}