fix(auth): answer the setup state for the record the payload describes

The account payload resolved the setup state for the actor while its module
map, its cycle flag and every count the checklist reads beside it answer for
the active record. A guardian looking at a child's dashboard therefore got the
child's rows ordered by their own answers, and the child's reading count
tested against their own flow state. The two halves of that component have to
agree about whose record they describe, so the field is record-scoped now,
like the module map next to it.

Under a grant narrowed to one section the answers come back empty, for the
reason the module map is masked: they name the domains the record tracks, and
a grant that opens readings does not open that. The shape of the flow still
comes through.

The three write routes stay actor-only and say why: a delegable declaration is
a reviewed entry in the sharing surface guard, and a read that is wider than
its write is the honest shape while that entry is still to come.
This commit is contained in:
Marc-André Bombeck committed 2026-09-10 12:06:02 +02:00
1 parent b10a3ef22e
commit f90307fd22
7 files changed
+162 -31

No files matched your search

+6 -5
View File
@@ -83,11 +83,12 @@ export interface AuthUser {
*/
onboardingTourProgress: AuthTourProgress | null;
/**
* v1.39 (C1) — the needs-based setup flow's state for this record: the nine
* ordered steps with their `pending | done | skipped` status, the answers as
* given, the flow's own completion stamp (distinct from
* `onboardingCompletedAt` above, which stays the first-run redirect's gate)
* and the one task the flow offered.
* v1.39 (C1) — the needs-based setup flow's state for the record the payload
* describes — the active one under a switch: the nine ordered steps with
* their `pending | done | skipped` status, the answers as given, the flow's
* own completion stamp (distinct from `onboardingCompletedAt` above, which
* stays the first-run redirect's gate) and the one task the flow offered.
* Under a scoped grant the answers come back empty.
*
* Optional in the type so a stale /me payload — an older server image, or a
* test fixture written before the field existed — coerces to "no flow" in