This is the exact reason why Experience League exists. I am glad you got it working.

This is an undocumented use case. However - here is an older thread that can help you determine the cause of the error -- No renderer for extension html, cannot render resource in sites page

The above article was a small example of use of Clientlibs. For a complete discussion - see this. In fact - we recommend that you go through all 6 sections. You will learn a lot - including use of CSS and clientlibs -- Getting Started with AEM Sites Part 3 - Client-Side Libraries and Responsive Grid...

I do not think that you can perform such an advanced use case without using API and Java code.For this use case - have you looked at using Workflow MBEAN functionality -- Creating Adobe Experience Manager 6.4 Sling Servlets that invoke MBean operationsYou can view available MBEAN functionality here ...

Here is an older community article built similiar to how you did it. See if this works. You should get a Blue UI by use of a CSS. Scott's Digital Community: Submitting Adobe Experience Manager form data to custom Sling Servlets Watch the video too.

See this doc for AEM -- Testing Your UI

See this GEMS Session that will address these questions: Adobe Experience Manager Help | Tools to use for testing Adobe Experience Manager applications

Are you following the Move Procedure here to move an Asset? Titled "Moving or Renaming Assets"Managing Assets with the Touch-Optimized UI

See this related thread - Custom actions on toolbar in Touch UI

Just confirmed with our Touch UI experts - they replied: just listen to dialog-ready event and disable, something like $document.on('dialog-ready', function(){ //get and disable here});More info -- Adobe Experience Manager Help | Using Event Handlers in Adobe Experience Manager Touch UI Components