@ccmsg/cli 0.2.7 → 0.2.8

package/README.md

@@ -7,13 +7,25 @@ together with its CLI and the plugins it hands to agents.
 
 - `daemon` — holds sessions, delivery, topics and the mesh, and answers the contract's ops over UDS / WS
 - `cli` — the entry point a session calls its instance through (`ccmsg`)
-- `plugins/claude` / `plugins/codex` — the plugins agents receive (`ccmsg plugin install`)
+- `plugin` — the plugin an agent receives (`ccmsg plugin install claude`). Claude Code is the only
+  agent that has one; a codex plugin is not implemented, and what it would take is tracked in
+  [`docs/issue/2026-09-09-codex-plugin-delivery-via-thread-queue.md`](./docs/issue/2026-09-09-codex-plugin-delivery-via-thread-queue.md)
 
 The wire contract is [`@ccmsg/protocol`](https://github.com/kawaz/ccmsg-protocol), pinned to a
 version here. Who may call what, and what comes back, is decided by the contract's attribute
 table and schemas; the daemon reads them rather than carrying validation or authorization
 branches of its own.
 
+## What it does not do
+
+- Serve the webui, or keep a conversation log of its own — the webui is its own static site, and transcript is the source of truth
+- Separate privileges, or mesh with an instance of a different uid / config home — that boundary is the OS's uid and file permissions
+- Re-derive an upstream judgment (the gateway's severity, Claude Code's permission decisions) or observe another config home
+- Carry validation of its own, or serve v1 alongside — the contract's validator is called, and the new lineage stands as a separate instance
+
+Authenticating a person is not on that list: the daemon answers "who came" itself, with a
+passkey. [docs/DESIGN.md](./docs/DESIGN.md) §9 carries the reason each of these ties back to.
+
 ## Documentation
 
 - [docs/DESIGN.md](./docs/DESIGN.md) — layers, delivery, the state model, the mesh, and how it is tested

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ccmsg/cli",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "description": "The ccmsg daemon, CLI and agent plugins for one instance (= one config home)",
   "license": "MIT",
   "author": "kawaz",

package/src/plugin/claude.ts

@@ -77,6 +77,15 @@ ccmsg peers --all      他ホストの instance が知っている分も含め
 居なくなったセッションで、各行の \`repo\` / \`ws\` / \`branch\` / \`title\` で見分けて
 \`sid\` を取る。\`send_message\` が \`true\` の相手には harness 自身の機能でも届く。
 
+## 相手セッションの扱い
+
+相手は基本、自分にとってのサブエージェントだと思えばよい。対等な会議を開く場ではないので、
+冒頭の挨拶・賛辞・締めの社交辞令を省き、用件だけを 1〜3 文で送る。
+
+やり取りの中身を人へリレーしない。人は全セッションを直接見ているので、相手の完了報告や
+根拠をこちらで要約し直しても情報は増えず、時間とコンテキストだけが減る。人に言うのは
+自セッション目線の事実 (何を頼んだ・何が返り・その結果こちらが何をしたか) だけ。
+
 ## 見ている人へ知らせる
 
 \`\`\`

package/src/service/program.ts

@@ -0,0 +1,140 @@
+/** Which path the init system is told to run, and what became of the one it was
+ * told.
+ *
+ * A unit file outlives the machine's software. The path this process is running
+ * as is the path of one version of it — a runtime under a version manager lives
+ * in a directory named after the version, and the next upgrade puts an
+ * identical program somewhere else and takes that directory away. Registered as
+ * it is, the supervisor works until the day it silently does not: the init
+ * system goes on asking for a path nothing is at, and the person finds out when
+ * nothing answers after a reboot.
+ *
+ * So a durable path is looked for before anything is written down, and what was
+ * written down is read back by `service status`. The judgement here is the
+ * coarse half of what `stable-which` does — whether the path names a version
+ * rather than a program — and the reading back is what makes the other half
+ * unnecessary: a pick that turns out wrong says so as a missing file rather
+ * than as silence. */
+import { existsSync, readFileSync, realpathSync, statSync } from "node:fs";
+import { basename, delimiter, join } from "node:path";
+import { ENTRY } from "../daemon/registry.ts";
+import type { Env } from "../instance/paths.ts";
+
+/** Directory names that belong to one version of something rather than to the
+ * thing itself. A path through any of them is gone at the next upgrade. */
+const VERSIONED = ["/nix/store/", "/Cellar/", "/installs/", "/versions/", "/node_modules/"];
+
+/** Whether this path is one a unit file may hold. */
+export function durable(path: string): boolean {
+  return !VERSIONED.some((mark) => path.includes(mark));
+}
+
+/** How large a file may be and still be read as a wrapper script. A wrapper is
+ * a few lines; anything else is the program itself. */
+const WRAPPER_MAX_BYTES = 64 * 1024;
+
+function isFile(path: string): boolean {
+  try {
+    return statSync(path).isFile();
+  } catch {
+    return false;
+  }
+}
+
+function sameFile(one: string, other: string): boolean {
+  try {
+    return realpathSync(one) === realpathSync(other);
+  } catch {
+    return false;
+  }
+}
+
+/** Every entry of this name on `PATH`, in the order `PATH` states them. */
+function onPath(name: string, env: Env): string[] {
+  return (env["PATH"] ?? "")
+    .split(delimiter)
+    .filter((dir) => dir !== "")
+    .map((dir) => join(dir, name))
+    .filter((path) => isFile(path));
+}
+
+/** Whether running this path runs what this process is running: the same file,
+ * or a wrapper that names the script this process was started with. */
+function leadsHere(candidate: string, self: string): boolean {
+  if (sameFile(candidate, self)) return true;
+  try {
+    if (statSync(candidate).size > WRAPPER_MAX_BYTES) return false;
+    return readFileSync(candidate, "utf8").includes(ENTRY);
+  } catch {
+    return false;
+  }
+}
+
+export interface Program {
+  /** What the init system is told to run. */
+  readonly command: string[];
+  /** Whether that first path is one that survives an upgrade. False means the
+   * best that could be found still names a version, which is worth saying
+   * rather than hiding: the registration works now and is the one to redo
+   * after the next upgrade. */
+  readonly durable: boolean;
+}
+
+/** The supervisor as a path an init system can keep asking for.
+ *
+ * A `ccmsg` on `PATH` that leads back here is preferred over the runtime: it is
+ * the program by its own name, and it stays put across a runtime upgrade
+ * because it is what names the runtime rather than what the runtime is. Failing
+ * that, the runtime by name on `PATH`, which at least resolves through whatever
+ * the version manager keeps current. Failing both, this process's own path,
+ * which is where it started. */
+export function supervisorProgram(env: Env = process.env): Program {
+  const self = process.execPath;
+  for (const candidate of onPath("ccmsg", env)) {
+    if (durable(candidate) && leadsHere(candidate, self)) {
+      return { command: [candidate, "daemon", "supervise"], durable: true };
+    }
+  }
+  for (const candidate of onPath(basename(self), env)) {
+    if (durable(candidate) && sameFile(candidate, self)) {
+      return { command: [candidate, ENTRY, "daemon", "supervise"], durable: true };
+    }
+  }
+  return { command: [self, ENTRY, "daemon", "supervise"], durable: durable(self) };
+}
+
+/** What a unit file names as its program, and whether anything is there now. */
+export interface RegisteredProgram {
+  readonly path: string;
+  /** Whether the registered path is one that survives an upgrade. A false here
+   * is a registration that works today and will stop working quietly, which is
+   * worth seeing before it does. */
+  readonly durable: boolean;
+  /** False on a registration whose program has moved: the init system is
+   * asking for a path nothing is at, and re-registering is the answer. */
+  readonly exists: boolean;
+}
+
+const ENTITY: Record<string, string> = { "&amp;": "&", "&lt;": "<", "&gt;": ">" };
+
+/** The program the registered unit names — read from the file rather than
+ * worked out again, because the question is what the init system was told and
+ * not what it would be told today. */
+export function registeredProgram(
+  unitFile: string,
+  kind: "launchd" | "systemd",
+): RegisteredProgram | null {
+  let text: string;
+  try {
+    text = readFileSync(unitFile, "utf8");
+  } catch {
+    return null;
+  }
+  const found =
+    kind === "launchd"
+      ? /<key>ProgramArguments<\/key>\s*<array>\s*<string>([^<]*)<\/string>/.exec(text)?.[1]
+      : /^ExecStart=(\S+)/m.exec(text)?.[1];
+  if (found === undefined) return null;
+  const path = found.replace(/&amp;|&lt;|&gt;/g, (entity) => ENTITY[entity] as string);
+  return { path, durable: durable(path), exists: existsSync(path) };
+}

package/src/service/service.ts

@@ -2,8 +2,8 @@ import { existsSync, mkdirSync, rmSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { dirname, join } from "node:path";
 import { CommandError } from "../daemon/link.ts";
-import { ENTRY } from "../daemon/registry.ts";
 import { type Env, resolveStateRoot } from "../instance/paths.ts";
+import { type RegisteredProgram, registeredProgram, supervisorProgram } from "./program.ts";
 
 /** What the host's init system was asked, and what it said.
  *
@@ -34,6 +34,13 @@ export interface ServiceState {
   readonly registered: boolean;
   readonly running: boolean;
   readonly pid?: number;
+  /** The program the registered unit names, and whether anything is at that
+   * path now. `null` when nothing is registered, so there is no unit to read.
+   *
+   * Here rather than left to be worked out by a reader: a supervisor that
+   * cannot start because its program moved with a runtime upgrade looks, from
+   * every other field, exactly like one that was never started. */
+  readonly program: RegisteredProgram | null;
   /** What the init system itself says, or `null` when it could not be asked.
    *
    * Beside the two fields above rather than folded into them: those are ccmsg's
@@ -101,7 +108,7 @@ export type LogSource =
  * registered from a shell where these were exported and started without them
  * would quietly manage a different set of instances. */
 function supervisorCommand(): string[] {
-  return [process.execPath, ENTRY, "daemon", "supervise"];
+  return supervisorProgram().command;
 }
 
 const CARRIED = [
@@ -211,6 +218,13 @@ class LaunchdService implements Service {
   }
 
   async state(run: Run): Promise<ServiceState> {
+    return {
+      ...(await this.#report(run)),
+      program: registeredProgram(this.unitFile, this.kind),
+    };
+  }
+
+  async #report(run: Run): Promise<Omit<ServiceState, "program">> {
     const registered = existsSync(this.unitFile);
     const printed = await run(["launchctl", "print", `${this.#domain}/${LAUNCHD_LABEL}`]);
     // A non-zero exit is launchd saying it has no such service, which is not
@@ -306,6 +320,13 @@ class SystemdService implements Service {
   }
 
   async state(run: Run): Promise<ServiceState> {
+    return {
+      ...(await this.#report(run)),
+      program: registeredProgram(this.unitFile, this.kind),
+    };
+  }
+
+  async #report(run: Run): Promise<Omit<ServiceState, "program">> {
     const registered = existsSync(this.unitFile);
     const shown = await run([
       "systemctl",