Avoid emu data overwrite

[uruwhy]

Description

Don't overwrite planners, fact sources, abilities, and adversary profiles that already exist

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[Copilot]

Pull Request Overview

Prevents EMU plugin from overwriting existing data by removing the pre-clean step and adding per-file existence checks before writing or copying.

• Removed directory deletion in hook to avoid wiping existing EMU data
• Added skip-on-exist logic for planners, adversaries, abilities, and sources with debug logs
• Preserved payload decryption and data population flow

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
hook.py	Removed rmtree of data subdirectories to stop wholesale deletion of existing EMU data before population.
app/emu_svc.py	Added existence checks and skip logic for planner copy and YAML writers for adversaries, abilities, and sources, with debug logs.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud