refactor: move UUID/username routing to application use case — fix handler boundary leak

crates/presentation/src/handlers/users.rs

@@ -9,7 +9,7 @@ use api_types::{
     responses::{ErrorResponse, ProfileField, RemoteActorResponse, UserResponse},
 };
 use application::use_cases::feed::list_users;
-use application::use_cases::profile::{get_user_by_username, update_profile};
+use application::use_cases::profile::{get_user_by_id_or_username, update_profile};
 use application::use_cases::search::search_users;
 use axum::{
     extract::{Path, Query, State},
@@ -32,16 +32,7 @@ pub async fn get_user(
     OptionalAuthUser(viewer): OptionalAuthUser,
     headers: HeaderMap,
 ) -> Result<Response, ApiError> {
-    // AP actor URLs use the user's UUID (e.g. /users/{uuid}). Fall back to UUID lookup
-    // so remote servers can fetch the actor JSON for HTTP signature verification.
-    let user = if let Ok(uuid) = uuid::Uuid::parse_str(&username) {
-        s.users
-            .find_by_id(&domain::value_objects::UserId::from_uuid(uuid))
-            .await?
-            .ok_or(ApiError::Domain(domain::errors::DomainError::NotFound))?
-    } else {
-        get_user_by_username(&*s.users, &username).await?
-    };
+    let user = get_user_by_id_or_username(&*s.users, &username).await?;
 
     let accept = headers
         .get(header::ACCEPT)