chore(dashboard): retire the GLP-1 tile

Drop the standalone GLP-1 dashboard tile and its data-fetch route.
The /api/dashboard/glp1 endpoint has no consumer outside the retired
tile (no native client reads it), so the route, the tile component,
its test, the e2e spec, the locale keys, the query-key entry and the
drift-guard assertion all retire together.

The medication detail page and its bidirectional contracts stay
untouched. An opt-in dashboard widget that surfaces the same level
chart will land later in this cycle, anchored on the existing
dashboard-layout toggle list.
This commit is contained in:
Marc-André Bombeck committed 2026-05-16 01:00:09 +02:00
1 parent 59ef95f284
commit 8e5f71b1b9
13 files changed
+7 -1459

No files matched your search

+1 -16
View File
@@ -10,8 +10,7 @@
* specific call-site key groups so a contributor who only edits one
* bundle gets a precise failure instead of a 200-line parity diff.
*
* Scope (mirrors v1.4.27 buckets B1, B3, B4, B5):
* - dashboard.glp1.* (B1 — drug-level + weight tabs)
* Scope (mirrors v1.4.27 buckets B3, B4, B5):
* - admin.carrier* + admin.providerWithings + admin.providerPasskey (B3 — login carrier chip)
* - insights.emptyState.* (B4 — per-metric empty states)
* - notifications.admin.* (B5 — admin notification messages)
@@ -67,20 +66,6 @@ const REQUIRED_KEY_SETS: Array<{
label: string;
required: string[];
}> = [
{
label: "dashboard.glp1.* (B1 — GLP-1 tile tabs)",
required: [
"dashboard.glp1.title",
"dashboard.glp1.tabLevel",
"dashboard.glp1.tabWeight",
"dashboard.glp1.tabsAria",
"dashboard.glp1.rangeStripLabel",
"dashboard.glp1.levelUnavailable",
"dashboard.glp1.weightUnavailable",
"dashboard.glp1.lastInjection",
"dashboard.glp1.nextInjection",
],
},
{
label: "admin.carrier (B3 — login carrier chip)",
required: ["admin.carrier", "admin.carrierUnknown"],