Commit Graph
7126 Commits
Author SHA1 Message Date
Marc-André Bombeck 33debe777f test(nutrients): pin the token arm, the day fold and the macro surfaces
Integration coverage for the nutrient batch under each credential (the
source row, the 403s, the module gate, re-post, backfill, coexistence
with the phone's row and the bridge bucket), kcal and g ingest with kJ
skipped, the day fold on the overview and in the correlation read, and
composition refusing energy, macros and alcohol. Route-level checks run
against Postgres rather than a stubbed handler. The energy card reports
a failed save through the shared error toast.
2026-11-17 19:05:32 +01:00
Marc-André Bombeck db0e4f9688 feat(nutrients): carry daily targets through backup, wipe and the API contract
Nutrient targets travel in the account-settings slice of the full
backup and are admitted code by code on restore, so an unknown code or
an out-of-range value is dropped and named while the rest come back. A
data wipe clears them. The targets route joins the OpenAPI registry,
and the regenerated contract carries the wider nutrient enums, the new
sources and the target and authority fields. Refs #1402.
2026-11-17 19:05:31 +01:00
Marc-André Bombeck 7c40ba8202 feat(nutrients): accept measurements:write tokens on the nutrient batch
A bridge such as a food tracker can now post daily nutrient totals with
the measurement token. The credential picks the source row: a scoped
token writes EXTERNAL, the native client keeps writing APPLE_HEALTH, and
the body has no say. Bridge tokens count in their own rate-limit bucket,
and the source is recorded in the audit row.

The write phase moves into writeNutrientDayTotals so the route keeps
only parsing, validation and bookkeeping. The scope guard now freezes
four doors for measurements:write. Refs #1402.
2026-11-17 18:47:11 +01:00
Marc-André Bombeck 8f96c2f0a2 feat(nutrients): track energy, macronutrients, sodium, potassium and alcohol
The catalog gains energy (kcal), protein, carbohydrates, fat, sugar and
fiber (g), sodium and potassium (mg) and alcohol (g of ethanol, no
HealthKit type). Each code now names its group and whether a
supplement's composition may list it; references name their authority
(EFSA, or IOM for protein and carbohydrates, NIH ODS for chromium).

Day totals fold through one rule everywhere: the largest of the
day-total sources (Apple Health, Health Connect, an external bridge)
counts, manual water and supplement doses add on top. This also stops
Apple Health and Health Connect totals for the same day from adding up.

The nutrients page gets an energy and macronutrient card with an inline
daily target, and an alcohol card next to caffeine. The correlation scan
gives the macros their own budget of two channels and leaves logged
alcohol out. Daily series and the MCP tool return the target the person
set. Refs #1402.
2026-11-17 18:47:02 +01:00
Marc-André Bombeck a68ec9421f feat(nutrients): store daily nutrient targets per account
A nullable users.nutrient_targets_json column (migration 0499) holds a
target or limit per catalog code in the code's canonical unit. GET and
PATCH /api/nutrients/targets read and merge it behind the nutrients
module; PATCH refuses unknown codes and values above the code's
plausibility cap, and audits the codes set, never the amounts.
2026-11-17 18:46:48 +01:00
Marc-André Bombeck 9c29fd1121 fix(insights): cap bulk measurement reads per type so a dense stream cannot starve sparse ones
The bulk measurement reads behind the insight features, the Coach snapshot
timelines, the mood cross-metric pairing, the correlation windows and the
weight and blood pressure status cards read newest-first across all their
types under a single row cap. On an account with a wearable heart rate
stream the cap filled within hours, and every weight, blood pressure or
other sparse reading fell out of the read, so blocks reported no data for
metrics with years of it.

All of them now go through one read that descends the live partial index
once per type, each type stopping at its own cap. The feature extraction
and the Coach snapshot cap each type at 6000, so a block built from one
type's read equals the block the full read builds (worst case 72,000 rows
for the twelve feature types). The mood, correlation and status reads keep
their old totals and share them fairly: each type keeps at least its share,
a sparse one all of its window.

