feat(client): package moltzapd process

[chughtapan]

Summary

• publish a real moltzapd process entry for one existing named profile
• keep the loopback MCP listener and sole central WebSocket connection alive in one Effect scope
• prove the spawned process uses MCP plus direct WebSocket operation without creating the legacy per-agent Unix socket
• install packed client and protocol tarballs in a fresh consumer and execute the generated moltzapd bin
• run the packed-install gate in CI and before npm publication

Boundary

This is the process prerequisite for adapter cutover. The caller still resolves the nonzero loopback port; durable profile-to-MCP location and adapter acquisition remain follow-up work. The existing moltzap bin remains transitional in this slice.

No canonical protocol or main-wire schema changes are included. Participant enrichment remains confined to the MCP-local harness projection in #946.

Stack and tracking

• stacked on feat(harness): project client-owned turns #946
• tracks One per-AgentId moltzapd and structurally compatible HarnessClient implementations #926
• upstream v1 control-plane simplification: #924

Validation

• pnpm nx run @moltzap/client:test — 32 files, 231 tests
• pnpm nx run @moltzap/client:test:integration — 16 files, 41 tests
• focused process integration — MCP status, WebSocket 0 -> 1 -> 0, graceful SIGTERM, no Unix socket
• pnpm nx run @moltzap/client:test:pack — fresh npm consumer and installed bin launch
• client build, test typecheck, lint, and architecture checks
• workspace root lint, formatting, architecture config, docs generation, constants, and import-resolution checks
• independent review found no blockers; both pack-gate hardening findings were resolved and rechecked

[chughtapan]

Superseded by #974, which collapses this stack into one PR against main. This branch's commits are all contained in it — nothing is lost, and this thread stays readable. Closing to leave one place to review.