Say whether each coverage case is an authored recipe or the default

Two branches met here. One made `configured` a required field so a caller
cannot stay silent and publish "not authored" for an account that chose its
own composition. The other wrote these cases before that existed, so they
compiled against the old shape and stopped compiling against the new one.

Filling the field in to satisfy the compiler would have thrown away the point
of making it required, so each case now states what it actually is: the two
with a hand-picked selection are authored, and the one whose own comment says
the account counts all eight is the default.
This commit is contained in:
Marc-André Bombeck committed 2026-07-31 20:34:29 +02:00
1 parent 778725834f
commit 88162eda07
1 file changed
+6
@@ -142,6 +142,8 @@ describe("Health Score coverage contract", () => {
const composite = computeComposite({
pillars: allPillars(selection),
availablePillars,
// An authored recipe: the person took four pillars out.
configured: true,
asOf: NOW,
});
@@ -175,6 +177,8 @@ describe("Health Score coverage contract", () => {
const composite = computeComposite({
pillars: allPillars(selection),
availablePillars: compositionFor(selection),
// An authored recipe.
configured: true,
asOf: NOW,
});
@@ -193,6 +197,8 @@ describe("Health Score coverage contract", () => {
const composite = computeComposite({
pillars: allPillars(withData),
availablePillars: compositionFor(SCORE_PILLAR_IDS),
// The full catalogue is this account's default, not a choice.
configured: false,
asOf: NOW,
});