Reusable workflow output exists in logs but the caller job still reads it as empty

The called workflow clearly sets an output, yet the parent pipeline sees an empty value because the output contract is not exposed on the boundary the caller is actually reading.