Resolve UNI family-table hardware (screws/nuts/washers) as components

These appear in the .asm binary as a family-table instance name (e.g.
"R6--_-_U6592<UNI6592>"), not a separate file on disk - only the generic
"uni6592.prt" is actually indexed. Extract just the "<UNI...>" content
instead of the full instance name, in both the standalone script and the
production scanner, so standard hardware stops being silently dropped as
"not found in index".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

scripts/ExtractCreoStrings.cs

@@ -22,7 +22,14 @@ string asmIniziale = args[0];
 string dbPath = args.Length > 1 ? args[1] : "cad_index.db";
 string outPath = args.Length > 2 ? args[2] : "BOM.txt";
 
-var codiceRegex = new Regex(@"(?<!ModelView#)\b\d{8,12}(?:_[A-Za-z]\d{2,4}|[A-Za-z]{0,2})\b", RegexOptions.Compiled);
+// Seconda alternativa: viti/dadi/rosette normalizzati UNI, definiti come family table in
+// Creo. Compaiono come "Componente ID N (R12--_-_U6592<UNI6592>.PRT)": "R12--_-_U6592" è
+// il nome della singola istanza (riga della family table, non un file separato su disco),
+// il file reale indicizzato è il generico "uni6592.prt.<versione>" - va quindi estratto
+// solo il contenuto tra "<" e ">".
+var codiceRegex = new Regex(
+    @"(?<!ModelView#)\b\d{8,12}(?:_[A-Za-z]\d{2,4}|[A-Za-z]{0,2})\b|(?<=<)UNI\d+(?=>)",
+    RegexOptions.Compiled);
 const int occorrenzeMinime = 2;
 
 HashSet<string> EstraiCodiciReferenziati(string percorsoAsm)