@memorax/memorax-code 0.1.2 → 0.1.4

package/lib/memorax-code-dsh-adapter/src/protocol.mjs

@@ -0,0 +1,145 @@
+export const MEMORY_HOOK_COMMAND_VERSION = 1;
+export const MEMORY_HOOK_CLIENT = "dsh";
+
+const TURN_SCOPED_EVENT_TYPES = new Set([
+  "step/start",
+  "step/end",
+  "assistant/chunk",
+  "assistant/message",
+  "tool/call",
+  "tool/result",
+]);
+
+export function createTurnStartCommand(input) {
+  return {
+    version: MEMORY_HOOK_COMMAND_VERSION,
+    client: MEMORY_HOOK_CLIENT,
+    sessionId: requiredString(input?.sessionId, "sessionId"),
+    turn: positiveSafeInteger(input?.turn, "turn"),
+    startSeq: nonNegativeSafeInteger(input?.startSeq, "startSeq"),
+    cwd: requiredString(input?.cwd, "cwd"),
+    prompt: requiredString(input?.prompt, "prompt"),
+  };
+}
+
+export function createWritebackCommand(input) {
+  const sessionId = requiredString(input?.sessionId, "sessionId");
+  const turn = positiveSafeInteger(input?.turn, "turn");
+  const startSeq = nonNegativeSafeInteger(input?.startSeq, "startSeq");
+  const endSeq = nonNegativeSafeInteger(input?.endSeq, "endSeq");
+  const cwd = requiredString(input?.cwd, "cwd");
+  const sessionHeader = sessionHeaderValue(input?.sessionHeader, sessionId, cwd);
+  const events = exactTurnWindow(input?.events, { turn, startSeq, endSeq });
+  return {
+    version: MEMORY_HOOK_COMMAND_VERSION,
+    client: MEMORY_HOOK_CLIENT,
+    sessionId,
+    turn,
+    startSeq,
+    endSeq,
+    cwd,
+    sessionHeader: structuredClone(sessionHeader),
+    events: structuredClone(events),
+  };
+}
+
+export function createSkillReminderCommand(input) {
+  return {
+    version: MEMORY_HOOK_COMMAND_VERSION,
+    client: MEMORY_HOOK_CLIENT,
+    sessionId: requiredString(input?.sessionId, "sessionId"),
+    turn: positiveSafeInteger(input?.turn, "turn"),
+    cwd: requiredString(input?.cwd, "cwd"),
+    content: requiredString(input?.content, "content"),
+    triggers: skillReminderTriggers(input?.triggers),
+  };
+}
+
+/**
+ * Select and verify the exact persisted interval after readFrom(). Later Turns
+ * may already be durable, so only the inclusive requested suffix is returned.
+ */
+export function exactTurnWindow(events, expected) {
+  if (!Array.isArray(events)) throw new TypeError("DSH persisted events must be an array");
+  const turn = positiveSafeInteger(expected?.turn, "turn");
+  const startSeq = nonNegativeSafeInteger(expected?.startSeq, "startSeq");
+  const endSeq = nonNegativeSafeInteger(expected?.endSeq, "endSeq");
+  if (endSeq < startSeq) throw new Error("DSH turn endSeq precedes startSeq");
+
+  const selected = [];
+  for (const event of events) {
+    if (!record(event) || !Number.isSafeInteger(event.seq) || event.seq < 0) {
+      throw new Error("DSH persisted event has an invalid sequence number");
+    }
+    if (event.seq > endSeq) break;
+    selected.push(event);
+  }
+  const expectedLength = endSeq - startSeq + 1;
+  if (selected.length !== expectedLength) {
+    throw new Error("DSH persisted turn interval is incomplete");
+  }
+  for (let index = 0; index < selected.length; index += 1) {
+    if (selected[index].seq !== startSeq + index) {
+      throw new Error("DSH persisted turn interval is not contiguous");
+    }
+  }
+
+  const first = selected[0];
+  const last = selected.at(-1);
+  if (first.type !== "turn/start" || first.data?.turn !== turn) {
+    throw new Error("DSH persisted turn interval has no matching start boundary");
+  }
+  if (last.type !== "turn/end" || last.data?.turn !== turn) {
+    throw new Error("DSH persisted turn interval has no matching end boundary");
+  }
+  for (let index = 1; index < selected.length - 1; index += 1) {
+    const event = selected[index];
+    if (event.type === "turn/start" || event.type === "turn/end") {
+      throw new Error("DSH persisted turn interval contains a nested turn boundary");
+    }
+    if (TURN_SCOPED_EVENT_TYPES.has(event.type) && event.data?.turn !== turn) {
+      throw new Error("DSH persisted turn event belongs to another turn");
+    }
+  }
+  return selected;
+}
+
+function sessionHeaderValue(value, sessionId, cwd) {
+  if (!record(value)) throw new TypeError("DSH sessionHeader must be an object");
+  if (value.id !== sessionId) throw new Error("DSH sessionHeader id does not match sessionId");
+  if (value.cwd !== cwd) throw new Error("DSH sessionHeader cwd does not match cwd");
+  return value;
+}
+
+function requiredString(value, name) {
+  if (typeof value !== "string" || !value.trim()) {
+    throw new TypeError(`DSH ${name} must be a non-empty string`);
+  }
+  return value.trim();
+}
+
+function positiveSafeInteger(value, name) {
+  if (!Number.isSafeInteger(value) || value < 1) {
+    throw new TypeError(`DSH ${name} must be a positive safe integer`);
+  }
+  return value;
+}
+
+function nonNegativeSafeInteger(value, name) {
+  if (!Number.isSafeInteger(value) || value < 0) {
+    throw new TypeError(`DSH ${name} must be a non-negative safe integer`);
+  }
+  return value;
+}
+
+function record(value) {
+  return value !== null && typeof value === "object" && !Array.isArray(value);
+}
+
+function skillReminderTriggers(value) {
+  if (!Array.isArray(value) || value.length === 0
+    || value.some((trigger) => trigger !== "cadence" && trigger !== "post_compaction")) {
+    throw new TypeError("DSH triggers must be a non-empty array of supported reminder triggers");
+  }
+  return [...new Set(value)];
+}

