The most problematic case is paired download/upload-artifact, which requires unique artifact names. Since we don't run this under a test matrix I don't think it should be a problem.
This ran CI successfully and generated identical artifacts (up to noise-level stuff like date tags on outputs) as main, so merging now to get those warnings off the table.
The most problematic case is paired download/upload-artifact, which requires unique artifact names. Since we don't run this under a test matrix I don't think it should be a problem.