Expand XCUI layout lab editor widgets

docs/plan/XCUI_Phase_Status_2026-04-05.md

@@ -10,6 +10,7 @@ Old `editor` replacement is explicitly out of scope for this phase.
 - Phase 1 sandbox batch committed and pushed as `67a28bd` (`Add XCUI new editor sandbox phase 1`).
 - Phase 2 common/runtime batch committed and pushed as `ade5be3` (`Add XCUI runtime screen layer and demo textarea`).
 - Current work has moved into Phase 3: stabilize schema/validation and continue filling the remaining common/runtime/editor gaps instead of replacing the old editor.
+- The current stable editor-layer batch is centered on `LayoutLab` as the widget proving ground for tree/list/property-section style controls.
 
 ## Three-Layer Status
 
@@ -47,22 +48,23 @@ Current gap:
 - `XCUI Demo` remains the long-lived effect and behavior testbed.
 - `XCUI Demo` now covers both single-line and multiline text authoring behavior.
 - `LayoutLab` now includes a `ScrollView` prototype and a more editor-like three-column authored layout.
+- `LayoutLab` now also covers editor-facing widget prototypes: `TreeView`, `TreeItem`, `ListView`, `ListItem`, `PropertySection`, and `FieldRow`.
 - Panel diagnostics were expanded to clearly separate preview/runtime/input state and native vs legacy paths.
 - `XCNewEditor` builds successfully to `build/new_editor/bin/Debug/XCNewEditor.exe`.
 
 Current gap:
 
 - The shell is still ImGui-hosted.
-- Editor-specialized widgets are still incomplete: tree, list virtualization, property grid, toolbar/menu, text area, icon atlas widgets.
+- Editor-specialized widgets are still incomplete at the shared-module level: the authored prototypes exist, but virtualization, selection models, command routing, property editing models, toolbar/menu chrome, and icon-atlas widgets are not yet extracted into reusable XCUI modules.
 
 ## Validated This Phase
 
 - `new_editor_xcui_demo_runtime_tests`: `7/7`
-- `new_editor_xcui_layout_lab_runtime_tests`: `5/5`
+- `new_editor_xcui_layout_lab_runtime_tests`: `6/6`
 - `new_editor_xcui_rhi_command_compiler_tests`: `6/6`
 - `new_editor_xcui_rhi_render_backend_tests`: `5/5`
 - `XCNewEditor` Debug target builds successfully
-- `core_ui_tests`: `19/19`
+- `core_ui_tests`: `14/14`
 - `core_ui_style_tests`: `5/5`
 
 ## Landed This Phase
@@ -71,6 +73,7 @@ Current gap:
 - Demo runtime multiline `TextArea` path in the sandbox and test coverage for caret movement / multiline input.
 - Demo authored resources updated to exercise the input field.
 - LayoutLab `ScrollView` prototype with clipping and hover rejection outside clipped content.
+- LayoutLab editor-widget prototypes for tree/list/property-style sections with dedicated runtime coverage.
 - Engine runtime layer added:
   - `UIScreenPlayer`
   - `UIDocumentScreenHost`
@@ -84,6 +87,7 @@ Current gap:
 - `new_editor` panel/shell diagnostics improvements for hosted preview state.
 - XCUI asset document loading changed to prefer direct source compilation before `ResourceManager` fallback for the sandbox path, fixing the LayoutLab crash.
 - `UIDocumentCompiler.cpp` repaired enough to restore full local builds after the duplicated schema-helper regression.
+- MSVC debug build hardening was tightened again so large parallel `engine` rebuilds stop tripping over compile-PDB contention.
 
 ## Phase Risks Still Open
 
@@ -91,11 +95,12 @@ Current gap:
 - `ScrollView` is still authored/static; no wheel-driven scrolling or virtualization yet.
 - `Image` widgets still do not have source-rect/atlas-subregion level API in the high-level draw command model.
 - Editor shell still depends on ImGui as host chrome.
+- Editor widget coverage is still prototype-driven inside `LayoutLab`; it has not yet been promoted into a reusable shared widget/runtime layer.
 
 ## Next Phase
 
 1. Cleanly stabilize schema/validation in `UIDocumentCompiler.cpp` and add targeted schema regression tests.
 2. Expand runtime/game-layer ownership from the current document host + layered `UISystem` into reusable menu/HUD stack patterns and engine runtime integration.
-3. Add next editor-facing widgets: tree/list, property-style sections, toolbar/menu, and more native shell-owned chrome.
+3. Promote the current editor-facing widget prototypes out of authored `LayoutLab` content and into reusable XCUI widget/runtime modules, then continue with toolbar/menu and more native shell-owned chrome.
 4. Move more diagnostics and shell affordances into XCUI-owned editor-layer surfaces instead of only ImGui HUDs.
 5. Continue phased validation, commit, push, and plan refresh after each stable batch.