Description

Mark recalled memories as used() in the existing Claude Code and OpenClaw examples so retrieval feedback feeds back into OpenViking hotness/ranking.

This keeps the change narrowly scoped to the example integrations that already perform recall.

Related Issue

N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

• Add sessionUsed() support to the OpenClaw example client.
• Mark recalled memory URIs as used() during OpenClaw recall before continuing with normal injection flow.
• Add the same fire-and-forget session.used() plus commit() feedback loop to the Claude Code memory example and auto-recall script.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Verified locally with:

cd examples/claude-code-memory-plugin
npm ci
npm run build

cd ../openclaw-plugin
npm ci
npm test

OpenClaw plugin tests are currently red on upstream main before this patch as well. The same two failures reproduce on a clean upstream-based worktree:

• context-engine-assemble.test.ts > assembles summary archive and completed tool parts into agent messages
• context-engine-assemble.test.ts > emits a non-error toolResult for a running tool

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Screenshots (if applicable)

N/A

Additional Notes

• This PR intentionally stays at the example layer and does not change core retrieval APIs.
• The OpenClaw-side diff is limited to marking recalled URIs as used; unrelated local-only runtime wiring is excluded.