package/lib/memorax-code-dsh-adapter/src/runtime-state.mjs

@@ -0,0 +1,132 @@
+import { readFileSync } from "node:fs";
+import { isAbsolute, join, relative, resolve, sep } from "node:path";
+
+import { parseDshVersion } from "./dsh-version.mjs";
+
+const PACKAGE_METADATA_VERSION = 1;
+const STATE_VERSION = 1;
+/** Read the current durable enablement authority for this installed DSH bundle. */
+export function requireEnabledDshRuntime(pluginRoot) {
+  const authority = requireDshRuntimeAuthority(pluginRoot);
+  if (!authority.enabled) throw disabledError();
+  return {
+    memoraxCodeCommand: authority.memoraxCodeCommand,
+    memoraxCodeHome: authority.memoraxCodeHome,
+    dshCommand: authority.dshCommand,
+    dshHome: authority.dshHome,
+    dshVersion: authority.dshVersion,
+    profiles: authority.profiles,
+    revision: authority.revision,
+  };
+}
+
+/** Validate one installed bundle's metadata against its durable lifecycle state. */
+export function requireDshRuntimeAuthority(pluginRoot) {
+  const root = resolveRequiredPath(pluginRoot, "pluginRoot");
+  const metadata = readRecord(join(root, ".memorax-code-package.json"));
+  if (metadata?.version !== PACKAGE_METADATA_VERSION
+    || !nonEmptyString(metadata.memoraxCodeCommand)
+    || !nonEmptyString(metadata.memoraxCodeHome)
+    || !nonEmptyString(metadata.dshCommand)
+    || !nonEmptyString(metadata.dshHome)
+    || !parseDshVersion(metadata.dshVersion)
+    || !nonEmptyString(metadata.sourceAdapterRoot)
+    || !nonEmptyString(metadata.runtimeBundleRoot)) {
+    throw disabledError();
+  }
+
+  const memoraxCodeHome = resolve(metadata.memoraxCodeHome);
+  const dshHome = resolve(metadata.dshHome);
+  const runtimeBundleRoot = resolve(metadata.runtimeBundleRoot);
+  if (!isPathInside(
+    runtimeBundleRoot,
+    join(memoraxCodeHome, "adapters", "dsh", "runtime", "generations"),
+  )) {
+    throw disabledError();
+  }
+  const state = readRecord(join(memoraxCodeHome, "adapters", "dsh", "state.json"));
+  if (state?.version !== STATE_VERSION
+    || state.runtime !== "dsh"
+    || state.integration !== "plugin"
+    || typeof state.enabled !== "boolean"
+    || resolveString(state.memoraxCodeHome) !== memoraxCodeHome
+    || resolveString(state.dshHome) !== dshHome
+    || resolveString(state.adapterRoot) !== resolve(metadata.sourceAdapterRoot)
+    || resolveString(state.runtimeBundleRoot) !== runtimeBundleRoot
+    || state.memoraxCodeCommand !== metadata.memoraxCodeCommand
+    || state.dshCommand !== metadata.dshCommand
+    || state.dshVersion !== metadata.dshVersion
+    || !Array.isArray(state.profiles)
+    || !state.profiles.every(validProfileName)
+    || !timestampString(state.updatedAt)) {
+    throw disabledError();
+  }
+
+  return {
+    enabled: state.enabled,
+    sourceAdapterRoot: resolve(metadata.sourceAdapterRoot),
+    runtimeBundleRoot,
+    memoraxCodeCommand: metadata.memoraxCodeCommand,
+    memoraxCodeHome,
+    dshCommand: metadata.dshCommand,
+    dshHome,
+    dshVersion: metadata.dshVersion,
+    profiles: [...state.profiles],
+    revision: state.updatedAt,
+  };
+}
+
+function readRecord(path) {
+  try {
+    const value = JSON.parse(readFileSync(path, "utf8"));
+    return value !== null && typeof value === "object" && !Array.isArray(value)
+      ? value
+      : undefined;
+  } catch {
+    return undefined;
+  }
+}
+
+function resolveRequiredPath(value, name) {
+  const normalized = nonEmptyString(value);
+  if (!normalized) throw new TypeError(`DSH ${name} must be a non-empty path`);
+  return resolve(normalized);
+}
+
+function resolveString(value) {
+  const normalized = nonEmptyString(value);
+  return normalized ? resolve(normalized) : undefined;
+}
+
+function nonEmptyString(value) {
+  return typeof value === "string" && value.trim() ? value.trim() : undefined;
+}
+
+function timestampString(value) {
+  const normalized = nonEmptyString(value);
+  return normalized && Number.isFinite(Date.parse(normalized)) ? normalized : undefined;
+}
+
+function validProfileName(value) {
+  return typeof value === "string"
+    && value.length > 0
+    && value !== "."
+    && value !== ".."
+    && value !== "node_modules"
+    && !value.includes("/")
+    && !value.includes("\\");
+}
+
+function isPathInside(value, parent) {
+  const child = relative(resolve(parent), resolve(value));
+  return child !== ""
+    && child !== ".."
+    && !child.startsWith(`..${sep}`)
+    && !isAbsolute(child);
+}
+
+function disabledError() {
+  const error = new Error("MemoraX Code DSH integration is not enabled");
+  error.code = "MEMORAX_CODE_DSH_DISABLED";
+  return error;
+}

