fix(cli): discover adapters authored with registerCommand

[ankitranjan7]

An adapter in ~/.webcmd/clis/ authored with registerCommand — a public export of @agentrhq/webcmd/registry — was never imported, so webcmd quotes list said the site was not installed while webcmd adapter status listed the same command as present.

The problem

Discovery gated every candidate file through a regex over its source text: /\b(?:cli|registerSiteAuthCommands|onStartup|onBeforeExecute|onAfterExecute)\s*\(/. Three consequences:

1. registerCommand( is not in that list, so a file using the public export was silently never imported.
2. The regex matches comments and strings — appending // cli( to the same file flipped it to discoverable.
3. adapter status reads the filesystem, so it reported commands discovery had refused to load.

What changed

1. Gate on the runtime import, not on call syntax (src/discovery.ts). A file can only register anything by importing the runtime, so discovery now tests for an import of @agentrhq/webcmd/{registry,plugin-runtime,hooks}. That covers every authoring style instead of an enumerated list of call names, and a call-shaped comment no longer decides anything. Helper modules that never import the runtime are still skipped, so their side effects still do not run at startup. Chosen over deleting the gate entirely, which would execute every helper module in an adapter directory at startup.
2. cli() is the only authoring API (src/registry-api.ts). registerCommand is removed from the public export surface: it takes the raw/lazy manifest shape used by the manifest fast path, not the authoring shape, and adapters written against it died at execution with has no func or pipeline. It is undocumented and unused outside the runtime. An adapter importing it now fails loudly at load with the missing-export error, instead of registering a command that cannot run.
3. Load failures are recorded and lead the error (src/discovery.ts). Every failed import is kept with its site, absolute path, and cause; missingPluginGuidance reports those instead of Site "X" is not installed. when the site has failing files.
4. adapter status agrees with availability (src/cli.ts). Each row carries loadError; the table annotates (failed to load: …) and the JSON output gained a loadError field.

Before / After

Before (node dist/src/main.js, HOME in a temp dir, adapter uses registerCommand):

$ webcmd quotes list
Site "quotes" is not installed.
Search: webcmd plugin search quotes
Install using the installSource returned by search.

$ webcmd adapter status
Local adapters in ~/.webcmd/clis/ (1 sites):

  quotes
    user adapter: quotes/list

After, same adapter:

$ webcmd quotes list
⚠  Failed to load adapter /tmp/…/.webcmd/clis/quotes/list.js: The requested module '@agentrhq/webcmd/registry' does not provide an export named 'registerCommand'
Site "quotes" has adapter files that failed to load:
  /tmp/…/.webcmd/clis/quotes/list.js
    The requested module '@agentrhq/webcmd/registry' does not provide an export named 'registerCommand'
Fix the file, then re-run. Adapters call cli({ ... }) from '@agentrhq/webcmd/registry'
and must declare access: 'read' | 'write' and func.

$ webcmd adapter status
Local adapters in ~/.webcmd/clis/ (1 sites):

  quotes
    user adapter: quotes/list (failed to load: The requested module '@agentrhq/webcmd/registry' does not provide an export named 'registerCommand')

After, same file rewritten with cli({ …, access: 'read', func }):

$ webcmd quotes list
- quote: hi

Tests

src/discovery.test.ts gains five cases: a cli() adapter in a temp HOME registers; a file whose only cli( is a comment registers nothing and records no failure; a module missing access records the real cause and missingPluginGuidance leads with it rather than "is not installed"; an adapter importing registerCommand does not register and its failure names the export; failed files are recorded by the absolute path adapter status keys off. src/cli.test.ts covers the new loadError JSON field.

npm run typecheck clean. npx vitest run --project unit: 2708 passed, 1 skipped, 0 failed (the suite needs npm run build first — 120 hosted/manifest tests fail without dist/ on main too). npm run build clean.

🤖 Generated with Claude Code

[github-actions]

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

• The automated review returned an invalid structured result.

This review is advisory and does not block merging.