feat(usage): treat priority as fast alias and re-enable Fast filter

When upstream gateways (e.g. sub2api) normalize a client's `service_tier:"fast"`
into the canonical `priority`, codex2api was storing `priority` verbatim, which
hid the Fast badge and broke the Fast-only filter. Normalize at write time and
fall back to recognizing both values for legacy rows; flip the Usage page Fast
filter back on now that it has data to act on.

Author: james-6-23

database/postgres.go

@@ -1918,10 +1918,12 @@ func (db *DB) ListUsageLogsByTimeRangePaged(ctx context.Context, f UsageLogFilte
 		paramIdx++
 	}
 	if f.FastOnly != nil {
+		// priority 是 fast 的同义词；新数据已在 resolveServiceTier 处归一化为 fast，
+		// 这里同时识别 priority 以兼容历史日志（issue #119 之前的 priority 透传记录）。
 		if *f.FastOnly {
-			where += ` AND COALESCE(u.service_tier, '') = 'fast'`
+			where += ` AND COALESCE(u.service_tier, '') IN ('fast', 'priority')`
 		} else {
-			where += ` AND COALESCE(u.service_tier, '') <> 'fast'`
+			where += ` AND COALESCE(u.service_tier, '') NOT IN ('fast', 'priority')`
 		}
 	}
 	if f.StreamOnly != nil {

frontend/src/pages/Usage.tsx

@@ -293,7 +293,7 @@ export default function Usage() {
   const [apiKeys, setAPIKeys] = useState<APIKeyRow[]>([])
   const [modelOptions, setModelOptions] = useState<string[]>([])
   const [apiKeyLoadFailed, setAPIKeyLoadFailed] = useState(false)
-  const showFastFilter = false
+  const showFastFilter = true
   const pageSizeOptions = [10, 20, 50, 100]
   const searchTimer = useRef<ReturnType<typeof setTimeout>>(null)
 
@@ -760,7 +760,7 @@ export default function Usage() {
                             {isImageUsageLog(log) && (
                               <ImageUsageBadge log={log} />
                             )}
-                            {log.service_tier === 'fast' && (
+                            {(log.service_tier === 'fast' || log.service_tier === 'priority') && (
                               <Badge
                                 variant="outline"
                                 className="text-[11px] font-semibold gap-0.5 border-transparent bg-blue-500/12 text-blue-600 dark:bg-blue-500/20 dark:text-blue-400"

proxy/translator.go

@@ -1103,17 +1103,25 @@ func sanitizeServiceTierForUpstream(body []byte) []byte {
 	}
 }
 
-// resolveServiceTier 从实际 tier 和请求 tier 中选择最终值
+// resolveServiceTier 从实际 tier 和请求 tier 中选择最终值。
+// 入库时把 "priority" 归一化为 "fast"：两者在 OpenAI Responses API 是同义词
+// （codex2api 把 fast → priority 后透传上游），codex2api 的 UI/筛选/徽章统一以
+// "fast" 为规范名。这样 sub2api 等中间层透传 service_tier="priority" 时，仍能
+// 在管理台正确显示 Fast 徽章和参与 fast 维度的统计/筛选。
 func resolveServiceTier(actualTier, requestedTier string) string {
 	requestedTier = strings.TrimSpace(requestedTier)
 	if requestedTier == "fast" {
-		return requestedTier
+		return "fast"
 	}
 	actualTier = strings.TrimSpace(actualTier)
-	if actualTier != "" {
-		return actualTier
+	final := actualTier
+	if final == "" {
+		final = requestedTier
 	}
-	return requestedTier
+	if final == "priority" {
+		return "fast"
+	}
+	return final
 }
 
 // 上游不支持的 JSON Schema 验证约束关键字

proxy/translator_test.go

@@ -32,6 +32,20 @@ func TestResolveServiceTier(t *testing.T) {
 	if got := resolveServiceTier("default", "fast"); got != "fast" {
 		t.Fatalf("expected requested fast to win for logging, got %q", got)
 	}
+	// priority 是 fast 的同义词，入库归一化为 fast，便于 UI 徽章/筛选统一识别
+	if got := resolveServiceTier("priority", ""); got != "fast" {
+		t.Fatalf("expected priority to normalize to fast, got %q", got)
+	}
+	if got := resolveServiceTier("", "priority"); got != "fast" {
+		t.Fatalf("expected requested priority to normalize to fast, got %q", got)
+	}
+	if got := resolveServiceTier("priority", "default"); got != "fast" {
+		t.Fatalf("expected actual priority to normalize to fast, got %q", got)
+	}
+	// flex / default 等其它 tier 保持原值
+	if got := resolveServiceTier("flex", ""); got != "flex" {
+		t.Fatalf("expected flex tier to be preserved, got %q", got)
+	}
 }
 
 func TestSanitizeServiceTierForUpstream_FastToPriority(t *testing.T) {