3 Commits

Include renames

Author	SHA1	Message	Date
ElebobaandClaude Opus 5.5	25728c4b31	feat(backend): API stage 1 on real data instead of fixtures ... Doctor list/card/alerts/ack/connect, dialog events/outbox/history and demo controls now read the identity and clinical DBs. Rule-based discontinuation risk index, trend, adherence; every doctor read is audited. Refs #12 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 12:34:40 +03:00
ElebobaandClaude Opus 5.5	4c0836a1be	feat(backend): monitoring service — snapshot, rules, alerts, status colour, clock persistence ... - app/services/snapshot.py: PatientSnapshot from the clinical DB (field mapping, age, therapy day, recent C-SSRS risk, weapon access from dialog facts) - app/services/monitoring.py: RuleMonitoring registered via register_monitoring; persists alert/crisis actions, crisis_acute audit, enhanced_monitoring flag, cached status_color, notifies the doctor (and the doctor on duty for crises) after commit; a running crisis is not restarted - demo clock offset persisted in clock_state, restored on scheduler start - tests: Andrey's 13 days through the service → G G G Y Y G G G G Y Y Y R Refs #38 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 03:13:57 +03:00
ElebobaandClaude Opus 5.5	b4731fb1d6	chore(core): stage 1 contracts — dialog, API schemas + fixtures, integrations, monitoring, modules ... Freeze interfaces between lanes A (bot), B (backend), C (dashboard) so three developers work in parallel without touching each other's files: dialog Event/Reply + engine registry with echo stub, integration protocols with in-memory defaults, MonitoringService with noop stub, /api/v1 schemas with fixture-backed routes, frozen main.py wiring, config/modules.yaml + due_scales(), DAR-5, tzdata, Andrey trajectory, lanes in WORKFLOW, ADR-010. Refs #34 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-03 15:22:25 +03:00