The feature context's data span now comes from index probes over every
type in the window rather than from the capped rows, and its measurement
count is the readings the blocks were built from.

Refs #1398
2026-11-16 08:05:00 +01:00
mailuminatti 383500b5fa fix(insights): update Coach source snapshot comment for type-restricted scoped read 2026-11-15 19:44:38 -05:00
mailuminatti dc947a5c2b fix(insights): restrict scoped feature bulk read to requested blocks' measurement types 2026-11-15 19:42:41 -05:00
mailuminatti 4d87643a0f fix(insights): update scoped feature read comment for type-restricted bulk read 2026-11-15 19:39:56 -05:00
Marc-André Bombeck e451f64c3a Merge remote-tracking branch 'origin/main' into chore/deps-2026-11-15
# Conflicts:
#	CHANGELOG.md
2026-11-16 00:06:17 +01:00
Marc-André Bombeck 6debd62326 build(deps): bump next and eslint-config-next to 16.4.6
16.4.6 keeps a single header value as a string, so the compression
middleware now sees a route handler's Content-Type and gzips the
response when the client accepts it. Route handlers were never
compressed before. Measured on a production build: JSON and CSV
exports go out gzipped with their Content-Disposition intact and still
flush chunk by chunk, so a streamed download keeps arriving as it is
written. The Coach and document chat streams send
Cache-Control: no-transform, which the middleware honours, so they stay
uncompressed and each frame arrives when it is written. A guard now
holds every text/event-stream surface to that directive.

The notification journey failed twice on the release candidate at the
same step: the e-mail address typed into the card was wiped. The spec
waited for the settings read with waitForResponse, which settles on the
headers, and treated that as the card having copied the server value
into the input. With compression the body follows the headers after a
round through zlib on the thread pool, which a loaded runner can hold
up, and the late copy overwrote the typed value. The spec now also
waits for each card's enable switch, which is disabled until its read
has landed and is enabled in the same render that does the copy.
2026-11-15 23:43:32 +01:00
Marc-André Bombeck 31253ff615 fix(labs): let a marker without a unit be edited
A marker minted from a text result (OCR, CSV import, inbound document)
stores an empty unit: none has been chosen yet, and its first numeric
reading sets it. The editor read that empty unit as a unit still to be
typed and refused to save, ticking "No unit" sent "1", and the update
route refused any unit change on a marker with readings. Every save of
such a marker failed, a plain rename included, because the form always
sent the unit.

- The form opens an empty unit with "No unit" ticked and sends the unit
  only when it changed; the empty unit and the unity count as the same
  "no unit" there, so a rename leaves the stored unit as it is.
- PUT /api/biomarkers/{id} locks the unit only on a real change while
  numeric readings exist (deleted ones included). Another spelling of
  the stored unit is no change, and text results carry no number the
  unit could misstate, so a text-only marker may take any unit.
- The empty unit stays distinct from "1": it still adopts the unit of
  its first number, which "1" must not. No stored value changes.

Refs #1393
2026-11-15 23:32:18 +01:00
Marc-André Bombeck f602336fcb build(deps): bump web-push from 3.6.7 to 4.0.0
4.0.0 moves the package to ESM and class syntax and drops minimist from
the CLI. The sender and the VAPID route load it with a dynamic import
and call generateVAPIDKeys, setVapidDetails and generateRequestDetails,
which keep their names, arguments and module-level VAPID state; the
request is still dialled through safeFetch, so the library's own
transport and error shapes are not on our path.

Every sender test mocks the library, so a contract test now runs the
real one: a stored VAPID pair is accepted, the request carries the same
headers (TTL of four weeks, Urgency, aes128gcm), the VAPID JWT verifies
against the public key with the endpoint origin as audience, and the
subscriber's keys decrypt the body back to the payload. It passes on
3.6.7 and on 4.0.0.
2026-11-15 23:21:37 +01:00
Marc-André Bombeck 0d5f1ec04a build(deps): bump the production-weekly group
@aws-sdk/client-s3 3.1169 and lib-storage 3.1167, @napi-rs/canvas 1.1.1,
@simplewebauthn/server 14.1.0, @tanstack/react-query 5.107.1,
dotenv 18.0.10, jose 6.2.17, lucide-react 1.73, mmdb-lib 3.0.5,
nodemailer 10.5.0 and pg-boss 12.38.2.

