fix: set_default_project skips config file update in cloud mode

[phernandez]

Summary

• Validate project exists in database before updating (fail-fast approach)
• Only update config file in local mode; cloud mode uses database as source of truth
• Raise ValueError if project not found instead of just logging error

Test plan

• Unit tests updated to expect ValueError for non-existent projects
• Verified existing tests pass

🤖 Generated with Claude Code

[github-actions]

Claude finished @phernandez's task in 2m 10s —— View job

---

PR #486 Code Review: set_default_project Cloud Mode Fix

Review Summary

This PR improves the set_default_project method with better error handling and cloud mode support. The changes follow fail-fast principles and correctly separate local vs cloud configuration concerns. ✅ APPROVED - Ready to merge when CI passes.

---

Code Quality & Standards ✅

Passes all checks:

• Python 3.12+ type annotations preserved
• 100-character line length maintained
• SQLAlchemy 2.0 async patterns followed
• Follows literate programming style with clear logic flow
• No commented-out code blocks

Code improvements identified:

1. Fail-fast approach: Changed from logging errors to raising ValueError ✅
2. Cloud mode awareness: Only updates config file in local mode ✅
3. Database-first validation: Validates project exists before updating ✅

---

Testing & Documentation ✅

Test coverage:

• Unit test updated in test_project_service.py:284 to expect ValueError
• Test name clarified: "raises error when project exists in config but not in database"
• Removes unnecessary cleanup code (simplified test)
• Edge case handled: config/database mismatch now fails fast

Code formatting cleanup:

• Minor formatting improvements in test_project_context.py (removed extra line breaks)
• Formatting fix in test_schemas.py (multi-line dict for readability)

Documentation:
The code changes are clear, and the comment explaining cloud mode behavior is already present at line 294! ✅

---

Basic Memory Architecture ✅

Architectural correctness:

• Preserves local-first architecture (database validation first)
• Cloud mode uses database as source of truth (skips config file)
• Local mode updates both config and database
• Proper use of fail-fast error handling
• No changes to public API surface

Logic flow improvement:
The new implementation is clearer:

1. Validate repository exists (defensive check)
2. NEW: Look up project in database first (fail if not found)
3. Update database as source of truth
4. Update config file only in local mode
5. Log success

This is better than the old approach which updated config first, then logged an error if database was out of sync.

---

Security & Performance ✅

Security:

• No hardcoded secrets or credentials
• Proper input validation (validates project existence)
• No SQL injection risks (uses ORM)
• Error messages don't leak sensitive information

Performance:

• Single database lookup to validate project
• No unnecessary operations
• Cloud mode skips config file I/O (performance win)

---

Compatibility ✅

Windows compatibility:

• No file path operations in this change
• No platform-specific code added
• No emoji/unicode in console output

---

Detailed Review by File

src/basic_memory/services/project_service.py:274-298 ✅

Before vs After:

Old behavior:

# Update config first
self.config_manager.set_default_project(name)
# Then check database, log error if not found
project = await self.get_project(name)
if project:
    await self.repository.set_as_default(project.id)
else:
    logger.error(...)  # Inconsistent state!

New behavior (this PR):

# Validate project exists first (fail-fast)
project = await self.get_project(name)
if not project:
    raise ValueError(f"Project '{name}' not found")

# Update database
await self.repository.set_as_default(project.id)

# Update config only in local mode
if not self.config_manager.config.cloud_mode:
    self.config_manager.set_default_project(name)

Analysis:

• ✅ Fail-fast improvement: Raises ValueError instead of logging and continuing
• ✅ Cloud mode fix: Skips config file update when cloud_mode=True
• ✅ Consistent state: No partial updates if project doesn't exist
• ✅ Better error message: Clear failure reason

---

tests/services/test_project_service.py:284-312 ✅

Changes:

1. Updated test name to reflect new behavior
2. Removed original_default variable (no longer needed)
3. Added pytest.raises(ValueError) assertion
4. Simplified cleanup code

Analysis:

• ✅ Test correctly validates the fail-fast behavior
• ✅ Matches the code change in project_service.py:289
• ✅ Cleaner test implementation (removed dead code)

---

tests/mcp/test_project_context.py ✅

Changes: Pure formatting (removed extra line breaks in with patch() statements)

Analysis:

• ✅ No functional changes
• ✅ Improves readability
• ✅ Consistent with project formatting standards

---

tests/schemas/test_schemas.py:109-111 ✅

Changes: Formatting only (multi-line dictionary for to_entity)

Analysis:

• ✅ Better readability
• ✅ Follows 100-character line length guideline
• ✅ No functional changes

---

Final Verdict

✅ APPROVED - This PR successfully implements the fail-fast approach and cloud mode awareness for set_default_project.

Strengths:

1. Fail-fast error handling (raises ValueError instead of logging)
2. Cloud mode respects database as source of truth
3. Simplified test code with better assertions
4. No breaking changes to public API
5. Follows Basic Memory's literate programming style
6. All code formatting changes improve readability

Minor observations:

• The formatting changes are welcome but could have been in a separate commit (minor - not blocking)
• All test updates correctly reflect the new behavior

Recommendation: ✅ Merge when CI passes. This is a clean improvement that fixes a real issue with cloud mode configuration management.

---