feat(score): compute a health score from the data a person actually has

Three distinct areas of health stops being the price of admission and
becomes what it always described: a recommendation. `evaluateScoreBreadth`
returns a tier instead of a pass/fail — `full` at three areas or more,
`partial` at two, `minimal` at one — and refuses only when not one pillar
came back usable, with the reason `no_usable_data`.

The arithmetic does not change with the tier. Same mean, same worst-pillar
band drag, same noise floor. A one-area score of 82 is an honest 82 that
rests on one area, and discounting it for the pillars somebody does not
track would have been a new invented target, which is the thing this score
spent two releases removing.

The physiological requirement becomes a labelling fact rather than a veto.
An account whose only readable pillar is activity or wellbeing gets its
number with `physiological: false` on the basis block; the old refusal told
that person nothing they could not already see.

`SCORE_MIN_ELIGIBLE_DOMAINS` is now `SCORE_RECOMMENDED_DOMAINS` and still
feeds `deriveCoverage`, so the coverage fraction and the confidence blend
keep telling the truth with no new machinery: a one-area score lands at low
confidence through the path that was already there. The fraction used to be
a floor every scored account had cleared; it is a real moving number now.

`SCORE_VERSION` 3 -> 4 and `SCORE_ALGORITHM_CHANGED_AT` moves to the
release date. Both are method-identity duties: deltas suppress as
`algorithm_changed` across the straddle window, the notice key rotates so
each account is told once, and stored days stamp 4. No v3 row is rewritten
and no v3 number changes meaning.

The settings write follows the same rule rather than a stricter one. It
refused two-area and non-physiological selections on the ground that they
could not produce a score; they can, so refusing the write would be the two
layers disagreeing about the one question they share. The empty selection
is still refused, under a single reason `no_pillars_selected`, and the seven
message catalogues trade the two old refusal sentences for one.

Also fixes the stale `./series.ts` reference in the config header — that
module was deleted as dead in v1.35; the columns the sentence describes are
still written by `./record.ts`.

src/components/settings/score-section.tsx

@@ -97,24 +97,25 @@ interface HealthScoreConfigPayload {
 }
 
 /**
- * The two refusals the write can return, in the reader's language.
+ * The refusals the write can return, in the reader's language.
+ *
+ * One, since v1.38: a selection with nothing in it. Two areas or one now
+ * save and score, so there is no longer anything to explain about them.
  *
  * Keyed on `meta.reason`, which is the machine-readable half of the
  * server's answer. The server's own English sentence is not shown: it
- * exists for callers without a locale, and rendering it would leave five
- * of the six locales reading English at exactly the moment the person
+ * exists for callers without a locale, and rendering it would leave six
+ * of the seven locales reading English at exactly the moment the person
  * needs to understand something.
  *
  * Typed as a total map over `ScoreBreadthFailure` rather than over
- * `string`, so a third refusal reason added to the rule cannot ship with
- * this surface quietly falling through to a generic "couldn't save". The
- * TYPE is imported, never the rule: the breadth question is answered
- * server-side and answered once.
+ * `string`, so a second refusal reason added to the rule cannot ship
+ * with this surface quietly falling through to a generic "couldn't
+ * save". The TYPE is imported, never the rule: the breadth question is
+ * answered server-side and answered once.
  */
 export const REFUSAL_KEYS: Record<ScoreBreadthFailure, string> = {
-  measured_physiological_domain_required:
-    "settings.sections.score.refusal.physiological",
-  three_domains_required: "settings.sections.score.refusal.domains",
+  no_pillars_selected: "settings.sections.score.refusal.empty",
 };
 
 function verdictsFrom(