Having poked around a bit at some of those builds, I would lean towards pausing further packaging work on the archival fork in favor of carving out bits to improve. This kind of splits the archival/new work lanes, but it will greatly help future efforts on the future of this fork. We can also make sure the updated/revised modules are back compat with the archival fork (if it makes sense) but also design them so that future feature improvements are easier to do.
All of this has the benefit of making contributing/colaborating much easier when the scope is a parser instead of everything 😁
Having poked around a bit at some of those builds, I would lean towards pausing further packaging work on the archival fork in favor of carving out bits to improve. This kind of splits the archival/new work lanes, but it will greatly help future efforts on the future of this fork. We can also make sure the updated/revised modules are back compat with the archival fork (if it makes sense) but also design them so that future feature improvements are easier to do.
All of this has the benefit of making contributing/colaborating much easier when the scope is a parser instead of everything 😁