Merge prod_v5 (catalog v2.7, warehouse locking, per-project accept) into integration

Conflict in init_db.py resolved keeping the audit_log table ensure
function (new-one) — prod_v5 predates it and its side was empty.
Both sides' SQL lands: audit_log table plus the category-free materials
model.

frontend/src/pages/Wizard/Step2LineItems.tsx

@@ -67,17 +67,18 @@ function materialBaseName(name: string, brand: string, specs: string[], category
   return base || fallback;
 }
 
-// مقادیر مجزای category/brand/spec داخل تاپیک
+// مقادیر مجزای category/brand/spec در کاتالوگ سراسری
 export function materialOptions(
   materials: Material[],
-  topic: string,
+  _topic: string,
   item: ItemDraft,
   field: "cat" | "brand" | "spec",
   allItems: ItemDraft[] = [],
   apiBrands: string[] = [],
   apiSpecs: string[] = [],
 ): string[] {
-  let list = materials.filter((m) => topic && normalize(m.topic) === normalize(topic));
+  // متریال‌ها سراسری هستند — مستقل از تاپیک
+  let list = materials;
   const cat = item.cat.trim();
 
   const fromRows = (sel: (it: ItemDraft) => string | string[]): string[] => {
@@ -92,7 +93,7 @@ export function materialOptions(
   };
 
   if (field === "cat") {
-    const base = new Set(list.map((m) => m.category).filter(Boolean));
+    const base = new Set<string>(materials.map((m) => m.category).filter(Boolean));
     fromRows((it) => it.cat).forEach((c) => base.add(c));
     return [...base].sort((a, b) => a.localeCompare(b, "fa"));
   }