[FIX] logger.ts outputs to console in plugin mode — breaks TUI

[four-bytes-robby]

Problem

logger.ts outputs to console.log/console.warn/console.error even when running in plugin mode (when _logClient is set via setLogClient()). The logger already sends structured logs via _logClient.app?.log() — the console output is a redundant second channel that breaks the terminal UI.

Rule

Per plugin conventions: **console.log/console.warn/console.error is ONLY valid for the initial plugin startup message** (key === "init"). All other logging MUST go through _client?.app?.log() exclusively when in plugin mode. Console output breaks the opencode terminal UI.

Fix

In src/logger.ts:

1. When _logClient is set (plugin mode): skip console output for ALL messages except the startup "init" message
2. When _logClient is NOT set (CLI mode / testing): console output is fine (current behavior)

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• fix: brain startup robustness — ensure first-run DB init, suppress console spam, chunk search fallback #1

🔗 Related PRs

#150 - fix: brain never reaches 'ready' status + console.warn → app.log [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!