aem content merge not importing new files

**Description**
the merge option is only updating existing local modified files, but not adding new files from da

**To Reproduce**
Steps to reproduce the behavior:
1. Go to your content in da.live
2. Create 3 new files (test1, test2 and test3)
3. import your content with aem content clone --path /your/path
4. add another file (test4) in da.live
5. change the document test1 and test2 in da.live
6. change the file test2 and test3 locally
7. you now have test1 updated in da, test2 updated in da and locally, test3 updated locally, test4 new in da
8. execute aem content merge
9. expected behavior: all changes from da are imported and in case of local changes merged
10. current behavior: test1 is not updated locally (not expected), test2 and test3 has the diffs in the file (expected), test4 is not imported at all (not expected), so only files which have been modified locally are modified/updated
11. See error**Expected behavior**A clear and concise description of what you expected to happen.

The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice

**Version:**
16.20.2

**Additional context**
The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice

Start with the `aem content merge` command and reproduce the sequence using `aem content clone --path /your/path`, the da.live files test1–test4, and local edits. Trace how merge handles unchanged, locally modified, and newly added files. Done means da.live changes are imported, including test4, while local changes are preserved or merged as expected.

Written by the indexing model from the issue text.