Marius Mutu 8681a92eec fix(logs): use status_at_run for per-run order counts and filtering ...

orders.status preserves IMPORTED over ALREADY_IMPORTED to avoid
overwriting historical data, so per-run journal views must use
sync_run_orders.status_at_run to show what actually happened in
that specific run.

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

2026-03-14 00:12:10 +02:00

..

__init__.py

feat: add FastAPI admin dashboard with sync orchestration and test suite

2026-03-11 14:35:16 +02:00

article_service.py

feat(sqlite): refactor orders schema + dashboard period filter

2026-03-13 16:18:57 +02:00

import_service.py

feat(dashboard): redesign UI with smart polling, unified sync card, filter bar

2026-03-13 17:55:36 +02:00

invoice_service.py

feat(sqlite): refactor orders schema + dashboard period filter

2026-03-13 16:18:57 +02:00

mapping_service.py

feat(dashboard): redesign UI with smart polling, unified sync card, filter bar

2026-03-13 17:55:36 +02:00

order_reader.py

feat: add FastAPI admin dashboard with sync orchestration and test suite

2026-03-11 14:35:16 +02:00

scheduler_service.py

feat: add FastAPI admin dashboard with sync orchestration and test suite

2026-03-11 14:35:16 +02:00

sqlite_service.py

fix(logs): use status_at_run for per-run order counts and filtering

2026-03-14 00:12:10 +02:00

sync_service.py

feat(dashboard): redesign UI with smart polling, unified sync card, filter bar

2026-03-13 17:55:36 +02:00

validation_service.py

feat(sqlite): refactor orders schema + dashboard period filter

2026-03-13 16:18:57 +02:00