fix(bun): always check for updates when plugin version is implied latest

[backnotprop]

Summary

Fixes an issue where plugins configured with implied "latest" version (or no version) were not updating to newer versions on subsequent OpenCode starts.

Problem

When a user configures a plugin like:

{
"plugin": ["@plannotator/opencode"]
}

The install flow was:

1. First start: version = "latest", installs package, resolves to "0.2.3"
2. Saves "@plannotator/opencode": "0.2.3" to cache
3. Next start: version = "latest", cache has "0.2.3"
4. Check: "0.2.3" === "latest" → false → proceeds to reinstall
5. But bun add --force uses cached registry data, doesn't fetch new version

Users were stuck on old versions unless they manually cleared ~/.cache/opencode/.

Solution

Skip the early cache return when version === "latest":

// Beforeif(parsed.dependencies[pkg]===version)returnmod// After if(version!=="latest"&&parsed.dependencies[pkg]===version)returnmod

This ensures:

• Pinned versions (e.g., @pkg@1.0.0) still skip reinstalls via cache
• Latest versions always run bun add to check for updates

Test plan

• Configure a plugin with "latest" version
• Verify it updates when a new version is published
• Verify pinned versions still skip unnecessary reinstalls

[backnotprop]

Probably don't merge this. Not tested extensively

[github-actions]

Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR.

[backnotprop]

It's still bad that this is a problem.