On coordinating efforts with the compiler CLI #4

Given that asinit is part of the compiler CLI, and that asbuild was first suggested as part of the compiler CLI as well (later amended to sit on top of asconfig), seeing a separate package being published right after merging asconfig, essentially establishing a new status quo over night was a bit surprising. I of course appreciate the amount of thought and work going into it in the first place, and sidestepping the efforts so far might have good reasons I'd like to understand and might as well lead to a better product than initially planned, but there is also the risk that it leads to fragmentation which I'd like to avoid in the interest of our users.

As such I'd like to understand the reasoning behind this move and what your future plans are, so we can coordinate our efforts on top of the status quo again.