senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
veza/docs/archive/v0-history/RETROSPECTIVE_V0701.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.2 KiB
Raw Blame History

Rétrospective v0.701 — Retry Transfers, Admin Dashboard & Deep Health

Ce qui a bien fonctionné

  • Transfer Retry Worker : Goroutine avec ticker, backoff exponentiel, métriques Prometheus dédiées
  • Admin Transfers Dashboard : Handler paginé avec filtres (status, seller_id), retry manuel, frontend AdminTransfersView avec badges et pagination
  • Deep Health : GET /health/deep avec disk space (syscall.Statfs), config summary (jwt_secret_set, stripe_connect_enabled, etc.), distinction unhealthy (DB) vs degraded (Redis/S3)
  • API Reference : docs/API_REFERENCE.md avec exemples curl pour auth, marketplace, seller, admin, health, webhooks
  • Tests : transfer_retry_test.go (5 cas), admin_transfer_handler_test.go (6 cas), health_deep_test.go (4 cas)

Points d'attention

  • Select component : AdminTransfersView utilise le Select avec options/value/onChange (pas Radix SelectTrigger/SelectContent)
  • Stripe Connect désactivé : Si Stripe Connect non configuré, RetryTransfer retourne 503 ; le worker ne démarre pas

Prochaines étapes (v0.702)

  • À définir selon V0_702_RELEASE_SCOPE.md
  • Pistes : reviews produits, factures PDF, remboursements