The Jenkins Allure plugin can't reliably resolve absolute paths when the workspace contains a space ("Phantasm All"), and the previous attempt to pass a BUILD_TAG-derived relative path didn't help because BUILD_TAG itself bakes the spaced job name in (jenkins-Phantasm All-NN).
- collect-artifacts.sh: also copy allure-results into qa-automation-hub/ allure-results/ (a fixed, space-free, relative path under the hub workspace) after clearing any stale staging from a previous build. Log the result so empty-Allure regressions are obvious in the console.
- Jenkinsfile Publish Allure stage: drop the readProperties dance and point the plugin at path: 'allure-results' (relative to the hub workspace). No absolute paths, no BUILD_TAG interpolation.
- run-project.sh: switch PROJECT_PATH back to printf '%q' so bash source in collect-artifacts.sh reconstructs the spaced path correctly. The previous "%s" quoted form looked OK to bash but Java's Properties parser kept the literal quotes inside the value, which is what broke the earlier path-with-LAST_PROJECT_ID approach.
allure-results/ is already covered by **/allure-results/ in .gitignore, so the staged copy never gets committed.