fix: don't block one-shot openclaw subcommands; migrate to current plugin SDK

Sidecar lifecycle:
- Move startSideCar() out of register() into an api.on("gateway_start", ...)
  handler. register() runs in every CLI subprocess that loads plugins
  (e.g. `openclaw completion`, `openclaw doctor`); eagerly spawning a
  long-lived process there hung `openclaw update`'s post-update steps.
- Spawn the sidecar with detached: true, stdio routed to a log file fd,
  and call .unref() so the host's event loop is never held by the child.
  Even if a future caller invokes startSideCar in a non-gateway context,
  it can no longer block that host from exiting.
- Sidecar logs now go to ~/.openclaw/logs/dirigent-sidecar.log instead of
  being piped through the host logger.

Plugin SDK convention update:
- Wrap default export with definePluginEntry({ id, name, description, register })
  per the current openclaw plugin authoring contract.
- Switch all imports from the deprecated root barrel "openclaw/plugin-sdk"
  to focused subpaths "openclaw/plugin-sdk/core" and
  "openclaw/plugin-sdk/plugin-entry".
- Modernize openclaw.plugin.json: drop entry/version, add description,
  declare contracts.tools[] for the 6 tools, set activation.onStartup: true
  so gateway_start fires for this plugin at boot.

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

plugin/core/channel-members.ts

@@ -1,4 +1,4 @@
-import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk/core";
 import type { IdentityRegistry } from "./identity-registry.js";
 
 const PERM_VIEW_CHANNEL = 1n << 10n;

plugin/core/moderator-discord.ts

@@ -1,4 +1,4 @@
-import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk/core";
 
 type Logger = { info: (m: string) => void; warn: (m: string) => void };
 

plugin/core/sidecar-process.ts

@@ -6,6 +6,7 @@ import { spawn, type ChildProcess } from "node:child_process";
 let noReplyProcess: ChildProcess | null = null;
 
 const LOCK_FILE = path.join(os.tmpdir(), "dirigent-sidecar.lock");
+const LOG_FILE = path.join(os.homedir(), ".openclaw", "logs", "dirigent-sidecar.log");
 
 function readLock(): { pid: number } | null {
   try {
@@ -88,18 +89,29 @@ export function startSideCar(
     env.DEBUG_MODE = debugMode ? "true" : "false";
   }
 
-  noReplyProcess = spawn(process.execPath, [serverPath], {
-    env,
-    stdio: ["ignore", "pipe", "pipe"],
-    detached: false,
-  });
+  // Spawn so the host process is never blocked from exiting:
+  //   - detached: sidecar is its own process group leader
+  //   - stdio piped to a log file fd (no parent-side pipes to drain)
+  //   - unref(): Node's event loop will not wait on this child
+  // stopSideCar() still works because we keep a ChildProcess handle for
+  // signalling, but the OS lifecycle of the sidecar is decoupled from us.
+  fs.mkdirSync(path.dirname(LOG_FILE), { recursive: true });
+  const logFd = fs.openSync(LOG_FILE, "a");
+  try {
+    noReplyProcess = spawn(process.execPath, [serverPath], {
+      env,
+      stdio: ["ignore", logFd, logFd],
+      detached: true,
+    });
+  } finally {
+    fs.closeSync(logFd);
+  }
 
   if (noReplyProcess.pid) {
     writeLock(noReplyProcess.pid);
   }
 
-  noReplyProcess.stdout?.on("data", (d: Buffer) => logger.info(`dirigent: services: ${d.toString().trim()}`));
-  noReplyProcess.stderr?.on("data", (d: Buffer) => logger.warn(`dirigent: services: ${d.toString().trim()}`));
+  noReplyProcess.unref();
 
   noReplyProcess.on("exit", (code, signal) => {
     logger.info(`dirigent: services exited (code=${code}, signal=${signal})`);
@@ -107,7 +119,7 @@ export function startSideCar(
     noReplyProcess = null;
   });
 
-  logger.info(`dirigent: services started (pid=${noReplyProcess.pid}, port=${port})`);
+  logger.info(`dirigent: services started (pid=${noReplyProcess.pid}, port=${port}, log=${LOG_FILE})`);
 }
 
 export function stopSideCar(logger: { info: (m: string) => void }): void {