insights-correlations (#22)

Reviewed-on: #22

crates/application/src/wrapup/get_ready_report.rs

@@ -6,23 +6,6 @@ use domain::{
 
 use crate::wrapup::deps::GetReadyReportDeps;
 
-/// Absorbs the year -> date-range conversion and the `status == Ready` +
-/// `report.is_some()` gating both HTML wrap-up handlers used to do by hand.
-///
-/// Takes `domain::models::wrapup::WrapUpScope` directly (the same type
-/// `wrapup::handle_requested` already matches on) rather than a second,
-/// use-case-local `WrapUpScope` — there is exactly one concept here, one type.
-/// `None` can no longer be silently passed for "global": callers must pick
-/// `WrapUpScope::User(uid)` or `WrapUpScope::Global` explicitly.
-///
-/// Error shape mirrors the deleted handlers exactly:
-/// - An unrepresentable `year` (can't form a valid `NaiveDate`) is
-///   `ValidationError` — the handlers used this to return a bare 400.
-/// - Everything else — no record, a record whose `status` isn't `Ready`, a
-///   `Ready` record with `report: None`, or even a repository error — collapses
-///   to `NotFound`, matching the old handlers' `_ => return StatusCode::NOT_FOUND`
-///   catch-all (which really did swallow repo errors into a 404, not just the
-///   "not ready yet" cases; preserved here rather than tidied).
 pub async fn execute(
     deps: &GetReadyReportDeps,
     scope: WrapUpScope,

crates/application/src/wrapup/tests/get_ready_report.rs

@@ -133,10 +133,6 @@ async fn ready_report_global_scope_ignores_user_id() {
         .unwrap();
 }
 
-/// The old handlers guarded `NaiveDate::from_ymd_opt` up front and returned a bare
-/// 400 for a year that can't form a valid date — that guard moved into the use
-/// case along with the rest of the year->date-range conversion. A distinguishable
-/// error (ValidationError, not NotFound) lets the handler still map it to 400.
 #[tokio::test]
 async fn ready_report_is_validation_error_for_unrepresentable_year() {
     let repo = InMemoryWrapUpRepository::new();