BC allows the cart to change without an associated page load, so if you could get the cart data through Liquid it may not always be accurate.

I wish BC had gone with ISO 8601 as the standard date string format. There's no ambiguity.

Those would be great.   What I'd really like to see, is basic filters on module_ tags, so we can reduce the set of returned elements before the infernal pagination limit is hit. (Wasn't this already…

I haven't seen this documented anywhere, and I can't replicate it for Administrator / Partner users of BC sites, but the toolbox does get closed (by default?) for some users in some circumstances.  …

Do you think it's because of changes that are expected to break beta code, or just a lack of regression tests?

You will need to insert the form on a page before you can edit the forms appearance.

Running code server-side on BC? You must be dreaming...        

I've been caught by this too. Means we have to parse the response HTML to detect the actual result success/fail status.

Thanks! Will the documentation be updated to show this correct usage?   Developer reference - Web Apps  

Yeah, having just created a test "webBasics+" level site, it doesn't have the Modules tab or the 'Media Downloads' menu.