Project Folder Validation Issues #283
Description
Problem
When a project folder is moved, renamed, or deleted from the filesystem, the application doesn't consistently detect or handle this situation. This leads to confusing user experiences where some actions work while others silently fail.
Current Behavior
- Inconsistent detection: Some ways of switching projects check if the folder exists, while others (like keyboard shortcuts Q/E) skip this check entirely
- Silent failures: When validation encounters an error, it assumes the folder exists and proceeds anyway
- Lost data without warning: Categories can fail to save without any notification, causing them to disappear on restart
- Confusing error messages: When a missing folder is eventually detected (e.g., when loading features), the error message appears disconnected from the actual cause
Expected Behavior
- All project switching methods should verify the folder exists before switching
- Users should always be notified when something fails to save
- Error messages should clearly explain the problem and offer actionable solutions (like removing the invalid project)
- The app should never silently enter a broken state
User Impact
- Users can get stuck viewing a project that no longer exists
- Work can be lost without warning (categories, settings)
- Debugging is difficult because errors appear unrelated to the root cause (missing folder)