@phnt *craft has the command pattern pipeline down (good) and they're using it to drive actions from the GUI, JSON-RPC, and MCP points (good), and the GUI has the usual vibe code scuff.

which i suspect is because the GUI side is never tested. in theory you should be able to store menu/toolbar/etc definitions in KDL (you're gonna want these to be customizable anyway), and you should be able to make requirements from a similar KDL file, like "can always do activity <make midi clip> using only mouse" and i suspect that model work would miraculously improve the GUI of all this kind of shit.

the bugs are because they are using a shit oracle that can only react to test pass/fail and then there isn't a pass/fail response for this. :blobcatwaitwhat: