fix(openclaw-plugin): prevent CONFLICT errors with commit lock

[leckylao]

Problem

When using the OpenClaw plugin with auto-capture enabled, we frequently encounter CONFLICT errors:

Error: OpenViking request failed [CONFLICT]: Session agent:main:discord:channel:xxx already has a commit in progress

This happens when two code paths try to commit to the same OpenViking session simultaneously:

1. afterTurn hook auto-capture
2. memory_store tool explicit commit

Solution

Add a simple in-memory lock mechanism in context-engine.ts:

const commitLocks = new Set<string>();

async afterTurn(afterTurnParams): Promise<void> {
  // ...
  if (commitLocks.has(OVSessionId)) {
    logger.info(`openviking: afterTurn skipped (commit in progress for ${OVSessionId})`);
    return;
  }
  commitLocks.add(OVSessionId);

  try {
    // ... existing commit logic ...
  } catch (err) {
    // ... error handling ...
  } finally {
    commitLocks.delete(OVSessionId);
  }
}

Behavior

• If a commit is already in progress for a session, afterTurn skips the auto-capture for that turn
• The lock is released in finally block to ensure cleanup even on error
• No data loss - the next turn will capture any missed messages

Testing

Tested on production OpenClaw instance with OpenViking 0.2.12. CONFLICT errors no longer appear.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Failed to generate code suggestions for PR

[Mijamind719]

Thank you for your submission. In the latest version of the code, we have added commit queues internally within OV, thus enabling concurrent commits on the client side.

[Mijamind719]

You can update the code to the latest version, or the latest v0.2.15.