CCC - is it just me ...

but is the workflow of CCC opaque/perverse/broken? Today, CCC immediately wanted to update itself and afterwards insisted on a reboot. Last month, I had added a 32-bit install of Splat (for those older project moments) alongside my go-to 64-bit install. Today, Manchester had appeared in CCC, so I selected "update all". After the usual whirring and grinding, the end result seemed to be that only the documentation had been updated. CCC still said "updates available". I clicked again and CCC told me that it was downloading "two files" (which I blithely assumed would take care of 32- and 64-bit Splat). I have "verbose install" set (because someone on this forum last month kindly told me to do that so as to be able to install 32- and 64-bit, which worked just fine). The less appealing consequence is that the Manchester installer then asked for confirmation of all kinds of things including 32- or 64-bit. Why in normal circumstances would I not wish to update both? But there is no option for "both". When the installer completed, I started both Splats in turn. 64-bit said Manchester, but 32-bit still said Lexington. CCC meanwhile no longer provided any update option. I checked to see what the "two files" were and it looks like one was an overwrite of the local documentation installer and the other was the Splat UP12 installer. I ran this (outside of CCC) and opted for a 32-bit install, which was apparently successful, so all's well that ends well.
 
So, is this long-winded workflow (which substantially exceeds the older method of just downloading the installer and running it) the product of my incompetence or the limitations of CCC or something else? There doesn't seem to be any help or other user documentation for CCC, so I resort to the old method of clicking on things and then seeing what happens.