@mark-lunarg The SPIRV-Tools changes are merged into ToT and this script is ready to be used.

• You will need the 1.2.152 headers as those are where the new SPIR-V built-in VUIDs are even added (will show as 0 VUIDs with 151 headers otherwise)
• We discussed the idea of having the file paths in SPIR-V Tools, but decided to simply the flow with just listing them here

@sfricke-samsung, yep, will get to it after 152 lands -- it had an unusual amount of VUID churn and so is taking a bit longer than usual. And after seeing your note that all the SPIR-V VUIDs were in one file, I agree that having the path here is the best thing to do.

@mark-lunarg Sounds good, there is really no rush for me for this change, I am going to focusing on closing the about 66% coverage cap (in terms of the new VUID labels added) currently in Built-Ins in SPIR-V Tools and just wanted a way to track it... this PR is more of my courtesy of not just dumping a new process on you without volunteering to add the code... so quite honestly don't feel afraid to just refactor this PR as much as you want to fit your flow

This seemed to work fine in my testing. Note that known-good is still set to behind your changes to spirv-tools, but it seems harmless enough to push. Thanks Spencer!