feat(status): resolve the effective version a session loads

[diegohb]

Summary

status now resolves and reports the effective version a session would load, per scope — rather than echoing the manifest version alone.

bunx opencode-architect status --online --path ../other --package some-pkg

ConfigEntriesReader      # raw plugin entries per config file (json/jsonc)
  LoadedVersionResolver  # entry → resolved source on disk
    EntrySpec           # classify: npm spec | path/file:// | { package } object
    NpmCache            # $XDG_CACHE_HOME/opencode/npm/<name>@<spec>
    PluginEntryResolver.packageRoot
  RegistryVersionChecker # --online: npm /latest, warn-and-continue, injectable fetch
→ per-scope line + effective verdict

Effective verdict (strongest source wins):

should load: 1.0.0 (cache copy, 2h old)          # resolved copy on disk
should load: 1.0.0 (pinned spec, local)          # exact semver, no copy cached
should load: 2.0.0 (npm latest)                  # @latest + --online
should load: 1.0.0 (manifest)                    # fallback
should load: nothing (not registered in any scope)

Key changes:

• Per-scope line carries config file, raw entry as written, resolved source + relative age, npm-latest= under --online.
• Double-scope annotates the verdict (local + global; both scopes register — double-load) and warns.
• Manifest without registration reports unregistered — the report answers what would load, not what was once installed.
• --online/--path are status-only (rejected elsewhere); --package applies to status/clear-cache; --path dir must exist.
• Relative path entries resolve against the config file's directory (not cwd); name matching is case-insensitive on Windows.
• Installer slimmed to install/uninstall/cache + manifestAt() seam; status()/StatusOutcome retired. Templates mirror suite (byte-sync test guards src ↔ templates).

Evidence

$ bun test
tests/status-effective-version.test.ts  → 502 lines: per-scope resolution, verdict sources, age hints, all warning cases
tests/cli.test.ts                       → status-only flag rejection, --path, --package
tests/templates.test.ts                 → src ↔ template byte-sync

Sample per-scope output:

local scope: mode=plugin config=/proj/.opencode/opencode.json entry=opencode-architect@latest resolved=1.0.0 (cache copy, 2h old) npm-latest=1.2.0
global scope: mode=none config=- entry=- resolved=-
should load: 1.0.0 (cache copy, local, npm-latest=1.2.0)
Warning: local: resolves 1.0.0 but npm publishes 1.2.0 (stale)

Merge Danger

Door: two-way — additive reporting, read-only; revert restores the old status output shape.

Blast Radius: moderate

• Generated packages inherit the new resolution — templates/installer.template.txt ships status() with full resolution; the byte-sync test catches any src drift from templates.
• Installer.status() removed; no in-repo callers remain after this change.
• Installer.manifestAt() added as the new seam for external callers.
• main was merged in (no rebase/squash): the branch now carries main's baseDir config-directory threading and case-insensitive plugin-name matching, applied to the status resolution as well. src/plugin-entry.ts stays self-contained and byte-identical to its template, per the byte-sync invariant.