Bohan Jiang d12d690c38 fix(usage): bucket workspace usage by task_usage.created_at, not enqueue time (#1176) ...

GetWorkspaceUsageByDay and GetWorkspaceUsageSummary had the same date
attribution bug as the runtime endpoint fixed in #1167: they bucketed
and filtered on agent_task_queue.created_at (enqueue time), so a task
that queued at 23:58 and reported usage at 00:05 was attributed to the
prior day, and ?days=N became a rolling now()-N window that clipped the
morning of the earliest day returned.

Switch both queries to task_usage.created_at (~= task completion time)
and snap the since cutoff to start-of-day via DATE_TRUNC, mirroring
ListRuntimeUsage.

These endpoints have no frontend caller today, but per offline
discussion they will back the upcoming workspace-level usage dashboard.
Fix preemptively so the dashboard inherits correct numbers.

Add a regression test covering both endpoints with the same
cross-midnight + earliest-day-cutoff scenarios used for runtime usage.

2026-04-16 19:06:49 +08:00

..

agent

fix(agent): resume codex thread across tasks on the same issue (#1166)

2026-04-16 18:06:11 +08:00

db

fix(usage): bucket workspace usage by task_usage.created_at, not enqueue time (#1176)

2026-04-16 19:06:49 +08:00

protocol

…

redact

…