fix(scripts): fix TCL command substitution and impl status race in all 5 build scripts

- Escape [extra] → \[extra\] to prevent TCL interpreting it as a command
  (Vivado resolved 'extra' to 'extract_files' causing ERROR [Common 17-163])
- Fix implementation status check: accept 'write_bitstream' status as success
  (Vivado auto-proceeds to write_bitstream, making status != '*Complete*')
- Wrap bitstream launch_runs in catch{} to handle already-running case

Fixes applied to: build17, build18, build19, build20, build21

9_Firmware/9_2_FPGA/scripts/build19_mmcm.tcl

@@ -186,7 +186,7 @@ set impl_status [get_property STATUS [get_runs impl_1]]
 puts "  Implementation status: $impl_status"
 puts "  Implementation time:   ${impl_elapsed}s ([expr {$impl_elapsed/60}]m [expr {$impl_elapsed%60}]s)"
 
-if {![string match "*Complete*" $impl_status]} {
+if {![string match "*Complete*" $impl_status] && ![string match "*write_bitstream*" $impl_status]} {
     puts "CRITICAL: IMPLEMENTATION FAILED: $impl_status"
     close_project
     exit 1
@@ -202,7 +202,10 @@ puts "  Phase 3/5: Bitstream Generation"
 puts "================================================================"
 
 set bit_start [clock seconds]
-launch_runs impl_1 -to_step write_bitstream -jobs 8
+# Handle case where Vivado auto-proceeds to write_bitstream after impl
+if {[catch {launch_runs impl_1 -to_step write_bitstream -jobs 8} launch_err]} {
+    puts "  Note: write_bitstream may already be in progress: $launch_err"
+}
 wait_on_run impl_1
 set bit_elapsed [expr {[clock seconds] - $bit_start}]
 puts "  Bitstream time: ${bit_elapsed}s"
@@ -292,7 +295,7 @@ report_cdc -details -file "${report_dir}/12_cdc.rpt"
 puts "  [13/15] Log scan — see build19.log"
 
 # --- Additional reports ---
-puts "  [extra] Generating additional diagnostic reports..."
+puts "  \[extra\] Generating additional diagnostic reports..."
 
 # report_exceptions can fail in Vivado 2025.2 — wrap in catch
 if {[catch {report_exceptions -file "${report_dir}/13_exceptions.rpt"} err]} {