Tracking of plugin assets

That’s a fair point, and I currently don’t have an example of why limiting ourselves to the plugin schema would cause issues, but we should be careful. We might find ourselves adding items to the schema just to support this.

Assuming we do go this path, how would you reconcile conflicts between the assets returned by the pull and build steps? What if they both return a set of python-packages, for example?