hm_ai_qc_report_tool/modules
nickviljoen 4aa74b114a HM QC: thread signed-in user into batch executor
Single-file QC populated executor.context['user'] from current_user_email()
in routes.py, but batch QC routed through BatchQCExecutor — which never
accepted a user kwarg or set context['user'] on its per-file QCExecutor
instances. Result: every LLM call from a batched HM QC run logged as
anonymous in the Usage dashboard, only single-file and Video QC runs
showed the user's email.

BatchQCExecutor now takes user and stamps it onto each per-file
executor's context just before execute(), matching the Video QC
batch executor pattern.
2026-05-09 20:40:00 +02:00
..
campaigns Phase 1: replace local username/password auth with Azure AD SSO 2026-05-09 13:59:29 +02:00
hm_qc HM QC: thread signed-in user into batch executor 2026-05-09 20:40:00 +02:00
printer_check Six tooling fixes from Dev test pass 2026-05-09 18:32:23 +02:00
reporting Reporting: show searched Box folder under the search input 2026-05-09 20:23:06 +02:00
usage Split input/output token tracking; refresh provider pricing table 2026-04-22 14:40:13 +02:00
video_master Video Master: revert campaigns folder + lenient name matching 2026-05-09 20:19:35 +02:00
video_qc Six tooling fixes from Dev test pass 2026-05-09 18:32:23 +02:00
__init__.py Add modular architecture, core framework, and web UI 2026-02-25 11:39:04 +02:00