From f93412c8e92f18c470ffc3b46df21dc713e9a908 Mon Sep 17 00:00:00 2001 From: bchanot Date: Tue, 27 Oct 2026 19:44:36 +0100 Subject: [PATCH] docs(supabase): close RESP-01, AVATAR-01 class A, AVATAR-02 ticket --- .claude/memory/journal.md | 1 + .claude/tasks/TODO.md | 10 +++++++++- docs/development/SUPABASE.md | 10 ++++++++-- 3 files changed, 18 insertions(+), 3 deletions(-) diff --git a/.claude/memory/journal.md b/.claude/memory/journal.md index ddc43933..4f818e74 100644 --- a/.claude/memory/journal.md +++ b/.claude/memory/journal.md @@ -455,3 +455,4 @@ R5.4: `draft/{labels,changelog,review_report,drawing,overlay,app_review,svg_comp ## 2026-10-27 (V1-1 post-acceptance: RESP-01 fix, AVATAR-01 diagnosis) - Owner recette: 19 lines FR detailed, EN global + 4 at 375 px, isolation ok. RESP-01 global scroll = owner browser zoom (owner DEV measures). Real defect found on sandbox: long account e-mail widens dashboard cards (implicit grid track). Fix DashboardRoute + `e2e/shell/responsive.spec.ts` (fails on old code). LRN-094. - AVATAR-01 = class A: DEV worker stopped, row `uploaded` waits, message by design (STORAGE §4.4). Sandbox repro with temp gateway + worker on sandbox net: clean in 1.1 s. Side finding (pre-V1-1): full reload doesn't resume the waiting row, new save supersedes it. DEV read-only only. +- Owner closure 2026-10-27: RESP-01 counter-check 6 PASS → closed; AVATAR-01 class A non-blocking, DEV worker stays off, Alice's waiting upload kept; AVATAR-02 ticket in TODO (no Gitea CLI). Pre-merge checkpoint, no merge. diff --git a/.claude/tasks/TODO.md b/.claude/tasks/TODO.md index eeae753c..e85307ca 100644 --- a/.claude/tasks/TODO.md +++ b/.claude/tasks/TODO.md @@ -514,7 +514,7 @@ Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheet - [ ] `pnpm db:test` on DEV: run 1 exit 1 (919 planned, 915 run, 914 passed: 007 storage collision, 010 13 due purge entries; 012-014 passed; DEV unchanged, pgtap absent after) - [x] 007 + 010 made independent of the base's data (007: seed key only, confirmation cleared in-tx, 20 assertions; 010: section 0 leases the base's queued work in-tx, leftovers by fixture prefix, 141); sandbox A clean + B DEV-like and latent conditions: old FAIL reproduced, new PASS 921; 11 mutations detected on A and B (same set as the old suites); LRN-093 - [x] rerun on DEV on the owner's go (2026-10-27): exit 0, 14 suites, 921 assertions, 83 integrity lines identical before/after, pgtap absent after - - [ ] owner: browser acceptance on DEV (19 lines × FR/EN × computer/375 px) + - [x] owner: browser acceptance on DEV (2026-10-27): 19 lines FR detailed, EN validated as a whole + 4 lines at 375 px recorded, isolation A/B/owner; RESP-01 closed (fixed a70166e, owner counter-check 6 PASS); AVATAR-01 class A, non-blocking (DEV worker stays stopped, Alice's `uploaded` row kept) - [ ] post-acceptance fixes (owner brief « corrections post-recette RESP-01 et diagnostic AVATAR-01»; no DEV write, no worker on DEV, no migration, no merge) - [x] RESP-01: owner's global overflow = browser zoom (owner's manual DEV measures, no zoom: /app and /app/clients 375 + 320 no overflow); real defect shown on the sandbox: dashboard grid has no explicit column below md, its implicit `auto` track takes the cards' min-content, the account card's e-mail never truncates → overflow from ~31 chars at 320 px, 44 chars overflow 320-430 px. Fix: explicit one-column track, e-mail wraps instead of being cut - [x] RESP-01 tests: e2e:shell responsive sweep 320/360/375/390/430 + desktop, FR/EN, long content (dashboard, client list/new/edit/page, animal list/new/edit/page, archive dialogs, drawer), e-mail fully visible @@ -522,6 +522,14 @@ Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheet - [x] gates: check:all, fresh verifier, security audit; docs (recette registry, SUPABASE.md acceptance note), registries; commit + push. Done: check:all exit 0 (cargo 1548 passed / 3 ignored, vitest 566 + 127 + 60, e2e:ui 26), e2e:shell sandbox 86 passed, responsive 4/4 after the fixture domain fix; verifier CONFORME 8/8; security PASS (2 LOW: fixture domain applied, pre-existing uuid interpolation noted); LRN-094. Next: owner counter-check of the dashboard at 375 px on DEV - [ ] after the owner's results: fixes if any (branch, gates, fresh verifier + security), CHANGELOG Unreleased, TODO closure, final report; merge only on the owner's explicit go - Owner cleanup (optional): rehearsal leftovers `/tmp/claude-1000/-home-bchanot-Documents-faunosteo/8d6890e5-060c-431d-b99f-545f2e315333/scratchpad/rehearsal/` (3 small files, fictitious data); the backup folder `~/faunosteo-backups` is kept until the acceptance is validated +- [ ] AVATAR-02 (ticket, out of V1-1; not created in Gitea: no Gitea CLI or token on this machine, `gh` is GitHub only) « Reprendre le suivi d'une photo en attente après rechargement de la page » + - Context: avatar processing is asynchronous (STORAGE.md §4): begin → quarantine upload → confirm (`uploaded`) → worker → `clean` / `rejected`; the page polls its own row 1 s, 30 s at most + - Repro (isolated stack only): upload a photo, leave the row `uploaded` (worker stopped), full page reload before processing + - Observed: AvatarSection mounts before the auth store has read the rows (`avatar` null) → phase idle, old photo shown, « Modifier » / « Supprimer » enabled, no polling; a new save supersedes the waiting row (`deleted`). An in-app return resumes. Pre-V1-1 (Step 8 / R1 mount logic) + - Expected: once the rows arrive, find the active waiting asset, resume its polling, show a coherent state; never create a second upload nor replace the first by the resume itself + - Cases: worker stopped (long-processing message, honest wording), processing finished during the reload (`clean` shown, no stale message), `rejected` (message per code), `deleted` / superseded, read errors per the closed AssetFailure kinds; own rows only (RLS unchanged) + - Tests: unit (store arrives after mount), e2e:shell on the sandbox with the worker stopped and running (gateway + worker on the sandbox network, as the AVATAR-01 repro); never DEV + - Limits: frontend only; no Storage contract, RPC, RLS, worker or migration change without owner approval - [ ] Code debt (not P0, no change on the doc branch): `docker/nginx.conf` still has `location /species/` (public/species deleted at Step 5); remove with its own `chore/` or `bugfix/` branch ## Release readiness track (owner 2026-10-25, distinct from the functional roadmap; nothing here authorises a release or exposure) diff --git a/docs/development/SUPABASE.md b/docs/development/SUPABASE.md index c0e8a23f..28424e29 100644 --- a/docs/development/SUPABASE.md +++ b/docs/development/SUPABASE.md @@ -722,11 +722,17 @@ checked. Two anomalies: conform by them). A real defect found apart, on the isolated stack: an account e-mail longer than the card (from about 31 characters at 320 px) widened the dashboard cards past a phone screen (implicit grid track); fixed, covered by - `e2e/shell/responsive.spec.ts`; the owner's check of the fix is pending. + `e2e/shell/responsive.spec.ts`. Owner counter-check on the fixed code: 375 px + FR and EN, card readability, client list at 375 px, dashboard at 320 px, + console measure at 320 px (0 px overflow): six PASS. Closed, fixed. - AVATAR-01, a new photo ends on « Le traitement prend plus de temps que prévu »: expected on DEV without a running worker (STORAGE.md §4 step 4); the pipeline completes once a worker runs (reproduced on the isolated - stack, never on DEV). Open until the owner decides how DEV runs the worker. + stack, never on DEV). Owner decision: class A, an operating constraint + that does not block V1-1; the DEV worker stays stopped on purpose, Alice's + waiting upload is kept as is and may be processed whenever a worker is + started later. No V1-1 regression shown. The reload gap found on the way + (STORAGE.md §4 step 4) is ticket AVATAR-02, out of V1-1. ## 4. Writing a migration