Hello, we have thousand of fake references between espaces, created by unused references, that are created wrong outdated espaces. 

Also are creating false positive architecture violations, and we suspect that can affect solution publish time. If we think that most of these references come from invisible actions, these should be and automatic action, on Service Studio publish, or on Service Center solution publish, like publish with full compilations one. 

In my opinion, in Service Center, its mandatory, specially when you have huge factory like ours with 1500 espaces, and you want to clean up legacy code.

To streamline the application development process in OutSystems, I propose a feature that automatically highlights or removes unused references and dependencies upon a one-click publish. This enhancement would focus on optimizing the development lifecycle by simplifying code management, improving system performance, and reducing technical debt.

When a developer clicks 'Publish,' the system will automatically detect any unused references and dependencies within the application.

1. Highlight and Prompt: Unused items will be highlighted, prompting the user to either confirm their removal or review them before proceeding with the publish.
2. Performance Impact: By eliminating unnecessary code and dependencies, the application will have reduced resource usage, leading to improved performance in both runtime and deployment speed.
3. Error Reduction: With this feature, developers can minimize the risk of errors associated with outdated or irrelevant code, thus improving the overall stability of the application.

This solution would provide developers with an intuitive, streamlined process to maintain clean code, enhance system performance, and facilitate faster, error-free deployments in OutSystems.