feat(paperclip-runtime): route Paperclip calls through paperclipai CLI in Local CLI mode

The Paperclip runtime card's Local CLI tab previously only derived an apiUrl
from the local config and then made HTTP calls itself, so the Test action and
the company/agent pickers ignored the user's onboarded CLI auth context.

Add CLI-backed variants for every Paperclip call that has a `paperclipai`
counterpart, and route through them when transport=cli — both from the
settings card and from the runtime adapter's prompt path.

- New plugin functions spawning `paperclipai … --json`:
  * probePaperclipViaCli, listCompaniesViaCli, listCompanyAgentsViaCli
    (settings card test + pickers)
  * createIssueViaCli, getIssueViaCli, agentsMeViaCli (runtime hot path)
- New dashboard routes: /providers/paperclip/cli-status, /cli-companies,
  /cli-agents (read-only façades over the plugin's CLI helpers)
- PaperclipRuntimeCard: branches on transport=cli to use the cli-* fetchers
- PaperclipRuntimeAdapter: stores transport on the session and routes
  createIssue/getIssue + identity derivation through CLI variants in CLI mode;
  raises a clear error when agentId is unset in CLI mode (paperclipai has no
  /agents/me equivalent)
- getIssueComments / wakeAgent / getRunEvents stay on HTTP (no matching
  paperclipai subcommands) and continue to use the apiKey discovered from
  the local paperclipai config, so CLI mode still works end-to-end
- Tests: 9 new paperclip-client tests covering each CLI variant + 5 new
  adapter tests for the Local-CLI transport branch (64/64 plugin tests pass)
- Update routes.test for the existing BUNDLED_PLUGIN_RUNTIMES fallback so
  the bundled hermes/openclaw/paperclip entries are expected alongside
  installed plugins

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

packages/dashboard/app/api/legacy.ts

@@ -1384,6 +1384,54 @@ export async function mintPaperclipApiKey(
   });
 }
 
+/**
+ * Probe Paperclip via the local `paperclipai` CLI (Local CLI tab). Carries the
+ * user's onboarded CLI context (profile / api-base / api-key) instead of having
+ * the dashboard server make the HTTP call directly.
+ */
+export async function fetchPaperclipCliStatus(opts: {
+  cliBinaryPath?: string;
+  cliConfigPath?: string;
+}): Promise<PaperclipProviderStatus> {
+  const params = new URLSearchParams();
+  if (opts.cliBinaryPath) params.set("cliBinaryPath", opts.cliBinaryPath);
+  if (opts.cliConfigPath) params.set("cliConfigPath", opts.cliConfigPath);
+  const qs = params.toString();
+  return api<PaperclipProviderStatus>(
+    `/providers/paperclip/cli-status${qs ? `?${qs}` : ""}`,
+  );
+}
+
+/** List companies via `paperclipai company list --json`. Empty array on failure. */
+export async function fetchPaperclipCliCompanies(opts: {
+  cliBinaryPath?: string;
+  cliConfigPath?: string;
+}): Promise<PaperclipCompanySummary[]> {
+  const params = new URLSearchParams();
+  if (opts.cliBinaryPath) params.set("cliBinaryPath", opts.cliBinaryPath);
+  if (opts.cliConfigPath) params.set("cliConfigPath", opts.cliConfigPath);
+  const qs = params.toString();
+  const r = await api<{ companies: PaperclipCompanySummary[] }>(
+    `/providers/paperclip/cli-companies${qs ? `?${qs}` : ""}`,
+  );
+  return r.companies ?? [];
+}
+
+/** List agents in a company via `paperclipai agent list -C <id> --json`. */
+export async function fetchPaperclipCliAgents(opts: {
+  cliBinaryPath?: string;
+  cliConfigPath?: string;
+  companyId: string;
+}): Promise<PaperclipAgentSummary[]> {
+  const params = new URLSearchParams({ companyId: opts.companyId });
+  if (opts.cliBinaryPath) params.set("cliBinaryPath", opts.cliBinaryPath);
+  if (opts.cliConfigPath) params.set("cliConfigPath", opts.cliConfigPath);
+  const r = await api<{ agents: PaperclipAgentSummary[] }>(
+    `/providers/paperclip/cli-agents?${params.toString()}`,
+  );
+  return r.agents ?? [];
+}
+
 /** Read the local paperclipai config to discover apiUrl + deploymentMode. */
 export async function fetchPaperclipCliDiscovery(opts: {
   cliConfigPath?: string;