feat: Add run_in_background parameter to sync endpoint with tests

[jope-bm]

Summary

• Add run_in_background query parameter to the /project/sync endpoint (defaults to true for backward compatibility)
• When run_in_background=false, the sync runs synchronously and returns a complete SyncReportResponse
• Add comprehensive test coverage for the new functionality
• Fix bug where foreground sync returned raw dataclass instead of properly serialized response

Changes

API Changes

• project_router.py: Add run_in_background query parameter to sync_project endpoint
  • Default: true (maintains backward compatibility)
  • When false: Runs sync synchronously and returns SyncReportResponse with detailed change information
  • When true: Runs in background and returns status message (existing behavior)
  • Fixed conversion to use SyncReportResponse.from_sync_report() for proper serialization

Tests Added

Three new comprehensive tests in test_project_router.py:

1. test_sync_project_endpoint_foreground - Verifies sync report structure when running in foreground
2. test_sync_project_endpoint_foreground_with_force_full - Tests foreground sync with force_full=true
3. test_sync_project_endpoint_foreground_with_changes - Tests that foreground sync detects actual file changes

Test Plan

• All existing tests pass (31/31 tests in test_project_router.py)
• New foreground sync tests pass
• Background sync (default) still works as expected
• Foreground sync returns proper SyncReportResponse with all fields including total
• Force_full parameter works with both background and foreground modes
• Coverage for project_router.py: 97% (up from previous coverage)

Benefits

• Enables synchronous sync operations for scenarios requiring immediate feedback
• Provides detailed sync report with counts of new/modified/deleted files
• Maintains full backward compatibility with existing API clients
• Comprehensive test coverage ensures reliability

🤖 Generated with Claude Code