package/lib/memorax-code-opencode-adapter/hooks/repo-memory-job.mjs

@@ -0,0 +1,37 @@
+#!/usr/bin/env node
+import { existsSync } from "node:fs";
+import { dirname, resolve } from "node:path";
+import { fileURLToPath } from "node:url";
+import { runRepoMemoryJob } from "../../memorax-code-adapter-common/src/repo-memory/repo-memory-job-supervisor.mjs";
+import { evaluateRepository } from "../../memorax-code-adapter-common/src/repo-memory/repo-memory-update-policy-evaluator.mjs";
+
+const hookDir = dirname(fileURLToPath(import.meta.url));
+const adapterRoot = dirname(hookDir);
+const packagedValidator = resolve(adapterRoot, "skills/memorax-code/scripts/validate_memory.py");
+const validatorPath = existsSync(packagedValidator)
+  ? packagedValidator
+  : resolve(adapterRoot, "../memorax-code-codex-adapter/skills/memorax-code/scripts/validate_memory.py");
+
+try {
+  const payload = runRepoMemoryJob(process.argv.slice(2), {
+    runner: "opencode",
+    finalMessageSource: "stdout",
+    memorySkillInvocation: "the `memorax-code` skill",
+    validatorPath,
+    evaluateRepository,
+    createCommand({ prompt, repo }) {
+      return [
+        process.execPath,
+        resolve(adapterRoot, "src/repo-memory-server-runner.mjs"),
+        "--repo",
+        repo,
+        "--prompt",
+        prompt,
+      ];
+    },
+  });
+  process.stdout.write(`${JSON.stringify(payload)}\n`);
+} catch (error) {
+  process.stderr.write(`${error instanceof Error ? error.message : String(error)}\n`);
+  process.exit(1);
+}

package/lib/memorax-code-opencode-adapter/package.json

@@ -0,0 +1,10 @@
+{
+  "name": "@memorax-code/opencode-adapter",
+  "version": "0.1.4",
+  "private": true,
+  "type": "module",
+  "description": "OpenCode plugin adapter for MemoraX Code memory services.",
+  "scripts": {
+    "test": "node --test test/*.test.mjs"
+  }
+}

