fix: add OpenClaw 2026.5 compiled runtime compatibility

[choucheyu]

Summary

This PR is scoped to OpenClaw 2026.5 runtime/plugin-contract compatibility for memory-lancedb-pro.

It includes:

• ship compiled runtime output under dist/
• point package.json / openclaw.extensions at ./dist/index.js
• bump package + manifest version to 1.1.0-beta.11
• declare registered agent tools in openclaw.plugin.json → contracts.tools
• guard registerMemoryCapability for hosts/test stubs that do not expose it
• fix backup/admission audit path double-resolution with api.resolvePath
• load LanceDB through ESM dynamic import() instead of require() so the compiled ESM runtime works under OpenClaw 2026.5
• update changelog notes

What this fixes

Validated locally against OpenClaw 2026.5.4:

• no TypeScript runtime-entry warning from openclaw doctor
• no contracts.tools registration error for this plugin
• no require is not defined during retrieval / auto-recall
• runBackup no longer fails from double-resolving an already-absolute dbPath
• runtime plugin loads with embedding: OK, retrieval: OK, FTS: enabled
• memory_store / memory_recall write-read path works against the existing LanceDB database

Related upstream work

Related to / overlaps parts of:

• OpenClaw 2026.5.x compat: missing contracts.tools + runBackup TypeError #744 — OpenClaw 2026.5.x compatibility issue
• fix: declare contracts.tools in plugin manifest (OpenClaw 5.2 compat) #737 / fix: declare contracts.tools for OpenClaw 2026.5.x compatibility #742 / fix: 補齊 contracts.tools 聲明以解決插件啟動錯誤 #749 — contracts.tools manifest declaration
• fix(backup+admission): drop redundant api.resolvePath on already-absolute paths (Issue #682, supersedes PR #695) #743 / fix(backup): guard resolvedDbPath + drop redundant api.resolvePath (Issue #682) #750 — backup path / runBackup path-resolution failures

This PR intentionally does not pull in the full broad changes from #743/#750. It only applies the minimal path-resolution fix needed for backup/admission audit paths.

It also does not claim to resolve all OpenClaw 2026.5 issues in the repo; other categories like broader backup workflows, locks/bulk-store, reflection/dreaming, retrieval-quality, and import-markdown remain separate work.

Validation

Local validation performed:

• npx tsc -p tsconfig.json
• node --test test/reflection-bypass-hook.test.mjs
• node test/plugin-manifest-regression.mjs
• node --test test/sync-plugin-version.test.mjs
• openclaw doctor --non-interactive
• runtime load test in OpenClaw 2026.5.4
• memory_store + memory_recall write-read marker test
• LanceDB transaction timestamp confirmed updated after write

Runtime result after installing/syncing this branch locally:

• plugin source: ~/.openclaw/extensions/memory-lancedb-pro/dist/index.js
• version: 1.1.0-beta.11
• startup: embedding: OK, retrieval: OK, FTS: enabled
• backup: completed successfully with existing DB entries