docs(docs): R4 plan rev 3 validated, contract
This commit is contained in:
1 parent
b895ecf136
commit
7575c67c47
2 files changed
+167
-24
No files matched your search
@@ -0,0 +1,119 @@
|
||||
# CONTRACT — r4-card-integrity
|
||||
|
||||
Plan: `.claude/tasks/plans/2026-11-16-r4-card-integrity-2337.md` (rev 3, validated 2026-11-17). Base: `b895ecf`.
|
||||
|
||||
## REQUEST (verbatim — IMMUTABLE)
|
||||
|
||||
### Owner brief 2026-11-16 (R3 closed, R4 start)
|
||||
|
||||
Je confirme avoir testé le volet repliable des filtres sur téléphone.
|
||||
|
||||
Tout fonctionne correctement et l'ergonomie me convient.
|
||||
|
||||
Je valide officiellement R3, y compris sa dernière amélioration mobile.
|
||||
|
||||
Je confirme également que « Réinitialiser les filtres » doit rester uniquement à l'intérieur du volet. Aucun bouton supplémentaire n'est nécessaire.
|
||||
|
||||
Tu peux enregistrer cette validation propriétaire dans la documentation, le suivi et la mémoire, puis committer et pousser les éventuelles mises à jour.
|
||||
|
||||
R3 est terminé.
|
||||
|
||||
Nous pouvons maintenant passer à R4 : affichage des erreurs d'intégrité sur les cartes du catalogue.
|
||||
|
||||
Reprends les décisions déjà validées, notamment D9 C, les maquettes R0 et le plan V1-2.6.
|
||||
|
||||
Je te laisse autonome pour auditer l'existant, préparer le plan technique et organiser les relectures habituelles.
|
||||
|
||||
Présente-moi les éventuelles décisions qui nécessitent mon accord avant l'implémentation.
|
||||
|
||||
Conserve BLK-015 et RR-13 comme chantiers séparés.
|
||||
|
||||
Aucune fusion ni intervention sur DEV.
|
||||
|
||||
### Owner validation 2026-11-17 (plan R4, decisions D1 to D4)
|
||||
|
||||
Je valide le plan R4 avec les décisions suivantes.
|
||||
|
||||
D1 : ALTERNATIVE.
|
||||
|
||||
Une version trop volumineuse doit afficher le message spécifique existant :
|
||||
|
||||
« Cette version dépasse les limites de taille d'une fiche. »
|
||||
|
||||
Je préfère distinguer un dépassement de limite d'un véritable problème d'intégrité.
|
||||
|
||||
Le bouton « Réessayer » n'est pas nécessaire dans ce cas, puisqu'un nouvel essai sans modification de la version ne changera rien.
|
||||
|
||||
D2 : RECOMMANDATION VALIDÉE.
|
||||
|
||||
Lorsqu'une illustration ne peut pas être dessinée alors que la version a passé le contrôle d'intégrité, affiche le message neutre existant.
|
||||
|
||||
Si le problème provient du moteur, utilise le traitement d'erreur et le bouton « Réessayer » prévus.
|
||||
|
||||
Je ne souhaite plus que ce type d'erreur soit ignoré silencieusement.
|
||||
|
||||
D3 : RECOMMANDATION VALIDÉE.
|
||||
|
||||
Utilise pnpm db:sandbox trial pour mon essai manuel de R4.
|
||||
|
||||
Je préfère ne pas créer de nouvelles fiches publiées de test dans db:trial.
|
||||
|
||||
Précise dans la procédure comment distinguer les anomalies déjà présentes dans la sandbox des comportements propres à R4.
|
||||
|
||||
D4 : RECOMMANDATION VALIDÉE.
|
||||
|
||||
Le nouveau test navigateur doit nettoyer uniquement les fiches et les droits qu'il a lui-même créés.
|
||||
|
||||
La suppression logique des fiches de test et le retrait du droit créé sont autorisés, avec les contrôles d'identité prévus.
|
||||
|
||||
Aucune donnée préexistante ne doit être modifiée.
|
||||
|
||||
Je valide également les autres choix retenus dans le plan :
|
||||
- Gestion du bouton « Réessayer ».
|
||||
- Gestion du focus et des annonces accessibles.
|
||||
- Affichage des refus d'accès.
|
||||
- Gestion des dates absentes.
|
||||
- Signalement des erreurs propres à chaque carte.
|
||||
|
||||
Tu peux maintenant implémenter R4 selon ton processus habituel, avec tes tests et relectures indépendantes.
|
||||
|
||||
Conserve BLK-015, RR-13 et l'anomalie A dans leurs chantiers respectifs.
|
||||
|
||||
À la fin, présente-moi :
|
||||
- Le bilan des modifications.
|
||||
- Les résultats exacts des tests.
|
||||
- Les éventuelles limites.
|
||||
- La procédure d'essai manuel sur la sandbox.
|
||||
|
||||
Aucune fusion ni intervention sur DEV.
|
||||
|
||||
## CLARIFICATIONS
|
||||
- Graphic reference: board 30 `docs/design/v1-2-6-r0/30-catalogue-carte-integrite.png` (approved as is, 2026-11-09). Wording: A10 (`docs/design/v1-2-6-r0/ARBITRAGES.md`), REVUE.md:85.
|
||||
- D4 ruling: the spec archives its own published sheets (reachable state, out of the catalogue) rather than soft-deleting them, because the application never deletes a sheet that had a published version (§6.9); the owner's authorisation of soft deletion covers it. Its own grant is revoked by id.
|
||||
|
||||
## ACCEPTANCE CRITERIA
|
||||
1. Integrity class: for `fingerprint_mismatch`, `drawing_hash_mismatch`, `drawing_missing`, `invalid_document`, the card shows « Contrôle d'intégrité échoué : cette version ne peut pas être affichée. » (EN « Integrity check failed: this version cannot be displayed. »), error tone, no « Réessayer »; name, « Publiée », « Version n » and « Consulter » (enabled, same href) kept. Unit-tested per kind through the real core.
|
||||
2. D1: `caps` shows « Cette version dépasse les limites de taille d'une fiche. » (existing key `catalogue.failure.caps`), never the integrity text, no « Réessayer ». Unit-tested.
|
||||
3. Other failures: warning tone, existing text (`catalogue.failure.<kind>`, `access_denied.title` for `denied`, the core's text for `core_unavailable`), « Réessayer » for that card only; `network` with the `wifi-off` glyph, others `alert`; no retry once the engine stopped for good. Unit-tested.
|
||||
4. D2: a version that passes but whose main view cannot be composed shows the existing `catalogue.failure.view` text in a neutral line with its counts; an engine failure there shows the core line with its retry. Never silent. Unit-tested.
|
||||
5. Retry: for `core_unavailable` it calls `coreRuntime().retry()` first; during an attempt the line and button stay mounted (`aria-disabled`, card `aria-busy`), clicks ignored; a repeated failure keeps the focus on « Réessayer » and is said again by a polite region cleared at each attempt; on success the focus moves to « Consulter » only if it was on that card's « Réessayer » or on `body`. Unit-tested, including unmount during an attempt (deferred answer, balanced blob URLs, one `free()` per preview).
|
||||
6. The card lines are not live regions; `Notice` keeps today's role and glyph at every existing call site (defaults tested).
|
||||
7. The check is never bypassed or changed: nothing under `crates/`, `packages/core-wasm/`, `apps/app/src/catalogue/catalogue.ts`, `apps/app/src/catalogue/preview.ts`.
|
||||
CHECK: cd /home/bchanot/Documents/faunosteo-v1-2 && [ -z "$(git diff --name-only b895ecf..HEAD -- crates packages/core-wasm apps/app/src/catalogue/catalogue.ts apps/app/src/catalogue/preview.ts)" ] && echo CHECK_UNTOUCHED
|
||||
EXPECT: CHECK_UNTOUCHED
|
||||
8. The sheet page is unchanged.
|
||||
CHECK: cd /home/bchanot/Documents/faunosteo-v1-2 && [ -z "$(git diff --name-only b895ecf..HEAD -- apps/app/src/app/routes/app/anatomy/SheetRoute.tsx apps/app/src/components/catalogue/CatalogueFailureNotice.tsx apps/app/src/catalogue/useSheetVersion.ts)" ] && echo PAGE_UNCHANGED
|
||||
EXPECT: PAGE_UNCHANGED
|
||||
9. One new key with the exact A10 texts, fr / en parity.
|
||||
CHECK: cd /home/bchanot/Documents/faunosteo-v1-2/apps/app && grep -q "'catalogue.card.integrity_failed': \"Contrôle d'intégrité échoué : cette version ne peut pas être affichée.\"" src/i18n/fr.ts && grep -q "'catalogue.card.integrity_failed': 'Integrity check failed: this version cannot be displayed.'" src/i18n/en.ts && echo A10_OK
|
||||
EXPECT: A10_OK (quote style may differ per the dictionaries' convention; the text is what binds)
|
||||
10. Browser proof on the sandbox (`apps/app/e2e/shell/catalogue-integrity.spec.ts`): integrity in fr and en at desktop and 375 px (line, « Consulter » opening the unchanged sheet page notice, axe, no sideways scroll, 44 px); network in fr on both projects (abort one version with `route.fallback()` for the rest, remount by search, « Réessayer », focus). Exact counts recorded.
|
||||
11. D4 / P2: the spec cleans only what it created, by captured id: each own sheet archived through `private.set_sheet_status` and read back, its own grant revoked by id and read back; no statement matches by pattern; a guard before / after shows no pre-existing row changed.
|
||||
12. P1: `V1-2-6_OWNER_TRIAL.md` §4.16 in French on `pnpm db:sandbox trial` names the sandbox's pre-existing failing entries (anomaly A, by name, from a read-only query) and tells them apart from R4's own behaviour; the offline step names the remount and the wait.
|
||||
13. Exact test results kept in `.claude/tasks/TODO.md` and the documents; no failed suite called green; BLK-015, RR-13 and anomaly A stay separate open tracks.
|
||||
14. Documents as built: `V1-2-6_U1_CORRECTIONS.md` §R4 and §5 row C, the review's Part II row, `CHANGELOG.md`, `BROWSER_TESTS.md`, `.claude/tasks/TODO.md`.
|
||||
15. Gates: typecheck, lint, app unit suite, build; `pnpm check:all` exit 0 at the final head.
|
||||
16. No merge, no deploy, DEV unchanged, no write on the trial stack.
|
||||
|
||||
## FILE SCOPE
|
||||
apps/app/src/{catalogue/failure.ts,catalogue/useCardDetails.ts,components/catalogue/CardFailure.tsx,components/catalogue/CatalogueCard.tsx,components/ui/Notice.tsx,components/ui/Icon.tsx,i18n/fr.ts,i18n/en.ts}, apps/app/tests/**, apps/app/e2e/{support/catalogue.ts,support/admin.ts,shell/catalogue-integrity.spec.ts}, docs/**, CHANGELOG.md, .claude/tasks/**.
|
||||
@@ -1,10 +1,14 @@
|
||||
# R4 Catalogue Card Integrity Warning Implementation Plan (V1-2.6), rev 2
|
||||
# R4 Catalogue Card Integrity Warning Implementation Plan (V1-2.6), rev 3
|
||||
|
||||
> **For agentic workers:** REQUIRED SUB-SKILL: Use subagent-driven-development to implement this plan task-by-task.
|
||||
> Steps use checkbox (`- [ ]`) syntax for tracking.
|
||||
|
||||
**Status:** DRAFT rev 2, waiting for the owner's answers to D1 to D4. No implementation before them. DEV unchanged,
|
||||
no merge. BLK-015 and RR-13 stay separate tracks. Rev 2 = rev 1 + three fresh challenges of 2026-11-16 (correctness
|
||||
**Status:** VALIDATED by the owner, 2026-11-17 (brief « Je valide le plan R4 avec les décisions suivantes »): D1
|
||||
ALTERNATIVE (a version over the size limits shows the existing caps text, no « Réessayer », told apart from an
|
||||
integrity failure); D2, D3, D4 as recommended; R-2 to R-7 accepted. Owner precisions, binding: (P1) the trial
|
||||
procedure says how to tell the anomalies already on the sandbox from R4's own behaviour; (P2) the spec cleans only
|
||||
the sheets and the right it created, identity checked, no pre-existing row changed. Implementation authorised on the
|
||||
sandbox. DEV unchanged, no merge. BLK-015 and RR-13 stay separate tracks. Rev 3 = rev 2 + the owner's answers. Rev 2 = rev 1 + three fresh challenges of 2026-11-16 (correctness
|
||||
FATAL(4), robustness FATAL(4), simplicity FATAL(3)); what became of each finding is in « Challenge round » at the end.
|
||||
|
||||
**Goal:** a catalogue card whose published version fails the core's integrity check says so inside the card, with
|
||||
@@ -45,26 +49,27 @@ the executor writes the JSX under TDD against board 30.
|
||||
| F11 | The core runtime does not retry a failed first load by itself: `ready()` answers false until `coreRuntime().retry()` is called; the sheet page and `CatalogueCanvas` call it before reloading. Each trap spends one of three recoveries for the whole tab. | `packages/core-wasm/src/runtime.ts:142-184`, `catalogue/useSheetVersion.ts:85-88`, `CatalogueCanvas.tsx:100-104` | The card's retry for `core_unavailable` calls `coreRuntime().retry()` first (R-2). |
|
||||
| F12 | e2e: the app talks to a fake `.invalid` origin served only by the `routeToSandbox` context route; Playwright runs the last route first. Every card loads at mount (156+ on the sandbox). | `e2e/support/sandbox.ts:12, 33-40`, `CatalogRoute.tsx:68` | A route that aborts one version must `route.fallback()` the rest and be removed alone; the spec searches its tag before any check (as `catalogue.spec.ts`). |
|
||||
|
||||
## Owner decisions pending
|
||||
## Owner decisions (answered 2026-11-17: D1 ALTERNATIVE, D2 to D4 recommendation)
|
||||
|
||||
| # | Question | Recommendation | Alternative(s) | Cost if wrong |
|
||||
|---|---|---|---|---|
|
||||
| D1 | `caps` (a version over the size limits) in a card | Integrity line, error tone, A10 text, no « Réessayer »: the core refuses the version itself and a retry cannot change it. | Its own line, existing text `catalogue.failure.caps` (« Cette version dépasse les limites de taille d'une fiche. »), error tone, no retry. | One mapping line. |
|
||||
| D2 | The version passes the check but its main view cannot be drawn (no thumbnail) | Say it: a neutral line (tone `info`, not a live region) with the existing text `catalogue.failure.view`; counts and « Consulter » kept; when the engine itself failed (F5) the core line with its retry instead. Nothing left silent, no new wording. | (a) Silent as today (no code). (b) A new shorter text for the card, to ratify (e.g. « L'aperçu de cette fiche ne peut pas être affiché. »). | One component branch and its test; built only if chosen. |
|
||||
| D3 | Where the owner tries R4 | `pnpm db:sandbox trial` (the automated-test stack served for a manual trial, used on 2026-11-09): its 4 failing entries show the integrity line as they are; the network line by hiding a card with a search, going offline in DevTools, clearing the search, waiting about 7 s, going back online, « Réessayer ». No write by Claude on any stack. The page loads slowly there (156 cards each load their version). | (a) Seed two published test sheets on the trial stack (one sound, one with a wrong stored fingerprint) through a new `db:trial` step: a script change and a write on the owner's trial data, its own go. (b) Both. | (a) adds a script and a write; the recommendation adds none. |
|
||||
| D4 | Cleanup of the browser spec's own data on the persistent sandbox (F9): published test sheets cannot be deleted | The spec archives its own sheets at the end, by SQL as postgres under the seed owner, the same « prior owner action » form as its seed (status `archived`, read back per id), and revokes its own catalogue grant the same way; it touches no other row. Archived sheets leave the catalogue. | (a) No cleanup, as `catalogue.spec.ts` today: every run leaves one broken card listed on the sandbox (and in the D3 trial). (b) Archive through the application RPC with an aal2 publisher account: one more account and grant per run (BLK-015). | (a) grows the shared catalogue with broken cards; the recommendation writes only the run's own rows. |
|
||||
| D1 | `caps` (a version over the size limits) in a card | Integrity line, error tone, A10 text, no « Réessayer »: the core refuses the version itself and a retry cannot change it. | Its own line, existing text `catalogue.failure.caps` (« Cette version dépasse les limites de taille d'une fiche. »), error tone, no retry. | One mapping line. ANSWER: alternative (own caps line, no retry). |
|
||||
| D2 | The version passes the check but its main view cannot be drawn (no thumbnail) | Say it: a neutral line (tone `info`, not a live region) with the existing text `catalogue.failure.view`; counts and « Consulter » kept; when the engine itself failed (F5) the core line with its retry instead. Nothing left silent, no new wording. | (a) Silent as today (no code). (b) A new shorter text for the card, to ratify (e.g. « L'aperçu de cette fiche ne peut pas être affiché. »). | One component branch and its test; built only if chosen. ANSWER: recommendation. |
|
||||
| D3 | Where the owner tries R4 | `pnpm db:sandbox trial` (the automated-test stack served for a manual trial, used on 2026-11-09): its 4 failing entries show the integrity line as they are; the network line by hiding a card with a search, going offline in DevTools, clearing the search, waiting about 7 s, going back online, « Réessayer ». No write by Claude on any stack. The page loads slowly there (156 cards each load their version). | (a) Seed two published test sheets on the trial stack (one sound, one with a wrong stored fingerprint) through a new `db:trial` step: a script change and a write on the owner's trial data, its own go. (b) Both. | (a) adds a script and a write; the recommendation adds none. ANSWER: recommendation; P1 on the procedure. |
|
||||
| D4 | Cleanup of the browser spec's own data on the persistent sandbox (F9): published test sheets cannot be deleted | The spec archives its own sheets at the end, by SQL as postgres under the seed owner, the same « prior owner action » form as its seed (status `archived`, read back per id), and revokes its own catalogue grant the same way; it touches no other row. Archived sheets leave the catalogue. | (a) No cleanup, as `catalogue.spec.ts` today: every run leaves one broken card listed on the sandbox (and in the D3 trial). (b) Archive through the application RPC with an aal2 publisher account: one more account and grant per run (BLK-015). | (a) grows the shared catalogue with broken cards; the recommendation writes only the run's own rows. ANSWER: recommendation (soft deletion and grant removal authorised; ruling in Task 2). |
|
||||
|
||||
## Recorded unless the owner objects
|
||||
|
||||
- R-1 Integrity class (error tone, A10 text in bold, glyph `alert`, no retry): `fingerprint_mismatch`,
|
||||
`drawing_hash_mismatch`, `drawing_missing`, `invalid_document` (board 30 note « Portée »), plus `caps` if D1 as
|
||||
recommended. `drawing_missing` includes Storage answering « not found » for the drawing (400 or 404, folded by
|
||||
`drawing_hash_mismatch`, `drawing_missing`, `invalid_document` (board 30 note « Portée »). D1 (owner): `caps` is NOT
|
||||
integrity: its own line, existing text `catalogue.failure.caps` (« Cette version dépasse les limites de taille
|
||||
d'une fiche. »), error tone, glyph `alert`, no « Réessayer » (a retry cannot change the version). `drawing_missing` includes Storage answering « not found » for the drawing (400 or 404, folded by
|
||||
`classifyDrawingError`): an illustration the server does not give is missing (board 30 « illustration manquante »).
|
||||
The executor checks which Storage answers fold there and pins them in a test.
|
||||
- R-2 Other class (warning tone, existing text, « Réessayer » for that card): every other kind; texts
|
||||
`catalogue.failure.<kind>`, `access_denied.title` for `denied`, the core's text and retry label for
|
||||
`core_unavailable` (its retry calls `coreRuntime().retry()` before reloading, F11). Retry offered unless the kind is
|
||||
integrity or the engine stopped for good, as `CatalogueFailureNotice`. A version that traps the core spends one of
|
||||
integrity or `caps`, or the engine stopped for good (the page's own rule, plus D1). A version that traps the core spends one of
|
||||
the tab's three recoveries per click, as on the sheet page (accepted, same blast radius).
|
||||
- R-3 Announcements and focus: the lines are not live regions (no burst of announcements at load when several
|
||||
cards fail). During a retry the line and « Réessayer » stay in place, the button `aria-disabled` and the card
|
||||
@@ -129,7 +134,7 @@ the executor writes the JSX under TDD against board 30.
|
||||
export function cardFailure(
|
||||
failure: CatalogueFailure,
|
||||
stopped: boolean,
|
||||
): { integrity: boolean; retry: boolean }
|
||||
): { integrity: boolean; refused: boolean; retry: boolean }
|
||||
|
||||
// catalogue/useCardDetails.ts
|
||||
export type CardState =
|
||||
@@ -145,20 +150,23 @@ const INTEGRITY: ReadonlySet<CatalogueFailure> = new Set([
|
||||
'drawing_hash_mismatch',
|
||||
'drawing_missing',
|
||||
'invalid_document',
|
||||
'caps', // D1
|
||||
])
|
||||
|
||||
/** How a catalogue card treats its failure (board 30, A10): never hidden, retried where it can work. */
|
||||
/**
|
||||
* How a catalogue card treats its failure (board 30, A10, owner D1): never hidden; `refused` when the
|
||||
* version itself is refused (integrity, or over the size limits), retried only where a retry can work.
|
||||
*/
|
||||
export function cardFailure(failure: CatalogueFailure, stopped: boolean) {
|
||||
const integrity = INTEGRITY.has(failure)
|
||||
const retry = !integrity && !(failure === 'core_unavailable' && stopped)
|
||||
return { integrity, retry }
|
||||
const refused = integrity || failure === 'caps'
|
||||
const retry = !refused && !(failure === 'core_unavailable' && stopped)
|
||||
return { integrity, refused, retry }
|
||||
}
|
||||
```
|
||||
|
||||
`CardFailure` derives the rest at its one render site: text (`catalogue.card.integrity_failed` for integrity,
|
||||
`CardFailure` derives the rest at its one render site: text (`catalogue.card.integrity_failed` for integrity, `catalogue.failure.caps` for caps,
|
||||
`coreFailureMessage(t, 'sheet.core_unavailable')` for the core, `access_denied.title` for `denied`, else
|
||||
`catalogue.failure.<kind>`), tone (`error` / `warning`), glyph (`wifi-off` for `network`, else `alert`), retry label
|
||||
`catalogue.failure.<kind>`), tone (`error` when `refused`, else `warning`), glyph (`wifi-off` for `network`, else `alert`), retry label
|
||||
(`sheet.core_retry` for the core, else `common.retry`).
|
||||
|
||||
Hook behaviour: today's loading and freeing order kept (preview freed once the canvas is composed, blob URL revoked
|
||||
@@ -185,13 +193,15 @@ into a plain async function and the hook.
|
||||
7. core first load fails (`coreRuntime().ready` stubbed to `false` once): the core line with `sheet.core_retry`;
|
||||
click: `coreRuntime().retry` called, the card loads.
|
||||
8. `session_expired` and `denied`: their texts, with « Réessayer ».
|
||||
8b. caps (D1): a document over a size limit (or `coreFailure('caps')` through a stubbed preview state): the card
|
||||
shows `fr['catalogue.failure.caps']`, error tone, NOT the integrity text, no « Réessayer », « Consulter » kept.
|
||||
9. the existing first test: « Chien, rachis » also shows `fr['access_denied.title']` (F7).
|
||||
10. English: the integrity line reads the EN text.
|
||||
11. `cardFailure` exhaustiveness: every member of `CatalogueFailure` gives the expected pair (the test lists the
|
||||
union's members and fails on a new one).
|
||||
12. `Notice` defaults: `error` keeps `role="alert"` and `alert`, `success` keeps `check`; `live={false}` removes the
|
||||
role; `icon` overrides the glyph.
|
||||
13. D2 only if chosen: the main view's canvas refused shows `catalogue.failure.view` (tone `info`, no role) with the
|
||||
13. D2 (owner, validated): the main view's canvas refused shows `catalogue.failure.view` (tone `info`, no role) with the
|
||||
counts; the canvas answering `core_unavailable` shows the core line with its retry.
|
||||
- [ ] **Step 2: Run, expect FAIL** `pnpm --filter @faunosteo/app exec vitest run tests/unit/routes.catalogue.test.tsx`.
|
||||
- [ ] **Step 3: Implement** `cardFailure`, `Notice`, `Icon`, the hook, `CardFailure`, the card, the two dictionary lines.
|
||||
@@ -209,10 +219,19 @@ into a plain async function and the hook.
|
||||
- Fixtures (`beforeAll`): one tag per run; one `listed` sheet with the core's fingerprint (« R4 <tag> saine »), one
|
||||
with `storedFingerprint: '0'.repeat(64)` (« R4 <tag> altérée »); one catalogue reader account and grant as
|
||||
`catalogue.spec.ts` does. Ids kept in the run's own list.
|
||||
- Cleanup (`afterAll`), per D4 as recommended: each own sheet archived on its own by SQL as postgres under the seed
|
||||
owner (the executor uses the migrations' own archive path, e.g. `private.set_sheet_status`, never a bare update
|
||||
that skips its triggers), read back `archived`; the run's grant revoked the same way and read back; failures
|
||||
listed, then asserted empty. If D4 is (a), no cleanup and the accumulation line goes to TODO.
|
||||
- Cleanup (`afterAll`), D4 (owner, validated): each own sheet id archived on its own by SQL as postgres, through
|
||||
`private.set_sheet_status(<seed owner>, <id>, 'active', 'archived', 'anatomical_sheet.archived')` (the migrations'
|
||||
own path, audit row included), then read back `status = 'archived'` for that id; the run's own catalogue grant
|
||||
revoked by id (`update public.anatomical_catalog_grants set revoked_at = now(), revoked_by = <its account>,
|
||||
revocation_reason = 'e2e cleanup' where id = <the grant id captured at seed> and revoked_at is null returning id`),
|
||||
read back. Every statement names one id the run captured; nothing matches by pattern. Failures listed, then
|
||||
asserted empty. `seedGrant` returns the grant id (additive). The run's account stays (accounts are not cleaned by
|
||||
any suite; tracked with BLK-015).
|
||||
Ruling (controller): archive, not soft delete, although the owner authorised soft deletion: the application
|
||||
never deletes a sheet that had a published version (§6.9, `delete_anatomical_sheet`), so a deleted row with
|
||||
published history is a state no screen can reach; archiving is reachable, takes the sheet out of the catalogue and
|
||||
stays inside the owner's authorisation. Cost if wrong: archived test sheets remain visible in the admin sheet
|
||||
list under « Archivée » (one line per run, tagged « R4 <tag> »).
|
||||
- Integrity, per locale (fr, en) and project (desktop, chromium-375): sign in, open the catalogue, search the tag;
|
||||
the altered card shows the integrity line, its « Consulter » focusable and opening the sheet page, which shows its
|
||||
unchanged `catalogue.failure.fingerprint_mismatch` notice; the sound card shows its counts; axe on the searched
|
||||
@@ -232,7 +251,12 @@ into a plain async function and the hook.
|
||||
- Mandatory: `V1-2-6_U1_CORRECTIONS.md` §R4 as built (classes, R-1 to R-8, D1 to D4 answers) and §5 row C closed;
|
||||
the review's Part II row (R-8); `CHANGELOG.md`; `.claude/tasks/TODO.md` (one line per run, shortcuts harvested).
|
||||
- One line each: `BROWSER_TESTS.md` (the new spec), `docs/design/README.md` (only if a deviation from board 30).
|
||||
- Per D3: `V1-2-6_OWNER_TRIAL.md` §4.16 in French, no em-dash, with the remount and the wait of the offline step.
|
||||
- D3 (owner, validated): `V1-2-6_OWNER_TRIAL.md` §4.16 in French, no em-dash, on `pnpm db:sandbox trial`, with the
|
||||
remount and the wait of the offline step. P1: it names the sandbox's pre-existing failing entries (anomaly A: the
|
||||
current versions stored with the fictitious fingerprint, listed by name from a read-only query at Task 3, and any
|
||||
other entry the catalogue shows failing, classified by kind) and says what is R4's own behaviour (the line inside
|
||||
the card, « Consulter » kept, the unchanged sheet page, « Réessayer » on a load failure) as opposed to the data's
|
||||
fault (why those versions fail, which R4 does not fix).
|
||||
- Gates, in order: task reviews, design review against board 30 (screenshots desktop and 375 px from the spec run),
|
||||
final code review, security review of the diff, fresh verifier on the contract, `pnpm check:all`.
|
||||
- Commit `docs(docs): R4 catalogue card integrity warning as built`.
|
||||
|
||||
Reference in new issue
Block a user