The pins that hold these move after reading the installed sources:

- pg-boss 12.38.2 keeps the failed-row ledger the 72-hour reader relies
  on: deletion still runs on completed_on + deletion_seconds against
  job_now(), with the 14-day retention, 7-day deletion, 15-minute expiry
  and two retries unchanged. The release only moves keep_until along
  with start_after on retry and resume.
- @simplewebauthn/server 14.1.0 adds passkeyProviderMetadata to the
  registration result. It is filled only by an initialised FIDO metadata
  service, which downloads from the FIDO Alliance; HealthLog initialises
  none, so the contract now pins the field as absent. The stored key
  bytes are unchanged. The new origin and RP ID checks reject a trailing
  slash or non-ASCII form, and both values already come from URL.origin
  and URL.hostname.
- dotenv 18.0.10 moves its CLI to a separate entry; the library API is
  unchanged. The Prisma CLI stage installs the same version.
2026-11-15 23:18:42 +01:00
Marc-André Bombeck 39a855b6ad Merge branch 'fix/1384-pregenerate-without-provider' into release/v1.47.6 2026-11-15 11:16:13 +01:00
Marc-André Bombeck 5152e68586 fix(jobs): step over a briefing night that attempted nobody
A night on which every account was skipped, for instance because every
provider was paused for background work, wrote all_failed false. The
repeated-failure alert read that as a successful run: it ended the
streak and announced a recovery while the provider was still down, and
nights then alternated between failed and paused so the streak never
reached the alert again.

The run now also records run_attempted. A completed run with
run_attempted 0 is neither a failure nor a recovery: the alert and
readConsecutiveRunFailures step over it.

Refs #1384
2026-11-15 11:16:13 +01:00
Marc-André Bombeck b4927e1ea4 Merge branch 'fix/e2e-flakes' into release/v1.47.6
# Conflicts:
#	CHANGELOG.md
2026-11-15 10:59:09 +01:00
Marc-André Bombeck e84c358fdf fix(charts): match chart loading shells to the charts they become
The footer reserve under a day-linked chart's loading shell still held the
caption line that was dropped from those charts, so every such shell stood
20 px taller than its chart (40 px on a phone). The dashboard's mood chart
loaded behind the generic shell, which is about 30 px shorter than the
mood card. When the shared chart chunk arrived late the dashboard's chart
row changed height under a reader already scrolled past it; the tablet
shell journey measured <main> right after such a swap and found it no
longer at its end.

The reserve now holds only the day rug, and the mood chart gets a shell
built from the same card primitives and boxes. The tablet journey also waits
for every chart cell to reveal and every loading shell to go before it
scrolls to the end, instead of trusting two equal heights 250 ms apart.
2026-11-15 10:58:13 +01:00
Marc-André Bombeck 23a6f85b0f fix(sharing): drop an account read answered across a record switch
Raising the record-session hold clears the query cache, which remounts the
account query, so the switching tab has a GET /api/auth/me in flight beside
its own POST /api/account/switch. When the server answered that read from
the record being left and the answer was applied after the commit, fetchMe
rewrote the scope mirror back to the old record. A peer tab that had already
settled read that write as a foreign switch and published a hold expecting
the old record, which no /me would ever confirm, so every tab sat behind the
hydration gate until the stored transition aged out.

The transition store now counts the changes a tab applies, and fetchMe
repeats a read whose request straddled one instead of applying it.
2026-11-15 10:58:06 +01:00
Marc-André Bombeck 75f8a648dc fix(jobs): stop counting an unusable provider as a failing briefing run
The nightly briefing pass settled an account as failed whenever its
generation failed, including when every provider of its chain was
benched for background work and no request was sent, and when the
provider refused the account's own credential. A key revoked at its
issuer stays saved and is refused every night, so a single-account
instance read as all-failed night after night and the repeated-failure
alert reported a broken job.

