MeshBenchRequest

The submitting side of the job construct/mesh-bench: a bench set in the paths of this machine becomes a job that names no path, and the job's outputs come back to the paths (audit QL-433).

In the namespace construct::bench. Declared in src/libs/libconstruct/construct/bench/MeshBenchJob.hpp.

Detailed description

MeshBenchWorker is Portable, so its job can run on another node. The owner ruled on 2026-10-11 that it takes its inputs by hash: the scenes, and the results DB it appends to, go into the node's artifact store, and the definitions travel in the job as text. The DB and the meshes come back by hash, and deliverMeshBenchOutputs() writes them where this machine keeps them. MeshLab and the OPAL task mesh.bench.run both submit through submitMeshBench(), so the two doors give one job.