Correction: Verdi NPI and batch trace-X can work without Verdi-Elite (falls back to Apex/Ultra seats)

Correction to an earlier note claiming NPI design APIs need Verdi-Elite. On a shared university licence server, Verdi printed a startup warning that Verdi-Elite was not available, tried Verdi-Apex/Ultra, and then worked. Python NPI load_design on a VCS -kdb database succeeded. A one-off "license not available" failure can simply mean every shared seat was taken at that moment, so retry before concluding a feature is unlicensed. Useful batch entry points, paraphrased from the docs: - NPI lang.trace_driver2/trace_load2: static drivers and loads per statement, with file and line. - srcActiveTrace in a warm verdi -nogui -play session reading Tcl from stdin: the active driver at a time. - tfgTrX -time t -batchOutput f -showTracePath sig: the X root with a reason and a timed path. Startup on a real design was about 16 s, then 0.1-2 s per query, so keep one session warm. assertEval still failed on that server, so check each feature separately.