Thanks for reporting this! We have logged a bug for this issue.  DXML-10566 – You can track the request through this JIRA ID.

Could you please confirm the Guides version in which you are experiencing this issue?

Guides upgrade will happen automatically when the new release of AEM image (the image that has not yet been made available to many customers) is updated.

Hi @ChrisDNYC  You have configured the program for automatic provisioning of AEM Guides solution(enabling through solutions and add-ons). so, the version upgrade will happen automatically once the base image (aem release) is updated.  

1. Yes, metadata rendering works on the elements inside topicmeta for plainmaps. //keywords[1]/keyword 2. Possibility of injecting JCR Assets metadata is something we are working on, and will be available by year end. 

TOC comes if it is part of the Map. Bookmap has the feature for TOC placeholder.

To add metadata information as variables or fields in your page layout: you can use the metadata elements that are added inside the bookmeta of your DITA map content.   Example: If I want to insert the metadata product name from the below DITA map.   I would create a custom metadata field for produ...

OOTB behavior (without making config update) where fmUuid value has the locale code appended at the end is applicable from version 4.1

Which version of Guides are you using? UUID filename patterns can be configured in the fmdita configuration com.adobe.fmdita.config.ConfigManager under UUID Filename Patterns property.  

@Rohan0794  It depends on how the third-party applications process it. In Guides, the fmUuid of the translated topic is same as the source language topic but it has a translated locale code appended at the end.  Eg: GUID-ea7a35ad-9c55-4269-934e-873a07d8235d (source)GUID-ea7a35ad-9c55-4269-934e-873a0...