Marc-André Bombeck d38ceb4beb fix(sleep): say why consistency or timing has no value ...

A rhythm sub-score below three nights with a main sleep was dropped from
the blend and its row read "no data", although the nights were there;
since a nap-only day no longer has a place on the clock, a ring worn
for only a few nights reaches that state more often. Each withheld
consistency or timing sub-score now carries the reason
(`few_nights`, `no_main_sleep`) and the score value carries how many
nights the rhythm is built from, so the row reads "not enough nights
yet (2 of 3)" or "latest night had no main sleep" instead. Neither is
ever shown as 0.

Refs #1204

2026-10-19 15:15:46 +02:00

..

de.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

en.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

es.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

fr.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

it.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

ko.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00

pl.json

fix(sleep): say why consistency or timing has no value

2026-10-19 15:15:46 +02:00