@aliyunrds/ctxdb 0.0.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [2023] [Taranjeet Singh]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,202 @@
+# @aliyunrds/ctxdb
+
+Unified access layer for RDS ContextDatabase. One `ctxdb` CLI (memory + KB ops), one `setup --agent <…>` installer, per-agent SKILL.md — supports multiple code agents from a single package.
+
+| Agent | Hooks | Skill install path | Skill style |
+|---|---|---|---|
+| **qoder** | ✅ UserPromptSubmit + Stop + SessionStart | `~/.qoder/skills/ctxdb/` | hooks-driven (auto capture/recall) |
+| **codex** | ✅ UserPromptSubmit + Stop + SessionStart | `~/.codex/skills/ctxdb/` | hooks-driven (auto capture/recall) |
+| **claude** | ✅ UserPromptSubmit + Stop + SessionStart | `~/.claude/skills/ctxdb/` | hooks-driven (auto capture/recall) |
+
+Config and logs live under `~/.ctxdb/`. `~/.ctxdb/ctxdb.json` is one file, but runtime config is isolated per agent under `agents.qoder`, `agents.codex`, and `agents.claude`. (Pre-2026-05-23 installs used `~/.ctxdb.json` at the home root; running `ctxdb setup --agent <name>` migrates the file into the selected agent section.)
+
+## Install
+
+```sh
+npm install -g @aliyunrds/ctxdb
+
+# Qoder (hooks + skill)
+ctxdb setup --agent qoder --api-key ctxdb-...
+# Codex (hooks + skill)
+ctxdb setup --agent codex --api-key ctxdb-...
+# Claude Code (hooks + skill)
+ctxdb setup --agent claude --api-key ctxdb-...
+
+# --base-url defaults to https://context-database.aliyuncs.com (public prod).
+#   Pass --base-url <host> only if you target a different deployment
+#   (e.g., a pre / staging host, or a self-hosted instance).
+# --user-id  defaults to "default". Pass --user-id <bucket> only if you
+#   need to isolate this install from another access layer or machine
+#   sharing the same workspace (see "Configuration" below).
+
+# Verify
+ctxdb status --json
+```
+
+Setup first checks that the target agent home exists (`~/.qoder`, `~/.codex`, or `~/.claude`). If the directory is missing, install or start that agent once before running `ctxdb setup --agent <name>`.
+
+For **qoder**, **codex**, and **claude**, restart the harness (CLI: just exit + restart; app: Cmd+R or quit/relaunch) so it picks up the new hooks/skill. For **codex**, setup also writes `[features].hooks = true` into `~/.codex/config.toml` (creating the file if missing) — Codex won't fire any hook entries without it. On first use Codex may prompt you to trust the new hook commands.
+
+## What it does
+
+For **qoder**, **codex**, and **claude**, hooks fire automatically:
+
+| Trigger | Hook | What runs |
+|---|---|---|
+| Session starts | `SessionStart` | Build a short cwd/git-signal query, recall relevant memories, and inject warm-up context as `additionalContext` |
+| User submits a prompt | `UserPromptSubmit` | Search `/v3/memories/search/`, format a `<recalled-memories>` block, inject as additional context. **By default only memory is recalled.** Set `recall_knowledge: true` in the selected agent config to also pull KB chunks into a `<external-knowledge>` block; otherwise the recommended path for KB is the agent calling `ctxdb kb search --agent <name>` explicitly when the user asks (see SKILL.md) |
+| Agent finishes its turn | `Stop` | Read transcript, detect KB-upload turns and skip capture (so uploaded content doesn't bleed into long-term memory), slice the current turn, sanitize the input, POST to memory store |
+
+Implementation note: qoder/Claude consume the JSON `hookSpecificOutput.additionalContext` shape; Codex has been verified on this machine through `~/.codex/hooks.json`, `[features].hooks = true`, and hook audit logs, where non-empty stdout from `UserPromptSubmit`/`SessionStart` is treated as injected context. The same hook core is shared; setup passes `--agent=<name>` so each hook reads its own config section.
+
+## CLI
+
+`ctxdb` ships 19 subcommands:
+
+- **Top-level**: `init` / `status` / `ping` / `setup` / `teardown`
+- **Memory**: `memory add|search|list|get|update|delete`
+- **KB**: `kb upload-text|upload-file|list|documents-list|document-get|search`
+
+See `ctxdb --help`.
+
+`setup` mandates `--agent <qoder|codex|claude>` because it mutates that agent's hooks/skills. Memory and KB commands also accept `--agent <name>` so agents use their own config section; when omitted, `CTXDB_AGENT` wins, otherwise `qoder` is used for backward compatibility. `teardown` loops every supported agent.
+
+`memory add … --no-infer` stores the text verbatim (skips server-side LLM
+fact-extraction). Use it when the user explicitly asks for a verbatim
+memory ("记住 / 请记忆 / 原文记下"); without `--no-infer` the server may
+rewrite, merge, or skip details.
+
+`kb search <query> [--kb=name1,name2] [--top-k=N] [--threshold=F]` is the
+agent-driven KB recall path — calls `POST /v1/knowledge/query` directly
+(distinct from `memory search --knowledge`, which is a memory + KB hybrid
+search). The SKILL points the agent here when the user explicitly asks for
+KB lookup ("结合知识库查询" / "从知识库召回"). `--kb` is comma-separated;
+omit it to search across all KBs.
+
+## Configuration
+
+Lives at `~/.ctxdb/ctxdb.json` (co-located with logs at `~/.ctxdb/logs/`). Schema:
+
+```json
+{
+  "version": 2,
+  "agents": {
+    "qoder": {
+      "api_key": "ctxdb-...",
+      "base_url": "https://context-database.aliyuncs.com",
+      "user_id": "default",
+      "auto_capture": true,
+      "auto_recall": true,
+      "warmup_recall": true,
+      "recall_knowledge": false,
+      "top_k": 5,
+      "threshold": 0.4,
+      "knowledge_top_k": 6,
+      "debug": false
+    },
+    "codex": { "...": "same schema, independent values" },
+    "claude": { "...": "same schema, independent values" }
+  }
+}
+```
+
+Agent selection is driven by `--agent <qoder|codex|claude>` on every CLI invocation, falling back to `CTXDB_AGENT` env, then to `qoder`. There is no `default_agent` field — older installs that have one written get it dropped on the next save.
+
+Field reference:
+
+| Key | Type | Default | Meaning |
+|---|---|---|---|
+| `user_id` | str | `"default"` | mem0-layer bucket key on every capture/recall call. The server's tenant isolation runs on `member_id` (injected from `X-API-Key`), so this is an optional per-user/agent slice. Override with `ctxdb setup --agent <a> --user-id <bucket>` or `CTXDB_USER_ID=<bucket>` when you need to isolate this install from another access layer or machine sharing the same workspace |
+| `auto_capture` | bool | `true` | Stop hook captures each turn into long-term memory for the selected agent |
+| `auto_recall` | bool | `true` | UserPromptSubmit hook recalls memory on each user prompt for the selected agent |
+| `warmup_recall` | bool | `true` | SessionStart hook recalls cwd/git-related memories for the selected agent |
+| `recall_knowledge` | bool | `false` | When `auto_recall` is on, also pull KB chunks alongside memory. Default is **off** — the recommended KB-recall path is the agent calling `kb search --agent <name>` explicitly when the user asks |
+| `top_k` / `threshold` | int / float | `5` / `0.4` | Memory recall pagination + similarity floor. `5` keeps the codex TUI `hook context: ...` line short enough to scan and bounds token spend on the modal recall path; raise it per-agent if you want more candidates |
+| `knowledge_top_k` | int | `6` | KB chunks pulled per recall (only effective when `recall_knowledge: true`) |
+| `debug` | bool | `false` | Verbose hook logging (`~/.ctxdb/logs/ctxdb.log`) |
+
+Env-var overrides apply to the selected agent config (env wins): `CTXDB_AGENT` / `CTXDB_API_KEY` / `CTXDB_BASE_URL` / `CTXDB_USER_ID`.
+
+## Architecture
+
+```
+@aliyunrds/ctxdb            ← this package (CLI + setup + hooks + skills)
+       │
+       └─ depends on @aliyunrds/ctxdb-shared  ← input sanitation,
+                                          prompt-injection defenses,
+                                          memory/KB types, recall pipeline
+                                          (also consumed by openclaw_memory_rds_ctxdb)
+```
+
+Two npm packages total. `@aliyunrds/ctxdb-shared` stays separate because OpenClaw's plugin fork also depends on it; this package owns everything user-facing (CLI bin, installer, per-agent skills, hooks).
+
+## Uninstall
+
+> ⚠️ **Order matters.** npm 7+ removed the `preuninstall` / `postuninstall` lifecycle hooks — `npm uninstall -g` does **not** run any cleanup we ship. If you `npm uninstall` first you'll leave agent hook entries pointing at a now-missing binary, plus orphaned skills and `~/.ctxdb/` state. Always run **`ctxdb teardown` first, then `npm uninstall -g`**.
+
+### Full removal (recommended)
+
+```sh
+# 1. Strip hooks + skills + (optionally) config + logs while the binary still works.
+ctxdb teardown --purge-all     # everything: hooks, skills, ~/.ctxdb/ctxdb.json, ~/.ctxdb/logs/
+
+# 2. Then drop the npm binaries.
+npm uninstall -g @aliyunrds/ctxdb @aliyunrds/ctxdb-shared
+```
+
+After step 1, `ctxdb teardown` prints the exact `npm uninstall` command to run next — copy it from your terminal.
+
+### Partial removal
+
+```sh
+# Per-agent only — unwires hooks, removes ~/.<agent>/skills/ctxdb, AND
+# deletes agents.<X> from ~/.ctxdb/ctxdb.json. Other agents' sections are
+# preserved verbatim. If <X> was the last configured agent, ~/.ctxdb/ctxdb.json
+# itself is unlinked so a future `ctxdb setup --agent <X>` runs through the
+# first-time install path cleanly.
+ctxdb setup --remove --agent qoder
+ctxdb setup --remove --agent codex
+ctxdb setup --remove --agent claude
+
+# Wholesale across all agents, but keep config + logs for re-setup later:
+ctxdb teardown                  # all agents, keeps ~/.ctxdb/{ctxdb.json,logs/}
+ctxdb teardown --purge-config   # also deletes ~/.ctxdb/ctxdb.json
+ctxdb teardown --purge-logs     # also deletes ~/.ctxdb/logs/
+```
+
+### What teardown does (and doesn't) touch
+
+- **Hook entries in `~/.qoder/settings.json`, `~/.codex/hooks.json`, and `~/.claude/settings.json`**: stripped precisely by marker (`_ctxdb = @aliyunrds/ctxdb`, plus legacy keys `_ctxdbQoder` / `_ctxdbPackage` and the legacy `@aliyunrds/ctxdb-qoder` value for installs predating the unified marker). Any hooks you added yourself stay. A timestamped `*.bak-ctxdb-<TS>` is written before each modification (rotation keeps the 5 most recent).
+- **Skill directories**: `~/.<agent>/skills/ctxdb/` for each set-up agent, plus legacy dirs (`ctxdb-qoder`, `rds-ctxdb-qoder`, `qoder-ctxdb`) under `~/.qoder/skills/` from older package names.
+- **`~/.ctxdb/` state**: only with `--purge-config` / `--purge-logs` / `--purge-all`. Defensive: `--purge-all` removes the `~/.ctxdb/` root only if it's empty after the named files are deleted (won't blanket-rm an unknown directory).
+- **`~/.codex/config.toml` `[features].hooks`**: **NOT** reverted. Setup adds `hooks = true` so Codex will fire ctxdb's hook entries; teardown leaves the flag alone because (a) the user may have wanted it on for non-ctxdb hooks, and (b) it's harmless when `~/.codex/hooks.json` is empty. If you want it off, edit the file by hand.
+- **`npm` itself**: never. `ctxdb teardown` does not call your host package manager — that's the second command above.
+
+## Remote SSH (Qoder IDE)
+
+When you connect to a remote host via Qoder IDE's SSH session, `ctxdb` does **not** travel with the Qoder server. Qoder syncs its own server bits to the remote machine, but `~/.qoder/{settings.json, skills/}` and `~/.ctxdb/ctxdb.json` are per-host — your local hooks, config, and skill are not propagated.
+
+To enable autoCapture / autoRecall in the remote session, run the same install on the remote machine:
+
+```sh
+# on the remote host
+npm install -g @aliyunrds/ctxdb
+ctxdb setup --agent qoder --api-key ctxdb-...
+# Both --base-url and --user-id are optional; they default to the public
+# prod host and the "default" bucket respectively. Override either when
+# you target a non-prod deployment or want per-host bucket isolation.
+```
+
+Each remote host needs its own one-time setup. Omitting `--user-id` lands every host on the shared `"default"` bucket, so memory flows freely across machines that share an API key. Pass a distinct `--user-id` per host when you want per-host bucketing.
+
+## Lightweight (no-node) alternative
+
+`SKILL-one-in-all.md` is a single-file bash-only skill: zero install, no node runtime, but no hooks and no streaming/upload helpers. Use it when you can't or don't want to ship the npm package; use this package when you want hooks (qoder/codex/claude) or a richer CLI surface.
+
+## Developer docs
+
+Maintainer-facing docs (source layout, dev/test workflows, server-config archives) live in the project's internal notebooks and are not packaged with this release. npm consumers can ignore this section.
+
+## License
+
+Apache-2.0

