feat: sync showcase with WRNexusJS 0.8.72 and @wrnexus/ui 0.8.88

- Sync app, public, scripts, test and examples from the framework's
  component-showcase: redesigned component demos, marketing blocks under
  /blocks, template and preview galleries, distinct Timeline/Section
  variants, Chat Bubble receipts, a top-placement Drawer demo, and the
  playground code panel fix (objects in array props no longer blank out).
- Standalone adaptations kept: the generator and tests read
  component-reference.json from the published @wrnexus/ui, and tests use
  the published @wrnexus/compiler and @wrnexus/syntax.
- Dependencies: every @wrnexus/* package to its latest release (ui 0.8.88,
  styles 0.8.26, core 0.8.16, cli 0.8.72, ...), happy-dom for the
  playground tests, Tailwind 4.3; bun.lock and package-lock.json refreshed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

app/pages/resources.wrn

@@ -8,14 +8,12 @@ page ResourcesGuide {
     <article class="page-docs guide-page">
       <nav class="docs-breadcrumbs" aria-label="Breadcrumb"><a href="/docs">Docs</a><span aria-hidden="true">/</span><span>Resources</span></nav>
       <header class="docs-intro"><span class="showcase-eyebrow">Getting Started</span><h1>Resources</h1><p>Use the component API pages, blocks, and templates as production starting points.</p></header>
-      <section class="guide-section guide-example"><h2>Configure and use it</h2><p>This is the smallest useful starting point. Copy it into the indicated application file or run it from the project root, then adjust the documented values for your product.</p><pre><code>bunx wrnexus doctor .
-bunx wrnexus inspect styles .
-bunx wrnexus update . --latest --dry-run</code></pre><h3>What changes after this</h3><p>You can move from component contract to composed block, diagnose ownership, and preview upgrades with supported tools.</p></section>
-      <section class="guide-section"><h2>Component contracts</h2><p>Each component page contains live variants, typed props, slots, outputs, copyable WRN source, behavior notes, and responsive guidance.</p></section><section class="guide-section"><h2>Blocks and templates</h2><p>Blocks demonstrate production composition patterns. Templates combine those patterns into public pages, authentication surfaces, and application dashboards.</p></section><section class="guide-section"><h2>Framework diagnostics</h2><p>Use inspect, explain, doctor, and typecheck when a component does not render or hydrate as expected. These commands expose resolved ownership rather than requiring guesswork.</p></section><section class="guide-section"><h2>Upgrade safely</h2><p>Preview framework migrations, commit the current application, apply the update, and review generated migration reports before deployment.</p></section>
-      <section class="guide-section"><h2>Verify the result</h2><p>Type-check the application, inspect the resolved package and styles, and build the production artifact. Test the page at a narrow viewport, with keyboard navigation, and in both color modes before shipping.</p><pre><code>bunx wrnexus typecheck .
-bunx wrnexus inspect packages .
-bunx wrnexus inspect styles .
-bunx wrnexus build .</code></pre><h3>Expected result</h3><p>The commands exit successfully, the build reports the installed UI components and active theme, and the rendered page remains usable before and after hydration.</p></section>
+      <section class="guide-section"><h2>Overview</h2><p>Use the component API pages, blocks, and templates as production starting points.</p></section><section class="guide-section"><h2>Configuration</h2><p>Use the design switcher in the header to test this setting live.</p></section><section class="guide-section"><h2>Component behavior</h2><p>The setting is inherited by components, blocks, templates, and playground previews.</p></section>
+      <section class="guide-section"><h2>Choose the right starting point</h2><p>Component pages document individual controls. Blocks combine controls into sections. Examples demonstrate complete workflows. Templates provide product-oriented starting pages with source you can adapt.</p><pre><code>// DataTable accepts arrays directly through bindings.
+state rows = [<span>&#123;</span> id: 1, name: "Northwind" <span>&#125;</span>]
+state columns = [<span>&#123;</span> key: "name", label: "Account" <span>&#125;</span>]
+&lt;DataTable rows="<span>&#123;</span>rows<span>&#125;</span>" columns="<span>&#123;</span>columns<span>&#125;</span>" /&gt;</code></pre><h3>Verify the result</h3><p>Open the matching component page, change its options, and try the keyboard controls. Copy the demonstrated configuration into your page, then replace sample content with your data.</p></section>
+      
       <nav class="guide-next"><a href="/components/button">Explore components <span aria-hidden="true">→</span></a><a href="/block-library">Browse blocks <span aria-hidden="true">→</span></a></nav>
     </article>
   }