@nocoo/basalt 2.1.0 → 2.1.7

package/ai/COMPATIBILITY.md

@@ -144,7 +144,7 @@ These notes cover the components, documentation, examples and palette changes in
 
 Chart gray retains its prior light/dark values. Marks use solid candy colors without contrasting outlines or shadows; their fills are not darkened. Raw candy fills can fall below 3:1 on light surfaces; use descriptive labels and `summary` / `dataAlternative` alongside them. Custom control palettes remain independent.
 
-Named Teal and Purple `Badge` variants use the Bondi and Grape control swatches with readable dark foregrounds in both themes. Their backgrounds use `--basalt-badge-teal` and `--basalt-badge-purple`, keeping named badge hues independent of the numbered chart aliases.
+Named Teal and Purple `Badge` variants use the Bondi and Grape control swatches. Solid color badges (`success`, `red`, `orange`, `teal`, `blue`, `purple`) keep white label text in both themes. Their backgrounds use `--basalt-badge-teal` and `--basalt-badge-purple`, keeping named badge hues independent of the numbered chart aliases.
 
 v2.1.0 includes the palette count and value changes above as an explicit exception to the usual minor-release compatibility policy. Consumers that index colors or persist palette choices must follow these migration notes. The unchanged export baseline alone does not prove runtime-value compatibility.
 

package/ai/INTEGRATION.md

@@ -23,6 +23,7 @@ Ship in this order. Each step has a section below. Do not skip ahead to cards.
 
 | Layer | Component | Owns | Does not own |
 |---|---|---|---|
+| Landing | public marketing route | full-width sections and document scrolling | dashboard width or scroll rules |
 | Login | app page, not `AppShell` | identity badge | rail, header, island |
 | Rail | `Sidebar` | product title, version pill, nav, user | page body |
 | Framework bar | `AppHeader` | ancestor breadcrumbs, current page name, top-right actions (`ThemeToggle`, …) | create, filters, cards |
@@ -34,9 +35,10 @@ Ship in this order. Each step has a section below. Do not skip ahead to cards.
 ### Tree
 
 ```
+LandingPage                       ← / only. Document scroll, no AppShell.
 LoginPage                         ← /login only. No AppShell.
 
-AppShell                          ← everything else
+AppShell                          ← dashboard and catalog routes
 ├── AppSkipLink
 ├── Sidebar                       ← product title + version + nav
 └── AppMain                       ← id="main-content"
@@ -51,6 +53,18 @@ AppShell                          ← everything else
 
 `AppHeader.title` is the current page in the top bar (`h1`, `text-sm`). `PageHeader.title` is the content heading (`h1`, `text-2xl`). They may use the same words. They are different roles. Do not put an icon + page name above `PageHeader` — that duplicates the bar.
 
+The landing page and its prerendered HTML share `LandingContent`. Load the site stylesheet from `index.html` so it also works without JavaScript. Scope marketing CSS to `.landing` and crawl summaries to `[data-crawl-page]`; do not set global `header`, `main`, or `footer` dimensions. Keep document scrolling available on `html`, `body`, and `#root`. `AppShell` contains the dashboard viewport, and `ContentIsland` owns its independent scroll. Give both a positioning context (`relative`) so absolutely positioned content, including screen-reader labels, stays inside the correct scroll boundary.
+
+Resolve the mobile breakpoint on the first client render. Do not briefly reserve a desktop sidebar on small screens; responsive charts would measure that narrow intermediate layout.
+
+Prerender non-root routes as `route.html` (for example, `ui/button.html`). Cloudflare's `auto-trailing-slash` handling and Vite preview serve these at the extensionless canonical URL `/ui/button`; directory index files would imply a different trailing-slash URL.
+
+Landing previews are real captures at a 1600 × 1000 viewport and 2× device scale, with 1200px variants selected through `srcset`. The large corner-tower artwork derives from the original `logo.png`; its subtle perspective motion pauses outside the viewport, in background tabs, and for reduced motion. Device tilt is off by default on mobile. Only the explicit Enable tilt button requests motion permission and starts listening; ordinary touches never request access. Horizontal dragging remains available while preserving vertical page scrolling. Calibrate tilt to the current grip and screen orientation, and keep its movement bounded. The brand card uses one rounded clip around a single painted backdrop; avoid separate inner radii, outlines, or a divider touching its bottom edge.
+
+The hero and elevated Forbidden City backgrounds each use a matched daylight/twilight pair. Generate each pair together on one 2880 × 2880 canvas, then crop at the exact horizontal midpoint into two 2880 × 1440 images. Preserve the same camera and scenery between themes. Native masters, references, prompts, and sanitized generation records live under `assets/landing/generated/`; `assets/landing/backgrounds.json` records the crop coordinates and export hashes. Keep the ambient light in a flat stacking context behind the artwork so perspective motion cannot bring it in front of the mark.
+
+The floating glass header uses an icon-only GitHub link and one light/dark theme button. Resolve the system preference until the visitor chooses a theme, then persist that explicit choice through the shared provider. The landing button switches from the currently resolved mode directly to its opposite.
+
 When `AppHeader` already has breadcrumbs, **omit** `PageHeader.breadcrumbs`.
 
 Live: `/login`, shell, first page `/data`, surfaces `/layout`. Catalog: `/ui/page-header`, `/ui/section-rule`.
@@ -765,6 +779,8 @@ When skip link, rail (260 / 68, 300ms), header `h-14`, and island are in place,
 
 Standalone login, loading, error, and landing pages use their own first-screen structure: `/login` preserves the visitor-badge composition, `/loading` is a named loading status, and `/404` and `/static-page` have independent headings. Library reference pages use their document heading and section navigation. These are deliberate layout exceptions, not alternate application-page templates.
 
+The showcase site's library index and dashboard examples use the app-local `ShowcaseHeader` with the landing page's paired day/night mountain imagery fading into the content island. Headings and actions align with the page's content grid; the landscape reaches the island's top edge and scrolls with it. The library has a more spacious opening, dashboards use the compact variant, and reference headings carry a quieter version. The original logo remains in the navigation. This site-specific treatment does not change the package's `PageHeader` or application layout recipe.
+
 The `/forms`, `/settings`, `/data`, and `/chat` examples demonstrate local state and simulated requests, including failure/retry and cancellation. Their viewmodels own data and timers; Views own native FormData, focus, and responsive layout. Replace the local service adapter when integrating a backend. Theme selection uses the shared provider; local profile, uploads, and chat changes do not update a real account.
 
 `PageHeader` is flush on `ContentIsland`. Do not wrap it in another card. Do not put an icon row above the heading.

package/ai/USAGE.md

@@ -1,6 +1,6 @@
 # Basalt AI & Machine Usage Guide
 
-This document describes how AI code assistants, automated agents, and developers can consume `@nocoo/basalt` (v2.1.0).
+This document describes how AI code assistants, automated agents, and developers can consume `@nocoo/basalt` (v2.1.7).
 
 ---