fix: use client.app.log() instead of console.error for plugin logging #26 follow-up

[four-bytes-robby]

Problem

PR #26 added the console logging rule to AGENTS.md but the plugin code (src/four-opencode-knowledge.ts) still uses console.error for non-startup messages:

• Line 21: console.error(\DB at ${dbPath}`)— should useclient.app.log()`
• Line 322: console.error(\ready`)— should useclient.app.log()`

Line 11 (v${pkg.version} loading…) is the compliant initial startup message.

Additionally, AGENTS.md uses _client?.app?.log() instead of client.app.log().

Both CodeRabbit and cubic flagged this in the PR #26 review.

Fix

1. AGENTS.md: _client?.app?.log() → client.app.log()
2. Plugin: Add client destructuring, create log helper, replace 2 console.error calls

Reference

• PR docs: add console logging rule — app().log only, console for startup only #26: docs: add console logging rule — app().log only, console for startup only #26
• CodeRabbit review: docs: add console logging rule — app().log only, console for startup only #26 (comment)

[coderabbitai]

🔗 Related PRs

#26 - docs: add console logging rule — app().log only, console for startup only [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!