test(labs): tie the category fields to their readers

A per-envelope guard walks the category leaves of LabOverviewResponse,
customPanels on ListBiomarkersResponse and adoptedPanel on
BiomarkerMergeResult out of the Zod schemas and ties each to the web
reader that renders it, so a new leaf without a reader fails. The
resolved-field guard gains a rule that bans the category ingredients
(catalogKeyForName, resolveMarkerCategory, summariseCategory,
categoriseOverview, ALIAS_PANEL, buildLocalisedLabelIndex) from client
code: the category, its order and its status are read, never rebuilt.

Refs #1349
This commit is contained in:
Marc-André Bombeck committed 2026-11-06 17:57:28 +01:00
1 parent c96e0e0f78
commit c0470df14c
3 files changed
+192 -1

No files matched your search

+1 -1
View File
@@ -208,7 +208,7 @@ const biomarkerMergeRequest = biomarkerMergeSchema.meta({
"Fold `sourceIds` (1..10, unique, without the target) into the marker in the path. `dryRun` (default false) answers the same result and writes nothing; a client shows it before asking to confirm, because a merge cannot be undone.",
});
const biomarkerMergeResult = z
export const biomarkerMergeResult = z
.object({
dryRun: z.boolean(),
target: biomarkerRow.describe(