init

.junie/plans/migrate-dtos-to-domain.md

@@ -57,15 +57,16 @@ Currently, each feature module in `src/routes/<module>/` contains a `dto.rs` fil
 
 # Delivery Steps
 
-###   Step 1: Create domain DTO directory and module structure
+### ✓ Step 1: Create domain DTO directory and module structure
 - Create `src/domain/dto/` directory along with `src/domain/dto/mod.rs`.
 - Set up module declarations for each DTO file (auth, user, channel, message, category, role, attachment, core, etc.) under `src/domain/dto/`.
 - Expose `pub mod dto;` in `src/domain/mod.rs`.
 
-###   Step 2: Migrate DTO files to `src/domain/dto/` and update imports
+### ✓ Step 2: Migrate DTO files to `src/domain/dto/` and update imports
 - Move each `dto.rs` file from `src/routes/<module>/dto.rs` into `src/domain/dto/<module>.rs`.
 - Update all import statements across handlers, mappers, services, and route files in `src/routes/` and elsewhere to reference `crate::domain::dto::<module>::*`.
 - Remove the old `dto.rs` files from `src/routes/<module>/` and remove `pub mod dto;` from `src/routes/<module>/mod.rs`.
 
-###   Step 3: Verify compilation and test suite
-- Run `cargo check` and `cargo test` to ensure all DTO types resolve correctly and there are no broken imports or compilation errors.\n- Verify OpenAPI schema generation (`utoipa`) correctly picks up the migrated DTO schemas.
+### ✓ Step 3: Verify compilation and test suite
+- Run `cargo check` and `cargo test` to ensure all DTO types resolve correctly and there are no broken imports or compilation errors.
+- Verify OpenAPI schema generation (`utoipa`) correctly picks up the migrated DTO schemas.