package/lib/memorax-code-opencode-adapter/skills/memorax-code/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: memorax-code
+description: >-
+  Use this skill as the single router for persistent coding and repository-local
+  memory. Invoke it whenever a request may involve prior-work knowledge,
+  repository memory, reusable procedures or rules, durable profile or
+  interaction preferences, or information worth retaining beyond the current
+  task. This applies without memory wording, including habits, preferences,
+  checklists, action sequences, prerequisites, gates, exceptions, validation
+  rules, communication style, preferred language, or result presentation.
+  Classify the request as coding memory, repository memory, personal procedure
+  memory, personal profile memory, or no persistent memory, then route it to the
+  matching operation. Invoking this router does not require coding-memory
+  search. Reuse a relevant coding-memory result already retrieved in this
+  conversation; otherwise let the matching operation decide on search. Prefer
+  this router over underlying memory workflows. Ask one focused question only when
+  memory authority remains ambiguous.
+---
+
+# MemoraX Code
+
+Classify the requested memory authority first, then its operation. Load only the matching reference unless the request genuinely spans authorities or operations.
+
+After selecting an operation reference, read it completely in a standalone
+tool call and wait for the full result before constructing or executing that
+operation. Never combine reading a required reference with the command or
+action it governs in the same shell command or tool call.
+
+## Authority Router
+
+### MemoraX Code Coding Memory
+
+Use MemoraX Code coding memory for reusable engineering knowledge learned across coding work: prior fixes, failed approaches, coding conventions, implementation pitfalls, validation patterns, and design rationale.
+
+- Read [references/memorax-search.md](references/memorax-search.md) to recall or search coding memory.
+- Read [references/memorax-add.md](references/memorax-add.md) to save a grounded reusable coding lesson.
+
+### Repo Memory
+
+Use repo memory for repository identity, architecture maps, module routing, local commit history, and GitHub or GitLab PR, MR, and issue evidence stored under `.repo_memory/PROFILE.md`, `.repo_memory/resources/`, and `.repo_memory/raw/`.
+
+- Read [references/repo-read.md](references/repo-read.md) to inspect existing repo memory.
+- Read [references/repo-build.md](references/repo-build.md) for first-time creation, full rebuilds, or full refreshes.
+- Read [references/repo-update.md](references/repo-update.md) for incremental updates to an existing bundle.
+- Read [references/repo-templates.md](references/repo-templates.md) only when the build or update operation needs to author repo memory files.
+
+### Personal Memory
+
+Use personal memory for user-owned repository procedures and durable profile or interaction preferences stored under `.repo_memory/procedure-memory/` and `.repo_memory/user-profile/`.
+
+- Read [references/personal-read.md](references/personal-read.md) to list, recall, or apply personal memory.
+- Read [references/personal-write.md](references/personal-write.md) to save, update, forget, or delete personal memory.
+
+## Tie Breakers
+
+- Route ordered actions, checklists, prerequisites, gates, exceptions, and validation rules to personal procedure memory, even when phrased as "I prefer", "I like", "我的习惯", or "我喜欢".
+- Route preferred name, answer language, tone, verbosity, explanation style, and result presentation to personal profile memory.
+- Route task-learned repairs, coding pitfalls, project engineering conventions, and reusable design lessons to MemoraX Code coding memory.
+- Route prior project discussions, experiment conclusions, saved engineering findings, earlier fixes, and reusable project lessons to MemoraX Code coding memory. Do not route them to repo memory merely because they concern a project. Use repo memory for repository identity, architecture, module maps, commits, PRs, MRs, and issues.
+- Route repository architecture, module maps, commit history, PRs, MRs, and issues to repo memory. Verify claims about current behavior against live code.
+- Use both repo memory and MemoraX Code coding memory only when a request genuinely needs distinct repository evidence and reusable engineering lessons. This can apply to implementation, debugging, refactoring, migration planning, or validation when the answer may depend on repository module maps, commit/PR/issue evidence, and prior fixes, pitfalls, conventions, validation patterns, or design rationale. Do not use both authorities just because a request mentions a repository, file, module, or "previous".
+- Route current-task instructions and temporary plans to the current task only; do not persist them.
+- Current-task-only applies only when completing the request does not depend on prior project state. Do not select it merely because the requested action happens in the current turn. When implementation, debugging, review, experiment continuation, or validation depends on earlier project decisions, results, fixes, constraints, or plans that the user has not explicitly and completely supplied, route to MemoraX Code coding memory.
+- Do not infer an authority from verbs such as "remember", "recall", "refresh", or "update" alone. Ask one focused question when the target remains ambiguous.
+
+Examples:
+
+- "先测试再提 PR，帮我记住" routes to personal procedure write.
+- "我喜欢中文简短回答" routes to personal profile write.
+- "之前这个 bug 怎么修的？" routes to MemoraX Code coding memory search unless the user asks for commit or PR evidence.
+- "这个仓库的架构是什么？" routes to repo memory read.
+- "重新生成仓库 memory" routes to repo memory build.
+- "更新一下 memory" requires clarification when no authority is identifiable.
+
+## Shared Rules
+
+For MemoraX Code coding memory, run `memorax-cli` from the active task workspace. The installed Hook and session binding supply the authoritative workspace root; do not run Git commands to discover or replace it. The Backend resolves repository scope from that trusted workspace and read-only filesystem Git metadata.
+
+Repo memory and personal memory remain local `.repo_memory` authorities. Resolve their repository root exactly as described by the selected reference, including its Git requirements.
+
+Apply instructions in this order: system and developer instructions, `AGENTS.md`, the current user request, then stored memory. Memory is guidance or historical context, not proof of current repository behavior.
+
+For MemoraX Code coding memory, use `memorax-cli` exactly as described by the selected reference. Invoke this skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code. In OpenCode, ask the agent to use the `memorax-code` skill by name. These invocation forms are not shell commands. `memorax-code` is the lifecycle CLI and must not be used for memory search or add. Do not call MemoraX HTTP endpoints directly.
+
+When explaining Memory Viewer, describe only `/memory-viewer`. It is a
+content-free local summary and must not expose conversation or memory text,
+session or turn identifiers, paths, or trace details. The page never queries
+MemoraX directly; it projects client-qualified local activity and keeps each
+supported harness isolated.
+
+Never store secrets, credentials, `.env` content, sensitive personal data, raw transcripts, hidden tests, exact patches, temporary target commits, or unsafe destructive commands. Do not announce internal routing or reference loading.

