fix(cma): scope alert list and alert locate to alert row entity_id; attach cash-balance suffix candidates to forecast baseline

- alerts list: filter KPIAlert.entity_id (was KPIDefinition.entity_id via join) -> entity2 225->223, rows 589/590 no longer leak into entity2 workspace

- resolve/process/escalate/create-action-plan: same row-level scope (4 sites)

- get_current_cash_balance: pass KPI_CODE_SUFFIXES[cash_balance] -> entity2 hits BH_CASH_BALANCE(434), entity6 hits DEMO_CASH_BALANCE(468)

no data changes; no SystemConfig fallback change; no period ordering change

backend/app/utils/cash_forecast_engine.py

@@ -224,7 +224,10 @@ def calc_trend(values: list) -> float:
 def get_current_cash_balance(db: Session, entity_id: int) -> Optional[float]:
     """获取当前现金余额（万元）— 优先级：KPI实际值 > SystemConfig > None"""
     from app.models import SystemConfig, KPIValue
-    kpi = find_kpi(db, entity_id, KPI_CODE_CANDIDATES["cash_balance"])
+    # C3(2026-09-19 dama-20260919)：补传实体前缀后缀候选（与 F2 的应收/应付路径一致）
+    # 修复前漏传 → 博海/演示企业一条候选都不命中 → 回退 SystemConfig.cash.current_balance(全库唯一键 -9.3)
+    kpi = find_kpi(db, entity_id, KPI_CODE_CANDIDATES["cash_balance"],
+                   KPI_CODE_SUFFIXES["cash_balance"])
     if kpi:
         latest_cash = db.query(KPIValue).filter(
             KPIValue.kpi_id == kpi.id,