@memorax/memorax-code 0.1.9 → 0.1.11

package/bin/memorax-code.mjs

@@ -1,13 +1,15 @@
 #!/usr/bin/env node
 import { spawn, spawnSync } from "node:child_process";
-import { existsSync, readFileSync } from "node:fs";
+import { readFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { dirname, join, resolve } from "node:path";
 import { fileURLToPath, pathToFileURL } from "node:url";
+import { runAutomaticUpdate } from "../lib/automatic-update.mjs";
 import { stagePackagedClientHookRuntime } from "../lib/client-hook-runtime.mjs";
 import { unsupportedNodeVersionMessage } from "../lib/node-version.mjs";
-import { resolveNpmInvocation } from "../lib/npm-invocation.mjs";
-import { runBackendEntrypoint } from "../lib/run-entrypoint.mjs";
+import { runNpmCommand } from "../lib/npm-invocation.mjs";
+import { ensureNpmPackageRuntimeEnv, runBackendEntrypoint } from "../lib/run-entrypoint.mjs";
+import { ensureWindowsNpmGlobalPath } from "../lib/windows-user-path.mjs";
 
 const nodeVersionError = unsupportedNodeVersionMessage();
 if (nodeVersionError) {
@@ -86,13 +88,6 @@ function printCommand(command, args) {
   console.log([command, ...args].join(" "));
 }
 
-function npmCommandCwd() {
-  for (const candidate of [process.env.HOME, homedir(), "/"]) {
-    if (candidate && existsSync(candidate)) return candidate;
-  }
-  return "/";
-}
-
 async function runAccountCommand(args) {
   if (args.includes("--help") || args.includes("-h")) {
     printAccountHelp();
@@ -127,6 +122,7 @@ async function runAccountCommand(args) {
 }
 
 async function runUpdateCommand(args) {
+  let automatic = false;
   let dryRun = false;
   let force = false;
   let requestedChannel;
@@ -134,7 +130,9 @@ async function runUpdateCommand(args) {
 
   for (let index = 0; index < args.length; index += 1) {
     const arg = args[index];
-    if (arg === "--dry-run") {
+    if (arg === "--automatic") {
+      automatic = true;
+    } else if (arg === "--dry-run") {
       dryRun = true;
     } else if (arg === "--force") {
       force = true;
@@ -173,6 +171,17 @@ async function runUpdateCommand(args) {
   }
 
   const pkg = readPackageJson();
+  if (automatic) {
+    if (dryRun || force || requestedChannel) {
+      console.error("memorax-code update: --automatic cannot be combined with channel, force, or dry-run options");
+      return 2;
+    }
+    return await runAutomaticUpdateCommand({
+      pkg,
+      memoraxCodeHome: requestedHome ?? requestedMemoraxCodeHome([]),
+    });
+  }
+
   const channel = requestedChannel ?? (pkg.version.includes("-") ? "preview" : "latest");
   const npmArgs = ["install", "-g", `${pkg.name}@${channel}`];
   if (force) npmArgs.push("--force");
@@ -183,51 +192,47 @@ async function runUpdateCommand(args) {
   }
 
   console.error(`memorax-code update: running ${["npm", ...npmArgs].join(" ")}`);
-  const cwd = npmCommandCwd();
-  let invocation;
+  let npmResult;
   try {
-    invocation = resolveNpmInvocation(npmArgs);
+    npmResult = await runNpmCommand(npmArgs, {
+      env: {
+        ...process.env,
+        ...(requestedHome ? { MEMORAX_CODE_HOME: requestedHome } : {}),
+      },
+      stdio: "inherit",
+    });
   } catch (error) {
-    console.error(`memorax-code update: ${error instanceof Error ? error.message : String(error)}`);
+    console.error(`memorax-code update: failed to start npm: ${error instanceof Error ? error.message : String(error)}`);
     return 1;
   }
-  const child = spawn(invocation.command, invocation.args, {
-    stdio: "inherit",
-    cwd,
-    env: {
-      ...process.env,
-      PWD: cwd,
-      ...(requestedHome ? { MEMORAX_CODE_HOME: requestedHome } : {}),
-    },
-  });
-  const npmExitCode = await new Promise((resolve) => {
-    child.on("error", (error) => {
-      console.error(`memorax-code update: failed to start npm: ${error.message}`);
-      resolve(1);
-    });
-    child.on("close", (code, signal) => {
-      if (signal) {
-        console.error(`memorax-code update: npm exited from signal ${signal}`);
-        resolve(1);
-      } else {
-        resolve(code ?? 1);
-      }
-    });
-  });
-  if (npmExitCode !== 0) return npmExitCode;
+  if (npmResult.signal) {
+    console.error(`memorax-code update: npm exited from signal ${npmResult.signal}`);
+  }
+  if (npmResult.exitCode !== 0) return npmResult.exitCode;
 
   const memoraxCodeHome = requestedHome ?? requestedMemoraxCodeHome([]);
-  if (!existsSync(join(memoraxCodeHome, "runtime", "backend", "backend.pid.json"))) {
-    console.error("memorax-code update: package updated; the managed Backend remains stopped; run `memorax-code setup` from a terminal to review client and Hook changes");
-    return 0;
-  }
   if (!setupCanPrompt()) {
-    console.error("memorax-code update: package updated; run `memorax-code setup` from a terminal to review client and Hook changes");
+    console.error("memorax-code update: package updated; run `memorax-code setup` from a terminal to reconcile clients and verify Hook changes");
     return 0;
   }
   return await runSetupCommand(["--home", memoraxCodeHome], { updateMode: true });
 }
 
+async function runAutomaticUpdateCommand({ pkg, memoraxCodeHome }) {
+  try {
+    const result = await runAutomaticUpdate({
+      env: process.env,
+      memoraxCodeHome,
+      packageRoot: packageRoot(),
+      packageName: pkg.name,
+      packageVersion: pkg.version,
+    });
+    return result.ok ? 0 : 1;
+  } catch {
+    return 1;
+  }
+}
+
 async function runSetupCommand(args, { updateMode = false } = {}) {
   if (args.includes("--help") || args.includes("-h")) {
     printSetupHelp();
@@ -247,6 +252,7 @@ async function runSetupCommand(args, { updateMode = false } = {}) {
     console.error("memorax-code setup: an interactive terminal is required");
     return 1;
   }
+  if (!updateMode) repairWindowsSetupPath();
   try {
     const { withSetupCompletionLock } = await loadSetupCompletionApi();
     return await withSetupCompletionLock(memoraxCodeHome, async (completion) => {
@@ -259,7 +265,7 @@ async function runSetupCommand(args, { updateMode = false } = {}) {
         return 0;
       }
       if (updateMode) {
-        console.error("memorax-code update: reviewing client and Hook changes in the foreground");
+        console.error("memorax-code update: reconciling clients and verified Codex Hook changes in the foreground");
       }
       return await spawnSetupProcess(memoraxCodeHome, {
         updateMode,
@@ -272,6 +278,28 @@ async function runSetupCommand(args, { updateMode = false } = {}) {
   }
 }
 
+function repairWindowsSetupPath() {
+  if (readPackageJson().name !== "@memorax/memorax-code") return;
+  const repair = ensureWindowsNpmGlobalPath();
+  if (repair.userPathChanged) {
+    console.error("memorax-code setup: added npm's global command directory to the Windows user PATH");
+  }
+  if (repair.processPathChanged) {
+    console.error("memorax-code setup: npm global commands are available to the setup process");
+  }
+  if (repair.restartRecommended) {
+    console.error("memorax-code setup: restart or refresh coding agents that were already running so they inherit the updated PATH");
+  }
+  if (repair.status === "warning") {
+    const detail = repair.reason === "npm_prefix_unavailable"
+      ? "the npm global command directory could not be determined"
+      : repair.reason === "global_shims_missing"
+        ? "the installed MemoraX Code command shims could not be verified"
+        : "the Windows user PATH could not be updated";
+    console.error(`memorax-code setup: Windows PATH repair was not completed because ${detail}; setup will continue`);
+  }
+}
+
 async function routeDefaultCommand() {
   const memoraxCodeHome = requestedMemoraxCodeHome([]);
   try {
@@ -378,6 +406,7 @@ function hasReadyMemoraxConfiguration(memoraxCodeHome) {
 }
 
 async function spawnSetupProcess(memoraxCodeHome, { updateMode = false, setupMode = "automatic" } = {}) {
+  ensureNpmPackageRuntimeEnv();
   const env = {
     ...process.env,
     MEMORAX_CODE_HOME: memoraxCodeHome,

package/docs/configuration.md

@@ -39,13 +39,13 @@ are not a compatibility contract.
 
 ## New configuration
 
-The generated template selects all four client integrations, disables automatic
+The generated template selects the existing client integrations, including the optional CodeBuddy/WorkBuddy adapter, disables automatic
 retrieval, enables automatic writeback, sets the preferred language to Chinese
 (`zh`), uses a five-turn skill reminder and the adaptive repository-update
-policy, and enables content-bearing local traces for Codex, Claude Code, and
-OpenCode. Foreground setup may narrow `[clients]` to clients detected on the
-host. The tables below list all fallbacks, including tuning fields omitted from
-the generated file.
+policy, and enables content-bearing local traces for Codex, Claude Code,
+CodeBuddy/WorkBuddy, and OpenCode. Foreground setup may narrow `[clients]` to
+clients detected on the host. The tables below list all fallbacks, including
+tuning fields omitted from the generated file.
 
 On POSIX systems MemoraX Code creates `$MEMORAX_CODE_HOME` with mode `0700`
 and a new `config.toml` with mode `0600`. Windows relies on the current user's
@@ -54,7 +54,7 @@ filesystem ACLs.
 ## Client selection
 
 If `[clients]` is absent, lifecycle commands select Codex, Claude Code, DSH,
-and OpenCode. If it is present, `codex`, `claude`, `dsh`, and `opencode` are
+and OpenCode; CodeBuddy is opt-in unless detected during installation. If it is present, `codex`, `claude`, `dsh`, `opencode`, and `codebuddy` are
 boolean fields. Omitted `codex`, `claude`, or `opencode` values are disabled;
 an omitted `dsh` value remains enabled so configurations written before DSH
 support can discover an existing local Harness. Set `dsh = false` explicitly
@@ -62,7 +62,7 @@ to disable that integration. The command-line override accepts a
 comma-separated subset:
 
 ```text
---clients codex|claude|dsh|opencode|<comma-separated subset>|all|none
+--clients codex|claude|dsh|opencode|codebuddy|<comma-separated subset>|all|none
 ```
 
 Foreground `memorax-code setup` refreshes `[clients]` from the clients
@@ -77,12 +77,14 @@ disabled client is offered for activation with a default of yes; declining
 keeps it disabled. A selected client that is temporarily unavailable remains
 selected instead of being permanently disabled. Direct npm installation does
 not detect clients or modify `[clients]`.
+Automatic update reconciliation also preserves the exact persisted selection;
+it does not offer or enable a newly detected client.
 
 Client selection controls managed client-integration lifecycle only. It does
 not change Codex, Claude Code, DSH, or OpenCode provider settings.
 `--clients none` runs the Backend without managing a client integration.
 
-## Setup and package-transition state
+## Setup, automatic update, and package-transition state
 
 npm installation and foreground setup are separate operations.
 `npm install -g @memorax/memorax-code` installs or replaces package files
@@ -104,8 +106,9 @@ Successful setup writes a private versioned record at:
 $MEMORAX_CODE_HOME/runtime/setup/setup-completion.json
 ```
 
-The record controls only no-argument CLI routing. When it is valid, the command
-shows status. When it is absent and an interactive terminal is available,
+The record controls no-argument CLI routing and eligibility for background
+update reconciliation. When it is valid, the command shows status. When it is
+absent and an interactive terminal is available,
 `memorax-code` validates and reuses a complete effective configuration, then
 runs setup and reconciliation once to write the record. If the configuration
 is incomplete or no interactive terminal is available, it points to
@@ -113,6 +116,32 @@ is incomplete or no interactive terminal is available, it points to
 product uninstall removes this marker while retaining `config.toml`; stop and
 partial client uninstall preserve it.
 
+After setup completion, the managed Backend schedules detached update checks
+while it remains running. It reads the next deadline from the private update
+record, so an active Backend continues checking even when the user stays in one
+client session. Stable installations follow npm `latest`; prerelease
+installations follow `preview`. A successful result is reused for eight hours,
+while a failed check, install, or reconciliation retries after 15 minutes. Set
+`MEMORAX_CODE_AUTO_UPDATE=false` before starting or restarting the managed
+Backend to disable the scheduler. Client startup Hooks only recover an
+unavailable Backend and do not schedule updates.
+
+The updater installs an exact published version and runs an internal
+non-interactive setup mode. That mode preserves `[clients]`, connection data,
+and memory preferences. For Codex, only new or changed Hooks returned by the
+incremental check are trusted silently, and the exact Hook selection is
+validated again before and after the config write. A changed marketplace
+identity or unverifiable Hook set prevents reconciliation from completing.
+The standalone `memorax-code codex-plugin trust-hooks` command still performs
+explicit review.
+
+The installed version and next check deadline are stored in another private
+record:
+
+```text
+$MEMORAX_CODE_HOME/runtime/install/automatic-update.json
+```
+
 Replacing a running managed Backend uses a separate private record:
 
 ```text
@@ -121,8 +150,8 @@ $MEMORAX_CODE_HOME/runtime/install/package-transition.json
 
 Preinstall records and retires the running installation. Postinstall restores
 and verifies it before consuming the record. A fresh or already-stopped
-installation has no transition and remains stopped. Do not edit either runtime
-record by hand.
+installation has no transition and remains stopped. Direct npm installation
+does not run product reconciliation. Do not edit these runtime records by hand.
 
 ## DeepSeek Harness integration paths
 
@@ -169,6 +198,31 @@ MemoraX Code does not add entries to or otherwise modify `opencode.json` or
 `opencode.jsonc`. Restart or refresh OpenCode after installation or after these
 managed assets change.
 
+## CodeBuddy and WorkBuddy integration paths
+
+The managed CodeBuddy/WorkBuddy marketplace plugin and shared Skill use the
+native plugin layout:
+
+```text
+<CODEBUDDY_HOME>/plugins/marketplaces/memorax-code-local/plugins/memorax-code-codebuddy-adapter/
+├── hooks/
+└── skills/memorax-code/
+```
+
+`CODEBUDDY_HOME` or `WORKBUDDY_HOME` overrides the default root. Windows prefers
+`%USERPROFILE%\.workbuddy` and falls back to an existing `%USERPROFILE%\.codebuddy`
+for legacy CodeBuddy installations. When both homes exist, setup removes only the
+legacy MemoraX-managed plugin state from `.codebuddy`; other platforms use
+`~/.workbuddy`. The Skill is
+materialized from the canonical MemoraX Code Skill and is owned by the managed
+marketplace plugin; user files outside that plugin are not modified.
+
+On Windows, setup writes destination-specific native Hook paths so PowerShell
+does not receive a `/c/Users/...` plugin path. `memorax-code-codebuddy status
+--json` reports `codebuddyHooks.status` as `unverified` until a real WorkBuddy
+Hook executes, `observed` afterward, and `invalid` when the installed Hook
+manifest or runtime is incomplete. Restart or refresh WorkBuddy after setup.
+
 The managed loader records the exact MemoraX Code home, OpenCode configuration
 directory, installed Node runtime, and `memorax-code` entrypoint. When the
 enabled plugin loads, it performs a best-effort Backend health check and uses
@@ -319,14 +373,22 @@ Supported policies are `every-commit`, `commit-count`, `daily`,
 `pull-request`, `pull-request-or-daily`, and `adaptive`. Invalid policy values
 fall back to `adaptive`.
 
-In Codex, Claude Code, DSH, and OpenCode, the first eligible prompt starts a
+In Codex, Claude Code, CodeBuddy/WorkBuddy, DSH, and OpenCode, the first eligible prompt starts a
 background build only when the Backend has authorized a Git worktree and that
 worktree has no `.repo_memory/PROFILE.md`. If the Backend or workspace
 authority is unavailable, the client integration skips that attempt instead
 of falling back to its local workspace path. DSH schedules this work through
 its native pre-step integration rather than a Hook.
 
-A relevant repo-read runs supervised maintenance in all four clients. The
+CodeBuddy/WorkBuddy repository jobs run the headless client under a bounded
+worker. `MEMORAX_CODE_REPO_MEMORY_JOB_TIMEOUT_MS` sets the client execution
+limit (default `600000` ms); `MEMORAX_CODE_REPO_MEMORY_JOB_KILL_GRACE_MS` sets
+the grace period before the worker force-terminates a client that ignores
+`SIGTERM` (default `5000` ms). A timeout is recorded as
+`codebuddy_timeout` (or `<runner>_timeout`) in the job state, so a stalled
+headless client cannot leave an active job and repository marker indefinitely.
+
+A relevant repo-read runs supervised maintenance in all supported clients. The
 configured policy may select a build, update, or no-op. DSH maintenance
 requires an enabled, managed Profile that includes `@deepseek-ai/dsh-headless`.
 OpenCode executes the job through its active local server. Desktop-only
@@ -334,16 +396,16 @@ installations do not require a standalone `opencode` executable in `PATH`.
 
 ## Local traces
 
-`[trace.codex]`, `[trace.claude]`, `[trace.dsh]`, and `[trace.opencode]`
+`[trace.codex]`, `[trace.claude]`, `[trace.dsh]`, `[trace.opencode]`, and `[trace.codebuddy]`
 support the same fields:
 
-| Field | Codex environment | Claude environment | DSH environment | OpenCode environment | Fallback |
-| --- | --- | --- | --- | --- | --- |
-| `enabled` | `MEMORAX_CODE_CODEX_TRACE_ENABLED` | `MEMORAX_CODE_CLAUDE_TRACE_ENABLED` | `MEMORAX_CODE_DSH_TRACE_ENABLED` | `MEMORAX_CODE_OPENCODE_TRACE_ENABLED` | `true` |
-| `capture_content` | `MEMORAX_CODE_CODEX_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_CLAUDE_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_DSH_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_OPENCODE_TRACE_CAPTURE_CONTENT` | `true` |
-| `retention_days` | `MEMORAX_CODE_CODEX_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_CLAUDE_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_DSH_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_OPENCODE_TRACE_RETENTION_DAYS` | `7` |
-| `max_event_chars` | `MEMORAX_CODE_CODEX_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_CLAUDE_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_DSH_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_OPENCODE_TRACE_MAX_EVENT_CHARS` | `20000` |
-| `max_file_bytes` | `MEMORAX_CODE_CODEX_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_CLAUDE_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_DSH_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_OPENCODE_TRACE_MAX_FILE_BYTES` | `52428800` |
+| Field | Codex environment | Claude environment | DSH environment | OpenCode environment | CodeBuddy/WorkBuddy environment | Fallback |
+| --- | --- | --- | --- | --- | --- | --- |
+| `enabled` | `MEMORAX_CODE_CODEX_TRACE_ENABLED` | `MEMORAX_CODE_CLAUDE_TRACE_ENABLED` | `MEMORAX_CODE_DSH_TRACE_ENABLED` | `MEMORAX_CODE_OPENCODE_TRACE_ENABLED` | `MEMORAX_CODE_CODEBUDDY_TRACE_ENABLED` | `true` |
+| `capture_content` | `MEMORAX_CODE_CODEX_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_CLAUDE_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_DSH_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_OPENCODE_TRACE_CAPTURE_CONTENT` | `MEMORAX_CODE_CODEBUDDY_TRACE_CAPTURE_CONTENT` | `true` |
+| `retention_days` | `MEMORAX_CODE_CODEX_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_CLAUDE_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_DSH_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_OPENCODE_TRACE_RETENTION_DAYS` | `MEMORAX_CODE_CODEBUDDY_TRACE_RETENTION_DAYS` | `7` |
+| `max_event_chars` | `MEMORAX_CODE_CODEX_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_CLAUDE_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_DSH_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_OPENCODE_TRACE_MAX_EVENT_CHARS` | `MEMORAX_CODE_CODEBUDDY_TRACE_MAX_EVENT_CHARS` | `20000` |
+| `max_file_bytes` | `MEMORAX_CODE_CODEX_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_CLAUDE_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_DSH_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_OPENCODE_TRACE_MAX_FILE_BYTES` | `MEMORAX_CODE_CODEBUDDY_TRACE_MAX_FILE_BYTES` | `52428800` |
 
 Depending on the enabled client capabilities, content capture can include
 prompts, responses, recalled memory, writeback content, reminder text, and
@@ -364,6 +426,7 @@ Common operator settings are:
 | Environment | Purpose |
 | --- | --- |
 | `MEMORAX_CODE_HOME` | Select the state and configuration root |
+| `MEMORAX_CODE_AUTO_UPDATE` | Set to `false` to disable client-start background update checks |
 | `MEMORAX_CODE_BACKEND_URL` | Override the Backend URL for one command or Hook |
 | `MEMORAX_CODE_BACKEND_HOST` / `MEMORAX_CODE_BACKEND_PORT` | Select the managed bind; default `127.0.0.1:8787` |
 | `MEMORAX_CODE_BACKEND_TOKEN` | Supply a transient Backend token |

package/docs/troubleshooting.md

@@ -42,6 +42,22 @@ Setup requires terminal input and terminal-visible stderr. A pipe, background
 process, or redirected stdin/stderr cannot complete setup; rerun it in a normal
 interactive terminal.
 
+On Windows, interactive setup verifies npm's global command directory and adds
+it to the current setup process and the Windows user `PATH` when needed. If the
+current shell cannot find `memorax-code`, use npm's actual global prefix to
+bootstrap setup:
+
+```powershell
+$NpmGlobalBin = (npm prefix -g).Trim()
+$env:Path = "$NpmGlobalBin;$env:Path"
+& (Join-Path $NpmGlobalBin "memorax-code.cmd") setup
+```
+
+The same npm package installs both `memorax-code` and `memorax-cli`; do not
+install a separate CLI package. Open a new terminal after setup changes the
+user `PATH`. Restart or refresh only coding agents that were already running
+or still cannot find `memorax-cli`.
+
 ## Setup does not complete
 
 Setup writes
@@ -99,6 +115,34 @@ migration. `memorax-code start` alone does not commit that migration. Once a
 fixed release has started the Backend from its private runtime directory,
 later updates do not require this workaround.
 
+## Automatic update does not run or repeatedly retries
+
+Background checks start only after setup has written a valid
+`$MEMORAX_CODE_HOME/runtime/setup/setup-completion.json` record and the managed
+Backend is running. Confirm that `MEMORAX_CODE_AUTO_UPDATE` was not set to
+`false` when that Backend started. Client SessionStart events are not update
+triggers. A successful check is reused for eight hours; failures retry after 15
+minutes.
+
+The installed version and next check deadline are recorded at:
+
+```text
+$MEMORAX_CODE_HOME/runtime/install/automatic-update.json
+```
+
+Do not edit that record while an update may be running. For an immediate
+foreground retry, run `memorax-code update` from an interactive terminal, then
+check `memorax-code status`.
+
+During Codex reconciliation, verified new or changed MemoraX Code Hooks are
+trusted silently. A changed marketplace identity, malformed Hook response, or
+Hook that changes again during the config write is not trusted; automatic
+reconciliation remains incomplete and retries later. After confirming the
+installed plugin source, use `memorax-code codex-plugin trust-hooks` for an
+explicit diagnostic review, then rerun `memorax-code setup` if needed. Direct
+npm installation replaces package files but does not perform this product
+reconciliation.
+
 ## Installed, but memory is unavailable
 
 The package and Backend can be healthy while MemoraX remains unconfigured. Run:
@@ -199,11 +243,12 @@ memorax-code start --clients codex
 memorax-code-codex doctor
 ```
 
-Codex requires review for new or changed Hook command hashes. A declined,
-non-interactive, or direct npm update can leave changed Hooks untrusted even
-though package replacement succeeded. Run `memorax-code setup` for foreground
-review; do not write trust entries directly. If the skill is missing, rerun
-`memorax-code start --clients codex`, then restart or refresh Codex.
+MemoraX Code update reconciliation silently trusts only the exact new or changed
+Hook hashes returned by Codex after the marketplace identity is verified.
+Direct npm installation does not run that reconciliation and can leave changed
+Hooks untrusted. Use the commands above instead of writing trust entries
+directly. If the skill is missing, rerun `memorax-code start --clients codex`,
+then restart or refresh Codex.
 
 ## Claude Code plugin or Hook is inactive
 
@@ -216,6 +261,28 @@ This reconciles the Claude Code marketplace plugin and Hooks. If the plugin is
 still missing or stale, restart or refresh Claude Code. Do not manually copy
 Hooks into Claude settings.
 
+## CodeBuddy or WorkBuddy Hook is inactive
+
+```sh
+memorax-code start --clients codebuddy
+memorax-code-codebuddy status --json
+```
+
+On Windows, the managed plugin prefers `%USERPROFILE%\.workbuddy` and falls back
+to an existing `%USERPROFILE%\.codebuddy` for legacy CodeBuddy installations,
+while `CODEBUDDY_HOME` or `WORKBUDDY_HOME` remains an explicit override. If both
+homes exist, setup removes only the MemoraX-managed plugin registration,
+marketplace, and cache from `.codebuddy`; unrelated data remains untouched. A
+`codebuddyHooks.status` value of `unverified` means the files are configured but
+the current plugin version has not yet produced a real Hook event. Restart or
+refresh WorkBuddy, submit one prompt, and check status again. `observed` means
+the Hook entrypoint and its shared runtime loaded; `invalid` means setup should
+be rerun.
+
+If WorkBuddy still reports a Hook command containing `/c/Users/...`, it is
+loading a stale plugin manifest. Rerun the start command above and fully
+restart WorkBuddy. Do not manually edit the installed Hook command.
+
 ## DeepSeek Harness Profile integration is inactive
 
 ```sh