fix(cases): בל"מ badge reads proceeding_type, not just appeal_subtype

After the proceeding_type field landed, users started flipping cases
to בל"מ via the edit dialog. But the case-header badge + cases-table
filter were still gated on isBlamSubtype(appeal_subtype), so the badge
didn't appear when only the proceeding_type changed. Now the badge
shows when either proceeding_type === 'בל"מ' OR appeal_subtype is an
extension_request_* variant — the legacy path stays so existing rows
that never got a proceeding_type still render correctly.

Also regen types.ts from prod (proceeding_type now in OpenAPI schema)
and register the one-shot process_pending_blam.py script.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

web-ui/src/components/cases/cases-table.tsx

@@ -55,7 +55,7 @@ const columns: ColumnDef<Case>[] = [
     header: "כותרת",
     cell: ({ row }) => (
       <div className="text-ink max-w-[420px] truncate flex items-center gap-2" title={row.original.title}>
-        {isBlamSubtype(row.original.appeal_subtype) && (
+        {(row.original.proceeding_type === 'בל"מ' || isBlamSubtype(row.original.appeal_subtype)) && (
           <Badge
             variant="outline"
             className="rounded-full px-1.5 py-0 text-[0.65rem] font-bold bg-warn/10 text-warn-deep border-warn/40 shrink-0"
@@ -113,8 +113,10 @@ export function CasesTable({
 
   const data = useMemo(() => {
     const all = cases ?? [];
-    if (blamFilter === "blam") return all.filter((c) => isBlamSubtype(c.appeal_subtype));
-    if (blamFilter === "regular") return all.filter((c) => !isBlamSubtype(c.appeal_subtype));
+    const isBlam = (c: Case) =>
+      c.proceeding_type === 'בל"מ' || isBlamSubtype(c.appeal_subtype);
+    if (blamFilter === "blam") return all.filter(isBlam);
+    if (blamFilter === "regular") return all.filter((c) => !isBlam(c));
     return all;
   }, [cases, blamFilter]);