WealthLedger/backend
5
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: harden auth and investment synchronization
Backend security / security (push) Successful in 8s
Details
Backend verify / verify (push) Successful in 11m9s
Details
Conventional commits / commits (pull_request) Successful in 28s
Details
Backend security / security (pull_request) Successful in 7s
Details
Backend verify / verify (pull_request) Successful in 10m38s
Details

Browse Source 
Resolve A01-A10 and C01-C07 from the backend audit.
Preserve auth failures, forced candle reconciliation and forecast freshness.
Validate MOEX responses and nested HTTP errors; remove unused legacy paths.

Verified: 209 unit tests, 262 SQLite e2e tests on Linux, OpenAPI and durability.
Record the remaining macOS native SQLite abort in the audit.
This commit is contained in:
ksv741
2026-09-27 14:09:05 +03:00
parent 5d3835e796
commit 4796d9d3f0
55 changed files with 1954 additions and 569 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.ai/conventions/http-api.md
+3 -3
View File
@@ -83,6 +83,6 @@ artifact отдельно; backend не читает их репозитории
HTTP prefix — `/api/v1`; Swagger доступен согласно `src/config/swagger.config.ts`.
Общий error response — `application/problem+json` со `status` и публичным `code`.
Validation требует `400 / VALIDATION_ERROR` и `errors: [{ pointer, detail }]`.
Известное ограничение: ValidationPipe сейчас формирует строковые сообщения,
а filter ожидает структурированные field errors; schema parity не доказывает
правильность `errors`. Изменение требует проверки реального HTTP pipeline.
ValidationPipe сохраняет структурированные field errors без `target/value`,
а filter формирует JSON pointers, включая вложенные поля. Schema parity не
доказывает правильность `errors`; изменения проверяются через реальный HTTP pipeline.