Problem
The adjustments table stores only created_at. As a result:
- Weekly and monthly summaries ignore manual adjustments.
- Only the all-time total summary reflects them.
This makes it impossible to attribute e.g. on-call comp time to the week/month it was earned.
Proposal
- Add an
effective_date TEXT NOT NULL DEFAULT (date('now')) column to adjustments, with schema migration keyed on schema_meta.schema_version.
- Update POST/PUT adjustment API to accept
effective_date.
- Roll adjustments into `/api/summary/weekly` and `/api/summary/monthly` bucketed by `effective_date`.
- Frontend: date picker on the adjustment form, default = today.
- Tests for bucketing + migration from v1 → v2.
Out of scope
Back-dating existing adjustments (will default to their created_at).
Problem
The
adjustmentstable stores onlycreated_at. As a result:This makes it impossible to attribute e.g. on-call comp time to the week/month it was earned.
Proposal
effective_date TEXT NOT NULL DEFAULT (date('now'))column toadjustments, with schema migration keyed onschema_meta.schema_version.effective_date.Out of scope
Back-dating existing adjustments (will default to their
created_at).