M12: complete daily operations cycle
This commit is contained in:
@@ -2296,3 +2296,21 @@ evidence yet."
|
||||
the full Unraid Compose suite: **203 passed, 1 warning**.
|
||||
- Exact next action: implement audited checkout/activation, maintenance capture and
|
||||
operations-manager user administration, then repeat the complete validation gate.
|
||||
|
||||
## Complete daily operations cycle (2026-08-10)
|
||||
|
||||
- Reserved bookings now have an audited checkout inspection. A safe inspection atomically
|
||||
activates the booking and marks the vehicle rented; odometer regression, dirt, damage
|
||||
or a technical warning blocks the booking and routes the vehicle to cleaning or
|
||||
maintenance without an unsafe activation.
|
||||
- Operations Managers can register persisted maintenance evidence, advance service and
|
||||
odometer values, explicitly release a vehicle only when no active rental or open
|
||||
high-severity vehicle issue remains, and create/activate/deactivate operational users.
|
||||
Self-deactivation and self-demotion are prevented. Rental employees receive 403 for
|
||||
manager actions.
|
||||
- Added localized web workflows for checkout, maintenance/release and user access
|
||||
administration. All actions use persisted API state and expose actionable errors.
|
||||
- Evidence: frontend lint and production build passed; ruff, mypy and diff check passed;
|
||||
focused Unraid contracts **19 passed** and the full suite **208 passed, 1 warning**.
|
||||
- Exact next action: harden MCP per-client authorization and evidence completeness, then
|
||||
replace inferred n8n status with explicit heartbeat/execution telemetry.
|
||||
|
||||
Reference in New Issue
Block a user