Prospero can't use prod repo according to the current analysis:

--local-repo - folder containing EAP offline repository (eg. unzipped EAP repository zip deliverable like jboss-eap-8.0.1-maven-repository.zip)

Prospero is not able to find maven-metadata-local.xml because EAP Maven repository ZIP from test release build does not contain metadata file for the channel artifact with such name. This repository should be used as a remote repository and in that case, the mechanism is looking after maven-metadata.xml file which is included in the repository.