@mulmobridge/chat-service 0.1.7 → 1.0.1

package/README.md

@@ -113,6 +113,13 @@ Part of the [`@mulmobridge/*`](https://www.npmjs.com/~mulmobridge) package famil
 - [`@mulmobridge/xmpp`](https://www.npmjs.com/package/@mulmobridge/xmpp) — XMPP / Jabber
 - [`@mulmobridge/zulip`](https://www.npmjs.com/package/@mulmobridge/zulip) — Zulip
 
+## Related projects
+
+Published from the MulmoClaude monorepo by [Receptron](https://github.com/receptron).
+
+- **[MulmoClaude](https://github.com/receptron/mulmoclaude)** — an open-source AI assistant platform that runs on your own computer. Claude Code as the engine, a personal wiki for long-term memory, schema-driven collections for your data, and chat that summons the right GUI (markdown, charts, forms, spreadsheets, wikis) for each task.
+- **[MulmoTerminal](https://github.com/receptron/mulmoterminal)** — a terminal-first cockpit for running many AI coding agents in parallel. One roster showing every session's summary and PR status, tmux-backed session persistence, git-worktree isolation, one-click PRs, and mobile push with remote reply.
+- **[MulmoTerminal manual](https://receptron.github.io/mulmoterminal/)** — setup, workflows, feature reference, configuration, mobile notifications, and alternative / local model providers. Available in English and Japanese.
 
 ## License
 

package/dist/atomic-write.js

@@ -1,9 +1,19 @@
 // Lightweight atomic write — write to a sibling tmp file, then rename.
 //
-// Inlined in this package (not imported from the host app) so
-// @mulmobridge/chat-service stays dependency-free beyond protocol.
-// Same contract as the host's writeFileAtomic: readers always see
-// either the old file or the new file — never a half-written one.
+// A DELIBERATE second implementation of `writeFileAtomic`, catalogued as such
+// in `docs/shared-utils.md`. The canonical one is
+// `@mulmoclaude/core/files` — but this package sits in the bridge tier, below
+// core, so importing it would be an uphill edge; and the helper needs
+// `node:fs`, which rules out the browser-safe `@mulmoclaude/common` leaf that
+// `errorMessage` / `escapeHtml` live in. @mulmobridge/chat-service therefore
+// stays dependency-free beyond protocol.
+//
+// This is a SMALLER contract, not a drifted one: no `mode`, no `uniqueTmp`.
+// Same core guarantee as the canonical — readers always see either the old
+// file or the new file, never a half-written one — but without the canonical's
+// Windows AV/Search-Indexer rename-retry loop, so a Windows-hosted bridge can
+// still surface an EPERM here. Fix bugs in the canonical first, then decide
+// whether this copy needs the same change.
 import { writeFile, rename, unlink, mkdir } from "fs/promises";
 import path from "path";
 import { randomUUID } from "crypto";

package/dist/commands.d.ts

@@ -1,4 +1,4 @@
-import type { BridgeSkillSummary, Role, SessionSummary } from "./types.js";
+import type { BridgeSkillSummary, GetSessionHistoryFn, ListSessionsFn, Role } from "./types.js";
 import type { ChatStateStore, TransportChatState } from "./chat-state.js";
 export interface CommandResult {
     reply: string;
@@ -41,23 +41,8 @@ export declare function createCommandHandler(opts: {
     getRole: (roleId: string) => Role;
     resetChatState: ChatStateStore["resetChatState"];
     connectSession: ChatStateStore["connectSession"];
-    listSessions?: (opts: {
-        limit: number;
-        offset: number;
-    }) => Promise<{
-        sessions: SessionSummary[];
-        total: number;
-    }>;
-    getSessionHistory?: (sessionId: string, opts: {
-        limit: number;
-        offset: number;
-    }) => Promise<{
-        messages: Array<{
-            source: string;
-            text: string;
-        }>;
-        total: number;
-    }>;
+    listSessions?: ListSessionsFn;
+    getSessionHistory?: GetSessionHistoryFn;
     /** Lists the skills the bridge command handler should expose.
      *  Drives both the slash-command allowlist (only matching names
      *  are forwarded to the agent) and the "Skills:" section in the

package/dist/index.d.ts

@@ -16,5 +16,5 @@ export interface ChatService {
     pushToBridge: PushFn;
 }
 export declare function createChatService(deps: ChatServiceDeps): ChatService;
-export type { ChatServiceDeps, StartChatFn, OnSessionEventFn } from "./types.js";
+export type { Attachment, ChatServiceDeps, StartChatFn, StartChatParams, OnSessionEventFn } from "./types.js";
 export { writeFileAtomic } from "./atomic-write.js";

package/dist/types.d.ts

@@ -1,35 +1,20 @@
+import type { Attachment } from "@mulmobridge/protocol";
+export type { Attachment };
 export interface Role {
     id: string;
     name: string;
 }
+/** Structurally identical to `StructuredLogger` in `@mulmoclaude/common`, where
+ *  the rest of that family was folded (#2486). This one stays local: rule 2 only
+ *  exempts a DECLARED package dependency, and this package's sole dependency is
+ *  `@mulmobridge/protocol` — adding common would give a published
+ *  `@mulmobridge/*` package its first `@mulmoclaude/*` edge, for a type. */
 export interface Logger {
     error(prefix: string, message: string, data?: Record<string, unknown>): void;
     warn(prefix: string, message: string, data?: Record<string, unknown>): void;
     info(prefix: string, message: string, data?: Record<string, unknown>): void;
     debug(prefix: string, message: string, data?: Record<string, unknown>): void;
 }
-/** A file attached to a bridge or UI message. Generic enough for
- *  images, PDFs, documents, videos, etc. The server decides what to
- *  do with each based on mimeType — images become vision content
- *  blocks, unsupported types are ignored with a log.
- *
- *  Either `data` (inline base64 bytes) or `path` (workspace-relative
- *  path the server can read) MUST be set:
- *
- *    - Bridges over the socket transport ship raw bytes, so they
- *      populate `data` (and usually `mimeType`).
- *    - The Vue UI uploads paste/drop and sidebar-pick files to disk
- *      before sending and populates `path`; the server reads bytes
- *      from disk and infers `mimeType` from the extension.
- *
- *  Mirrors `@mulmobridge/protocol`'s `Attachment` (kept structurally
- *  duplicated here per the package-contract rules in this file). */
-export interface Attachment {
-    mimeType?: string;
-    data?: string;
-    path?: string;
-    filename?: string;
-}
 export interface StartChatParams {
     message: string;
     roleId: string;
@@ -75,6 +60,25 @@ export interface SessionSummary {
     preview: string;
     updatedAt: string;
 }
+/** List recent sessions (paged). Backs the `/sessions` bridge command. */
+export type ListSessionsFn = (opts: {
+    limit: number;
+    offset: number;
+}) => Promise<{
+    sessions: SessionSummary[];
+    total: number;
+}>;
+/** Recent messages in a session (paged, newest-first). Backs `/history`. */
+export type GetSessionHistoryFn = (sessionId: string, opts: {
+    limit: number;
+    offset: number;
+}) => Promise<{
+    messages: Array<{
+        source: string;
+        text: string;
+    }>;
+    total: number;
+}>;
 export interface ChatServiceDeps {
     /** Relay a user turn into the agent loop. */
     startChat: StartChatFn;
@@ -101,27 +105,12 @@ export interface ChatServiceDeps {
      * Omit if session listing is not available (command will reply
      * "not available").
      */
-    listSessions?: (opts: {
-        limit: number;
-        offset: number;
-    }) => Promise<{
-        sessions: SessionSummary[];
-        total: number;
-    }>;
+    listSessions?: ListSessionsFn;
     /**
      * Get recent messages from a session. Used by /history command.
      * Returns newest-first array of {source, text} pairs.
      */
-    getSessionHistory?: (sessionId: string, opts: {
-        limit: number;
-        offset: number;
-    }) => Promise<{
-        messages: Array<{
-            source: string;
-            text: string;
-        }>;
-        total: number;
-    }>;
+    getSessionHistory?: GetSessionHistoryFn;
     /**
      * Resolve the roleId a given session was started with. Used by the HTTP
      * `/connect` route so the persisted bridge state's role tracks the target

package/dist/types.js

@@ -10,7 +10,10 @@
 //     host app uses. They look like the real `Role` / `Logger` /
 //     `StartChatParams` types so the same functions plug in, but
 //     they are defined here so the package has no compile-time
-//     link back to the host.
+//     link back to the host. Importing from a declared package
+//     dependency is fine — `Attachment` comes from
+//     `@mulmobridge/protocol` (already a runtime dep) rather than
+//     being redeclared here (#2488).
 //  3. When you add a new dependency, extend `ChatServiceDeps` and
 //     thread it through the factory functions — do NOT reach out
 //     to a module import. See #269 / #305 for the rationale.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mulmobridge/chat-service",
-  "version": "0.1.7",
+  "version": "1.0.1",
   "description": "Server-side chat service for MulmoBridge — socket.io + REST bridge to Claude Code agents",
   "type": "module",
   "main": "./dist/index.js",
@@ -27,7 +27,7 @@
   "license": "MIT",
   "author": "Receptron Team",
   "dependencies": {
-    "@mulmobridge/protocol": "^0.1.4"
+    "@mulmobridge/protocol": "^1.0.1"
   },
   "peerDependencies": {
     "express": "^5.0.0",
@@ -36,5 +36,22 @@
   "devDependencies": {
     "@types/express": "^5.0.0",
     "typescript": "^6.0.3"
+  },
+  "homepage": "https://github.com/receptron/mulmoclaude/tree/main/packages/chat-service#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/receptron/mulmoclaude.git",
+    "directory": "packages/chat-service"
+  },
+  "keywords": [
+    "mulmobridge",
+    "chat-service",
+    "socket.io",
+    "express",
+    "ai-agent",
+    "server"
+  ],
+  "bugs": {
+    "url": "https://github.com/receptron/mulmoclaude/issues"
   }
 }