feature: local-usage-stats (2/4)

[myk1yt]

Stack Position

• Feature Branch: feature/local-usage-stats
• Stage: 2/4
• Depends on: feature: local-usage-stats (1/4) #25

Description

Full Feature Description

• Feature Branch: feature/local-usage-stats
• Feature Name: Local Usage Statistics
• Purpose: Resolves the problem where users cannot locally view token usage, cache effects, cost, and period-based trends by provider, and where differing usage formats across providers make consistent aggregation difficult. Provides a privacy-preserving dashboard that collects only numeric usage and non-secret identifiers locally, without collecting prompts, responses, or credentials.
• Full Change Description: B13 adds data-minimized event/query contracts and an append-only NDJSON event store. B14 adds aggregation by date, provider, model, and mode, cache ratio, and provider-aware cost recalculation. B15 records final usage exactly once from the API attempt completion path, including success/error/cancel/retry. B16 adds transactional SQLite projection, idempotent migration, local-day rollup, query/stream IPC, stale epoch prevention, and dashboard summary/session/heatmap UI.
• Impact Scope: Affects usage-stats.ts, src/services/stats, the provider/task capture paths Task.ts, the stats IPC usageStatsMessageHandler.ts, and the UI DashboardView.tsx and useDashboardStatsStream.ts.
• Errors and Edge Cases: Raw events are append-only and derived rollups must be reconstructable. Duplicate idempotency keys are not re-recorded. Corrupt tails preserve the valid prefix and leave only a hash in the quarantine report instead of the original text. Migrations must be transactional/idempotent. Local day and DST boundaries are calculated per-timestamp by offset. Previous subscription epochs must not overwrite new range results. The store must not contain prompts, responses, API keys, endpoint credentials, or workspace paths.
• Testing Method: Run contract/store, aggregation/cost, exactly-once capture, database/migration/projection/stream, IPC, dashboard reducer/component, performance, locale, and visual tests step by step. Manually create complete/cancel/retry attempts, verify event counts, then rapidly switch ranges in two dashboard windows and add events, verifying convergence without stale loading or duplicate totals. Inspect stored files to confirm no sensitive fields are present.

Why Split Into 17 PRs

Instead of submitting this feature as a single unified PR, it was split into individual PRs because as code size grows, safely reviewing a PR becomes very difficult. The feature was broken into mutually exclusive individual PRs so that each can be reviewed independently.

What This PR Specifically Changes

Adds date/provider/model/mode grouping, totals, cache ratio, unknown event handling, and provider-aware cost recalculation. Does not include live capture, database, IPC, or UI.

Included Files

• src/services/stats/UsageAggregator.ts
• src/services/stats/UsageStatsService.ts
• src/services/stats/costRecalculation.ts
• Direct tests for each module

Exclusion Scope

• Task/provider live capture
• Database rollup, migration, webview IPC, dashboard UI
• Duplicate changes to B13 store/contract
• All items in the common removal rules

[myk1yt]

Closing to recreate with main as target base branch. This PR had stale base branch references after fork sync.