Feature/memrok openclaw compatibility fixes

[christophermallory]

Fix for issue #2.

• Switches to node:sqlite for compatibility with Openclaw plugin installer.
• Removes hard-coded file paths and uses Openclaw agent directories for scanning memories.
• Allows the use of Openclaw providers and models or overriding via config.
• Adds Openclaw slash commands for manual reindexing.
• Updates readme.md for openclaw-plugin to reflect changes.

[MichaelSchmidle]

Thanks, this is a genuinely useful contribution and the overall direction makes sense, especially the node:sqlite switch and the OpenClaw compatibility cleanup.

I can’t merge it as-is yet because the branch currently fails to parse/compile, with blocking issues in packages/store/src/store.ts and packages/store/src/schema.ts.

Once that’s cleaned up, I’d be happy to take another look.

[MichaelSchmidle]

Thanks again for this, and sorry the branch drift got worse while we were moving quickly on main.

I’ve now routed issue #2 into our v0.7.0 milestone, and I still think the core direction in your PR is valuable, especially around OpenClaw compatibility.

At this point I don’t think we should try to merge the whole PR as one large blob anymore, because has changed a lot in the plugin path since you opened it and the branch is now conflicting in several of the same files.

If you’re still up for it, the most helpful next step would be to rebase and narrow this PR to the compatibility core for #2:

• installer/runtime compatibility
• path discovery / indexing correctness
• provider/model inheritance

The more optional operator surface (manual commands, broader polish, etc.) can be separate if needed.

If you’d rather not keep chasing a moving target, that’s also totally understandable. Either way, thank you, this issue helped surface a real gap in the product and shaped how we’re planning the next arc.

[christophermallory]

I don't mind contributing. I'll free up in a few days and take a look.