PR #65914: fix(memory): respect qmd status timeout and skip checkpoint exports

• Repository: openclaw/openclaw
• Author: shawnduggan
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/65914

Description (problem / solution / changelog)

Summary

This PR fixes two concrete QMD recall issues in extensions/memory-core/src/memory/qmd-manager.ts:

1. probeVectorAvailability() now respects the configured memory.qmd.limits.timeoutMs
2. QMD session export now excludes .checkpoint. transcript snapshots from exported session documents

Problem 1: false QMD vector-health failures

Before this change, probeVectorAvailability() hard-capped qmd status to 5 seconds:

const result = await this.runQmd(["status"], {
  timeoutMs: Math.min(this.qmd.limits.timeoutMs, 5_000),
});

That means a config like this:

{
  "memory": {
    "qmd": {
      "limits": { "timeoutMs": 10000 }
    }
  }
}

still timed out after 5 seconds during the status probe.

Why that matters

openclaw memory status and related vector-health checks can then report QMD as unavailable even when the underlying QMD index is healthy and just needs longer than 5 seconds to answer qmd status.

That is a misleading health signal, because the configured timeout is being ignored specifically on the probe path.

Fix

Use the configured timeout directly:

timeoutMs: this.qmd.limits.timeoutMs

Problem 2: checkpoint transcript noise in session recall

Before this change, exportSessions() iterated every session file returned by listSessionFilesForAgent(this.agentId) and exported all of them into the QMD session collection.

That included checkpoint snapshots like:

• some-session.checkpoint.123.jsonl

Those files are valid recovery artifacts, but they are poor recall documents because they duplicate live session content and add noisy near-duplicates to semantic search.

Why this change is intentionally narrow

This PR excludes only .checkpoint. files at the QMD export layer:

const files = (await listSessionFilesForAgent(this.agentId)).filter((sessionFile) => {
  const baseName = path.basename(sessionFile);
  return !baseName.includes(".checkpoint.");
});

I kept this scoped to checkpoint snapshots because that is the cleanest low-risk duplicate class. I did not broaden the PR to other transcript artifact types here.

Validation

Added tests for both behaviors:

• uses the configured qmd timeout for status probes
• excludes checkpoint transcripts from exported qmd session documents

Ran:

pnpm vitest run extensions/memory-core/src/memory/qmd-manager.test.ts src/memory-host-sdk/host/session-files.test.ts

Result:

• 2 test files passed
• 91 tests passed

File references

Main code changes:

• extensions/memory-core/src/memory/qmd-manager.ts:1179-1183
• extensions/memory-core/src/memory/qmd-manager.ts:1918-1921

Added tests:

• extensions/memory-core/src/memory/qmd-manager.test.ts

Related issue

Separate issue for a different QMD default-collection bug, not fixed in this PR:

• #65913

Changed files

• extensions/memory-core/src/memory/qmd-manager.test.ts (modified, +70/-0)
• extensions/memory-core/src/memory/qmd-manager.ts (modified, +5/-2)

PR #66141: fix(memory): unify default root memory handling

• Repository: openclaw/openclaw
• Author: mbelinky
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/66141

Description (problem / solution / changelog)

Summary

• treat workspace root memory as a single slot instead of separate MEMORY.md and memory.md default QMD collections
• make QMD prefer exact MEMORY.md, fall back to legacy lowercase memory.md only when the canonical file is absent, and stop generating/searching phantom memory-alt-* collections
• align builtin memory file discovery with the same uppercase-first fallback rule so both backends share one root-memory model
• harden QMD upgrade/rebind logic so legacy memory-alt collections that still own the root slot can be rebound to memory-root-* during repair

Why

OpenClaw had real source-of-truth drift around default root memory handling. The workspace/bootstrap rules already treat lowercase memory.md as legacy fallback only, but the QMD default collection resolver still modeled it as a second default collection. That let runtime search and repair target phantom memory-alt-* collections when only MEMORY.md existed.

User impact

• removes noisy phantom QMD lookups and fallback-to-builtin behavior for normal MEMORY.md workspaces
• keeps lowercase-only legacy workspaces working
• makes builtin and QMD root-memory behavior consistent

Validation

• pnpm test -- packages/memory-host-sdk/src/host/internal.test.ts
• pnpm test -- packages/memory-host-sdk/src/host/backend-config.test.ts
• pnpm test -- extensions/memory-core/src/memory/qmd-manager.test.ts
• commit hook passed pnpm check

Related

• #65913
• #65908
• #65890

Changed files

• CHANGELOG.md (modified, +1/-0)
• extensions/memory-core/src/memory/qmd-manager.test.ts (modified, +165/-0)
• extensions/memory-core/src/memory/qmd-manager.ts (modified, +73/-5)
• packages/memory-host-sdk/src/host/backend-config.test.ts (modified, +88/-3)
• packages/memory-host-sdk/src/host/backend-config.ts (modified, +35/-2)
• packages/memory-host-sdk/src/host/internal.test.ts (modified, +19/-0)
• packages/memory-host-sdk/src/host/internal.ts (modified, +25/-4)