I'm working on implementing the GUI part of this. It'd be convenient if inbuild would generate the confirmation page such that clicking the confirm button would call project().confirmAction(...) with one argument (instead of zero as it currently does). The argument would be the exact path that was given with the -install argument on inbuild's command line.

That way, the confirmation flow could be stateless.

Currently, the app has to remember the path of the extension it most recently tried to install with inbuild. This is not a huge problem because I don't think it's currently possible to get the app into a state where the Report tab is showing a confirmation page that refers to a different extension than the app's internal state containing the last remembered extension, but statelessness would preclude any bugs of this nature altogether.