chore(sql): renumber sales-tracker MV migration 161→164 (avoid collision)

backend/app/services/site_finder/sales_tracker_mv_refresh.py

@@ -2,7 +2,7 @@
 
 Two independent materialized views built from the Объектив sales-tracker
 ("шахматки") snapshots (objective_lots / objective_lots_history), created by
-data/sql/161_mv_sales_tracker_velocity_absorption.sql:
+data/sql/164_mv_sales_tracker_velocity_absorption.sql:
 
   1. mv_sales_tracker_velocity_by_district  — per (district, month) sold/total/
      avg-sold-price. Feeds the Site Finder Velocity Score (4th scoring criterion).

backend/app/workers/tasks/mv_sales_tracker_refresh.py

@@ -11,7 +11,7 @@ Both MVs are built from the Объектив sales-tracker ("шахматки")
 (objective_lots / objective_lots_history). Source data refreshes via the
 objective_sync beat job, so a weekly MV refresh keeps the aggregates current.
 
-MV-source migration: data/sql/161_mv_sales_tracker_velocity_absorption.sql.
+MV-source migration: data/sql/164_mv_sales_tracker_velocity_absorption.sql.
 """
 
 from __future__ import annotations

data/sql/164_mv_sales_tracker_velocity_absorption.sql

@@ -1,4 +1,4 @@
--- 161_mv_sales_tracker_velocity_absorption.sql
+-- 164_mv_sales_tracker_velocity_absorption.sql
 -- Issue #61 — Velocity materialized views for Site Finder Velocity Score (4th scoring
 -- criterion) + recommend_mix smart unit-mix. Foundation for sellout forecast.
 --