feat: the score says when a pillar stopped counting

A pillar can leave the set behind the number without anybody choosing it:
a window rolls past its floor, a module goes off, a source goes quiet. The
delta already refuses to narrate that as a health event, which stops a
false "you dropped six points" and puts nothing in its place. The level
moves, the panel shows a different number, and the cause is nowhere on the
surface. Under the adaptive minimum this matters more rather than less,
because compositions are smaller now and sit closer to their floors.

The report carries `compositionNotice` when today's set differs from the
last local day the account has a stored score for. Optional and nullable,
the additive shape the score's wire has used six times, so a payload
cached before it existed stays valid. It names what left and what joined
as pillar ids; the surfaces already own the labels, and the reason a
departed pillar stopped counting comes from that pillar's own row in the
same report rather than from a second vocabulary.

Two changes deliberately do not raise it. A method move and a recipe
change each already have their own note, and telling someone twice about
one event teaches them to ignore both.

The key is `health-score:v<version>:composition:<hash of the sorted set>`
and rides the existing dismissed-item ledger, so a dismissal holds until
the set moves again rather than until tomorrow. The read excludes today on
purpose: the row for today is written by the same request that computed
the report, so comparing against the newest row would find today's own
composition on the second load of the same page and the note would vanish
between two views of it.

This gives `HealthScoreRecord` its first production reader. Since it
shipped it has been written on every scored read and consumed by nothing
but backup and restore, which is the write-only shape the contributor
notes call a liability and which nothing in the gate can notice, because
every check proves one end. The round trip is proved against real
Postgres: raise the note, wipe the table, restore it through the admin
route, get the same note back, and hold the dismissal across it.

Rendering is one muted line on the score card and a card of its own on the
settings page, beside the recipe note rather than inside it. Deliberately
not a push.

Four fake Prisma clients gain the new read. They are doubles of a client
the reader really does call now; leaving them short and guarding the call
site instead would have been a shim for a caller that does not exist.

docs/api/openapi.yaml

@@ -50111,6 +50111,51 @@ components:
                 - dismissed
               additionalProperties: false
             - type: "null"
+        compositionNotice:
+          description: "A pillar joined or left the set behind the number since the account's last stored local day. Raised only
+            for a change nobody chose: a method move or a recipe change is the algorithm notice's subject instead, and
+            raising both would announce one event twice. Optional so a payload cached before the field existed stays
+            valid; null when there is nothing to say. Dismissed through `POST /api/daily/digest/dismiss` with this
+            `itemKey`, which is keyed on the resulting SET so it re-raises when the set moves again rather than every
+            day."
+          anyOf:
+            - type: object
+              properties:
+                itemKey:
+                  type: string
+                left:
+                  type: array
+                  items:
+                    type: string
+                    enum:
+                      - BLOOD_PRESSURE
+                      - GLYCAEMIA
+                      - ACTIVITY
+                      - SLEEP
+                      - ADIPOSITY
+                      - WELLBEING
+                      - LIPIDS
+                joined:
+                  type: array
+                  items:
+                    type: string
+                    enum:
+                      - BLOOD_PRESSURE
+                      - GLYCAEMIA
+                      - ACTIVITY
+                      - SLEEP
+                      - ADIPOSITY
+                      - WELLBEING
+                      - LIPIDS
+                dismissed:
+                  type: boolean
+              required:
+                - itemKey
+                - left
+                - joined
+                - dismissed
+              additionalProperties: false
+            - type: "null"
         restMode:
           description: Attached when an illness episode was active as of the scored instant — the instant the score was computed
             for, not a fresh now. The score is NOT penalised; this frames it. Null when no episode was open. On this