M34: enforce domain integrity in PostgreSQL
This commit is contained in:
@@ -2762,3 +2762,16 @@ evidence yet."
|
||||
- Validation: isolated booking API suite **12 passed**; backend Ruff clean; frontend
|
||||
TypeScript lint and production build passed.
|
||||
- Exact next action: add database invariants/indexes and harden the shared public demo reset.
|
||||
|
||||
## M34 — database-enforced domain integrity (2026-08-10)
|
||||
|
||||
- Added named PostgreSQL checks for booking windows/status/odometers, vehicle state and
|
||||
non-negative counters, quality rule/severity/lifecycle values, outbox state/attempts and
|
||||
audit actor types. Model metadata and migration `c24f6a9d013e` stay aligned.
|
||||
- Added workload indexes for vehicle availability windows, quality work queues, outbox
|
||||
retries and audit filtering/entity traces.
|
||||
- Validation: migration upgraded from an empty PostgreSQL database to head; the complete
|
||||
deterministic seed loaded with the expected 2/180/50/254/75/40/33/20 counts; four
|
||||
direct invalid-state writes were rejected by their named constraints; Ruff passed.
|
||||
- Exact next action: serialize and rate-limit shared demo reset, add production web guards
|
||||
and cache MCP reachability evidence.
|
||||
|
||||
Reference in New Issue
Block a user