- Close the true remaining duplication between `HierarchyPanel` and the project left tree after the `TreePanelHost` / `UIEditorTreePanelBehavior` cleanup.
- Keep the solution rooted in existing modules instead of creating new `Behavior` / `Host` / `Support` files.
- Reduce code only where the duplication is structurally real, not where product semantics differ.
## Why A New Plan Is Needed
- The previous plan completed the removal of the tree glue layer.
- That did not automatically mean the hierarchy tree and project tree were free of all true duplication.
- The remaining work is smaller in scope, but it is real and should be tracked separately instead of being hidden under the completed root plan.
## Confirmed Residual Duplication
### 1. Hosted panel command focus claiming is still duplicated
Current duplicated shape:
-`HierarchyPanel::ClaimCommandFocus(...)`
-`ProjectPanel::ClaimCommandFocus(...)`
-`InspectorPanel::ClaimCommandFocus(...)`
This is app-layer hosted panel behavior, not tree-business behavior.
### 2. Tree rename host skeleton is still partially duplicated
Current duplicated shape:
-`ClearRenameState(...)`
-`QueueRenameSession(...)`
-`TryStartQueuedRenameSession(...)`
-`UpdateRenameSession(...)`
Notes:
-`HierarchyPanel` has a single tree surface.
-`ProjectPanel` has both tree and grid rename surfaces.
- The commit side-effects must stay local, but the session host skeleton still contains real duplication.
### 3. Tree append/update skeleton must be re-audited carefully
- Some call order is shared: tree background, tree foreground, inline rename overlay, drop preview.
- But `ProjectPanel` also owns splitter, breadcrumb, grid, context menu, asset drag/drop, and dual-surface rename.
- This area must not be “abstracted for symmetry” unless the extracted part is truly stable and reduces code clearly.
## Explicit Non-Goals
- Do not merge panel refresh loops.
- Do not merge project tree and asset grid logic.
- Do not move project or scene runtime semantics into `XCEditor`.
- Do not create any new `Behavior`, `Host`, `Helper`, `Support`, or similar glue files.
- Do not refactor for visual symmetry when code ownership would become less clear.