fix(measurements): store a hand-entered night in the unit the field asks for

The manual sleep field is labelled in hours. The column stores minutes, because
that is what every sync source delivers and because a single stage segment is
only a few of them. The form sent the typed number straight through, so a night
entered as 7.5 was filed as seven and a half minutes and the list showed eight
minutes of sleep.

Nothing rejected it. Seven and a half minutes is inside the column's
plausibility band — a stage really can be that short — so the entry looked
accepted and the loss was silent.

Both ends were already right: the field says hours, the list formats minutes as
hours and minutes. The assembly between them was where the factor went missing,
which is why the round-trip test runs the whole of it — the form's conversion,
the shipped POST, the stored row, and the formatter the list paints with.

The storage unit stays minutes. The conversion sits at the entry boundary in
one place with its inverse beside it, so a future editing surface cannot land
on a different answer, and it rounds to whole minutes rather than storing
437.99999999999994 for 7.3 hours.

The value field also lost "7,5" outright. `type="number"` sanitises a decimal
comma away on the engines that do not localise the field, so the entry arrived
as an empty string with no explanation, and `parseFloat` would have read it as
7 on the engines where it survived. The field now takes the same shape the labs
and custom-metric fields use — a numeric keypad and a submit path that reads
the comma — so every decimal metric on the form gains it, not only sleep.

`scripts/diagnose-manual-sleep-hours.ts` lists the rows already stored this
way. It reports and does not repair: an eight-minute stage and a night typed as
eight hours are the same number in the same column, and only the person who
entered it knows which it was.

src/components/measurements/measurement-form.tsx

@@ -26,6 +26,10 @@ import { Loader2, MoreHorizontal, Plus, RotateCcw } from "lucide-react";
 import { toast } from "sonner";
 import { useTranslations } from "@/lib/i18n/context";
 import { useUnitDisplay } from "@/hooks/use-unit-display";
+import {
+  entryValueToCanonical,
+  parseDecimalEntry,
+} from "@/lib/measurements/entry-units";
 import {
   invalidateKeys,
   measurementDependentKeys,
@@ -343,7 +347,17 @@ export function MeasurementForm({
         // identity path — `fromDisplay` returns the typed number unchanged, so
         // the payload is byte-identical to before. Round only the converted
         // imperial value so 210 lb stores as 95.25 kg, not 95.25439770….
-        const typed = parseFloat(value);
+        //
+        // A second boundary sits beside it: a few types are stored in a unit
+        // the form does not ask for. Sleep is entered in hours and stored in
+        // minutes, and sending the typed number through unconverted filed a
+        // 7.5-hour night as seven and a half minutes — inside the column's
+        // plausibility band, so nothing objected.
+        const typed = parseDecimalEntry(value);
+        if (typed === null) {
+          setError(t("measurements.saveError"));
+          return;
+        }
         let canonicalValue = typed;
         if (unitDisplay.isTransformed(type)) {
           const inverted = unitDisplay.fromDisplay(type, typed);
@@ -352,6 +366,7 @@ export function MeasurementForm({
               ? Math.round(inverted * 100) / 100
               : inverted;
         }
+        canonicalValue = entryValueToCanonical(type, canonicalValue);
         await apiPost("/api/measurements", {
           type,
           value: canonicalValue,
@@ -533,9 +548,13 @@ export function MeasurementForm({
         >
           <Input
             id="value"
-            type="number"
+            // Not `type="number"`: its sanitisation drops a decimal comma on
+            // the engines that do not localise the field, and "7,5" then
+            // arrives as an empty string with no explanation. `inputMode`
+            // still raises the numeric keypad, and the submit path reads the
+            // comma — the same shape the labs and custom-metric fields use.
+            inputMode="decimal"
             enterKeyHint="next"
-            step="any"
             value={value}
             onChange={(e) => setValue(e.target.value)}
             placeholder={

src/lib/measurements/entry-units.ts

@@ -0,0 +1,73 @@
+/**
+ * Where the entry form asks for one unit and the column stores another.
+ *
+ * This is not the metric/imperial display transform in `display-transform.ts`:
+ * that one follows a preference and is the identity for anyone on metric. This
+ * one holds regardless of preference, because the storage unit was chosen for
+ * the sync sources rather than for the person typing.
+ *
+ * Sleep is the case. `SLEEP_DURATION` is stored in minutes — every provider
+ * delivers minutes, and a per-stage segment is only a few of them — while a
+ * person logging a night by hand thinks in hours and the field says so. The
+ * form sent the typed number straight through, so a night entered as 7.5 was
+ * stored as seven and a half MINUTES and read back on the list as eight
+ * minutes of sleep. Nothing rejected it: seven and a half minutes is inside
+ * the column's plausibility band, because a single sleep STAGE really can be
+ * that short.
+ *
+ * The storage unit stays minutes. The conversion belongs at the entry
+ * boundary, in one place, with the inverse beside it so a future editing
+ * surface cannot land on a different answer.
+ */
+
+export const MINUTES_PER_HOUR = 60;
+
+/**
+ * Entry unit → canonical unit multiplier, per measurement type. A type absent
+ * from this table enters in the unit it is stored in.
+ */
+const ENTRY_TO_CANONICAL_FACTOR: Readonly<Record<string, number>> = {
+  SLEEP_DURATION: MINUTES_PER_HOUR,
+};
+
+/** Whether the type's entry unit differs from the unit its column stores. */
+export function hasEntryUnitConversion(type: string): boolean {
+  return type in ENTRY_TO_CANONICAL_FACTOR;
+}
+
+/**
+ * Convert a value as typed in the entry form to the unit the column stores.
+ *
+ * The result is rounded to the nearest whole canonical unit for a converted
+ * type: 7.3 hours is 438 minutes, and floating-point multiplication would
+ * otherwise store 437.99999999999994 for it. An unconverted type is returned
+ * untouched, so no existing metric changes shape.
+ */
+export function entryValueToCanonical(type: string, entered: number): number {
+  const factor = ENTRY_TO_CANONICAL_FACTOR[type];
+  if (factor === undefined || !Number.isFinite(entered)) return entered;
+  return Math.round(entered * factor);
+}
+
+/** The inverse: a stored value expressed in the unit the entry form asks for. */
+export function canonicalValueToEntry(type: string, canonical: number): number {
+  const factor = ENTRY_TO_CANONICAL_FACTOR[type];
+  if (factor === undefined || !Number.isFinite(canonical)) return canonical;
+  return canonical / factor;
+}
+
+/**
+ * Read a number out of an entry field, accepting the decimal comma.
+ *
+ * Most of the application's readers are German, and "7,5" is how they write
+ * seven and a half. `parseFloat` reads that as 7 and discards the rest without
+ * complaint — the worst shape of wrong, since the entry looks accepted.
+ * Returns `null` for anything that is not a number, so the caller decides what
+ * an empty field means rather than inheriting a `NaN`.
+ */
+export function parseDecimalEntry(raw: string): number | null {
+  const trimmed = raw.trim().replace(",", ".");
+  if (trimmed === "") return null;
+  const parsed = Number(trimmed);
+  return Number.isFinite(parsed) ? parsed : null;
+}