Have claude update the plan for the backend with the current status. (#5)

Reviewed-on: #5
Co-authored-by: Drew Galbraith <drew@tiramisu.one>
Co-committed-by: Drew Galbraith <drew@tiramisu.one>

CLAUDE.md

@@ -29,6 +29,26 @@ Captain's Log is a GTD-inspired personal task management system designed to mini
 - **Dev Database**: SQLite for easy setup and portability
 - **Production Database**: PostgreSQL for scalability
 - **Authentication**: Simple session-based auth (single user)
+- **Architecture**: Active Record pattern with models handling persistence
+- **Testing**: Unit tests + Hurl API integration tests
+
+#### Backend Project Structure
+```
+backend/
+├── src/
+│   ├── main.rs                 # Application entry point with health endpoint
+│   ├── database/
+│   │   ├── mod.rs              # Database module exports
+│   │   └── connection.rs       # Database connection utilities
+│   ├── models/
+│   │   ├── mod.rs              # Models module
+│   │   └── task.rs             # TaskModel with CRUD methods
+│   └── services/
+│       ├── mod.rs              # Error handling and exports
+│       └── tasks.rs            # HTTP handlers for task endpoints
+├── tests/api/                  # Hurl API integration tests
+└── migrations/                 # SQLx database migrations
+```
 
 ### Frontend: Vite + React + Tailwind CSS
 - **Build Tool**: Vite for fast development and optimized builds
@@ -41,10 +61,11 @@ Captain's Log is a GTD-inspired personal task management system designed to mini
 
 ### Core Data Models
 ```sql
--- Tasks (Phase 1 MVP)
-tasks (id, title, description, priority, due_date, status, created_at, updated_at, completed_at)
+-- Tasks (Phase 1 MVP - Current Implementation)
+tasks (id, title, description, status, created_at, updated_at, completed_at)
 
 -- Future phases will add:
+-- priority and due_date fields to tasks table
 -- projects (id, name, description, color, status, created_at, updated_at)
 -- contexts (id, name, description, color, icon)
 -- task_contexts (task_id, context_id)
@@ -56,10 +77,15 @@ tasks (id, title, description, priority, due_date, status, created_at, updated_a
 ### Testing
 ```bash
 # Backend tests
-cargo test
-cargo tarpaulin --out Html  # Coverage report
+just test-unit              # Unit tests (cargo test)
+just test-coverage          # Coverage report (tarpaulin HTML)
+just test-integration       # API tests (Hurl)
 
-# Frontend tests  
+# Individual commands
+cargo test                  # Direct unit test execution
+hurl --test tests/api/*.hurl # Direct API test execution
+
+# Frontend tests (when implemented)
 npm test                    # Unit tests
 npm run test:e2e           # End-to-end tests
 npm run test:coverage      # Coverage report
@@ -68,21 +94,30 @@ npm run test:coverage      # Coverage report
 ### Development Server
 ```bash
 # Backend (Rust server)
-cargo run
+just dev                    # Run backend server (cargo run)
 
-# Frontend (Vite dev server) 
-npm run dev
+# Other backend commands
+just build                  # Build project
+just migrate               # Run database migrations
+just reset-db              # Reset database
+just fmt                   # Format code
+just lint                  # Run clippy
+
+# Frontend (when implemented)
+npm run dev                # Vite dev server
 ```
 
-## Current Phase: Core MVP
+## Current Phase: Core MVP Backend ✅
 
-**Focus**: Basic task management with CRUD operations
-- Task properties: title, description, priority, due_date, status
-- Simple web interface with mobile responsiveness
-- Testing framework setup with >80% backend coverage target
-- RESTful API endpoints for all task operations
+**Status**: Backend implementation completed
+- ✅ Task properties: title, description, status, timestamps
+- ✅ RESTful API endpoints for all task operations
+- ✅ Testing framework with unit tests and API integration tests
+- ✅ Coverage reporting setup (currently 32.41%)
+- ⏳ Frontend implementation (next phase)
 
-See `/plan/01_CORE_MVP/plan.md` for detailed implementation plan.
+See `/plan/01_CORE_MVP/backend.md` for implementation details.
+See `/plan/future_improvements.md` for architectural enhancement opportunities.
 
 ## Future Phases