desktop/src-tauri/crates/core/tests/tiered_retention.rs

Comment 1, line 1

//! Tiered retention (2026-09-26 request): details, hourly, daily and week/month/year archives.

//! Store completed period rows before deleting daily rows; queries combine retained days with archives.

//! Hourly charts use persisted hourly rows after detail deletion.

// September is complete; its last day still belongs to the current ISO week.

// Equal daily cardinality, higher revision, completed month in an open week.

// The local processing marker cannot establish validity of imported future revisions.

// Use completed 2025-12-15 week/month/year plus current-week 09-22/09-25.

// Ongoing week/month/year starts are protected: today 2026-09-26 protects 2026-01-01 onward.

// Use 2025 history to exercise daily deletion; see the module's protection rules.

// Retain details one day, hours two days, days three days, with longer week/month archives.

// All events precede the detail cutoff at today's start and are deleted.

// Delete hours before 09-25: remove 2025-12-15/09-22, retain 09-25.

// Daily cutoff is 09-24; year protection from 2026-01-01 leaves only 2025-12-15 deleted.

// Store one 2025 row per week/month/year (one call, 110 tokens). Ongoing current periods

// use protected daily rows instead of stored period rows.

// Cross-year weekly queries combine the archived 2025-12-15 week with daily 2026-09-21 week.

// Repeated retention adds no usage; deleted 2025 days cannot be rematerialized, so archives stay.

// Existing 2026 days belong to ongoing periods, giving materialized=0.

// Details may outlive hourly rows; this redundancy loses no data.

// Coarser summaries cannot have a shorter retention range than finer summaries.

// Use an in-memory database while testing rejection of an invalid policy.