fix: correct dev database path resolution in main.py

Fix critical bug where dev mode was initializing the production database
path instead of the dev database path. The initialize_dev_database() call
now correctly uses get_db_path() to resolve to data/jobs_dev.db.

Impact:
- Before: DEV mode would reset data/jobs.db (production database)
- After: DEV mode correctly resets data/jobs_dev.db (dev database)

Testing:
- Verified database isolation between dev and prod
- Confirmed PRESERVE_DEV_DATA flag works correctly
- Validated dev mode banner and deployment mode detection

Documentation:
- Added comprehensive manual verification results
- Documented all test cases and outcomes
- Recorded fix details for future reference

Task: Task 12 - Manual Verification and Final Testing
Plan: docs/plans/2025-11-01-dev-mode-mock-ai.md

main.py

@@ -114,7 +114,9 @@ async def main(config_path=None):
         log_api_key_warning()
 
         # Initialize dev database (reset unless PRESERVE_DEV_DATA=true)
-        initialize_dev_database("data/jobs.db")
+        from tools.deployment_config import get_db_path
+        dev_db_path = get_db_path("data/jobs.db")
+        initialize_dev_database(dev_db_path)
         print("=" * 60)
 
     # Get Agent type