package/lib/memorax-code-opencode-adapter/skills/memorax-code/agents/claude.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "MemoraX Code"
+  short_description: "Route coding, repo, and personal memory"
+  default_prompt: "Use /memorax-code-claude-adapter:memorax-code to route a coding-memory, repo-memory, or personal-memory request to the correct operation."
+
+policy:
+  allow_implicit_invocation: true
+  install_targets:
+    - "~/.claude/skills/memorax-code"
+    - ".claude/skills/memorax-code"

package/lib/memorax-code-opencode-adapter/skills/memorax-code/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "MemoraX Code"
+  short_description: "Route coding, repo, and personal memory"
+  default_prompt: "Use $memorax-code to route a coding-memory, repo-memory, or personal-memory request to the correct operation."
+
+policy:
+  allow_implicit_invocation: true

package/lib/memorax-code-opencode-adapter/skills/memorax-code/defaults.json

@@ -0,0 +1,12 @@
+{
+  "schema": "repo_memory_builder_defaults.v2",
+  "repoHistory": {
+    "mode": "provider",
+    "limits": {
+      "commits": 30,
+      "prs": 30,
+      "issues": 30
+    }
+  },
+  "summaryChars": 4000
+}

package/lib/memorax-code-opencode-adapter/skills/memorax-code/references/memorax-add.md

@@ -0,0 +1,86 @@
+# MemoraX Code Coding Memory Add
+
+Use these instructions only to add reusable coding knowledge through `memorax-cli`. Invoke the skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code. In OpenCode, ask the agent to use the `memorax-code` skill by name. Do not route memory operations through the lifecycle-only `memorax-code` CLI. Do not use this authority for personal procedures, interaction preferences, generated repository facts, or one-off task details.
+
+## Eligible Knowledge
+
+Add a coding memory only when the task yields stable, grounded, reusable engineering knowledge, such as:
+
+- a verified repair invariant or validation pattern;
+- a reusable failed-attempt lesson;
+- a confirmed coding convention, lifecycle boundary, or implementation pitfall;
+- durable design rationale that will help future coding work.
+
+Route user-owned ordered actions, checklists, gates, and work rules to personal procedure memory. Route preferred language, tone, verbosity, name, and presentation to personal profile memory. Route commit, PR, issue, architecture-map, and repository-history facts to repo memory.
+
+Do not add positive repair lessons based only on unverified edits or assistant self-report. Verification may come from a focused test, evaluator, CI check, accepted review, manual reproduction, or deployed behavior. A failed attempt may be saved as negative evidence when the failure itself is clear and reusable.
+
+## Add Workflow
+
+For a proactive add, write all generated prose in `--memory`, `--reason`, and the confirmation in the language of the user's current request; preserve exact code, API, path, workflow, and project identifiers.
+
+Run from the active task workspace. Pass the memory and reason directly. Put every dynamically generated `--memory` and `--reason` value in single quotes, never double quotes. Treat `$HOME`, backticks, and `$(command)` as literal text inside those quotes. Replace each literal single quote in a value with the exact POSIX sequence `'\''`.
+
+```bash
+memorax-cli add \
+  --memory 'Concise reusable memory.' \
+  --type procedural \
+  --reason 'Capture reusable coding memory.'
+```
+
+Use an appropriate supported type such as `core`, `semantic`, `procedural`, `episodic`, or `unclassified`. Use `preference` only for an engineering convention owned by MemoraX Code coding memory, not for a personal interaction preference.
+
+For a complex verified repair or failed approach, use this compact card when it improves later retrieval:
+
+```text
+CODE_AGENT_MEMORY
+repo: <repository or product area>
+scope: <module/path::symbol/API or lifecycle boundary>
+status: <verified|failed_attempt|candidate>
+signal: <test, CI, review, reproduction, deployment, failure, or unknown>
+problem: <small behavioral symptom or engineering situation>
+technical_context: <stable API, lifecycle, state owner, or data-shape detail>
+surfaces: <observable producer/consumer or setup/runtime/cleanup boundaries>
+failed_shape: <reusable wrong assumption or unsafe patch shape, or none>
+validation: <small reusable check contract>
+principle: <abstract invariant or decision rule>
+anchors: <stable repository source, tests, or public docs>
+```
+
+Keep the card under 1,100 characters when practical. It must guide future investigation while still requiring live-code inspection.
+
+Pass a completed multi-line card as one single-quoted `--memory` argument:
+
+```bash
+memorax-cli add \
+  --memory 'CODE_AGENT_MEMORY
+repo: owner/name
+scope: module/path::symbol
+status: verified
+signal: focused test passed
+problem: concise reusable symptom
+technical_context: stable implementation fact
+surfaces: affected boundary
+failed_shape: reusable pitfall or none
+validation: smallest reusable check
+principle: reusable invariant
+anchors: stable/source/path' \
+  --type procedural \
+  --reason 'Capture verified reusable coding memory.'
+```
+
+If add fails, report the exact failure and do not retry automatically, bypass the CLI, or call MemoraX directly.
+
+If a successful Add result reports `workspaceScopeFallbackReason: git_metadata_invalid`, malformed or incomplete metadata inside a direct `.git` directory was downgraded to the normalized local folder scope. Add has already been submitted with the reported `effectiveUserId`. Present its `userNotice` once without pausing the current task or asking the user to repair Git first, then continue the current task. After the repository or `.git` metadata is repaired, later Search, Add, and automatic writeback in the same client session automatically use the restored Git repository scope.
+
+If `memorax-cli add` reports `workspace_scope_mismatch` or `workspace_scope_unavailable`, do not bypass the scope. Do not change the CLI working directory and retry. Tell the user that the memory was not submitted and no request was sent to MemoraX, then present the CLI's `userAction` in natural language. Continue the current task using only live code and documentation.
+
+## Exclusions
+
+Do not add secrets, credentials, private URLs, raw authorization headers, exact patches, target commits, hidden tests, target diffs, vulnerability details, exploit steps, copied source, long logs, stack traces, raw transcripts, temporary errors, or facts directly recoverable from current files and git history.
+
+Do not add speculation, assistant-only praise, or a current instruction merely because it contains "remember". Return to `SKILL.md` when the content belongs to personal memory or repo memory.
+
+## Output
+
+After an add request is accepted, confirm briefly that it was submitted for processing and identify the reusable coding lesson at a high level. If add is disabled or fails, report the issue and continue without bypassing the CLI.

