doctor reports oh-my-openagent/plugin version unknown even when package resolves 3.17.15

[Yeachan-Heo]

Summary

A user reported that oh-my-openagent doctor --verbose prints unknown for the plugin/package version even though both Bun and npm resolve the published package as 3.17.15. The doctor check passes overall, so this looks like a metadata lookup / package alias issue rather than a broken install.

User output

bunx oh-my-openagent@latest version -> oh-my-opencode v3.17.15
bunx oh-my-opencode@latest version  -> oh-my-opencode v3.17.15
npm view oh-my-openagent version     -> 3.17.15
npm view oh-my-opencode version      -> 3.17.15

Doctor:
  ✓ opencode    1.14.39
  ✓ oh-my-openagent unknown
  ✓ bun         1.3.13
  ✓ path        /Users/allen/.opencode/bin/opencode

System:
  OpenCode: 1.14.39
  Plugin expected: unknown
  Plugin loaded: unknown
  Bun: 1.3.13

Configuration:
  Path: /Users/allen/.config/opencode/oh-my-openagent.jsonc

Summary:
  4 passed, 0 failed, 0 warnings

Expected behavior

Doctor should not report unknown for the plugin/package version when the resolved CLI package is clearly 3.17.15. If the loaded plugin path lacks adjacent package metadata, doctor should distinguish that state, for example:

CLI package: oh-my-openagent/oh-my-opencode 3.17.15
Loaded plugin metadata: unavailable from <path>

Suspected causes

• package alias mismatch between oh-my-openagent and oh-my-opencode
• doctor is reading the generated plugin/config path instead of the resolved package metadata
• OpenCode Desktop/package cache has a copied plugin without package.json metadata next to it

Notes

The functional checks pass, so this should likely be treated as a doctor metadata/reporting bug, not an install failure.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]