feat(5.7): raspuns API onest la blocaje + mapare inline din detaliu

Raportat din client VFP: POST /v1/prezentari raspundea submission_id+status
fara motiv pe randuri blocate (erori se popula doar pe on_unmapped_error=True),
deci un needs_data/needs_mapping parea succes.

API (aditiv): SubmissionResult += nemapate + motiv. create_prezentari
populeaza erori (validare continut, 3 niveluri) / nemapate (coduri fara
mapare, COD_NEMAPAT) / motiv (rezumat uman) pe TOATE caile non-queued —
enqueue, respins (on_unmapped_error=True) si reactivare dedup peste error,
prin helperele _rezultat_enqueue / _rezultat_respins / _motiv_clasificare.
on_unmapped_error=True pastreaza erori=COD_NEMAPAT (compat clienti vechi).

Web: mapare inline in panoul de detaliu trimitere — ruta
POST /trimitere/{id}/mapeaza (reuse save_mapping + reresolve_account, scoped
sesiune + CSRF, re-rezolva pe batch_id-ul randului), helper
_nemapate_pentru_submission + context in _detaliu_ctx, sectiune in
_trimitere_detaliu.html (selector cod RAR cu sugestie fuzzy preselectata).
Apare doar pe operatii nemapate reale (nu pe auto_send=0).

/code-review high: reparat raspuns neonest la reactivare + dublu
load_nomenclator in _detaliu_ctx.

Teste: pytest -q 765 passed. Backend trimitere (worker/masina stari/
idempotenta) si schema NEATINSE. PRD: docs/prd/prd-5.7-*.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude Agent
2026-06-23 20:51:16 +00:00
parent 6bad6bc01e
commit ac57b9250a
10 changed files with 688 additions and 21 deletions

View File

@@ -117,6 +117,40 @@ def test_resubmit_peste_queued_ramane_deduped(client):
assert res.get("reactivated", False) is False
def test_reactivare_pe_needs_data_expune_erori(client):
"""PRD 5.7: reactivarea unui rand error care re-clasifica needs_data trebuie sa
expuna erori/motiv (raspuns onest), nu doar status + reactivated."""
# rand initial valid -> queued; il fortam error
r1 = client.post("/v1/prezentari", json=_body())
sid = r1.json()["results"][0]["submission_id"]
_force_status(sid, "error")
# resubmit cu aceeasi cheie de continut DAR data in viitor -> reactivare pe needs_data
r2 = client.post("/v1/prezentari", json=_body(data_prestatie="2099-01-01"))
res = r2.json()["results"][0]
# cheia de continut difera (alta data) -> NU dedup; e un rand nou. Verificam ca
# oricum raspunsul onest e populat pentru needs_data (calea de enqueue).
assert res["status"] == "needs_data"
assert any(e["cod"] == "DATA_VIITOR" for e in res["erori"])
assert res["motiv"]
def test_reactivare_acelasi_continut_pastreaza_onest(client):
"""Reactivare cu EXACT acelasi continut peste un rand error -> reactivated=True;
daca starea noua e blocata, erori/motiv sunt populate (altfel goale pe queued)."""
r1 = client.post("/v1/prezentari", json=_body(vin="WVWZZZ1OZIQ45678")) # VIN invalid -> needs_data
sid = r1.json()["results"][0]["submission_id"]
assert r1.json()["results"][0]["status"] == "needs_data"
_force_status(sid, "error")
r2 = client.post("/v1/prezentari", json=_body(vin="WVWZZZ1OZIQ45678"))
res = r2.json()["results"][0]
assert res["submission_id"] == sid
assert res["reactivated"] is True
assert res["status"] == "needs_data"
# raspuns onest la reactivare: erori populate
assert any(e["field"] == "vin" for e in res["erori"])
assert res["motiv"]
def test_resubmit_peste_needs_data_ramane_deduped(client):
r1 = client.post("/v1/prezentari", json=_body())
sid = r1.json()["results"][0]["submission_id"]