package/dist/chunk-464RHJDQ.js

@@ -0,0 +1,136 @@
+#!/usr/bin/env node
+import {
+  CtxdbError
+} from "./chunk-L4YJ7LDI.js";
+
+// src/lib/recall-orchestrator.ts
+import {
+  buildExternalKnowledgeBlock
+} from "@aliyunrds/ctxdb-shared";
+
+// src/lib/format-recall.ts
+import {
+  formatRecalledMemoriesBlock
+} from "@aliyunrds/ctxdb-shared";
+var OPEN_TAG = "<recalled-memories>";
+var CLOSE_TAG = "</recalled-memories>";
+var TIME_ANCHOR_RE = /^\[Time anchor:[^\]]*\]\s*/;
+var IMPORTANCE_SUFFIX_RE = /\s*\(\d+%\)\s*$/;
+var CATEGORY_LABEL_RE = /^[A-Z][A-Za-z0-9_-]*:$/;
+function slimRecalledMemoriesBlock(memories, userId) {
+  const raw = formatRecalledMemoriesBlock(memories, userId);
+  if (!raw.includes("Stored memories for ")) {
+    return raw;
+  }
+  return slimRewrite(raw, userId);
+}
+function slimRewrite(raw, userId) {
+  const lines = raw.split("\n");
+  const isBullet = (l) => l.startsWith("- ");
+  const isCategory = (l) => CATEGORY_LABEL_RE.test(l) && !l.startsWith("Stored");
+  let bulletCount = 0;
+  let categoryCount = 0;
+  for (const l of lines) {
+    if (isBullet(l)) bulletCount++;
+    else if (isCategory(l)) categoryCount++;
+  }
+  const dropCategoryLabels = categoryCount <= 1;
+  const out = [];
+  for (let i = 0; i < lines.length; i++) {
+    const line = lines[i];
+    if (line === OPEN_TAG || line === CLOSE_TAG) {
+      out.push(line);
+      continue;
+    }
+    if (line.startsWith("Stored memories for ")) {
+      out.push(`Recalled ${bulletCount} memories for "${userId}":`);
+      continue;
+    }
+    if (line === "") continue;
+    if (dropCategoryLabels && isCategory(line)) continue;
+    if (isBullet(line)) {
+      let body = line.slice(2);
+      body = body.replace(TIME_ANCHOR_RE, "");
+      body = body.replace(IMPORTANCE_SUFFIX_RE, "");
+      let j = i + 1;
+      const continuations = [];
+      while (j < lines.length) {
+        const next = lines[j];
+        if (isBullet(next) || isCategory(next) || next === "" || next === CLOSE_TAG)
+          break;
+        continuations.push(next);
+        j++;
+      }
+      if (continuations.length > 0) {
+        body = body + " " + continuations.join(" ");
+      }
+      i = j - 1;
+      body = body.replace(IMPORTANCE_SUFFIX_RE, "");
+      body = body.replace(/\s+/g, " ").trim();
+      if (body) out.push(`\xB7 ${body} `);
+      continue;
+    }
+    out.push(line);
+  }
+  return out.join("\n");
+}
+
+// src/lib/recall-orchestrator.ts
+var EMPTY = {
+  ok: false,
+  reason: "",
+  additionalContext: "",
+  memoryCount: 0,
+  knowledgeChunkCount: 0
+};
+async function recallTurn(prompt, cfg, client) {
+  if (!prompt.trim()) return { ...EMPTY, reason: "empty_prompt" };
+  if (!cfg.apiKey || !cfg.baseUrl) {
+    return { ...EMPTY, reason: "config_incomplete" };
+  }
+  if (!cfg.autoRecall) return { ...EMPTY, reason: "auto_recall_disabled" };
+  const body = {
+    query: prompt,
+    user_id: cfg.userId,
+    top_k: cfg.topK,
+    threshold: cfg.threshold
+  };
+  if (cfg.recallKnowledge) {
+    body.knowledge = { enable: true, top_k: cfg.knowledgeTopK };
+  }
+  let resp;
+  try {
+    resp = await client.postJson("/v3/memories/search/", body);
+  } catch (err) {
+    const msg = err instanceof CtxdbError ? err.message : String(err);
+    return { ...EMPTY, reason: `http_error: ${msg}` };
+  }
+  if (!resp || typeof resp !== "object") {
+    return { ...EMPTY, reason: "bad_response_shape" };
+  }
+  const r = resp;
+  const memories = Array.isArray(r.results) ? r.results : Array.isArray(r.memories) ? r.memories : [];
+  const knowledge = r.knowledge && typeof r.knowledge === "object" ? r.knowledge : null;
+  const chunks = Array.isArray(knowledge?.chunks) ? knowledge.chunks : [];
+  const blocks = [];
+  if (memories.length > 0) {
+    blocks.push(slimRecalledMemoriesBlock(memories, cfg.userId));
+  }
+  if (chunks.length > 0) {
+    blocks.push(buildExternalKnowledgeBlock(chunks, cfg.userId));
+  }
+  if (blocks.length === 0) {
+    return { ...EMPTY, ok: true, reason: "nothing_to_inject" };
+  }
+  return {
+    ok: true,
+    reason: "ok",
+    additionalContext: blocks.join("\n\n"),
+    memoryCount: memories.length,
+    knowledgeChunkCount: chunks.length
+  };
+}
+
+export {
+  recallTurn
+};

package/dist/chunk-GDJVHVIT.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+
+// src/lib/logger.ts
+import { appendFileSync, mkdirSync } from "fs";
+import { homedir } from "os";
+import { dirname, join } from "path";
+function logPath() {
+  return join(homedir(), ".ctxdb", "logs", "ctxdb.log");
+}
+var _enabled = null;
+function setDebug(enabled) {
+  _enabled = enabled;
+}
+function debug(tag, msg, data) {
+  if (_enabled !== true) return;
+  const ts = (/* @__PURE__ */ new Date()).toISOString();
+  let line = `${ts} [${tag}] ${msg}`;
+  if (data !== void 0) {
+    const s = typeof data === "string" ? data : JSON.stringify(data, null, 2);
+    line += `
+${s}`;
+  }
+  line += "\n";
+  const p = logPath();
+  try {
+    mkdirSync(dirname(p), { recursive: true });
+    appendFileSync(p, line, "utf-8");
+  } catch {
+  }
+}
+
+export {
+  setDebug,
+  debug
+};