- A chain that sent nothing settles as skipped (provider_benched), with
  no 45-minute retry.
- A refused credential of the account's own settles as auth_failed,
  which the run reports as partial but does not fail over; a refusal of
  the operator's shared key still fails the run.
- The generator's failed outcome names the provider that failed first,
  whether its credential was refused and whether anything was sent.
- The run's facts carry failure_cause and failure_provider.

The admin Background jobs card listed only pg-boss failures, while the
alert also counts runs that completed with every account failed, so an
operator sent to the card read that nothing had failed. The card now
lists those runs, and the card and the alert describe them in words
with the cause and provider instead of quoting the run's JSON.

The warm tally counted a status card that fell back to its deterministic
text as a warmed assessment; it now counts model-written notes only.

Refs #1384
2026-11-15 10:45:21 +01:00
Konrad Garbal 851d52b137 fix(illness): allow creating episodes before noon 2026-11-15 09:22:26 +01:00
Marc-André Bombeck 4b500dc66c Merge remote-tracking branch 'origin/main' into feat/1371-medication-note
# Conflicts:
#	CHANGELOG.md
2026-11-14 09:36:45 +01:00
Marc-André Bombeck d0b7749a99 fix(medications): keep the request schemas out of the wizard bundle
The note field imported its length limit from the validation module,
which pulled zod and the medication request schemas into the client and
put the medications list and detail pages over their bundle budget. The
limit lives in a zod-free module now, and the validation re-exports it.
2026-11-14 09:35:35 +01:00
Marc-André Bombeck 4537ff0d8e feat(medications): add a note to the medication (#1371)
Directions such as "30 to 60 minutes before food" had nowhere to go: a
medication carried no free text of its own, only the notes on a dose
change or a course. The medication now has one note, edited on the last
step of the wizard and shown under the name on the detail page, above
the dose actions on both card variants, under the picked medication in
the log-dose sheet, and per row in the take-all-due list. One
MedicationNote component renders it everywhere, in foreground text.

The note is sealed at rest in Medication.noteEncrypted (migration
0498_medication_note, lock-bounded), with no plaintext column. Create
and update take an optional `note`: trimmed, at most 500 characters, an
empty string or null clears it, absent keeps it. The wizard sends it on
an edit only when it changed, so an unrelated save never clears it. The
list and detail reads strip the ciphertext and answer `note`.

Both ends of the data path carry it: the backup (decrypted in a portable
file, ciphertext in a disaster-recovery file), the restore, the data
export, the key-rotation registry and script, and the MCP medication
schedule, resources and fetch, fenced as user text. The doctor report
and the FHIR export leave it out: it is the person's own reminder, and
the report has no selection for personal prose.

The size baselines rise by the one-line wiring of the field in the
medication page, detail tabs, cards, log-dose sheet, wizard step and
list read; the wizard payload grows by the field's own encode and
hydrate.
2026-11-14 09:30:40 +01:00
Marc-André Bombeck e715e428a6 Merge remote-tracking branch 'origin/main' into fix/1372-record-menu-and-push-errors
# Conflicts:
#	CHANGELOG.md
2026-11-14 09:10:24 +01:00
Marc-André Bombeck 422decc9d9 fix(notifications): say when the browser's push service refuses
Enabling Browser Push showed only "Activation failed" whenever
pushManager.subscribe() rejected. Brave keeps push messaging off by
default and rejects with "AbortError: Registration failed - push
service error", which left people with nothing to act on.

The browser's own refusal is now classified apart from the server
answers around it. An AbortError from subscribe reads as the push
service refusing and links the Browser Push docs; in Brave the message
names the setting under brave://settings/privacy. A blocked permission
stays blocked, and a dismissed prompt or a rejected key keeps the
generic message. The subscribe flow moves out of the card component so
it stays under the function size baseline.

Refs Discussion #1378
2026-11-14 08:56:25 +01:00
Marc-André Bombeck cfa834510e fix(nav): open the records inside the account menu on a phone
The record switcher opened as a side sub-menu next to the account menu.
On a phone the account menu sits against the right edge and takes most
of the width, so the 240 px sub-menu had room on neither side and ran
off the screen with the names cut off. Below the sm breakpoint the
trigger now unfolds the records in place inside the account menu;
wider screens keep the sub-menu. The trigger, list and entry slots are
unchanged, so the journeys read the same at either width.

Refs #1372
2026-11-14 08:56:18 +01:00
Marc-André Bombeck 2167e251c1 feat(custom-metrics): accept the measurement token on value logging
A script or a home-automation rule holding a measurement token can now
post a value to POST /api/custom-metrics/{id}/entries for a custom metric
its owner already created. The route names MEASUREMENTS_WRITE_SCOPE on
the POST only; the value list, the metric list and every create, edit,
delete and restore leg still name no scope and refuse the token 403.

The token stays on its owner's record: requireAuth refuses any account
selector, and an id that is unknown, deleted or another account's answers
the same 404. The entry has no source column, so the audit row names the
token that wrote it.

The bearer-scope guard now freezes the scope's reach at three files, with
the custom-metric file naming it once and only on the POST. Integration
cases cover the admitted write, idempotent retry, the foreign and deleted
ids, five other narrow scopes, every other custom-metric leg, and a shared
record. The OpenAPI descriptions and the token card text in every locale
say what the token can do and where a metric's id is found.

Refs #1377
2026-11-14 08:47:42 +01:00
Marc-André Bombeck d0763e273f fix(dashboard): give the tappable averages a 44 px touch target
The averages on a dashboard tile open their colour hint on a tap now,
which made them touch targets of 16 px height. On a touch screen the
trigger is 44 px tall, and a negative margin keeps the tile's line
where it was.
2026-11-12 17:16:10 +01:00
Marc-André Bombeck 3366a7a74c test: lower the size and comment baselines after the merges
Functions and files that shrank across the merged branches; every entry goes down.
2026-11-12 16:35:13 +01:00
Marc-André Bombeck 919c508d59 revert(sheets): take out Back closing the open sheet
Opening a sheet pushed a history entry, and closing it took that entry
off again with a history back. The browser answers that back later, so
when the close started a navigation it landed after the router's push
and undid it: the medication wizard stayed on the list instead of
opening the new medication, a section picked from the settings list on
a phone stayed on the account page, and a link followed from a sheet
could put the page under it back.

The sheet history goes, with its wiring in ResponsiveSheet, the
document sheet's opt-out, the account form's deference to it, Back
answering the discard question, and their tests. Back behaves as
before: it leaves the page and the sheet goes with it, and the account
form's own Back guard answers every Back again. A tap outside, Escape,
the X and a swipe still ask before dropping typed input. The two size
baselines return to their earlier numbers.
2026-11-12 16:27:10 +01:00
Marc-André Bombeck 6994cb5ce8 Merge remote-tracking branch 'origin/main' into release/v1.47.5 2026-11-12 15:46:29 +01:00
Marc-André Bombeck 80ee228899 fix(pwa): clear the leftover app badge from the page, not the worker
A badge call from the service worker stalled Chromium's worker thread
while it activated, awaited or not: the worker reached "activated" but
never claimed its pages, so no page was ever controlled and every
offline path was gone. The worker no longer touches the badge. The
installed app clears a leftover count from the page once the worker is
registered; a browser tab leaves it alone.

The filter-sync test no longer reads `history.length`, which the
browser caps; the recorded push without a replace already proves the
new entry.
2026-11-12 15:28:37 +01:00
Marc-André Bombeck 159f40c0fc test(reminders): run the ketone checkup cases beside the glucose ones
The two ketone cases repeated the glucose cases with one type changed; they are now one parametrized case each, which keeps the mocked client casts at their count.
2026-11-12 15:22:46 +01:00
Marc-André Bombeck 352a170313 docs: past tense for the Fitbit turndown, plain punctuation in new text
The Fitbit guide still called the integration experimental and spoke of
the 30 October 2026 turndown as ahead. Three new files carried em
dashes in a doc comment and two test titles.
2026-11-12 15:19:19 +01:00
Marc-André Bombeck 9ed27c47f4 fix(i18n): release notes label, neutral discard and prefill wording
- The About button opens the release notes and now says so in all ten
  languages; six of them still showed the English word "Changelog".
- The discard question now also covers edit sheets, where "Discard this
  entry?" read like deleting the target or episode being edited. It
  asks about the changes in every language; Russian also loses the
  ambiguous "Отменить" on both the title and the button.
- The 7-day trend figure on a dashboard tile had an English screen
  reader label in every language.
- Outlier terms in the new checkup and ketone strings follow each
  catalog (ru "Кетоны в крови", "Коуч"; es "Desactivado"; nl
  "rusthartslag"), the French steps question reads naturally, and the
  shared Polish and Russian Coach question no longer assumes a
  masculine speaker.
2026-11-12 15:19:19 +01:00
Marc-André Bombeck d7eac1f87e chore: drop tooling and host references from templates and comments
- The translation issue template called eight locales "AI-initial",
  left Russian out of its list and its dropdown; it now says they
  started as machine-translated drafts reviewed by the community.
- The pull request template asked for two locales where the checks
  require all ten, and pointed at an ignored docs folder.
- Code comments named the maintainer notes file, a release by its
  working name and an internal host; old changelog entries explained
  the notes files by their tool-specific names. A fixture token and
  the deploy webhook test's application id (a real one) are replaced.
2026-11-12 15:17:06 +01:00
Marc-André Bombeck 7dd251184f test: describe analytics fixtures without tying them to a real profile
Several test titles and comments said whose readings a fixture came
from, with a host name beside them: a blood pressure average, a month
of paired readings with dates, a cached insight about weight, cycle
history and dose timing. They now describe the fixture itself (a
profile averaging 134/87, a ten-pair month, a long history); the values
and what each test proves are unchanged.
2026-11-12 15:14:46 +01:00
Marc-André Bombeck c9264c047e docs(nutrients): keep the batch eviction note to its old length
The longer note pushed the batch handler one line past its size baseline.
2026-11-12 15:14:45 +01:00
Marc-André Bombeck a6c3916910 docs: point comments at the queue table's home and fix a bench note
Four comments still named `queue-runtime.ts` without its folder after it
moved under src/__tests__/helpers/, and the v1.45.0 boot page described
two dumps that are no longer kept.
2026-11-12 15:13:07 +01:00
Marc-André Bombeck 442d97cc66 fix(nutrients): refresh the correlation scan after a water or nutrient write
Water, caffeine and the nutrient channels feed the correlation scan
behind /api/insights/correlations and the Coach read line on the metric
pages, but the water and nutrient batch writes evicted only the
dashboard snapshot. After logging water both could serve the read taken
before it until the cell went stale. Both writes now sweep the record's
analytics cells, as measurement and mood writes do.
2026-11-12 15:12:47 +01:00
Marc-André Bombeck d430981caa fix(workouts): refresh the Insights Workouts pill after a workout write
The tab strip shows the Workouts pill from the presence read, which
stays fresh for five minutes and was not part of the workout write's
invalidation. After the first manual workout, or after deleting the
last one, the pill stayed missing or stayed on for up to five minutes.
2026-11-12 15:12:07 +01:00
Marc-André Bombeck 6f8a342edf fix(insights): offer no metric pill inside a switched-to record
Inside a managed child's record, or as a delegate with manage access,
the tab strip showed Weight, Pulse, Blood pressure and the other metric
pills, and every one of them opened an error. The strip now reads the
record's own presence answer, but the metric pages read /api/analytics,
which serves only the signed-in account's own record and refuses a
switched session. The strip again shows those pills only in the
account's own record, as before; mood, medication, workout and ECG
pills keep following the presence answer.
2026-11-12 15:11:40 +01:00
Marc-André Bombeck 6e8554fd37 fix(reminders): gate ketone checkups on the Glucose module
A "Measure blood ketones" checkup kept sending its push, Telegram or
email with the Glucose module switched off, while the glucose checkup
beside it went quiet. The checkup job kept its own copy of the module
map, which knew glucose but not ketones.

The job now asks the one ownership table the rest of the app gates on.
That table did not list the four mental-wellbeing screenings, which only
the job's copy knew, so they join it under the mental-health module; a
screening score row now also follows that module in the day view and
search.
2026-11-12 15:10:53 +01:00
Marc-André Bombeck 7b6d518ca6 fix(mobile): coach padding with the keyboard up, chip remove targets
- The Coach thread kept 80 px free under the last message for the New
  conversation button while the keyboard hid that button.
- The remove buttons on lab alias chips and attached-document chips
  reached sideways into their own label and the next chip, and an
  alias is removed at once. Their tap area now stays inside the chip's
  gaps sideways and keeps its height.
- A capture menu comment described a dialog that is gone.
2026-11-12 15:09:34 +01:00
Marc-André Bombeck cb569b6c9d fix(sheets): stop two capture forms asking before anything was entered
The symptom form and the dashboard's medication intake asked "Discard?"
on every close, untouched. The sheet's fallback check read the input
Radix keeps for the intensity slider (value "0" before anyone moves
it) and the dose the form fills in from the preselected medication as
typed input.

The check now skips a slider's own input and counts a slider moved off
unanswered instead, and compares a field against the value its form
says it filled in (`data-seed`). A controlled input's defaultValue
follows its value, so it cannot tell the two apart. The dose field
names the medication's dose, one line more for the form's baseline.
2026-11-12 15:09:29 +01:00
Marc-André Bombeck 218986ea89 fix(sheets): let Back answer the discard question with "keep editing"
Back on a sheet with unsaved input asks whether to discard it. A second
Back while that question was open put the sheet's entry back and asked
again, so the Android button could never get past the question. It now
closes the question and keeps the sheet and its entry, like Cancel.
2026-11-12 15:09:22 +01:00
Marc-André Bombeck 555a529260 fix(sheets): keep Back on the page a closed sheet returns to
Three ways the sheet's history entry could still cost a Back:

- A close that also writes the URL (the day's date picker, the life
  event sheet opened by ?add=lifeEvent) let the router's answer to that
  write land on the page entry with the closed sheet's mark. The next
  sheet close then stepped one entry past the page, and on an installed
  app opened from a notification that closed the app. A write that
  carries the mark of a sheet that is gone now loses it.
- A sheet's entry started empty, and landing below it copied that empty
  state onto the page entry, so an open day or document lost the key it
  keys its own Back on. The sheet's entry now starts as a copy of the
  page entry's state.
- The account form's Back guard heard the sheet's own Back first when
  it was mounted before the first sheet of the visit, and asked to
  discard the form's edits for closing the section list. The guard now
  leaves a popstate the sheet history owns to it.

The browser tests run against Chromium's session history and fail
without each fix.
2026-11-12 15:09:13 +01:00
Marc-André Bombeck 3faf1b1c8b Merge branch 'release/v1.47.4' into release/v1.47.5
# Conflicts:
#	src/__tests__/baselines/source-file-lines.json
#	src/__tests__/baselines/source-function-lines.json
#	src/__tests__/baselines/test-as-never.json
#	src/__tests__/baselines/test-source-reads.json
#	src/__tests__/baselines/version-stamp-comments.json
#	src/app/auth/login/page.tsx
2026-11-12 14:47:38 +01:00
Marc-André Bombeck 5ac998e4f0 Merge remote-tracking branch 'origin/main' into release/v1.47.5
# Conflicts:
#	src/__tests__/baselines/source-file-lines.json
#	src/__tests__/baselines/source-function-lines.json
#	src/__tests__/baselines/test-as-never.json
#	src/__tests__/baselines/version-stamp-comments.json
#	src/__tests__/sharing-surface-guard.test.ts
2026-11-12 14:25:05 +01:00