@leed-ai/cli 0.0.0-stage → 6.19.0

package/dist/static/tailwind/docs/components/docs-pagination.css

@@ -0,0 +1,71 @@
+/**
+ * The DOCUMENTATION pager — previous/next at the foot of a docs page.
+ *
+ * Not the site pager. `components/pagination.css` styles the numbered pager a
+ * paginated list page emits (.pagination-list, .pagination-active, …). These
+ * two were both called "pagination" and used different naming conventions, so
+ * a reader could not tell which file governed which component; the classes
+ * here carry a docs- prefix to match the #documentation scope they live in.
+ *
+ * Colors resolve through --component-pagination-*, which reads --docs-* first
+ * — every shipped docs theme sets those — then --site-*, then the default.
+ */
+#documentation {
+  nav#docs-pagination {
+    @apply sm:grid sm:grid-cols-2 w-full mt-6 gap-x-4 flex flex-col gap-y-4;
+
+    /* Empty grid cells to maintain layout */
+    &::before,
+    &::after {
+      @apply content-[""] block;
+    }
+
+    /* The pager link color (and its hover) are DEFAULTS a site is expected to
+       override — the sibling `.docs-pagination__sublabel` already uses the same
+       value unforced. `nav#docs-pagination` sits outside `#leed-docs-copy`, so
+       the theme's anchor rule cannot reach these links and nothing competes.
+       Do not reinstate the `!`. */
+    .docs-pagination__link {
+      @apply flex flex-col p-4 rounded-md transition-all duration-200 no-underline border border-(--component-border-color) text-sm text-(--component-text-color)/80 hover:shadow-none hover:text-(--component-text-color) hover:border-(--component-anchor-text-color);
+
+      &:hover i {
+        @apply text-(--component-pagination-icon-color-hover) dark:text-(--component-pagination-icon-color-hover);
+      }
+      &:hover .docs-pagination__sublabel {
+        @apply text-(--component-pagination-icon-color-hover) dark:text-(--component-pagination-icon-color-hover);
+      }
+    }
+
+    .docs-pagination__link--prev {
+      @apply col-start-1 col-end-2 text-left w-auto;
+    }
+
+    .docs-pagination__link--next {
+      @apply col-start-2 col-end-3 text-right w-auto ml-auto;
+    }
+
+    .docs-pagination__sublabel {
+      @apply text-sm text-(--component-text-color)/80 font-normal;
+    }
+
+    .docs-pagination__label {
+      @apply flex items-center font-semibold text-(--component-header-3-color) text-base gap-1;
+
+      &:hover {
+        @apply text-(--component-header-1-color);
+      }
+    }
+
+    .docs-pagination__link--next .docs-pagination__label {
+      @apply justify-end;
+    }
+
+    .docs-pagination__icon--prev {
+      @apply mr-2 fa-solid leed-icon-chevron-left text-[9px] text-(--component-pagination-icon-color) hover:text-(--component-pagination-icon-color-hover);
+    }
+
+    .docs-pagination__icon--next {
+      @apply ml-2 fa-solid leed-icon-chevron-right text-[9px] text-(--component-pagination-icon-color) hover:text-(--component-pagination-icon-color-hover);
+    }
+  }
+}

package/dist/static/tailwind/docs/components/mobile-bar.css

