fix(insights): route alert-card compliance through the cadence-aware engine + deep data cleanups

The insights alert cards computed medication compliance with the naive
`schedules.length × days` denominator, so a fully-adherent weekly
injectable read ~14% and fired a false low-compliance alert (and a paused
medication mis-fired the same way). Route the alert path through the
canonical `calculateCompliance` engine like every other compliance
surface — pause eras, schedule revisions and dose windows honoured.

Document confirm: committing a numeric observation against an existing
biomarker silently replaced the stated unit with the catalog's, with no
conversion — a stated "6.1 mmol/L" against a mg/dL marker committed
"6.1 mg/dL". Reject on a unit mismatch (fail closed) so the user
reconciles on the review screen, the same posture as the unit-required
guard.

Wire grip strength, waist (with waist-to-height) and pain into the
briefing feature set and the grounding allow-set so the clinical-depth
signals reach the daily narrative; the mental-health screeners stay
excluded by construction.

Biomarker detail: fall back to a generic description for catalog-less
markers, and keep the heading + description with a retry on the error
state. Collapse the medication External-API and Lifecycle groups by
default. Re-enable the insights scroll-to-top regression and assert the
shipped main-content reset.

Align the EN haemoglobin/haematocrit display names to British spelling.

Drop the redundant `(userId, deletedAt)` index on inbound documents — a
strict prefix of the new three-column index. Trim the dead
MedicalDisclaimer variants to the one live `dataPosture`. Move the
crisis-resources card off the retired amber tint to a calm
destructive-subtle border. Add a registry invariant asserting every
biomarker signal key resolves to a real catalog slug.

src/lib/documents/commit.ts

@@ -71,6 +71,23 @@ async function commitObservation(
     referenceHigh: isQualitative ? null : data.referenceHigh,
     panel: null,
   });
+  // Fail closed on a unit mismatch against an EXISTING marker. A freshly
+  // minted marker adopts the document's unit, so this only bites when the
+  // stated unit disagrees with the catalog's authoritative one (e.g. a
+  // document states "6.1 mmol/L" against a marker stored in mg/dL). Writing
+  // the stated number under the catalog's unit would corrupt the reading AND
+  // break the "transcribe verbatim" contract — so reject the fact and let the
+  // user reconcile on the review screen, exactly like the `unitRequired` gate.
+  if (!isQualitative) {
+    const stated = (data.unit as string).trim().toLowerCase();
+    const target = biomarker.unit.trim().toLowerCase();
+    if (stated !== target) {
+      throw new FactCommitError(
+        "observation.unitMismatch",
+        `The stated unit (${(data.unit as string).trim()}) does not match the saved unit for ${biomarker.name} (${biomarker.unit || "none"}). Reconcile the unit before saving.`,
+      );
+    }
+  }
   const created = await prisma.labResult.create({
     data: {
       userId,