Context
The disasters table only stores the current status (active/contained/resolved). There is no record of when status transitions happened. The mobile app Before/During/After lifecycle view would benefit from knowing:
- When did this fire go from active to contained?
- How long was it active?
- Timeline of the disaster progression
Proposed Change
Add a disaster_status_history table to auto-log transitions via trigger on the disasters table. Include a statusHistory field on GET /api/v1/disasters/:id.
Priority
P3 - Nice to have for MVP. Important for the full Before/During/After narrative.
Context
The disasters table only stores the current status (active/contained/resolved). There is no record of when status transitions happened. The mobile app Before/During/After lifecycle view would benefit from knowing:
Proposed Change
Add a disaster_status_history table to auto-log transitions via trigger on the disasters table. Include a statusHistory field on GET /api/v1/disasters/:id.
Priority
P3 - Nice to have for MVP. Important for the full Before/During/After narrative.