TL;DR

Persisting and restoring the full memory capability in the plugin registry cache is likely to fix the issue of zero artifacts being returned on cached plugin-load paths.

Guidance

• Verify that the memory-core is loaded and the workspace contains valid memory artifacts before running openclaw wiki bridge import.
• Check the dist/loader-*.js files to ensure that the cached plugin restore is correctly restoring the memory runtime, prompt, and flush state.
• Consider modifying the plugin registry cache to include the registered memory capability, as proposed in the issue.
• Test the import process with a fresh registration to confirm that artifacts are exposed correctly, and then try with a cached restore to identify the difference in behavior.

Example

No specific code snippet is provided, as the issue implies a modification to the dist/loader-*.js files, which is not explicitly stated.

Notes

The proposed fix involves persisting and restoring the full memory capability, which may have implications for the plugin registry cache and the memory runtime. It is essential to test this fix thoroughly to ensure that it does not introduce any new issues.

Recommendation

Apply the proposed workaround of persisting and restoring the full memory capability in the plugin registry cache, as it addresses the root cause of the issue and should fix the problem of zero artifacts being returned on cached plugin-load paths.