Dehydrated devices: automatic claim at start / 4S unlock, rotation schedule, full state set (§10.4.7) #149

New issue

Closed

opened 2026-08-27 19:21:15 +02:00 by thecrealm · 0 comments

thecrealm commented

2026-08-27 19:21:15 +02:00

Owner

Review finding 2026-08-27 (B8). Claim and rotation run only when the consumer calls manageDehydratedDevice; neither session start nor unlockSecretStorage triggers them (SessionCrypto.kt:899-903 only loads the key); the "claim before the first sync request" ordering is unimplemented; non-404 GET/PUT failures throw instead of Failed(cause); the state enum lacks Disabled/Claiming/Failed(cause), Active carries no device id, ClaimFailed no cause; no rotation test and no engine test of the M_UNRECOGNIZED → Unsupported path.

Acceptance (§10.4.7-4/5/7, D73): each MUST above implemented and tested, or the spec amended where the decider prefers opt-in (record as D-entry).

Review finding 2026-08-27 (B8). Claim and rotation run only when the consumer calls `manageDehydratedDevice`; neither session start nor `unlockSecretStorage` triggers them (`SessionCrypto.kt:899-903` only loads the key); the "claim before the first sync request" ordering is unimplemented; non-404 GET/PUT failures throw instead of `Failed(cause)`; the state enum lacks Disabled/Claiming/Failed(cause), `Active` carries no device id, `ClaimFailed` no cause; no rotation test and no engine test of the M_UNRECOGNIZED → Unsupported path. Acceptance (§10.4.7-4/5/7, D73): each MUST above implemented and tested, or the spec amended where the decider prefers opt-in (record as D-entry).

thecrealm added the

labels

2026-08-27 19:22:00 +02:00

thecrealm added

now

and removed

labels

2026-09-01 17:28:47 +02:00

thecrealm referenced this issue from a commit

2026-09-01 17:59:50 +02:00

Dehydrated devices run by themselves: claim at start ahead of the first sync request, on 4S unlock, after a claim and on rotation; sealed standing with typed causes; DehydrationConfig (§10.4.7, D95, closes #149)

thecrealm closed this issue