blocker phase 12

client/src/services/patientRecords/constants.ts

@@ -2,13 +2,14 @@
  * When true, the patient-records domain is served by the in-memory mock (`apis/mockApi.ts`) behind the
  * `PatientRecordsApi` seam.
  *
- * **Mock is primary this phase.** b14 serves the nurse-authored **visit-note history** (`care_records`
- * GET/POST) — those two methods are real — but the **family-owned editable record** (medications/routine/
- * tasks) and the **access check** have **no backend at all** (neither the contract nor the data model has
- * them; **REQ-027**). The mock seeds a default family record + a multi-nurse continuity history per patient,
- * enforces a foreign-patient **access-denied** (403) path, and lets the nurse append notes that appear in the
- * history. Flip to `false` once REQ-027 lands — only `clientApi.ts`'s family-record/access methods flip; the
- * history/append methods already map the real routes.
+ * **Mock is primary — the backend is fully built, but the shapes don't match yet.** `PatientCareRecordsController`
+ * implements every route this seam needs: `care_records` GET/POST (visit-note history/append), `care_record`
+ * GET/PUT (the family care plan), and `record_access` GET. The blocker is a genuine schema mismatch, not a
+ * missing endpoint — see `mvp/fix-plan.md`'s "Patient records" follow-up: the client's medication/routine
+ * shape (structured dose amount/unit, frequency preset codes, a multi-select `timeOfDay`) was built after the
+ * server shipped a simpler one (one free-text dose, one required frequency string, no `timeOfDay` at all),
+ * and which side to change is a product decision, not something to guess in code. Flip to `false` once that's
+ * resolved and `clientApi.ts`'s family-record methods are updated to match.
  */
 export const USE_PATIENT_RECORDS_MOCK = true;