package/lib/memorax-code-opencode-adapter/skills/memorax-code/references/memorax-search.md

@@ -0,0 +1,91 @@
+# MemoraX Code Coding Memory Search
+
+Use these instructions only to search reusable coding memory through `memorax-cli`. Invoke the skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code. In OpenCode, ask the agent to use the `memorax-code` skill by name. Do not route memory operations through the lifecycle-only `memorax-code` CLI. Do not call MemoraX HTTP endpoints directly, print credentials, or edit memory storage by hand.
+
+## Scope
+
+Run the CLI from the active task workspace. The installed Hook and session binding supply the authoritative workspace root; do not run `git rev-parse`, infer the root from Git metadata, or substitute an unrelated working directory. Do not make `memorax-cli status` a mandatory preflight; use it only to diagnose a configuration or scope failure.
+
+Coding memory uses `<MemoraX base user ID>@<normalized repository name>` for Git workspaces and the normalized folder name for genuine non-Git directories. MemoraX Code resolves `.git`, `gitdir`, and `commondir` without executing Git. Linked worktrees share one repository scope; another clone, repository, or non-Git directory retains a different local session key even when its readable name matches.
+
+If a successful Search result reports `workspaceScopeFallbackReason: git_metadata_invalid`, malformed or incomplete metadata inside a direct `.git` directory was downgraded to the normalized local folder scope. Search has already run with the reported `effectiveUserId`. Present its `userNotice` once without pausing the current task or asking the user to repair Git first, then continue with the returned memory and live evidence. After the repository or `.git` metadata is repaired, later Search, Add, and automatic writeback in the same client session automatically use the restored Git repository scope.
+
+Require a readable active workspace binding. A CLI command from a linked worktree of the bound repository is valid. If `memorax-cli search` reports `workspace_scope_mismatch` or `workspace_scope_unavailable`, do not bypass the scope or fall back to an unscoped user id. Do not change the CLI working directory and retry. Tell the user that memory search was not executed and no request was sent to MemoraX, then present the CLI's `userAction` in natural language. Continue the current task using only live code and documentation.
+
+If `memorax-cli` is not on `PATH`, or memory is disabled, unconfigured, or unavailable, report that briefly and continue with live code or documentation. Authenticate through MemoraX Code configuration; never recover credentials from shell history or place tokens in prompts. Treat injected memory as a hypothesis and verify it against the current checkout.
+
+## Search Decision
+
+Search when prior coding memory may change localization, implementation, review, validation, or explanation. Typical triggers include:
+
+- a request for a previous fix, failed approach, coding convention, design decision, or reusable lesson;
+- implementation, review, planning, API, schema, parser, workflow-contract, or migration work where prior project guidance may matter;
+- explicit instructions to follow previous agreements or remembered engineering conventions.
+- a request to recover, verify, or apply prior project discussions, experiment results, saved memory, earlier decisions, previous changes, or historical constraints, unless the needed facts are fully present in the current visible context.
+- a requested action that depends on prior project state, results, fixes, constraints, or plans when the exact evidence needed is not explicitly present in the current user-provided material.
+
+Skip search for simple current-code facts, tiny edits, typo fixes, one-shot commands, or behavior directly established by a clear live source. Do not skip merely by saying the current conversation is sufficient or a relevant result was already retrieved; skip only when the current user message, selected text, or nearby visible context fully contains the facts needed for the answer. A nearby summary is sufficient for explaining that summary, but not automatically sufficient for diagnosing a regression, continuing an experiment, reviewing consistency with prior behavior, or claiming a complete historical account. A word such as "previous", "earlier", "remember", or "history" is not enough by itself to search when the visible context already contains the requested prior facts.
+
+Do not search merely because a prior result or fix might exist. For an exact calculation from currently available data, or a current screenshot or reproducible symptom with sufficient live evidence, use the current evidence first. Search only when the user request or visible context establishes a concrete historical dependency.
+
+Choose the closest coding scene to shape the query:
+
+- **Development:** implementation, debugging, refactoring, test repair, build failures, feature work, API design, or migration planning.
+- **Review:** diff, commit, PR, patch, audit, risk assessment, or review-comment handling.
+- **Understanding:** implementation location, module explanation, architecture rationale, or repository comprehension when repo memory is not the requested authority.
+
+If the user asks for commit, PR, MR, issue, or repository architecture evidence, return to `SKILL.md` and route to repo memory instead.
+
+## Query Workflow
+
+Before searching, identify the user's current action, target, concrete behavior or symptom, and the historical knowledge that could change the next action. When the request is fragmented, derive one narrow working intent from only its explicit target, condition, and requested or implied outcome. Do not add generic security, authorization, concurrency, auditing, reliability, or best-practice concerns unless the request names that boundary or it is necessary to resolve the working intent. Ask one focused question when no actionable intent can be named.
+
+Run up to two focused first-round searches before answering or editing: a primary query for the smallest user-facing decision, and a materially different complementary query only when a second independent fact can change the action. Keep one query when the request describes one strongly coupled calculation, diagnosis, ownership question, or lifecycle decision; do not split it merely to create coverage. Run independent first-round searches in parallel by default. If parallel execution encounters a transport, rate-limit, or caller-environment failure, run any remaining searches serially; do not switch solely because a successful search returns an unexpected number of items. After merging the first-round results, run at most one follow-up query only when one named residual gap can change implementation, localization, risk, or validation. Do not use the follow-up merely because results are few, generic, or incomplete.
+
+Write each query as one short natural-language question or intent statement, not a keyword list. Derive it from the user's retrieval goal instead of copying or concatenating nouns from the prompt. Follow the user's language for the prose while preserving exact code, API, path, workflow, and project identifiers. Retain at least one distinctive noun phrase from the user's wording as an anchor, together with any explicit negation, time/order, quantity, or scope qualifier. Also retain one stable task entity explicitly established by the current conversation or live code/documentation when it is needed to resolve that anchor or make the target decidable; do not drop it merely because it is absent from the newest fragmented user message. Do not replace an anchor or stable entity with a more abstract mechanism, a more specific implementation guess, or an unverified term. Preserve whether a retained detail is an observed symptom, desired outcome, disputed field or hypothesis, or explicit exclusion; do not turn an observation into a required invariant or replace a named disputed field with a generic reference.
+
+Preserve the user's requested answer shape as well as the target: for example, whether a value was introduced by a prior code change, which failed experiments require rerun, how a negative case differs, what source boundary applies, or which existing plan remains current. Encode an explicit exclusion, source boundary, or qualifier such as only, previous, failed, negative, not, latest, or before/after when it changes the answer. Do not turn an imperative, URL, copied log, or full task request into the query verbatim; extract the smallest reusable historical fact that could change the next action. When the user explicitly names several independent deliverables and their respective historical facts could change different next actions, use the existing two-query allowance for complementary coverage: let the primary query cover the central implementation or decision, and let the complementary query cover the separate validation, artifact, reporting, or boundary question. Do not split one tightly coupled task or create a second query merely to enumerate every noun.
+
+State a fact-sized relationship that can change the next action: a target under a condition, and the decision, invariant, consequence, root cause, ownership, compatibility, validation question, or requested answer at issue. For behavior, data, and lifecycle work, every query must use this visible shape: `<target>: <condition>，<decision / invariant / consequence / validation question>?`. Keep the colon in both Chinese and English so the target, condition, and decision boundary remain explicit. Do not emit a generic topic, a keyword list, a label such as `primary query`, or an explanation around the query.
+
+For a complementary first-round pair, each query must stand alone and cover a different decision boundary. Use a complementary pair only when the provided context gives each decision boundary a distinct exact code, API, path, workflow, or project identifier; otherwise keep one focused combined query that preserves both user-stated facts. Do not merely restate the same question with synonyms. If the user describes only one tightly coupled decision, emit exactly one query. Use one or two stable exact identifiers when they sharpen the query, and integrate them grammatically instead of appending search tags or filler. Use only user-provided anchors and stable terms from live code or documentation; do not reconstruct unseen fact wording from recalled memory.
+
+Pass the query directly with `--query`. Put every dynamically generated query in single quotes, never double quotes. Treat `$HOME`, backticks, and `$(command)` as literal text inside those quotes. Replace each literal single quote in the value with the exact POSIX sequence `'\''`.
+
+Use these actual output shapes as examples. They are queries themselves, not full user prompts or instructions for the user. Each Chinese/English pair is a language variant: choose the one matching the user, never run both merely because both are shown. The comments explain the example only and are not part of emitted query text.
+
+```bash
+# One tightly coupled decision: emit one query.
+memorax-cli search --query 'Trace 生产版本：升级后到达的记录中，应以哪个客户端版本字段判断由旧插件产生，而非新版本上传进程？'
+memorax-cli search --query 'Trace producer version: after an upgrade, which client-version field shows that an event came from the old plugin rather than the new uploader?'
+
+# Two independent boundaries: emit a complementary pair.
+memorax-cli search --query '任务上下文：升级新包后已打开任务仍按旧提示，是否绑定旧版本且必须新开对话？'
+memorax-cli search --query '包缓存版本冲突：本地新包与缓存冲突时，已打开任务为何仍使用旧提示，如何确认实际加载版本？'
+memorax-cli search --query 'Task context after upgrade: can an already-open task keep old injected context, and must validation use a fresh task?'
+memorax-cli search --query 'Package-cache version collision: how do we confirm which version the active task actually loaded?'
+
+# Preserve an explicit lifecycle condition and the required invariant.
+memorax-cli search --query '自动写回：事件回调不等待 Promise 时，如何在消息终态后执行并防止重复？'
+memorax-cli search --query 'Automatic writeback: when an event callback does not await a Promise, how should it run after message terminal state without duplicates?'
+
+# Preserve a source boundary rather than turning it into a generic SDK question.
+memorax-cli search --query '桌面 SDK 数据权威：无原生命令行时，应从哪些规范化消息和会话生命周期事件获取数据？'
+memorax-cli search --query 'Desktop SDK authority: without a native CLI, which normalized messages and session lifecycle events are authoritative?'
+```
+
+Keep queries under 25 words when practical for the language, but do not shorten them into ungrammatical fragments. Exclude secrets, private URLs, full prompts, raw transcripts, copied files, long logs, stack traces, and one-off task details.
+
+Do not use abstract query facets such as "state", "fix", "safety", or "best practice" unless they are the concrete target. Do not use generic security or safety queries as complementary queries; bind every query to an exact target, condition, and behavior boundary.
+
+Merge and deduplicate first-round results by item identity when available, otherwise by matching scope, condition, claim, and consequence. Accept a memory only when all three checks pass: it has the same component, API, workflow, or ownership boundary; it has the same behavior, symptom, condition, or change; and it supplies a condition, conclusion, consequence, fix, or validation idea that can change the current action. Read or summarize at most two accepted direct hits. Prefer memories matching the current repository, module, API, lifecycle surface, ownership boundary, behavior, and failure mode. Treat verified memories as routing and validation hints, not patch recipes. Treat failed-attempt memories as negative evidence. Ignore stale or unrelated items and anything conflicting with current source, tests, or durable documentation. For application questions, reject retrieval-strategy, evaluation, prompting, or workflow-process memories as domain evidence even if they repeat application terms. If no memory passes all three checks, say that memory is insufficient for the requested decision rather than filling the gap with a generic principle.
+
+## Transport Failures
+
+If search fails with `fetch failed`, `This operation was aborted`, a timeout, DNS failure, `ENOTFOUND`, `EAI_AGAIN`, or a similar transport or sandbox error, retry the same `memorax-cli search` once in an approved network-enabled execution mode when one is available. Preserve the same query, workspace, and environment variables.
+
+Do not apply this retry to `memorax-cli add`, authentication or configuration failures, or HTTP errors. If no approved mode is available or the one retry fails, report the exact CLI failure and continue with live evidence. Do not interpret a transport failure as an empty result, bypass the CLI, or call MemoraX directly.
+
+## Output
+
+Mention only an invariant, pitfall, convention, or validation idea that materially affects the answer. Ground claims about current implementation behavior in live code and checks.