bot-backend 9c12407c09 fix(tradein/quota): per-user quota override + no burn on empty result ... Two bugs hit the first paying pilot (user2/Брусника): 1. Bonus attempts were granted via negative `used` hack (account_estimate_usage.used = -35), which made /quota return {limit:15, used:-35, remaining:50} -> frontend rendered the absurd "Осталось 50 из 15". Replaced with a proper personal monthly limit: account_quota_overrides table (migration 184) + account_quota.user_limit() used across get_status/check_and_raise/increment instead of the hardcoded global MONTHLY_LIMIT. get_status now clamps remaining = max(0, limit - max(0, used)) so remaining can never exceed limit even if a negative used leaks through again. Migration seeds user2 -> monthly_limit=50 and resets the old hack (used<0 -> 0), so user2 now sees "50 из 50". 2. POST /estimate unconditionally called account_quota.increment() after estimate_quality, even when the address failed to geocode and the handler returned the _empty_estimate fallback (median=0, n_analogs=0, insufficient_data=True, HTTP 200) -- burning a paid slot for a null result. Now increment is skipped when result.insufficient_data is True; the #747 TOCTOU-safe atomic increment/429 gate is unchanged for real results.		2026-07-13 22:53:14 +03:00
..
v1	fix(tradein/quota): per-user quota override + no burn on empty result	2026-07-13 22:53:14 +03:00
__init__.py	feat: add tradein-mvp subproject (Trade-In Estimator под /trade-in)	2026-05-21 00:25:39 +03:00