fix(memory): define config before v2 memory lock retry settings access

[heaoxiang-ai]

Description

Fix a NameError in openviking/session/compressor_v2.py when the v2 memory extraction path enters the lock acquisition retry branch.

SessionCompressorV2.extract_long_term_memories() reads config.memory.v2_lock_retry_interval_seconds and config.memory.v2_lock_max_retries, but config was not defined in that method scope. This change initializes the OpenViking config before those settings are
accessed so v2 memory extraction can retry lock acquisition as intended.

Related Issue

N/A

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

• Initialize OpenViking config inside SessionCompressorV2.extract_long_term_memories()
• Fix access to memory.v2_lock_retry_interval_seconds and memory.v2_lock_max_retries in the lock retry path
• Verify the lock retry branch with the existing targeted compressor v2 test

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

Additional Notes

• This is a minimal bug fix scoped to the v2 memory lock retry path.
• The targeted pytest run passed, but the full test suite was not run in this session.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.