From 6f1594b390dea8586c2f84fab9fab6a7a8604c65 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Thu, 25 Jun 2026 02:23:31 +0000
Subject: [PATCH] docs: synchronize XamlLoader documentation

- Update README.md to articulate XamlLoader binding mechanism.
- Validate documentation code snippets against .NET 10.0 compilation.
- Record documentation drift and epistemological updates in .jules/codex.md.

Co-authored-by: tedd <493224+tedd@users.noreply.github.com>
---
 .jules/codex.md | 5 +++++
 README.md       | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/.jules/codex.md b/.jules/codex.md
index c2c4758..18494a0 100644
--- a/.jules/codex.md
+++ b/.jules/codex.md
@@ -85,3 +85,8 @@
 **Observation:** The README.md exhibited documentation drift regarding the newly integrated `Separator` component. It lacked explicit articulation of this control, which inherits from `Control`, explicitly sets `Focusable = false`, and renders a horizontal line using the `\u2500` character to match the DOS-era styling, implementing standard XAML parity for menus and layouts.
 
 **Strategic Action:** Synchronized the README.md to articulate the `Separator` architecture under the 'Rich Control Suite' section. This ensures epistemological alignment with the current framework capabilities for menu and layout separators.
+## 2024-06-25 - Documentation Synchronization of XamlLoader Component
+
+**Observation:** The README.md exhibited documentation drift regarding the integration of `XamlLoader`. It lacked explicit articulation of this structural component's mechanism, specifically how it leverages `Tedd.TUI.XamlLoader.Load(xml, controller)` to dynamically load UI elements from XML strings and automatically bind named controls to a provided controller instance via reflection.
+
+**Strategic Action:** Synchronized the README.md to precisely articulate these architectural realities under the 'XAML Support' section. Executed `.NET 10.0` syntax validation on the provided code examples to ensure exact epistemological alignment with the current framework capabilities while cleanly differentiating from hypothetical concepts.
diff --git a/README.md b/README.md
index d319352..3bfeaa7 100644
--- a/README.md
+++ b/README.md
@@ -231,7 +231,7 @@ The framework's current iteration achieves robust WPF structural parity. However
 
 ## XAML Support
 
-Tedd.TUI supports defining UI in XAML. You can load XAML at runtime using `XamlLoader`.
+Tedd.TUI supports defining UI in XAML. You can load XAML at runtime using `Tedd.TUI.XamlLoader`. This established framework capability allows UI elements to be dynamically loaded from XML strings using `Tedd.TUI.XamlLoader.Load(xml, controller)`. The mechanism automatically resolves logical elements and dynamically binds named controls to the provided controller instance via reflection, cleanly decoupling the visual tree definition from the operational code.
 
 **Example XAML (`demo.xaml`):**
 ```xml