The log is only for  dam:AssetContent Can you share the log for  dam:Asset as well. Query looks good to me. If it’s not working for one of the instance can you check on another server also can you check this query after reindexing the  /oak:index/damAssetLucene by making the reindex property true fr...

Do you want to say that validation works only fir the first time you edit the component and after that?

Are you using aem forms or normal HTML5 forms. You can achieve that functionality by creating the forms in accordion and doing the front end validation on the click of each accordion to check if form in existing accordion is filled or not. 

If you put the categories as cq.authoring.dialog it will load the clientlibs for all component while editing and if you want to load it only for some specific clientlibs than you can use extraclientlibs property on your aem dialog xml. There are lots of document available for this one as well. One f...

First check that when you open the component your custom css files are loading or not the. You can play with some properties like !important to make sure your css is final and try to add css with the class name that ootb component is using

I won’t recommend to override the coralui3.css instead you can create your custom client libs css files to override the css properties and add those client line for the components for you want to override 

You need to check the author error log since publishing is happening there also check the replication queue and log while publishing. Can you also share the screenshot from crx/de for /etc/acs-commons/lists node. Make sure you are logged in as admin on both author and publisher to test.  

I believe you need to over ride the html in your component as well

How did you created the custom metadata. I think you can’t edit on existing OOTB metadata and also there should be a lock button. If you have to add addition field in metadata then you need to copy the one of the OOTB metadata and create new metadata and on the new one you should be able to edit the...

Then it seems your publishing is not happening. Are you publishing with your own user and do you have permissions to publish those nodes? Can you try re-publishing the nodes and at the same time can you check the error.logs to check what happens during the replication? Can you also share the list ja...