Compare commits

..

2 commits

Author SHA1 Message Date
8ea4c3fd10 docs(session): pre-/compact resume — questions Q1 Claude smoke + Q2 audit Postgres/Baserow
Some checks failed
CI / Lint bridge (Biome) (push) Has been cancelled
CI / Security scan (push) Has been cancelled
E2E Playwright / Playwright e2e (chromium) (push) Has been cancelled
CI / Type-check bridge (push) Has been cancelled
CI / Tests unit bridge (push) Has been cancelled
CI / Tests integration bridge (push) Has been cancelled
CI / Docker build + healthcheck (push) Has been cancelled
2026-05-08 10:44:51 +02:00
590f4cb062 docs(session): update SESSION-RESUME post Patch 017 — 0 TS errors, all tests green
- Documents Patch 017: vitest->jest migration, Zod v4 UUID fixes, JwtAuthGuard
  overrides, jest.Mock typing, excalidraw/main.tsx mocks
- Client: 38/38 suites, 313/313 tests; server acadenice: 21/21 suites, 210/210 tests
- Both sides: 0 TypeScript errors

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-08 10:37:04 +02:00

View file

@ -1,4 +1,4 @@
# SESSION RESUME — formation-hub Acadenice (last update post R3.8 — R3 ENTIEREMENT TERMINE)
# SESSION RESUME — formation-hub Acadenice (last update post Patch 017 — 0 TS errors, 0 test failures)
## RECAP SESSION 2026-05-07 (lecture obligatoire post-/compact)
@ -29,6 +29,15 @@ Bridge state : 380/380 tests verts (+44 R3.1.a +6 retry/fake-redis, +11 SSE rout
**Fork DocAdenice (`docmost/`, gitignored, branche `acadenice/main`, local-only)** :
```
4cf0408 fix(acadenice): resolve test suite failures across R3 sub-blocks (Patch 017)
- 17 server specs converted from vitest to Jest (vi -> jest globals)
- jest.mock stubs for ESM-only prosemirror/html and collaboration modules
- Zod v4 strict UUID fixtures fixed (version byte [1-8][89abAB] required)
- JwtAuthGuard.overrideGuard added to all controller specs
- jest.Mock explicit types to prevent 'never' arg inference
- Client: deleted vitest.config.ts (CJS), kept vitest.config.mts (ESM)
- Client: global mocks for @excalidraw/excalidraw and @/main.tsx
- Result: client 38/38 suites 313/313 tests, server acadenice 21/21 suites 210/210 tests, 0 TS errors
be951a2 feat(acadenice): add inline comments threads for R3.8 (30 tests, Patch 016)
7d076aa feat(acadenice): add mentions notifications system for R3.7 (45 tests, Patch 015)
614533f feat(acadenice): add page templates system for R3.6 (65 tests, Patch 014)
@ -93,7 +102,22 @@ Owner=`admin:*`, Admin=tout sauf `*:delete` et `roles:manage`, Editor, Member, G
- **R3 ENTIEREMENT TERMINE**
### Mode Loop full autonome (decision 2026-05-08)
Loop autonome jusqu'a fin R3 (R3.1.d -> R3.8). Pas de checkpoint user. Apres chaque sub-bloc : commit + push + update SESSION-RESUME, puis sub-bloc suivant.
Loop autonome R3.1.d -> R3.8 termine. Patch 017 fix typecheck post-install pnpm. Etat final : 0 TS error client + server, 313 tests client + 210 tests server + 380 tests bridge tous verts.
### Questions ouvertes a trancher post-/compact (2026-05-08)
**Q1 — Strategie test E2E AI-driven (Claude Code / Stagehand / Computer Use)**
- Constat : Playwright (R3.1.e livre) couvre les chemins critiques deterministes. Manque coverage exploratoire.
- Option A : ajouter `R3.1.f Claude Code smoke` — workflow CI pre-release qui invoke Claude via Agent SDK avec acces Playwright + scenario en markdown. ~$0.50/run Sonnet, ~$2 Opus.
- Option B : decaler en R4.x post-release stabilization.
- Position complementaire (pas de remplacement Playwright) : Playwright = CI a chaque push deterministe, Claude smoke = nightly creatif decouverte UX.
- Decision a prendre : R3.1.f ou R4.x ?
**Q2 — Repartition Postgres DocAdenice vs Baserow (deja livre, audit possible)**
- Regle implicite appliquee R3.2/R3.6/R3.7/R3.8 : Baserow = donnees user-visibles (les "databases" Notion-like que Ludo cree et regarde). Postgres DocAdenice = etat plateforme (auth, RBAC, contenu pages, notifs, comments, templates, backlinks).
- 6 tables creees dans Postgres : `acadenice_backlink`, `acadenice_template`, `acadenice_notification`, `acadenice_notification_preferences`, `acadenice_page_comment`, `acadenice_row_comment`. Plus les 3 tables RBAC R2.1.
- Justifications : FK CASCADE, latence <50ms requise pour panel backlinks, RBAC Docmost natif applique server-side, pas de pollution workspace Ludo, coherence yjs collab pour comments.
- A reverifier ensemble si certaines de ces 6 tables devraient migrer vers Baserow (ex: templates editables comme une table user). Mon avis : non, mais ouvert au debat.
### TODO connus non bloquants
- Hook `WorkspaceService.create` pour seed live RBAC (actuellement seed au prochain boot)