CP/M needed a disk to function. If this is ported to machines that could load from tape, it would be very fun for machines like the msx or speccy.
Many of the applications have platform specific code and need to be ported as well.
A project like this is a useful reference point, but rarely directly usable.
Just in case you get the wrong idea: I'm very grateful that you put CP/Mish out there. My Z80 retroboard project benefited from it (I used the ZCPR1/ZSDOS .rel outputs directly in my board's emulator, plus the project served as a useful reference source) with no contribution back.
I don't think it would have helped anyone if I'd tried to make it support my board in your build process. There's one of my board in the world, with zero users now I'm working with its replacement design. I already had a BIOS written for zasm, and no removable storage (socketed ROM might count as removable I guess) so I wasn't trying to build a bootable disk image.
If, say, I had a vintage Model IV and wanted to make disks for it, it might be a different story, but for a retrobrew z80 machine it's a good reference but IMO not a good basis for the software part of the project.
The tapes for the Adam were referred to as Digital Data Packs. They were standard cassette tapes with some extra holes. If you were handy you could turn a standard tape cassette into a DDP saving yourself some money. Data was stored on them in a digital format consisting of 2 tracks with 128 sectors. The tape drives were built directly into the Adam and it directly controlled them allowing it to access specific sectors on the tape as needed. In other words it had the same track and sector access ability as a floppy. This is what allowed it to run CP/M from tape.
When CP/M was booted from tape the 1st tape drive was CP/M drive A and the 2nd tape drive was drive B.