docs(docs): V1-2.5 administration, MFA, catalogue documented

CLAUDE.md overview and folder map, IDENTITY §1 and §4, BROWSER_TESTS shell specs, V1-2 contract §16.6 state and §5.7.3-§5.7.4 pointers, design README owning steps with two deviations.
This commit is contained in:
bchanot committed 2026-11-02 17:48:50 +01:00
1 parent c12702bac1
commit 3d2b5a5f1c
5 files changed
+97 -32

No files matched your search

+20 -7
View File
@@ -57,6 +57,10 @@ business decisions ratified 2026-10-25, BDR-073; architecture and N1-N9 validate
the animal screens and the relations (`/app/animals`, contract §11.8; D11: drawer only, no tab bar)).
V1-2 contract (decisions O1-O23 ratified 2026-10-28, BDR-082; contract under the owner's final review, no implementation before
the owner's go): `docs/development/V1-2_ANATOMICAL_SHEETS.md`, branch `feature/v1-2-anatomical-sheets`.
V1-2.5 (2026-11-02, sandbox only, not on DEV) added the administration space `/app/admin` (rights, species, official sheets,
behind a step-up to `aal2`), TOTP factors in Mon compte, Sécurité with the step-up inside the actions GoTrue refuses below
`aal2`, the catalogue `/app/anatomy` for readers, and M7 `sheet_admin_reads` (admin read RPCs, deprecated fingerprint)
(`docs/development/IDENTITY.md` §4).
---
@@ -158,7 +162,7 @@ pnpm e2e:avatar # = pnpm db:sandbox avatar-e2e: the worker container and
pnpm test:run # vitest run — all tests, single pass, CI-safe
pnpm test # vitest watch — dev loop
pnpm e2e:ui # Playwright Chromium, no backend: Dialog test page + local tool dialogs, desktop + 375 px, axe (in check:all when the pinned Chromium is installed)
pnpm e2e:shell # Playwright Chromium against `pnpm db:sandbox` (must be up): sign-in, dashboard, photo confirmation, phone drawer, client, animal and relation journeys; never DEV (`pnpm db:sandbox e2e-shell <spec> [--grep]` for one file)
pnpm e2e:shell # Playwright Chromium against `pnpm db:sandbox` (must be up): sign-in, dashboard, photo confirmation, phone drawer, client, animal and relation journeys, administration (A0, A1, S1, MFA step-up, access per right) and catalogue (P1); never DEV (`pnpm db:sandbox e2e-shell <spec> [--grep]` for one file)
```
Browser suites (`apps/app/e2e`, `docs/development/BROWSER_TESTS.md`): Chromium only until V1-5,
@@ -201,14 +205,20 @@ faunosteo/
│ │ ├─ routes/app/{Dashboard,Account}Route.tsx ← behind RequireAuth, inside AppLayout
│ │ ├─ routes/app/clients/{ClientsList,ClientCreate,ClientDetail,ClientEdit}Route.tsx ← V1-1.5, behind RequireWorkspace
│ │ ├─ routes/app/animals/{AnimalsList,AnimalCreate,AnimalDetail,AnimalEdit}Route.tsx ← V1-1.6, same RequireWorkspace; the first client arrives in the navigation state, never the URL
│ │ ├─ guards/{RequireAuth,RedirectIfSignedIn,SessionLoading,RequireWorkspace}.tsx ← RequireWorkspace: personal workspace ready, remount per workspace, species labels (SpeciesProvider)
│ │ ├─ routes/app/anatomy/{Catalog,Sheet}Route.tsx ← V1-2.5 catalogue (`/app/anatomy`, `/:sheetId`, `/:sheetId/versions/:number`), behind RequireCatalog
│ │ ├─ routes/app/admin/{AdminHome,AdminSheets,AdminSheetCreate,AdminSheet,AdminSpecies,AdminAccess}Route.tsx ← V1-2.5 administration, behind RequireAdmin
│ │ ├─ guards/{RequireAuth,RedirectIfSignedIn,SessionLoading,RequireWorkspace,RequireCatalog,RequireAdmin}.tsx ← RequireWorkspace: personal workspace ready, remount per workspace, species labels (SpeciesProvider); RequireCatalog decides nothing (the server's refusal does); RequireAdmin: step-up to aal2 before any admin request
│ │ ├─ useLeaveGuard.ts + usePageHeading.ts ← unsaved changes (beforeunload + in-app links via AppLayout); heading focus on page open
│ │ └─ providers/{ConfigProvider,AuthProvider}.tsx ← AppConfig context; session + locale sync start
│ ├─ auth/{validation,redirects,useAuthFailureMessage}.ts ← Zod schemas (i18n keys), safe next path, failure phrasing
│ ├─ auth/{navigationHint,stepUp,useStepUp,useMfaFailureMessage}.ts ← V1-2.5: nav entries from own grants + roles (a hint, never a gate), verified factors for a step-up, in-action step-up on aal2_required, MFA failure phrasing
│ ├─ admin/{filters,labels,permissions,useAdminQuery,validation}.ts ← V1-2.5 admin screens: sheet list filters, status labels, capability checks for display, page-local query, form schemas
│ ├─ catalogue/{catalogue,failure,framing,preview,useCardDetails,useCatalogue,useFraming,useSheetVersion,versionText}.ts ← V1-2.5 catalogue: reads, closed failure kinds, canvas zoom and pan, PreviewSheet load path (hash, fingerprint, caps checked by the core)
│ ├─ account/{validation,useProfileForm}.ts ← account section schemas + one-save form hook
│ ├─ config/env.ts ← runtime config resolution
│ ├─ sheets/{provider,useSheet}.ts ← raw bundled payload; useSheet loads it into the core (ready / none / core_unavailable / invalid_sheet + retry), useSheetAvailability without the core
│ ├─ core/{runtime,sheetOps,reportOps}.ts ← the page's CoreRuntime (Vite asset URLs, lazy), typed sheet-bound and free core operations
│ ├─ core/sheetDocumentOps.ts ← V1-2.5: `sheet.empty`, a new sheet's empty document from the core
│ ├─ services/
│ │ ├─ sheetIndex.ts ← SheetIndex class: reads the core's SheetIndexData (ids, never labels) + `ops`
│ │ └─ localeSync.ts ← profiles.locale ↔ localeStore (account wins on sign-in)
@@ -236,12 +246,14 @@ faunosteo/
│ │ ├─ report/{ReportHeader,PractitionerForm,AnimalForm,EditInfosDialog,DisclaimerDialog,
│ │ │ ConclusionPanel,NextAppointmentPicker,CoreUnavailable,HeldSessionPanel,ReplaceSessionDialog}.tsx
│ │ ├─ brand/{Brand,AppHeader,Footer,LanguageSwitcher,HomeSpaceLink}.tsx
│ │ ├─ auth/{AuthLayout,OAuthButtons,PasswordField,UnavailableNotice,AuthLink}.tsx
│ │ ├─ auth/{AuthLayout,OAuthButtons,PasswordField,UnavailableNotice,AuthLink,TotpCodeForm,InlineStepUp}.tsx ← TotpCodeForm: factor choice + code (V1-2.5); InlineStepUp: the challenge in place of an action GoTrue refused below aal2
│ │ ├─ clients/{ClientForm,ClientAnimals,ArchiveClientDialog,ClientNotFound}.tsx
│ │ ├─ animals/{AnimalForm,ArchiveAnimalDialog,AnimalNotFound}.tsx
│ │ ├─ relations/{AnimalRelations,RelationPanel,RelationActionDialog,RelationDialogs,RecordPicker,Pickers}.tsx ← in-page link panel, end / dates / void confirmations
│ │ ├─ shell/{AppLayout,SidebarNav,MobileDrawer,UserBadge,SignOutButton}.tsx
│ │ └─ account/{SectionCard,SaveRow,AvatarSection,PersonalInfoForm,ProfessionalInfoForm,PreferencesForm,SecurityPanel,RoleBadges}.tsx
│ │ ├─ admin/{ActivateSpeciesDialog,GrantList,GrantPanel,RevokeGrantDialog,SheetBadges,SpeciesDialog,WorkingCopyAction}.tsx ← V1-2.5 rights, species and sheet pieces
│ │ ├─ catalogue/{CatalogueCanvas,CatalogueCard,CatalogueFailureNotice,SheetAside,VersionLine,ZonePanel}.tsx ← V1-2.5 catalogue pieces (boards 01 to 03)
│ │ ├─ shell/{AppLayout,SidebarNav,MobileDrawer,UserBadge,SignOutButton,AccessDenied}.tsx ← AccessDenied: « Accès non autorisé » on the server's refusal (V1-2.5)
│ │ └─ account/{SectionCard,SaveRow,AvatarSection,PersonalInfoForm,ProfessionalInfoForm,PreferencesForm,SecurityPanel,RoleBadges,MfaFactors,EnrolTotp}.tsx ← MfaFactors + EnrolTotp: TOTP factors in Sécurité (V1-2.5; the secret lives in component state only)
│ ├─ account/avatarTransport.ts ← magic-byte sniff (never SVG), createImageBitmap → canvas ≤ 1024 px → JPEG transport blob
│ ├─ pdf/ ← the app side of the PDF (export on the core's session since R4.6; the import runs in the worker, `core/worker`)
│ │ ├─ export.ts + labels.ts ← exportReportToPdf (snapshot + branding + labels → ExportSession, rasters one by one, Blob of the parts, abort on unmount), defaultPdfLabels (25 keys); the tests' in-process import lives in tests/helpers/pdfImport.ts (the module's reader)
@@ -252,7 +264,7 @@ faunosteo/
├─ tests/
│ ├─ setup.ts
│ └─ unit/*.test.ts
├─ e2e/ ← Playwright (V1-1.3): playwright.{ui,shell}.config.ts, support/{browser,sandbox,shell,records}.ts, ui/*.spec.ts, shell/*.spec.ts, harness/dialog.{html,tsx} (dev server only, never built)
├─ e2e/ ← Playwright (V1-1.3): playwright.{ui,shell}.config.ts, support/{browser,sandbox,shell,records,admin,catalogue}.ts, ui/*.spec.ts, shell/*.spec.ts (V1-2.5: admin, catalogue), harness/dialog.{html,tsx} (dev server only, never built)
├─ docker/
│ ├─ entrypoint.sh ← injects env.js at container start
│ └─ nginx.conf ← SPA fallback + PORT envsubst
@@ -270,11 +282,12 @@ faunosteo/
├─ packages/supabase/ ← @faunosteo/supabase
│ ├─ src/{index,client,database.types,anatomical-sheets,assets}.ts ← typed client, generated types, publish gate, avatar flow (closed AssetFailure kinds)
│ ├─ src/{records,workspaces,clients,species,animals,relations,field-limits}.ts ← V1-1 record access (closed RecordFailure kinds, keyset pages), D-R7 bounds
│ ├─ src/{sheets,mfa}.ts ← V1-2 sheet workflow, admin and catalogue reads (closed SheetFailure kinds); V1-2.5 TOTP factors and assurance level (closed MfaFailure kinds)
│ ├─ tests/e2e/avatar-flow.e2e.ts + vitest.e2e.config.ts ← real-stack end-to-end (`pnpm e2e:avatar` = `pnpm db:sandbox avatar-e2e`), fails on any target but the sandbox gateway and database
│ └─ tests/{client,anatomical-sheets}.test.ts, tests/db/ ← PGlite harness, shim, pgTAP runner, schema↔types test
├─ supabase/
│ ├─ config.toml, seed.sql ← CLI config (public schema only), local dev accounts
│ ├─ migrations/*.sql ← forward-only; foundation, profiles, platform_roles, anatomical_sheets, storage, sheet_document_schema_v2, profiles_professional, files_foundation (assets, buckets, avatar policies, purge queue, RPCs), workspaces (V1-1.1: personal workspace per account, access helpers), clients (V1-1.2: client RPCs and search, write budget per workspace), animals_relations (V1-1.4: species rows, animals, relations with history and voiding, their RPCs and reads), sheet_access_hardening + sheet_review_workflow (V1-2.1 M4, M5), sheet_verification_jobs (V1-2.3 M6: the worker's verdict RPCs, service role only)
│ ├─ migrations/*.sql ← forward-only; foundation, profiles, platform_roles, anatomical_sheets, storage, sheet_document_schema_v2, profiles_professional, files_foundation (assets, buckets, avatar policies, purge queue, RPCs), workspaces (V1-1.1: personal workspace per account, access helpers), clients (V1-1.2: client RPCs and search, write budget per workspace), animals_relations (V1-1.4: species rows, animals, relations with history and voiding, their RPCs and reads), sheet_access_hardening + sheet_review_workflow (V1-2.1 M4, M5), sheet_verification_jobs (V1-2.3 M6: the worker's verdict RPCs, service role only), sheet_admin_reads (V1-2.5 M7: admin reads, deprecated fingerprint)
│ ├─ seed/anatomical-sheets/equine/
│ │ ├─ legacy-sources/ ← the historical Horse.svg, Horse_head.svg, pathologies.json, vertebrae.ts (importer input, never edited)
│ │ ├─ legacy-import/ ← GENERATED baseline: document, id map, IMPORT-REPORT, SVG copies (no SQL)
+4 -2
View File
@@ -90,7 +90,9 @@ still open). Approved as they stand at `74aa8f6`, no file regenerated: board `12
`object_conflict` message and « à arbitrer » marks that the approval settled; REVUE.md and the V1-2 contract
§17.9 hold the ratified wordings.
Owning steps of what the boards show (nothing built yet): `01`–`03`, `10`, `11` and the complementary page
with V1-2.5 (catalogue, Administration entry, access page); `04`, `05` and board `06` A with V1-2.6 (editor,
Owning steps of what the boards show: `01`–`03`, `10`, `11` and the complementary page with V1-2.5
(catalogue, Administration entry, access page), built on 2026-11-02 on the sandbox, with two deviations:
no « Sélection : … » tag over the canvas on desktop (`02`), and « Références » shown as a plain card on a
phone instead of a folded section (`03`); `04`, `05` and board `06` A with V1-2.6 (editor,
narrow-screen read-only mode, draft check); `06` B–D, `07`–`09` with V1-2.7 (verification states, review,
publication); the labels of `12` with the step that shows each of them.
+14 -2
View File
@@ -10,7 +10,7 @@ engines are installed. The suites live in `apps/app/e2e`.
| Command | Backend | Dev server | Content |
|---|---|---|---|
| `pnpm e2e:ui` | none | Vite on `127.0.0.1:5191` | `e2e/ui/dialog.spec.ts`: the D13 contract of the shared Dialog on a test page; `e2e/ui/local-tool.spec.ts`: the disclaimer, edit and replace dialogs on the real local-tool routes |
| `pnpm e2e:shell` | the isolated stack of `pnpm db:sandbox` | Vite on `127.0.0.1:5192` | `e2e/shell/shell.spec.ts`: sign-in, dashboard, the account photo confirmation, the phone drawer; `e2e/shell/clients.spec.ts`: the client journeys (V1-1.5); `e2e/shell/animals.spec.ts`: the animal and relation journeys (V1-1.6, contract §11.8); `e2e/shell/responsive.spec.ts`: no sideways scroll on nine shell pages, the archive confirmations and the drawer at 320, 360, 375, 390 and 430 px (phone project) and 1280 px, long values, the dashboard e-mail shown whole (RESP-01) |
| `pnpm e2e:shell` | the isolated stack of `pnpm db:sandbox` | Vite on `127.0.0.1:5192` | `e2e/shell/shell.spec.ts`: sign-in, dashboard, the account photo confirmation, the phone drawer; `e2e/shell/clients.spec.ts`: the client journeys (V1-1.5); `e2e/shell/animals.spec.ts`: the animal and relation journeys (V1-1.6, contract §11.8); `e2e/shell/responsive.spec.ts`: no sideways scroll on nine shell pages, the archive confirmations and the drawer at 320, 360, 375, 390 and 430 px (phone project) and 1280 px, long values, the dashboard e-mail shown whole (RESP-01); `e2e/shell/admin.spec.ts` (V1-2.5): A0 the owner's bootstrap (two TOTP factors from Sécurité, the step-up at `/app/admin` and inside a factor action, no second factor from `aal1`, refresh keeping `aal1` and `aal2`, rights granted and revoked with their reason), A1 a sheet created by an editor on a new inactive species, S1 a species created inactive then activated by the owner, access per right, axe and no sideways scroll on every admin page; `e2e/shell/catalogue.spec.ts` (V1-2.5): P1 a reader searches, opens a sheet, picks a zone, reads a retired version, drafts and archived sheets never listed, the same refusal for an existing and an unknown sheet without access, 320, 375 and 430 px with the whole drawing in the box at opening |
Each suite runs on two Chromium projects: `chromium-desktop` (1280 × 800) and
`chromium-375` (375 × 667, mobile viewport, touch). A test tagged `@phone`
@@ -33,7 +33,19 @@ fictitious display name, the profile locale of the test), and seeds the clean
avatar the worker would have produced (the `assets` row as postgres, the
object with the service key). Rows around the subject of a test (clients,
animals, relations) are written as postgres by `e2e/support/records.ts`,
every value quoted as an SQL literal. `pnpm db:sandbox down` removes all of it.
every value quoted as an SQL literal. The V1-2.5 suites set up what lies
before the page the same way: platform roles, catalogue grants and other
accounts' verified TOTP factors by `e2e/support/admin.ts` (roles through the
operator path, grants as postgres, a factor enrolled and verified on the real
GoTrue, its secret kept in the test's memory); official sheets by
`e2e/support/catalogue.ts` as SQL fixtures (published, retired, archived and
draft-only versions carrying the curated equine draft under names of their
own, the drawing in the private bucket under its content key), each published
or retired version's fingerprint computed in Node by the shipped core module
(`packages/core-wasm/pkg`, `preview.state`), the one the page runs. A0, A1 and
S1 are desktop journeys, skipped on the phone project (6 skips by design); the
admin screens at 375 px have their own test.
`pnpm db:sandbox down` removes all of it.
`pnpm db:sandbox e2e-shell <args>` passes its arguments to Playwright: one
spec file, `--project`, `--grep`. Every shell suite removes its routes after
each test without waiting for them (`dropLateReplays`), so an answer still in
+42 -18
View File
@@ -18,13 +18,23 @@ by side until the plan's Step 14 decides what goes behind authentication.
| `/reset-password` | none; needs the recovery session | new password ×2; "invalid or expired link" otherwise |
| `/auth/callback` | none | landing of OAuth redirects and confirmation links; waits for the session then goes to `/app` (or `?next=`) |
| `/app` | `RequireAuth` | dashboard: greeting, profile completeness card, local tool card, account card |
| `/app/account` | `RequireAuth` | Mon compte: profile photo (Step 8, `STORAGE.md` §4), personal, professional, preferences (language, timezone), security (password, MFA note, sign out) |
| `/app/account` | `RequireAuth` | Mon compte: profile photo (Step 8, `STORAGE.md` §4), personal, professional, preferences (language, timezone), security (password, TOTP factors since V1-2.5 (§4), sign out) |
| `/app/anatomy`, `/:sheetId`, `/:sheetId/versions/:number` | `RequireAuth`, `RequireCatalog` (V1-2.5) | catalogue of official sheets, a sheet's current version, an earlier version; « Accès non autorisé » on the server's refusal, the same for an unknown sheet |
| `/app/admin`, `/sheets`, `/sheets/new`, `/sheets/:sheetId`, `/species`, `/access` | `RequireAuth`, `RequireAdmin` (V1-2.5, step-up to `aal2`) | administration home, official sheets, species, rights (owner); each page shows what the caller's capabilities allow |
`RequireAuth` waits for the client to read the persisted session, then sends
a visitor to `/login?next=<path>`; `next` is honoured only when it is a
same-origin path (`safeNextPath`). `/app/*` under the guard renders inside
`AppLayout` (desktop sidebar, light top bar, mobile drawer).
`RequireCatalog` decides nothing: the pages ask the server and show
« Accès non autorisé » (`AccessDenied`) when it refuses. `RequireAdmin`
renders the admin pages only on an `aal2` session, so no admin data is
requested before the step-up (§4). The « Fiches anatomiques » and
« Administration » entries of the sidebar and drawer follow a hint built from
the caller's own grant rows and roles (`auth/navigationHint.ts`): a hidden
entry protects nothing, every RPC checks the capability and `aal2` itself.
A deployment without Supabase (`APP_SUPABASE_URL` empty) shows an
"unavailable" notice on the auth screens; `/app` redirects to `/login`; the
Home header shows no entry to the space. With Supabase configured, the Home
@@ -44,7 +54,8 @@ header shows "Se connecter" or "Mon espace".
(`display_name, first_name, last_name, phone, locale, timezone,
practice_name, professional_title, siret`). `active`,
`phone_verified_at` and roles are server-only.
- Platform roles are read-only badges (`shell.role.*`); no admin screen yet.
- Platform roles are read-only badges (`shell.role.*`). The administration
space (V1-2.5) manages catalogue rights and species, never platform roles.
- GoTrue errors never reach the screen: `classifyAuthError` folds codes into a
closed `AuthFailureKind`, phrased by `auth.failure.*`.
@@ -79,25 +90,38 @@ that made the request (the code verifier lives in its localStorage). Opened
elsewhere, the email is still confirmed server-side but no session opens; the
callback page says so and the user signs in normally.
## 4. MFA: what the foundations have, what is missing
## 4. MFA (TOTP)
Architecture §2 wants TOTP mandatory for `owner/admin/moderator/support`,
enforced by an RLS helper `has_mfa()` on admin tables. Today:
Architecture §2 wants TOTP mandatory for platform roles; V1-2 decision
BDR-083 requires `aal2` for every platform role change and every catalogue
right (`V1-2_ANATOMICAL_SHEETS.md` §5.6, §5.7). State since V1-2.5:
- server: TOTP enrolment/verification enabled (this step); nothing enforces it;
- SQL: no `private.has_mfa()` helper (would read `auth.jwt() ->> 'aal' = 'aal2'`);
the role helpers `private.is_platform_*` ignore the assurance level;
- app: no enrolment UI (QR + code), no `aal2` step-up on sign-in;
- there is no admin table or screen yet to protect.
- server: TOTP enrolment and verification on (`[auth.mfa.totp]`). Since M4
(`20261028100000_sheet_access_hardening.sql`) `private.has_mfa()` reads the
token's `aal` claim, and `private.has_aal2_session()` also requires the
token's session to still be `aal2` in `auth.sessions`; the role and rights
RPCs use the second, the catalogue policies and RPCs the first. The
`is_platform_*` helpers still ignore the level: the RPCs that need it call
the helpers above.
- Mon compte, Sécurité (`components/account/{MfaFactors,EnrolTotp}.tsx`):
the factor list (verified and unverified), adding a factor (name, QR code,
secret for manual entry shown once and kept in the component's state only,
then a code), removal after a confirmation. An unverified factor the
enrolment made is removed on cancel or unmount (a dormant factor is a path,
V1-2 contract §5.7.3). `packages/supabase/src/mfa.ts` folds GoTrue's answers into the
closed `MfaFailure` kinds (`mfa.failure.*`).
- Step-up at `/app/admin` (`RequireAdmin`): an `aal1` session is asked for a
code from one of its verified factors; without one, it is sent to Sécurité.
- Step-up inside an action (`auth/useStepUp.ts`, `components/auth/InlineStepUp`):
when GoTrue refuses below `aal2` (`aal2_required`: a second factor, the
removal of a verified one, a password change), the challenge opens in place
and the action is sent to GoTrue again once it succeeds, never bypassed.
- Password reset (`/reset-password`): an account with a verified factor
steps up before the new password is sent, the recovery session included
(§4.1).
V1-2 decision (BDR-083): `aal2` is required for every platform role change,
see `V1-2_ANATOMICAL_SHEETS.md` §5.7 (rule, bootstrap, recovery).
The Security section shows a note instead. To close the gap (a later step):
migration adding `private.has_mfa()` and folding it into `is_platform_*` (or
into the policies of the first admin table) with pgTAP allowed/denied cases;
enrolment + challenge screens in Mon compte; step-up at sign-in for accounts
holding a platform role.
Still open: the recovery runbook for a lost factor (V1-2 contract §5.7.7) is
rehearsed at V1-2.9.
### 4.1 GoTrue v2.197.0 behaviour, measured on the sandbox (V1-2.5)
+17 -3
View File
@@ -605,7 +605,8 @@ management waits, and the first factor can always be enrolled at `aal1`.
#### 5.7.3 Additional, removed and replaced factors
Native behaviour of GoTrue v2.197.0 (source read, V1-2.5 proves it):
Native behaviour of GoTrue v2.197.0 (source read, V1-2.5 proves it; measured
on the sandbox: `IDENTITY.md` §4.1, V1-2.5):
- a second factor: `EnrollFactor` needs `aal2` once a verified factor exists
(403 `insufficient_aal`). A stolen password therefore cannot add a factor;
@@ -629,7 +630,8 @@ Native behaviour of GoTrue v2.197.0 (source read, V1-2.5 proves it):
owner choice under O4, not part of this contract (§5.7.9).
If the sandbox shows `aal1` can enrol a second factor or remove a verified
one, V1-2.5 stops for an owner decision (as §5.6 already says).
one, V1-2.5 stops for an owner decision (as §5.6 already says). It did not
fire (`IDENTITY.md` §4.1).
#### 5.7.4 Password change and reset
@@ -641,7 +643,9 @@ accepted first-factor case, harmless while no role or capability is held, and
the reason the owner role is assigned after enrolment (§5.7.1) and a
capability only to an account with a verified factor (§5.2). Email change and
identity linking stay as configured (`enable_manual_linking = false`); V1-2.5
adds a test that none of them raises a session to `aal2`.
adds a test that none of them raises a session to `aal2` (measured on the
sandbox: `IDENTITY.md` §4.1, V1-2.5; with a verified factor, a password change
or reset is itself refused at `aal1`, so the recovery screens step up first).
#### 5.7.5 Operator path
@@ -2277,6 +2281,16 @@ V1-2.7 on.
and readable by id; every other actor refused in the UI and in SQL.
- Rollback: branch revert.
- Checkpoint: gates only (owner at V1-2.6).
- State 2026-11-02: built and tested on the sandbox, slices A to J of the step
plan: A GoTrue MFA behaviour measured (`IDENTITY.md` §4.1), B M7
`sheet_admin_reads` (with BDR-098), C core op `sheet.empty`, D the
`packages/supabase` accessors (MFA, species, rights, admin and catalogue
reads), E navigation, `RequireCatalog`, `RequireAdmin` and « Accès non
autorisé », F TOTP factors in Mon compte with the step-up, G administration
page, species and rights, H sheet list, creation, overview and working copy,
I catalogue list, sheet and version pages, J the `e2e:shell` journeys.
pgTAP 1941, unit 864, `e2e:shell` 108 passed (6 skipped by design). DEV
untouched; the checkpoint gates are pending.
### 16.7 V1-2.6 Editor level 1