chattercatcher 0.1.7 → 0.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chattercatcher",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "本地优先的飞书/Lark 家庭群知识库机器人",
   "type": "module",
   "main": "dist/index.js",

package/docs/superpowers/plans/2026-04-28-gateway-background-start.md

@@ -1,86 +0,0 @@
-# Gateway Background Start Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Make `chattercatcher gateway start` launch Gateway/Web UI in the background by default while preserving `--foreground` for the current blocking behavior.
-
-**Architecture:** Keep the existing Gateway runtime as the foreground implementation, and add a thin detached launcher around it. The default `gateway start` process only checks state, opens the log file, spawns the same CLI with `gateway start --foreground`, prints PID/log instructions, and exits; the child process owns Gateway/Web UI startup and PID cleanup.
-
-**Tech Stack:** Node.js 20+, TypeScript ESM, Commander, `child_process.spawn`, existing ChatterCatcher config/runtime/log helpers, Vitest.
-
----
-
-## File Structure
-
-- Modify `src/gateway/runtime.ts`: extend PID records with optional `logFile`, add `getGatewayLogPath()`, keep old PID files readable.
-- Create `src/gateway/detached.ts`: background-launch helper that builds child command, opens log streams, spawns, and returns a launch result.
-- Modify `src/gateway/index.ts`: surface `logFile` in Gateway status.
-- Modify `src/cli.ts`: add default detached start and `--foreground` option.
-- Modify `tests/gateway/runtime.test.ts`: cover `logFile` read/write, compatibility, and status.
-- Create `tests/gateway/detached.test.ts`: cover command construction, running-PID guard, and launch result.
-- Modify `package.json` and `package-lock.json`: bump patch after verification.
-
-Do not create commits unless the user explicitly asks for commits.
-
----
-
-### Task 1: Extend Gateway runtime state with log file support
-
-**Files:** `src/gateway/runtime.ts`, `tests/gateway/runtime.test.ts`
-
-1. Add runtime tests for PID `logFile` read/write and backward compatibility with old PID files.
-2. Run `npm test -- tests/gateway/runtime.test.ts` and verify failure before implementation.
-3. In `src/gateway/runtime.ts`, add `import { getLogsDirectory } from "../logs/reader.js";`, extend `GatewayPidRecord` with `logFile?: string`, add `getGatewayLogPath(): string` returning `path.join(getLogsDirectory(), "gateway.log")`, and preserve `parsed.logFile` only when it is a string.
-4. Run `npm test -- tests/gateway/runtime.test.ts` and verify pass.
-
-### Task 2: Add detached Gateway launcher helper
-
-**Files:** `src/gateway/detached.ts`, `tests/gateway/detached.test.ts`
-
-1. Create tests that mock `node:child_process.spawn` and cover:
-   - `buildGatewayForegroundSpawnCommand(["/usr/local/bin/node", "/repo/dist/cli.js"])` returns command `/usr/local/bin/node` and args `["/repo/dist/cli.js", "gateway", "start", "--foreground"]`.
-   - `startDetachedGateway()` creates logs dir, spawns detached child with stdout/stderr to log, returns `started: true`, `pid`, and log path.
-   - A running PID record prevents spawning and returns `started: false` with a message containing `正在运行`.
-2. Run `npm test -- tests/gateway/detached.test.ts` and verify failure before implementation.
-3. Create `src/gateway/detached.ts` with `GatewayForegroundSpawnCommand`, `DetachedGatewayStartInput`, `DetachedGatewayStartResult`, `buildGatewayForegroundSpawnCommand()`, and `startDetachedGateway()`.
-4. `startDetachedGateway()` must call `getGatewayStatus()`, use `getGatewayLogPath()`, guard `running`, open append log fds, call `spawn(command, args, { detached: true, stdio: ["ignore", out, err], windowsHide: true })`, call `child.unref()`, and close fds on spawn throw.
-5. Run `npm test -- tests/gateway/runtime.test.ts tests/gateway/detached.test.ts`.
-
-### Task 3: Surface log file in Gateway status
-
-**Files:** `src/gateway/index.ts`, `tests/gateway/runtime.test.ts`
-
-1. Update existing status test so the PID record includes `logFile` and expected status includes `logFile`.
-2. Run `npm test -- tests/gateway/runtime.test.ts` and verify failure before implementation.
-3. Add optional `logFile?: string` to `GatewayStatus`.
-4. Return `logFile: runtime.record.logFile` in running and stale branches.
-5. Run `npm test -- tests/gateway/runtime.test.ts` and `npm test -- tests/gateway/detached.test.ts`.
-
-### Task 4: Wire CLI foreground/background behavior
-
-**Files:** `src/cli.ts`
-
-1. Import `startDetachedGateway` from `./gateway/detached.js` and `getGatewayLogPath` from `./gateway/runtime.js` by merging with the existing runtime import.
-2. Rename existing `startGatewayCommand()` to `startGatewayForegroundCommand()`.
-3. Change foreground PID write to pass a record with `pid`, `startedAt`, `command`, and `logFile: getGatewayLogPath()`.
-4. Add `startGatewayCommand(options: { foreground?: boolean } = {})` that routes foreground to `startGatewayForegroundCommand()`, otherwise loads config/secrets, calls `startDetachedGateway({ config, secrets })`, and prints message, optional PID, log path, logs follow command, and stop command.
-5. Change `gateway start` Commander setup to add `.option("--foreground", "在当前终端以前台模式运行")` and `.action(startGatewayCommand)`.
-6. Keep `gateway restart` calling `await startGatewayCommand()` so it restarts in background.
-7. Run `npm run lint` and fix changed-file TypeScript errors only.
-
-### Task 5: Verify tests and build
-
-1. Run `npm test -- tests/gateway/runtime.test.ts tests/gateway/detached.test.ts`.
-2. Run `npm test`.
-3. Run `npm run lint`.
-4. Run `npm run build`.
-5. If verification fails, diagnose and fix the smallest relevant issue.
-
-### Task 6: Bump npm patch version
-
-**Files:** `package.json`, `package-lock.json`
-
-1. Run `npm version patch --no-git-tag-version`.
-2. Verify `package.json` and `package-lock.json` root package version moved from current value to the next patch.
-3. Run `git diff -- package.json package-lock.json` and confirm only version metadata changed.
-4. Run `npm run lint`.