[Tree] Fix recover() not forwarding treeRootNode to verify(), causing unscoped forest verification

[ashrafthamir]

Problem

recover() accepts a treeRootNode option to scope recovery to a single tree, but the internal verify() call does not forward it. This causes verify() to check the entire forest instead of only the target tree.

If any other tree in the forest has errors, the early-exit optimisation is bypassed and the target tree is unnecessarily recovered. At scale (many roots, large trees), the unscoped verify() iterates every lft/rgt index across all trees, producing a query per index and leading to timeouts.

Solution

Forward treeRootNode to verify(), which already supports it.

[Copilot]

Pull request overview

Fixes a performance/correctness issue in the Tree NestedTreeRepository::recover() flow where recovery scoped to a single root node still performed an unscoped verify() across the entire forest, potentially triggering unnecessary recovery work and large verification queries.

Changes:

• Forward treeRootNode from recover() into the internal verify() call to keep verification scoped.
• Add a regression test ensuring recover(['treeRootNode' => ...]) does not get forced to run due to errors in other trees.
• Document the fix in CHANGELOG.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
tests/Gedmo/Tree/NestedTreeRootRepositoryTest.php	Adds a regression test to confirm recovery verification is properly scoped to the specified root tree.
src/Tree/Entity/Repository/NestedTreeRepository.php	Forwards treeRootNode into the early-exit verification inside recover().
CHANGELOG.md	Notes the bugfix under Unreleased.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.