Service to centrally track and cleanup generated files in detectors

Problem

Multiple detectors within the component-detection project are generating temporary or output files and performing their own cleanup. As more detectors are added, this approach becomes difficult to manage, increases risk of resource leakage, and complicates code maintenance.

Proposal

Introduce a centralized service to:

• Track all files generated by detectors during their operation
• Provide a unified cleanup mechanism that ensures files do not linger after execution
• Offer standardized APIs for detectors to register files for tracking and cleaning

Benefits

• Reduces code duplication and errors in individual detectors
• Simplifies detector implementation
• Helps prevent file buildup and potential resource leaks
• Easier management and auditing of generated files across all detectors

Additional Info

This would help future-proof the project as detector count and complexity grows.

Start by surveying the detector implementations in the component-detection repository to identify how they generate, register, and clean up temporary or output files. Define the service boundary and standardized registration and cleanup behavior from those existing patterns. Done means detectors can use the centralized service and generated files are reliably cleaned up after execution.