feat(client): package moltzapd process

.github/workflows/ci.yml

@@ -27,6 +27,7 @@ jobs:
 
       - run: pnpm install --frozen-lockfile
       - run: pnpm build
+      - run: pnpm nx run @moltzap/client:test:pack
       - run: node scripts/test/simulator-packages.mjs
       - run: pnpm typecheck
       - run: pnpm lint

.github/workflows/publish.yml

@@ -142,6 +142,9 @@ jobs:
       - name: Build all packages
         run: pnpm build
 
+      - name: Verify client package executable
+        run: pnpm nx run @moltzap/client:test:pack
+
       - name: Verify simulator package consumers
         run: node scripts/test/simulator-packages.mjs
 

README.md

@@ -151,9 +151,9 @@ you have two supported surfaces:
 - **Host a server.** Run the bin (`npx @moltzap/server-core`) and
   configure it with `moltzap.yaml` — see `moltzap.example.yaml` for
   every option.
-- **Build agents.** Use `@moltzap/client` (CLI + TypeScript client) to
-  connect over the wire as an agent, open conversations, and send and
-  receive messages. The full flow is documented in
+- **Build agents.** Use `@moltzap/client` (packaged daemon + TypeScript
+  harness client) to connect over the wire as an agent, open conversations,
+  and send and receive messages. The full flow is documented in
   [`docs/guides/two-agent-chat.mdx`](docs/guides/two-agent-chat.mdx).
 
 ## Simulating agent societies
@@ -200,7 +200,7 @@ offline analysis tools use `@moltzap/simulator/ledger`.
 |---------|-------------|
 | [`@moltzap/server-core`](packages/server) | Server: standalone mode, services, RPC, WebSocket |
 | [`@moltzap/protocol`](packages/protocol) | Effect `Schema` wire contracts and RPC descriptors for the JSON-RPC protocol |
-| [`@moltzap/client`](packages/client) | Client SDK and `moltzap` CLI |
+| [`@moltzap/client`](packages/client) | Harness client, packaged `moltzapd` daemon, and `moltzap` CLI |
 | [`@moltzap/openclaw-channel`](packages/openclaw-channel) | OpenClaw gateway plugin |
 | [`@moltzap/nanoclaw-channel`](packages/nanoclaw-channel) | Smoke-test channel (workspace-only, not published) |
 | [`@moltzap/simulator`](packages/simulator) | Code-first society simulator, production router, runtimes, and typed ledger |

docs/introduction.mdx

@@ -87,7 +87,7 @@ Choose the path that best fits your needs:
     icon="link"
     href="/guides/two-agent-chat"
   >
-    Client service and `moltzap` CLI: connection management, conversation state, agent registration, and messaging
+    Harness client and packaged `moltzapd` daemon: connection management, conversation state, and messaging
   </Card>
   <Card
     title="@moltzap/openclaw-channel"

package.json

@@ -40,6 +40,7 @@
     "test:compute-next-version": "bash scripts/release/compute-next-version.test.sh",
     "simulator:example": "pnpm simulator:example:check && node --experimental-strip-types examples/simulator/hello.ts",
     "simulator:example:check": "pnpm nx build @moltzap/simulator && pnpm exec tsc -p examples/simulator/tsconfig.json",
+    "test:pack:client": "pnpm nx run @moltzap/client:test:pack",
     "test:pack:simulator": "pnpm nx build @moltzap/simulator && node scripts/test/simulator-packages.mjs",
     "prepare": "husky && node scripts/setup/restore-tsgo-exec-bit.mjs",
     "effect:source": "./scripts/setup/prepare-effect.sh",

packages/client/AGENTS.md

@@ -1,8 +1,8 @@
 # @moltzap/client
 
 Client SDK for MoltZap: WebSocket transport, RPC service object,
-channel-core inbound handling, and the `moltzap` CLI binary. Pick the
-lowest surface that meets the need:
+channel-core inbound handling, the packaged `moltzapd` daemon, and the
+`moltzap` CLI binary. Pick the lowest surface that meets the need:
 
 | Surface | Use when |
 |---|---|
@@ -32,8 +32,9 @@ lowest surface that meets the need:
 - `src/channel-base/` — shared channel-adapter primitives.
 - `src/notification/` — notification stream + consumer helpers.
 - `src/pagination.ts` — cursor-paginated list-RPC drainer.
-- `src/cli/` — `moltzap` CLI binary, per-command files under
-  `commands/`.
+- `src/cli/moltzapd-main.ts` — packaged daemon process entry.
+- `src/cli/` — process argument parsing for `moltzapd` and the `moltzap`
+  CLI; the latter keeps its per-command files under `commands/`.
 
 Subpath exports: `./channel-base`, `./harness-client`, `./test-utils`, `./auth`,
 `./pagination`, `./notification`.

packages/client/package.json

@@ -14,7 +14,8 @@
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
-    "moltzap": "./dist/cli/index.js"
+    "moltzap": "./dist/cli/index.js",
+    "moltzapd": "./dist/cli/moltzapd-main.js"
   },
   "exports": {
     ".": {
@@ -71,6 +72,33 @@
           "command": "eslint . --cache --max-warnings=0"
         }
       },
+      "test:integration": {
+        "executor": "nx:run-commands",
+        "dependsOn": [
+          "build",
+          "^build"
+        ],
+        "options": {
+          "cwd": "packages/client",
+          "command": "vitest run --config vitest.integration.config.mjs"
+        }
+      },
+      "test:pack": {
+        "executor": "nx:run-commands",
+        "dependsOn": [
+          "build",
+          "^build"
+        ],
+        "inputs": [
+          "production",
+          "^production",
+          "{workspaceRoot}/scripts/test-client-package.mjs"
+        ],
+        "cache": false,
+        "options": {
+          "command": "node scripts/test-client-package.mjs"
+        }
+      },
       "arch:check": {
         "executor": "nx:run-commands",
         "options": {

packages/client/src/README.md

@@ -1,14 +1,16 @@
 # Client source boundary
 
-This tree implements the public client SDK, its local service process, and the
-`moltzap` CLI.
+This tree implements the public client SDK, the packaged `moltzapd` service
+process, and the `moltzap` CLI.
 
 - Root modules own the SDK clients, `MoltZapService`, channel dispatch,
   registration, configuration, profiles, pagination, and local-daemon RPC.
 - `channel-base/` contains runtime-neutral primitives shared by channel
   adapters.
-- `notification/` owns notification-stream helpers, while `cli/` owns command
-  parsing and local-daemon transport.
+- `notification/` owns notification-stream helpers, while `harness/` owns the
+  private MCP client and wire contract.
+- `cli/` owns executable argument parsing for `moltzapd` and the `moltzap`
+  control CLI.
 - `test-utils/` and `__tests__/` contain cross-package fixtures and integration
   coverage.