Marc-André Bombeck c016ec8aec fix(recovery): claim no Oura permission the server cannot prove ...

The empty recovery note told every connected Oura account without a
recorded permission gap that its permission covers resilience. The
server cannot know that: the scope note is cleared on each reconnect
and written only by a sync that reached Oura, and a missing health
block says nothing either way. The note now asks for a reconnect only
when the gap is recorded and otherwise says only that no level has
arrived, pointing at the Oura card. It also waits for the connection
status instead of showing the general note first and swapping it.

Refs #1204

2026-10-19 18:31:45 +02:00

..

de.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

en.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

es.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

fr.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

it.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

ko.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00

pl.json

fix(recovery): claim no Oura permission the server cannot prove

2026-10-19 18:31:45 +02:00