Fix/increment update dir vector store

[myysy]

Description

This PR adds a directory-only L0/L1 vector index migration helper to VikingFS and integrates it into the incremental sync path, ensuring directory summary/overview indexes stay consistent after sync/move operations.

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

• Move and implement a private VikingFS._mv_vector_store_l0_l1(old_uri, new_uri) helper to migrate only directory L0/L1 vector index records, with locking and directory validation.
• Extend VikingVectorIndexBackend.update_uri_mapping and VikingFS._update_vector_store_uris to support levels filtering (so only selected levels are migrated) and apply owner_space restriction for USER contexts.
• Fix incremental sync flow to correctly await the L0/L1 index migration and guard failures with logging to avoid breaking directory sync.

Contributors

Co-authored-by: @gilangjavier

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)

Additional Notes

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Lock Scope Verify if locking only old_path in _mv_vector_store_l0_l1 is sufficient to prevent race conditions when moving directory vector indexes, especially if concurrent operations might target new_path. try: async with LockContext( get_lock_manager(), [old_path], lock_mode="mv", mv_dst_parent_path=dst_parent, src_is_dir=True, ): Query Limit Confirm that the limit=100 in the filter call for update_uri_mapping will not miss records in cases where a single URI might have more vector index entries (unlikely but possible with multiple levels or other dimensions). records = await self.filter(filter=And(conds), limit=100, ctx=ctx)

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.