Spike: define the supported OpenClaw and HotMem memory boundary

[valiantone]

Summary

Investigate the current OpenClaw memory extension surface and select the supported HotMem integration boundary before building a showcase.

Scope

• Verify the current supported OpenClaw version and extension interfaces.
• Map USER.md, MEMORY.md, daily memory files, and knowledge-wiki artifacts.
• Compare: workspace import plus sidecar retrieval; active memory-plugin integration; and a wiki bridge.
• Define read/write ownership, sync direction, provenance, and failure behavior.
• Produce an architecture decision and a minimal implementation contract for the selected approach.

Acceptance criteria

• The selected OpenClaw version and official extension surface are recorded.
• The decision names one supported integration boundary and rejects unsupported claims.
• The design preserves local-first behavior and does not read credentials or unrelated workspace files.
• The design states whether HotMem augments or replaces any OpenClaw memory path.
• A follow-up showcase issue has concrete inputs, outputs, and tests.

Out of scope

• Shipping an unverified integration.
• Silent bidirectional synchronization.
• Mandatory remote services.