feat: add health data management workspace

.trellis/tasks/07-02-operations-module-roadmap/implement.md

@@ -0,0 +1,42 @@
+# Implementation Plan
+
+## Execution Order
+
+1. Start and implement `07-02-care-service-workspace` (`新增健康照护后台管理页`).
+2. Start and implement `07-02-care-execution-workspace` (`护理服务执行工作台`).
+3. Start and implement `07-02-emergency-incident-workspace` (`安全应急事件工作台`).
+4. Start and implement `07-02-elder-bed-context-optimization` (`老人床位联动优化`).
+5. Start and implement `07-02-operations-dashboard-integration` (`运营看板整合优化`).
+6. Review parent acceptance criteria after all children are complete.
+
+## Per-Child Gate
+
+Before starting each child:
+
+- Read its `prd.md`.
+- For complex children, add or refresh `design.md` and `implement.md`.
+- Load `trellis-before-dev` and relevant backend/frontend/shared specs.
+
+Before finishing each child:
+
+- Run `pnpm lint`.
+- Run `pnpm type-check`.
+- Run `pnpm build`.
+- Run `pnpm db:generate` and review SQL when schema changes are made.
+- Confirm default workspace seed data is real persisted data when seed examples are added.
+
+## Parent Completion Gate
+
+The parent task is complete only after:
+
+- Each child task is completed or explicitly moved out of scope by the user.
+- The dashboard reflects completed module data.
+- Existing elder, bed, admission, auth, settings, and audit workflows still pass validation.
+- Final `pnpm lint`, `pnpm type-check`, and `pnpm build` pass.
+
+## Risk Notes
+
+- Schema migrations across multiple children can conflict if implemented out of order.
+- Default seed file already has active edits; every child that touches it must read it before editing.
+- Permission additions must keep role seeding idempotent.
+- Dashboard integration should not start before the data sources exist.