@@ -0,0 +1,83 @@
+/* Mini TOC for mobile */
+#docs-mini-bar {
+  @apply sticky top-(--height-header) align-middle items-center w-full text-sm border-b border-(--component-header-border-color)/5 py-2 bg-(--component-bg-color);
+
+  a {
+    @apply text-(--component-text-color);
+  }
+
+  [aria-current="location"] {
+    @apply text-(--component-body-link-color);
+  }
+
+  #docs-mini-toc {
+    @apply absolute top-full left-0 /* Align with left edge of parent */ right-0 /* Align with right edge of parent */ mt-2 /* Increased margin to make it appear below */ border border-(--component-header-border-color)/5 bg-(--component-menu-bg-color) rounded-b-md shadow-lg z-40;
+  }
+
+  /* Dropdown styling */
+  #docs-mini-toc [x-show="isOpen"] {
+    @apply mt-1 border border-(--component-header-border-color)/5 rounded-md;
+  }
+
+  #docs-mini-bar-buttons {
+    @apply gap-4;
+    button.mini-menu {
+      @apply text-(--component-text-color) order-1 ml-4 md:ml-0 flex items-center rounded-md transition-colors;
+
+      i {
+        @apply fa-regular leed-icon-panel-toggle text-(--component-text-color)/80 text-xl origin-center transition-transform duration-200;
+      }
+    }
+
+    button.mini-toc {
+      @apply flex justify-self-end order-3 md:order-2 ml-auto mr-4 md:mr-0 py-1 px-3 items-center border border-(--component-header-border-color)/30 hover:border-(--component-header-border-color)/50 rounded-md transition-colors;
+
+      #leed-mini-toc-button-text {
+        @apply font-medium;
+      }
+
+      i {
+        @apply fa-solid leed-icon-chevron-right text-xs ml-3 origin-center transition-transform duration-200;
+      }
+    }
+
+    #leed-mini-toc-current {
+      @apply flex flex-1 order-2 md:order-1 text-left text-(--component-text-color);
+    }
+  }
+
+  #leed-mobile-toc-container {
+    @apply p-0;
+
+    /* Base list styling */
+    .leed-nav-toc {
+      ol {
+        @apply list-none m-0 p-0 text-xs;
+      }
+
+      /* Remove default spacing from list items */
+      li {
+        @apply m-0 p-0;
+      }
+
+      /* Apply border to ALL links by default */
+      a {
+        @apply block py-2 px-4 text-(--component-text-color) hover:text-(--component-body-link-color) border-b border-(--component-header-border-color)/5 hover:bg-(--component-current-location-bg-color) transition-colors w-full;
+      }
+
+      ol {
+        @apply list-none! m-0! p-0!;
+      }
+
+      /* Nested list links with indent */
+      ol ol a {
+        @apply pl-8;
+      }
+
+      /* Active link styling */
+      a[aria-current="location"] {
+        @apply font-medium text-(--component-body-link-color) bg-(--component-current-location-bg-color) border-l-2 border-l-(--component-header-border-color);
+      }
+    }
+  }
+}

package/dist/static/tailwind/docs/components/navigation.css

