gtiandClaude Sonnet 5 72edff0510 test: regression for the wrong-GTIN attest incident (similar-name products stay independent, EAN_AUSENTE is never terminal, shared-description local rows resolve independently from one KB verification) ...

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-27 12:58:35 -03:00

..

alembic

feat: visible per-product enrichment status, flagged re-evaluation (panel/Reprocessar/Sincronizar/KB decision), operator NCM decision, deterministic name-only match, stale-write guard; 1.3.5

2026-09-26 14:37:37 -03:00

app

fix: KB dashboard search was applying the strict fiscal name-match rule (used to authorize automatic writes) to human browsing, so a natural query (e.g. missing the unit word) found nothing; now a separate, lenient, global, paginated server-side search — filter over the whole KB, then count/order/paginate. 1.3.6 (Hub only)

2026-09-27 10:33:45 -03:00

scripts

fix: OSCBR role is IDENTITY (V3 contract has no NCM/CEST): v3 endpoint, provides_ncm=false, leading-zero NCM guard, backfill refuses until NCM is proven

2026-09-26 12:00:05 -03:00

static

feat: explain RTC blockers when no R3 candidates are eligible

2026-09-25 16:04:29 -03:00

templates

fix: KB dashboard search was applying the strict fiscal name-match rule (used to authorize automatic writes) to human browsing, so a natural query (e.g. missing the unit word) found nothing; now a separate, lenient, global, paginated server-side search — filter over the whole KB, then count/order/paginate. 1.3.6 (Hub only)

2026-09-27 10:33:45 -03:00

tests

test: regression for the wrong-GTIN attest incident (similar-name products stay independent, EAN_AUSENTE is never terminal, shared-description local rows resolve independently from one KB verification)

2026-09-27 12:58:35 -03:00

__init__.py

chore: establish project baseline

2026-09-21 15:51:47 -03:00

alembic.ini

chore: establish project baseline

2026-09-21 15:51:47 -03:00

Dockerfile

chore: establish project baseline

2026-09-21 15:51:47 -03:00

pyproject.toml

fix: KB dashboard search was applying the strict fiscal name-match rule (used to authorize automatic writes) to human browsing, so a natural query (e.g. missing the unit word) found nothing; now a separate, lenient, global, paginated server-side search — filter over the whole KB, then count/order/paginate. 1.3.6 (Hub only)

2026-09-27 10:33:45 -03:00