Gatling OSS and GitHub Actions: retaining timestamped HTML reports from ephemeral agents

A CI pipeline runs Gatling OSS simulations on ephemeral GitHub Actions runners and needs the generated HTML report available after the job ends. Gatling writes the report to a timestamped directory under target/gatling/-/, where the run ID changes on every execution. Hard-coding the artifact path in actions/upload-artifact therefore risks missing files or failed uploads on re-runs.

The goal is to reliably capture the latest Gatling HTML report directory as a workflow artifact without assuming a fixed directory name. It is unclear whether a glob pattern such as target/gatling/**/index.html consistently matches the intended report when multiple simulations or matrix jobs run in parallel, and whether the captured directory remains browsable after download.

Can a glob-based artifact path reliably capture the timestamped Gatling report directory? Should the workflow capture simulation.log and regenerate HTML with reportsOnly in a separate job instead? What version assumptions apply to the Gatling Maven plugin and the Java toolchain on the runner?