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/sizing.wrn

@@ -8,13 +8,11 @@ page SizingGuide {
     <article class="page-docs guide-page">
       <nav class="docs-breadcrumbs" aria-label="Breadcrumb"><a href="/docs">Docs</a><span aria-hidden="true">/</span><span>Sizing</span></nav>
       <header class="docs-intro"><span class="showcase-eyebrow">Customization</span><h1>Sizing</h1><p>Compact through large scales adjust the complete component system consistently.</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>&lt;Button size="sm"&gt;Compact action&lt;/Button&gt;
-&lt;Input size="lg" label="Search" /&gt;</code></pre><h3>What changes after this</h3><p>Control size and application density remain consistent without shrinking accessible touch targets.</p></section>
-      <section class="guide-section"><h2>Component size</h2><p>Use xs, sm, default, md, lg, or xl when a component needs an explicit scale. Related controls should use the same size within one task.</p></section><section class="guide-section"><h2>Interface density</h2><p>Compact, default, comfortable, and large adjust the system globally. Choose density from audience and task complexity rather than viewport alone.</p></section><section class="guide-section"><h2>Responsive composition</h2><p>Let containers, grids, columns, navigation, and sections adapt layout. Avoid shrinking touch targets to force desktop arrangements onto mobile.</p></section><section class="guide-section"><h2>Override deliberately</h2><p>Use tokens for application-wide spacing changes and component props for local intent. Measure dense tables and large marketing layouts separately.</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>Component size</h2><p>Every component accepts xs, sm, default, md, lg, and xl.</p></section><section class="guide-section"><h2>Global density</h2><p>Compact, default, comfortable, and large scale the complete interface.</p></section><section class="guide-section"><h2>Responsive sizing</h2><p>Component sizing cooperates with responsive breakpoints.</p></section>
+      <section class="guide-section"><h2>Match density to the task</h2><p>Use compact controls for dense toolbars and tables, and the default size for forms. Keep related controls at the same size and retain usable touch targets on small screens.</p><pre><code>&lt;Button label="Filter" size="sm" /&gt;
+&lt;Input label="Project name" size="default" /&gt;
+&lt;RangeSlider label="Scale" min="0" max="5" step="0.2" value="2.4" /&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>
   }