refactor: remove legacy code code_task_v1

[ObservedObserver]

Remove file based storage code_task_v1 (server/utils/code_task_v1.py) and related code, since we are not using the old file based storage for tasks anymore.

@claude review the code and finish refactor.

[claude]

Claude finished @ObservedObserver's task —— View job • claude/issue-13-20250617_181422 • Create PR ➔

---

Refactor: Remove Legacy Code code_task_v1 ✅

I've successfully completed the refactoring to remove the legacy file-based storage code for code_task_v1.

Todo List:

• Check for repository setup instructions (CLAUDE.md)
• Review the target file server/utils/code_task_v1.py
• Search for all references to code_task_v1 across the codebase
• Remove the main file and clean up all references
• Run linting/testing commands to validate changes
• Commit and push changes

Changes Made:

1. Deleted server/utils/code_task_v1.py (564 lines removed)

   • Removed legacy in-memory task storage (tasks = {})
   • Removed file persistence system (tasks_backup.json)
   • Removed deprecated run_ai_code_task() and _run_ai_code_task_internal() functions
   • Removed legacy Docker container execution code

2. Cleaned up server/utils/__init__.py

   • Removed commented import: # from .code_task_v1 import run_ai_code_task, _run_ai_code_task_internal
   • Removed commented legacy function calls in sequential processor
   • Simplified conditional logic to only handle v2 tasks

Verification:

• ✅ All references to code_task_v1 have been removed from the codebase
• ✅ All imports now only reference the v2 Supabase-based system
• ✅ server/tasks.py was already fully migrated and requires no changes
• ✅ No broken imports or function calls remain

Impact:

The legacy file-based storage system has been completely removed. The application now exclusively uses the v2 Supabase-based task storage system, which provides better scalability, persistence, and multi-user support.

---