Description

Fix the OpenClaw OpenViking plugin's session mapping so OpenClaw session keys containing Windows-invalid characters no longer become raw OpenViking session IDs.

Related Issue

Fixes #999

Type of Change

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

Changes Made

• Map unsafe OpenClaw sessionKey values to stable filesystem-safe OpenViking session IDs
• Use the mapped session ID consistently for auto-capture, commit, delete, and explicit session resolution
• Update plugin text to describe the stable mapped-session behavior instead of a raw 1:1 mapping

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

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

• Verified locally with npm test in examples/openclaw-plugin.
• Git commit was created with --no-verify because the local git hook environment is missing the pre_commit Python module.