@@ -0,0 +1,279 @@
+/* Base sidebar styling */
+.docs-sidebar {
+  @apply border-r border-(--component-border-color) shrink-0 transition-all duration-300 overflow-y-auto lg:sticky lg:top-(--height-header) lg:h-[calc(100vh-var(--height-header))] w-72 pr-8 pb-0 pt-4 z-99 lg:z-9 lg:pl-8 lg:bg-transparent;
+
+  /* Mobile behavior - closed */
+  &[aria-hidden="true"] {
+    @apply hidden lg:block;
+
+    #docs-navigation {
+      @apply -translate-x-full lg:translate-x-0;
+    }
+  }
+
+  /* Mobile behavior - open */
+  &[aria-hidden="false"] {
+    @apply fixed inset-0 mt-0 lg:top-(--height-header) lg:mt-0 lg:sticky;
+
+    .docs-mobile-menu-overlay {
+      @apply fixed z-9999 inset-0 bg-black/20 backdrop-blur-sm lg:hidden!;
+    }
+
+    /* Mobile navigation content when open.
+
+       Carries NO padding, deliberately. `lg:p-4 lg:px-3` used to be repeated
+       here, identical to the copy in the `#docs-navigation` rule below, and the
+       duplicate was silently authoritative: this selector compiles to
+       `.docs-sidebar[aria-hidden="false"] #docs-navigation` at (1,2,0), which
+       ties every layout's `.docs-layout-* .docs-sidebar #docs-navigation` and
+       wins the tie on source order, because the layout files are emitted before
+       this one. `aria-hidden="false"` is set at every width, desktop included,
+       so alpha's `lg:p-0`, bravo's `lg:p-0` and charlie's `lg:px-0` were all
+       being discarded — none of the three had ever taken effect.
+
+       That is what made #docs-nav-filter slide: a layout's attempt to zero this
+       padding never landed, so 1rem of it stayed above the sticky box, the box
+       rested 1rem below where it sticks, and it traveled that far on the first
+       scroll.
+
+       Padding belongs in the rule below, at (1,1,0), where a layout can
+       legitimately outrank it. Do not reintroduce a padding utility here. */
+    #docs-navigation {
+      @apply fixed lg:static bg-(--component-bg-color) lg:bg-transparent top-0 z-99999 lg:w-auto h-full lg:h-auto overflow-y-auto lg:overflow-y-visible;
+    }
+  }
+
+  /* Navigation content styling */
+  #docs-navigation {
+    @apply w-[80%] max-w-105 lg:w-full lg:max-w-none lg:p-4 lg:px-3 md:p-0;
+
+    > ul li:first-child {
+      @apply mt-0!;
+    }
+
+    /* Sidebar link colors are DEFAULTS a site is expected to override.
+       These selectors already outrank `#docs-navigation .leed-menu__item--wrapper`
+       (and resolve to the same token), so `!` changed nothing visually — it only
+       made the sidebar unrestylable without an unlayered `!important` file.
+       Do not reinstate the `!`. */
+    a {
+      @apply text-(--component-text-color);
+
+      &:hover {
+        @apply text-(--component-primary-color) bg-(--component-sidebar-link-hover-bg-color);
+      }
+    }
+
+    ul.leed-submenu li {
+      @apply ml-0 cursor-default;
+    }
+
+    ul.leed-submenu--level-1 li:has(ul.leed-submenu) {
+      @apply ml-3;
+
+      div.leed-menu__item--wrapper:hover {
+        @apply bg-transparent cursor-default;
+      }
+    }
+    ul.leed-submenu--level-1 > li:has(ul.leed-submenu) {
+      @apply ml-0;
+    }
+
+    > ul > li[aria-haspopup="menu"] {
+      @apply cursor-pointer mt-6;
+
+      .leed-menu__item--no-link {
+        @apply font-bold;
+      }
+      .leed-menu__item--toggle {
+        @apply text-[10px];
+      }
+      li:has(ul[aria-hidden="false"]) .leed-menu__item--toggle {
+        @apply rotate-90;
+      }
+      li:has(ul[aria-hidden="true"]) .leed-menu__item--toggle {
+        @apply rotate-0;
+      }
+    }
+
+    /* Hide toggle button specifically for top-level menu items that are disabled */
+    > ul > li[aria-haspopup="menu"][aria-disabled="true"] > div .leed-menu__item--toggle {
+      @apply hidden;
+    }
+
+    /* Current-page color and the no-link hover ground are DEFAULTS a site is
+       expected to override. Both selectors already outrank the base rules they
+       replace, so the `!` was redundant paint-forcing. Do not reinstate it. */
+    [aria-current="page"] > a.leed-menu__item--wrapper {
+      @apply font-semibold text-(--component-primary-color) bg-(--component-sidebar-link-current-bg-color);
+    }
+    & .leed-menu__item--wrapper.leed-menu__item--no-link {
+      @apply hover:bg-transparent;
+    }
+  }
+}
+
+#docs-navigation {
+  @apply w-full lg:py-4 lg:px-3 text-sm leading-5;
+
+  [aria-current="page"] > .leed-menu__item--wrapper {
+    @apply font-medium text-(--component-current-location-text-color) bg-(--component-current-location-bg-color);
+  }
+
+  [aria-expanded="true"] > .leed-menu__item--wrapper {
+    @apply font-medium text-(--component-text-color);
+  }
+
+  /* `bg-(--component-sidebar-link-bg-color)` is the RESTING row ground, and it
+     resolves to `transparent` unless a theme or a site says otherwise — so this
+     changed nothing when it was added. It sits at (1,1,0), below every rule
+     that paints a row for a reason: the hover and current grounds in the
+     `.docs-sidebar` block above (1,2,1)/(1,3,1), the `[aria-current="page"]`
+     wrapper rule below (1,2,0), and charlie's transparent overrides. A resting
+     ground must lose all of those, so do not raise this selector. */
+  .leed-menu__item--wrapper {
+    @apply flex lg:my-0.5 no-underline w-full py-2 px-3 text-(--component-text-color) bg-(--component-sidebar-link-bg-color) hover:bg-transparent border-b border-(--component-header-border-color)/5 lg:border-b-0 lg:rounded-md transition-colors duration-200 items-baseline justify-between;
+
+    .leed-menu__item--icon {
+      @apply inline-flex items-baseline mr-2;
+
+      &.api-endpoint {
+        @apply mt-1;
+      }
+    }
+
+    .leed-menu__item--name {
+      @apply grow wrap-break-word whitespace-normal flex-wrap items-baseline;
+    }
+
+    .leed-menu__item--leave {
+      @apply fa-solid leed-icon-external-square ml-1 whitespace-nowrap inline-block align-baseline;
+    }
+
+    .leed-menu__item--toggle {
+      @apply fa-solid leed-icon-chevron-right ml-2 shrink-0 transition-transform origin-center duration-200 ease-in-out my-auto;
+    }
+
+    /* Default hover ground, overridable at normal specificity. Do not force
+       with `!` — a site must be able to paint this row. */
+    ul.leed-menu > li > .leed-menu__item--no-link {
+      @apply hover:bg-transparent;
+    }
+  }
+
+  [aria-expanded="true"] > .leed-menu__item--wrapper > .leed-menu__item--toggle {
+    @apply rotate-90;
+  }
+
+  .leed-submenu[aria-hidden="true"] {
+    @apply hidden;
+  }
+
+  .leed-submenu {
+    @apply pl-0;
+
+    .leed-menu__item--text {
+      @apply flex items-center;
+    }
+  }
+
+  /* Nav filter visibility channel. Written with `&` so it compiles to
+     `#docs-navigation[data-filtering="true"] …` — nesting the literal id would
+     produce `#docs-navigation #docs-navigation[…]`, which matches nothing.
+     Hiding non-matches is all the filter asks of CSS. Revealing a collapsed
+     section deliberately is NOT done here: a rule that outranks the collapse
+     rule above would paint focusable links while aria-hidden="true" kept them
+     out of the accessibility tree, so NavFilterManager flips the submenu's
+     aria-hidden instead and the collapse rule stops matching on its own. */
+  &[data-filtering="true"] {
+    li[data-filter-hidden] {
+      @apply hidden;
+    }
+  }
+
+  /* Sits after the menu rather than inside #docs-nav-filter, so a site that
+     hides the box still gets the "no matches" message. */
+  .docs-nav-filter__empty {
+    @apply px-3 py-4 text-(--component-text-color)/70;
+
+    &[hidden] {
+      @apply hidden;
+    }
+  }
+}
+
+/* Deliberately a TOP-LEVEL rule and deliberately declaring no `display`.
+   Nested inside #docs-navigation this would compile to (2,0,0) and beat a
+   site's own `#docs-nav-filter { display: none }` opt-out — which the site
+   docs tell sites to write inside `layer(components)`, so it only wins on
+   source order and needs this rule to stay at (1,0,0). Never add !important
+   here, and never add a `display` declaration. */
+#docs-nav-filter {
+  /* Two negative numbers, canceling two different things. Keep them in step.
+
+     `top` cancels the scrollport's own top padding. A sticky offset resolves
+     against the content edge, so a plain `top: 0` parks the box 1rem down and
+     leaves a strip above it for menu rows to scroll through in full view.
+     `pt-4` puts that 1rem back inside the box, where the background travels
+     with it instead of staying behind.
+
+     `margin-top` cancels every top padding between that same scrollport edge
+     and the box, so the box rests exactly where it will stick. Miss one and
+     the filter slides by the difference the first time the menu scrolls.
+
+     GATED AT `lg`, and the pair is NOT a no-op where there is no padding to
+     cancel — that is the part that reads wrong and has been re-derived wrongly
+     twice. Measured at 500px on charlie, drawer open, with the pair applied:
+     the box rests at -16 and sticks at -16, and its own `pt-4` is off-screen
+     the whole time, so the input sits flush against the top edge with no gap
+     above it at all. The negative offset does not paint into a region that is
+     never seen; below `lg` it crops the box.
+
+     So the pair belongs only where a scrollport actually has top padding, and
+     below `lg` none of the three layouts has any:
+       - charlie — never did.
+       - alpha, layouts/alpha.css:37 — `md:px-4 md:pb-4 lg:p-0`.
+       - bravo, layouts/bravo.css:45 — `px-0 pb-4 md:px-4 lg:p-0`.
+     alpha and bravo used to give their open drawer a top padding as part of
+     `p-4` / `py-4`. It was removed rather than canceled here, because the box
+     supplies that 1rem itself through `pt-4` and a drawer that has none needs
+     no offset. If you restore a drawer top padding in a layout, restore the
+     negative pair there too, at that breakpoint.
+
+     At `lg` the pair assumes exactly one 1rem above the box — `.docs-sidebar`'s
+     `pt-4` — with the layout zeroing `#docs-navigation`'s. alpha and bravo do
+     it with `lg:p-0`, charlie with `lg:pt-0`. A layout that leaves a second
+     padding in place must zero it there. Widening the margin here would fix
+     that layout and break the other three. */
+  @apply sticky top-0 lg:-top-4 mt-0 lg:-mt-4 pt-4 z-10 pb-2 mb-1 bg-(--component-bg-color);
+
+  .docs-nav-filter__field {
+    @apply relative flex items-center;
+  }
+
+  .docs-nav-filter__icon {
+    @apply fa-solid leed-icon-search absolute left-3 text-xs text-(--component-text-color)/50 pointer-events-none;
+  }
+
+  .docs-nav-filter__input {
+    @apply w-full py-1.5 pl-8 pr-8 text-sm rounded-lg bg-transparent text-(--component-text-color) border border-(--component-header-border-color)/50 focus:ring-0 focus:border-(--component-header-border-color)/50;
+  }
+
+  /* WebKit renders its own clear affordance on type="search"; the explicit
+     button is what the other engines need, and two of them side by side is a
+     confusing control. */
+  .docs-nav-filter__input::-webkit-search-cancel-button {
+    -webkit-appearance: none;
+    appearance: none;
+  }
+
+  .docs-nav-filter__clear {
+    @apply fa-solid leed-icon-close absolute right-3 cursor-pointer border-0 bg-transparent text-xs text-(--component-text-color)/50 hover:text-(--component-text-color);
+
+    /* The class above sets a `display`, which would otherwise outrank the user
+       agent's `[hidden]` rule. */
+    &[hidden] {
+      @apply hidden;
+    }
+  }
+}

