First-attempt commit3a5c6e184only 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 ofbec75f143(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 in3a5c6e184and remain in place — this commit does not modify .gitignore. Refs: AUDIT_REPORT.md §11
1.1 KiB
1.1 KiB
Rétrospective v0.603 — Transfer automatique, Commission & Stabilisation
Ce qui a bien fonctionné
- Transfer automatique : Injection propre de
TransferServiceviaWithTransferService, logiqueprocessSellerTransfersclaire (groupement par vendeur, calcul commission, enregistrement en DB) - Tests unitaires : Mock
TransferServicepermet de tester sans Stripe ; 3 cas couverts (success, multi-seller, transfer-fails) - Archivage docs : 17 fichiers pre-v0.501 déplacés vers
docs/archive/, références mises à jour - Commission configurable :
PLATFORM_FEE_RATEen env, défaut 10 %, simple à ajuster
Points d'attention
- Stripe Connect : En cas d'échec transfer, la commande reste
completedet les licences sont créées ; le transfer est enregistré enfailedpour retry manuel ou cron v0.604 - Multi-vendeur : Une commande avec plusieurs produits de vendeurs différents génère un transfer par vendeur
Prochaines étapes (v0.604)
- À définir selon V0_604_RELEASE_SCOPE.md
- Pistes : retry cron pour transferts
failed, dashboard admin transferts, paiement scheduling