In the mean time I had already gone ahead and uploaded a package which I announced to multiple other places.
The package is available to download on my eepsite - same as my username, just add .i2p - it is directly on the main page as a .torrent download link.
When you say "run from within I2P", what are you referring to?
There used to be a MuWire applet that ran under the I2P node, the same way as I2PSnark but it was actually discontinued by zab some time even before he decided to stop the project.
If you mean from within an isolated machine, be my guest and set up a VM to test this with.
If that machine has to be not Windows, things are out of my competence as I have no experience with that.
For some reason MuWire doesn't work with a dedicated node. It only ever starts to connect and work with the builtin one. I tried to connect to my localhost port 7657 but it won't do anything. It only runs with its internal node.
The contents of the package have evolved since I first announced my intention:
http://retrobbs.i2p/rocksolid/article-f ... shared.i2p
This is a big read with some technical aspects included but also builtin I2P node updates have been automated and no longer rely on a local install of I2P Java. The updater script fetches I2P node updates from I2P's official clearnet site via curl.exe so if your machine is isolated strictly within I2P, it will not work. On the other hand you could just read the .bat instructions to figure out what files you need to put where yourself if you wanna update the node manually.
Also discussed in that posting is what exactly is easy to audit and what not. The short of it is that most of the package save for a few tens of .jar files in a folder are entirely reproducible by you the user, if you just download the JRE and I2P node files by yourself. The scripts are plaintext and can be read, and in case you are satisfied with the update script's safety you can even modify the txt file in the startup folder to fake the I2P node version and force the script to redownload the latest official files just for you.
I've tried building MuWire from zab's git but it only produces a handful of jar files. These can be placed in the muwirelibs folder over the ones included in the archive, as long as their names are preserved. I do not know about the rest of the files, they appear to be external libraries and I am not knowledgeable enough to know where you get them.
Ideally the entire package could be automated to just be a series of downloads and git pulls + build that recreate the entire package out of nothing but the download scripts themselves and the extra scripts and files sprinkled on top, which are all human-readable and easy to audit. I'm sure JRE download can be automated. But until I find a way to automate assembling the whole rest of the package, this is the maximum level of trust that I'm able to provide.