One of the challenges of a customizable UI is that sometimes you don't know how to remove something that you can see. One idea would be that because jetpack controls the addition of chrome, you could layer all jetpack-added chrome with common affordances to allow you to a) find out what it is, b) find out how to remove it.
Yeah! I dig it.
Agree with the sentiment- could be something similar to the OS X dashboard where you click a button and little x's appear to remove jetpacks. This is a hard-ish problem because we want to allow for both known and unknown types of jetpack interaction. Assigning to Aza to see if he has time to investigate.
We will be monitoring all these issues after the rebooted Jetpack code base is released in the first week of March to ensure their causes are not duplicated. Many of the bugs/issues with the prototype version of Jetpack will be made irrelevant given the structure of the new SDK.