anentrypoint-design 0.0.179 → 0.0.181

package/app-shell.css

@@ -330,7 +330,14 @@ pre .n { color: var(--green-2); }
   align-self: stretch;
   height: 100%;
 }
-.app-main > * { min-height: 0; }
+/* Document children (hero, sections, panels) keep their natural height in the
+   scrolling flex column. Without flex-shrink:0 the flex algorithm shrinks them
+   toward min-height:0 once total content exceeds the fixed-height .app-main,
+   collapsing every section to 0 and piling content on top of itself — the
+   failure mode any long-scroll page (a marketing/landing route) hits. Grow
+   children (.chat/.grow/etc.) re-assert flex:1 1 auto below via higher
+   specificity, so a single full-height pane still fills the region. */
+.app-main > * { min-height: 0; flex-shrink: 0; }
 /* The main region scrolls its own overflow at every breakpoint (previously
    only ≥901px), so a fixed-height .app never clips route content and inner
    panels don't fight the page scroll. */
@@ -787,8 +794,13 @@ table tr.clickable:focus-visible td { background: var(--bg-2); }
   .app-topbar {
     gap: var(--space-2); padding: 12px var(--space-3);
   }
+  /* When the topbar is folded into .app-chrome it is a flex:0 0 auto child, so
+     it sizes to its nav's content and overflows the viewport instead of letting
+     the nav's own overflow-x:auto engage. Constrain it to the chrome width so
+     the horizontally-scrolling nav stays inside the screen. */
+  .app-chrome > .app-topbar { max-width: 100%; min-width: 0; flex-basis: 100%; }
   .app-topbar > nav {
-    flex: 1 1 100%; margin-left: 0; order: 3;
+    flex: 1 1 100%; margin-left: 0; order: 3; min-width: 0; max-width: 100%;
     display: flex; gap: 2px; flex-wrap: nowrap;
     overflow-x: auto; scrollbar-width: none; -webkit-overflow-scrolling: touch;
   }

package/dist/247420.css

@@ -731,7 +731,14 @@
   align-self: stretch;
   height: 100%;
 }
-.ds-247420 .app-main > * { min-height: 0; }
+/* Document children (hero, sections, panels) keep their natural height in the
+   scrolling flex column. Without flex-shrink:0 the flex algorithm shrinks them
+   toward min-height:0 once total content exceeds the fixed-height .app-main,
+   collapsing every section to 0 and piling content on top of itself — the
+   failure mode any long-scroll page (a marketing/landing route) hits. Grow
+   children (.chat/.grow/etc.) re-assert flex:1 1 auto below via higher
+   specificity, so a single full-height pane still fills the region. */
+.ds-247420 .app-main > * { min-height: 0; flex-shrink: 0; }
 /* The main region scrolls its own overflow at every breakpoint (previously
    only ≥901px), so a fixed-height .app never clips route content and inner
    panels don't fight the page scroll. */
@@ -1188,8 +1195,13 @@
   .ds-247420 .app-topbar {
     gap: var(--space-2); padding: 12px var(--space-3);
   }
+  /* When the topbar is folded into .app-chrome it is a flex:0 0 auto child, so
+     it sizes to its nav's content and overflows the viewport instead of letting
+     the nav's own overflow-x:auto engage. Constrain it to the chrome width so
+     the horizontally-scrolling nav stays inside the screen. */
+  .ds-247420 .app-chrome > .app-topbar { max-width: 100%; min-width: 0; flex-basis: 100%; }
   .ds-247420 .app-topbar > nav {
-    flex: 1 1 100%; margin-left: 0; order: 3;
+    flex: 1 1 100%; margin-left: 0; order: 3; min-width: 0; max-width: 100%;
     display: flex; gap: 2px; flex-wrap: nowrap;
     overflow-x: auto; scrollbar-width: none; -webkit-overflow-scrolling: touch;
   }