As more teams deploy from external IDEs , how can we prevent "Shadow Development" debt—where code logic lives in external repos but loses critical metadata context within the ServiceNow App Engine?
@ShontuB - Isn't fluent exactly the methodology to spill out xml metadata to prevent anything critical to be left out within ServiceNow eco-space. The extra stuff is irrelevant from ServiceNow PoV, however is critical when changes are synched from ServiceNow <--> Repository (e.g. GitHub) <--> External IDE code structure (e.g VS Code using Claude Code)
