[BUG] getBus() missing onWarn callback — bus warnings go to console.warn instead of app.log

[four-bytes-robby]

Problem

In src/status.ts, the getBus() function calls BusClient.connect() WITHOUT an onWarn callback. This means all bus warnings (stderr output, fallback messages) go to raw console.warn instead of opencode's structured app.log.

Expected

All bus warnings should be routed through _client?.app?.log with proper structured logging.

Proposed Fix

Add onWarn callback to BusClient.connect() that:

1. Safely JSON-stringifies args (try/catch for circular references)
2. Routes warnings through _client?.app?.log as level: warn

Affected File

• src/status.ts — getBus() function (lines ~95-106)

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Route BusClient fallback warnings to app.log + toast instead of console.warn #153

🔗 Related PRs

#145 - feat: migrate to scoped bus API (forService/forSession) [merged]
#148 - fix: sidebar always subscribes to brain/status for ingest progress [merged]
#150 - fix: brain never reaches 'ready' status + console.warn → app.log [merged]
#155 - feat: project-scoped bus + immediate auto-ingest + app.log warnings #151 #152 #153 [merged]
#158 - fix: route bus warnings through app.log via onWarn callback [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!