### What needs to get done When debugging a failed `rockcraft pack`, as a user it is a challenge to understand what **should** have happened already given how rockcraft parts have multiple steps and can come `after` one another. It would be helpful to a user if a summary was given (or at least accessible somehow, if in a debug session). I think it is probably recreatable if you've enabled detailed logs, but reading that does not feel easily accessible for an average user. ### Why it needs to get done Debugging is hard already, it does not need to be made harder by used needing to guess where they are in their build process. This would help make engineers more productive