senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
veza/docs/archive/v0-history/RETROSPECTIVE_V0502.md
senke 7c9eece09a
Some checks failed
Backend API CI / test-unit (push) Has been cancelled
Details
Backend API CI / test-integration (push) Has been cancelled
Details
Veza CI / Rust (Stream Server) (push) Has been cancelled
Details
Veza CI / Backend (Go) (push) Has been cancelled
Details
Veza CI / Notify on failure (push) Has been cancelled
Details
Veza CI / Frontend (Web) (push) Has been cancelled
Details
Frontend CI / test (push) Has been cancelled
Details
Security Scan / Secret Scanning (gitleaks) (push) Has been cancelled
Details
chore(cleanup): J1 — purge 220MB debris, archive session docs (complete) 
First-attempt commit 02728909f only captured the .gitignore change; the
pre-commit hook silently dropped the 343 staged moves/deletes during
lint-staged's "no matching task" path. This commit re-applies the intended
J1 content on top of 24af2f72b (which was pushed in parallel).

Uses --no-verify because:
- J1 only touches .md/.json/.log/.png/binaries — zero code that would
  benefit from lint-staged, typecheck, or vitest
- The hook demonstrated it corrupts pure-rename commits in this repo
- Explicitly authorized by user for this one commit

Changes (343 total: 169 deletions + 174 renames):

Binaries purged (~167 MB):
- veza-backend-api/{server,modern-server,encrypt_oauth_tokens,seed,seed-v2}

Generated reports purged:
- 9 apps/web/lint_report*.json (~32 MB)
- 8 apps/web/tsc_*.{log,txt} + ts_*.log (TS error snapshots)
- 3 apps/web/storybook_*.json (1375+ stored errors)
- apps/web/{build_errors*,build_output,final_errors}.txt
- 70 veza-backend-api/coverage*.out + coverage_groups/ (~4 MB)
- 3 veza-backend-api/internal/handlers/*.bak

Root cleanup:
- 54 audit-*.png (visual regression baselines, ~11 MB)
- 9 stale MVP-era scripts (Jan 27, hardcoded v0.101):
  start_{iteration,mvp,recovery}.sh,
  test_{mvp_endpoints,protected_endpoints,user_journey}.sh,
  validate_v0101.sh, verify_logs_setup.sh, gen_hash.py

Session docs archived (not deleted — preserved under docs/archive/):
- 78 apps/web/*.md     → docs/archive/frontend-sessions-2026/
- 43 veza-backend-api/*.md → docs/archive/backend-sessions-2026/
- 53 docs/{RETROSPECTIVE_V,SMOKE_TEST_V,PLAN_V0_,V0_*_RELEASE_SCOPE,
          AUDIT_,PLAN_ACTION_AUDIT,REMEDIATION_PROGRESS}*.md
                        → docs/archive/v0-history/

README.md and CONTRIBUTING.md preserved in apps/web/ and veza-backend-api/.

Note: The .gitignore rules preventing recurrence were already pushed in
02728909f and remain in place — this commit does not modify .gitignore.

Refs: AUDIT_REPORT.md §11
2026-04-14 17:12:03 +02:00

1.6 KiB
Raw Blame History

Rétrospective v0.502 — Chat Server Rewrite (Rust → Go)

Date : 2026-02-22 Durée : 6 sprints

Ce qui a bien fonctionné

  1. Architecture claire : Le plan ADR-002 a fourni une décision architecturale bien documentée
  2. Modèle Hub/Client : Le pattern existant (playback_websocket_handler.go) a servi de base solide
  3. Compatibilité protocole : Les 19 types entrants et 20 types sortants sont identiques au Rust
  4. Tests unitaires : 15 tests passent dès la première exécution avec SQLite in-memory
  5. Migration frontend transparente : Dérivation automatique de WS_URL depuis API_URL

Ce qui pourrait être amélioré

  1. Couverture E2E : Les tests E2E sont taggés integration et nécessitent un setup complet
  2. Rate limiter : Actuellement in-memory seulement, pas Redis (suffisant pour single-instance)
  3. Presence tracking : Simplifié à hub.IsUserOnline(), pas de persistence
  4. Message search : ILIKE basique, pas de full-text search PostgreSQL

Métriques

Métrique Valeur
Fichiers Go créés 15
Fichiers Go modifiés 3
Migrations SQL 4
Tests unitaires 15
Tests E2E 6
Lignes de code Go (chat) ~1500
Types message protocole 39 (19 in + 20 out)

Points d'action pour v0.503+

  • Ajouter Redis-backed rate limiter
  • Implémenter presence tracking avec persistence
  • Ajouter PostgreSQL full-text search pour messages
  • Benchmark performance (100+ connexions simultanées)
  • Supprimer le dossier veza-chat-server/ du repo (archivage)