CadQuery is definitely under active development, with a long to-do list they still want to tackle. For a beginner, it can be occasionally disorienting learning a moving target. Generally speaking it's better to have an active and evolving project rather than relying on something that has been abandoned, but it's definitely a double-edged sword.

On the upside, new features are being added. Reading through documentation I noticed a new section "Free function API" just popped up. That page doesn't explain exactly why someone would or would not use this new API. Or at least, if it did the explanation didn't make sense to this beginner.

And on the downside, sometimes things break. I am still learning the basics of CadQuery assemblies, so I noticed the assembly constraint solver demonstrations have gone out of whack. What used to be a nicely laid out door with doorway built of aluminum enclosures is now a jumbled arrangement of parts.

I copy/pasted the example code into my copy of cq-editor and it looks OK. I wonder if a newer build of cq-editor would mirror this regression. Whatever generated this documentation page certainly had some sort of problem I don't understand.

There's one upside to this bug: it told me these aren't static screenshot images. And I thought "I wonder if these are actual 3D viewer controls" and they are! I could click inside the area and change my viewpoint. There were no visible controls or anything giving me a hint this might have been the case, until I noticed the error.

I looked on CadQuery issues database and didn't see anything that directly mentions this problem, so I opened issue #1585. We'll see where this goes. [UPDATE: the developers found an angle unit degree/radian mixup in conversion to JSON, a code path used by sphinx-doc interface to generate documentation. The bug was inadvertently introduced alongside free function API, and the bug has been fixed.]