@master/internal-site 0.2.3 → 0.2.5

package/src/styles/blog-article.css

@@ -313,12 +313,13 @@
    * clear of the rails and their rulers. Narrower (below a 1392px window), the contents disclosure the post places in
    * its text stands in.
    */
-  .blog-article-contents {
+  /* The article owns visibility even when the shared .ui-toc stylesheet loads later. */
+  .blog-article-contents.ui-toc {
     display: none;
   }
 
   @container blog-article (width >= 80rem) {
-    .blog-article-contents {
+    .blog-article-contents.ui-toc {
       /* Its ticks start on the header logo's edge, without the documentation rail's inset, so the titles keep their
          room beside the wide frame; air is kept before the left ruler (2rem outside the frame). The caption sits on
          the first line of text. */
@@ -366,7 +367,7 @@
   }
 
   @container blog-article (width >= 88rem) {
-    .blog-article-contents {
+    .blog-article-contents.ui-toc {
       --air: 2.5rem;
     }
   }
@@ -613,7 +614,7 @@
       background: none;
     }
 
-    .blog-article-contents,
+    .blog-article-contents.ui-toc,
     .blog-article-end,
     .blog-article-footer {
       display: none;

package/src/styles/system/DESIGN.md

@@ -27,7 +27,7 @@ Pages load foundation → interface → documents → component styles in that o
 
 MDX imports only the Markdown mappings and built-in JSX components used by its transformed AST. The legacy `markdownComponents` export remains available to explicit consumers. Do not restore its blanket style side effects or substitute a runtime registry. Nested MDX keeps its own static imports.
 
-The shared Astro build integration flattens only unconditional same-directory compiler fragments, preserving order and repeated occurrences. Entries with unresolved imports stay intact. It combines adjacent plain stylesheet links only when their complete route usage is identical; foundation, interface and documents remain separate. Original assets remain available for JS references. This changes delivery, never progressive rendering, runtime or hydration.
+The shared Astro build integration flattens only unconditional same-directory compiler fragments, preserving order and repeated occurrences. Entries with unresolved imports stay intact. It combines adjacent plain stylesheet links only when their complete route usage is identical; foundation, interface and documents remain separate. Original assets remain available for JS references. This changes delivery, never the pre-rendered Master CSS of a page.
 
 Use native classes for roles, tokens for shared semantic values, mixins for repeated declarations, and utilities for local decisions. Keep global native pruning disabled. Explicit opt-in currently covers `menu`, `logos`, `scroll` and `checks`; their finite native classes are present in shared sources. Product homepage rules opt in in the product repository, with full literal class maps for dynamic states. Other files retain native rules until their states and dependency closure can be proven. A package must opt in at its own source. Coverage alone cannot justify removing a rule.