Support OpenClaw 2026.8.1 protected same-agent private transcript recall

[TurboTheTurtle]

Problem / Motivation

OpenClaw 2026.8.1 adds protected cross-session recall from previous private conversations. Alternative memory providers only participate when they explicitly register the protected-recall capability and expose a deterministic recall tool that honors OpenClaw's trusted conversation authorization context.

memory-lancedb-pro does not currently register:

• supportsPrivateTranscriptRecall: true
• deterministicRecallToolName

Its deterministic recall path also does not consume ctx.conversationRecall, so OpenClaw cannot safely enable the feature while this plugin is selected.

The optional canonicalCorpus.includeSessionTranscripts index is not an equivalent substitute. It discovers recent JSONL files by agent and indexes them as transcript documents, but it does not implement the protected product boundary: recognized private-session classification, same-agent authorization, active-conversation exclusion, forgotten/policy-blocked source exclusion, or fail-closed handling of missing authorization context.

This leaves users with two poor options after upgrading: lose protected private transcript recall while keeping the plugin, or switch memory providers and lose memory-lancedb-pro functionality.

Proposed Solution

Add explicit support for OpenClaw's protected same-agent private transcript recall contract.

Acceptance criteria:

• Register supportsPrivateTranscriptRecall: true and a stable deterministicRecallToolName in the memory capability.
• Make the named deterministic recall tool require and honor ctx.conversationRecall.
• Restrict eligible sources to recognized previous private conversations owned by the same agent.
• Exclude the active conversation.
• Exclude group/channel sessions, other agents, unknown session types, forgotten sessions, and policy-blocked sources.
• Fail closed when the authorization context is absent, malformed, or incomplete.
• Keep this protected path distinct from the broader opt-in canonicalCorpus.includeSessionTranscripts feature.
• Add boundary tests for private vs. group/channel, same-agent vs. cross-agent, previous vs. active conversation, forgotten/policy-blocked sources, and unknown chat/session types.
• Document the minimum supported OpenClaw version and the security boundary.

Alternatives Considered

• Use OpenClaw's built-in memory provider: enables the product feature but gives up the plugin's retrieval, storage, and governance functionality.
• Enable canonicalCorpus.includeSessionTranscripts: broader indexing is useful for other purposes, but it is not authorization-equivalent and should not be presented as protected private-memory support.
• Leave protected recall unavailable: safe, but makes the plugin incompatible with a significant OpenClaw 2026.8.1 memory feature.

Area

Scopes / Access Control; Retrieval / Search; Auto-capture / Auto-recall

Additional Context

• OpenClaw 2026.8.1 release notes
• createOpenClawMemoryCapability currently omits protected-recall capability fields
• discoverSessionDocuments currently enumerates recent per-agent JSONL transcripts
• Existing issue canonicalCorpus never indexes: sync() is never invoked, and workspace resolution reads agents.list instead of agents.entries #980 and PR fix: activate the canonical corpus indexer (agents.entries + startup sync) #982 concern activating the generic canonical transcript index; they do not implement the protected recall contract described here.