package/dist/static/tailwind/docs/components/table.css

@@ -0,0 +1,54 @@
+/**
+ * Tables that scroll rather than crush.
+ *
+ * docs.css styles the table itself — margins, header rule, row rules, cell
+ * padding. What it does not decide is what happens when a table is wider than
+ * the column it sits in, and the answer until now was "crush the cells". A
+ * reference table has a width below which it stops being readable, and a
+ * narrow column takes it straight through: a flag column wrapping `--env` over
+ * two lines is a column of noise where the whole point is a value you can scan.
+ *
+ * CSS alone cannot fix it. `overflow-x` on a `<table>` only applies with
+ * `display: block`, and that shrinks the inner table box to the block's width,
+ * so the cells crush and nothing ever overflows. The element that scrolls has
+ * to be a real wrapper, and markdown emits a bare `<table>` with nothing
+ * around it — so `TableManager` in documentation.js inserts one, the same way
+ * `setupCopyButtons` wraps a `<pre>`.
+ *
+ * Everything here is therefore inert until that runs. With JavaScript off the
+ * table is exactly what docs.css leaves: readable, just narrow. Nothing is
+ * hidden by this, which is the right way to fail.
+ *
+ * Scoped to `#leed-docs-copy` — the article body doc-article.hbs and
+ * api-article.hbs both emit — so a table used for layout elsewhere in the
+ * chrome is left alone.
+ */
+.leed-documentation {
+  /* The wrapper is the thing that scrolls. The table inside keeps normal table
+     layout, so header and body columns stay aligned; that alignment is the
+     reason for a wrapper rather than `display: block` on the table.
+
+     `overscroll-behavior-x: contain` keeps a horizontal flick inside the table
+     instead of letting it become a browser back-navigation. */
+  #leed-docs-copy .table-scroll {
+    @apply max-w-full overflow-x-auto;
+    overscroll-behavior-x: contain;
+  }
+
+  /* `max-content` so the table takes the width its cells actually need rather
+     than the width it is handed, and `min-width: 100%` so a short table still
+     fills the column instead of huddling at the left edge. */
+  #leed-docs-copy .table-scroll > table {
+    width: max-content;
+    min-width: 100%;
+  }
+
+  /* Only the header row and the first column are held on one line: those are
+     the labels, and a wrapped label is worse to read than a scrollbar is to
+     use. Prose cells still wrap, so the table is only ever as wide as it
+     genuinely needs — most tables never overflow at all. */
+  #leed-docs-copy table th,
+  #leed-docs-copy table td:first-child {
+    @apply whitespace-nowrap;
+  }
+}

package/dist/static/tailwind/docs/components.css

@@ -0,0 +1,6 @@
+@import "./components/blockquote.css";
+@import "./components/button.css";
+@import "./components/mobile-bar.css";
+@import "./components/navigation.css";
+@import "./components/docs-pagination.css";
+@import "./components/table.css";