geoo has popped into IRC after his trip to Tanzania. That's good timing.
Plan for the next few days: I want to gather Proxima's proposals to the community pack, and release again. My replay repository on github is out of date, I have to put in Proxima's replays. Reasoning: This makes it easiest for geoo to review all changes. We can still revert afterwards.
Lix will get the --coverage switch in that release. Combined with --verify, --coverage lists levels without at least 1 working replay, as long as the levels reside in a directory from which you have tested at least 1 level. Reasoning: When we have more than 1 replay per level, we don't care anymore about any single replay in particular; we want to cover every level by at least 1 working replay.
geoo manages levels and replays on github. We should decide how to merge. Big singularity commit, then revert single files when geoo doesn't agree with a particular change? Or leave geoo's repository alone until we have 100 % D Lix solvability coverage, because it's in good shape for C++ Lix?
-- Simon