Proto UI 0.2.0-rc.7

Proto UI 0.2.0-rc.7

Published on August 11, 2026 under the npm next channel. All 40 public packages, the v0.2.0-rc.7 tag, the GitHub prerelease, and the immutable spec snapshot share this exact release identity.

Fixed and hardened

Continuous trigger groups and Dialog hit boundaries

• Directly and continuously nested asTrigger() instances are no longer described as proxying events one way to either the outermost or innermost Trigger. They merge into one trigger group with a distinct default outer anchor, member set, default inner interaction surface, and shared semantic activation route.
• Every member retains its own behavior declarations. Semantic activation registrations converge on the current surface's shared target, while host:* listeners remain on each instance's own host root.
• Pointer activation may now enter the group semantic route only when its native hit origin is within the current surface root or its content. Hits on the extra host box of the anchor or another non-surface member are rejected instead of being redirected into a surface activation.
• This fixes ShadcnDialogClose > ShadcnButton compositions where the outer Close wrapper is wider than the inner Button and clicking the adjacent blank area incorrectly closed the Dialog. The same rule covers blank space around ShadcnDialogTrigger > ShadcnButton.
• The shared Dialog journey for Web Component, React, and Vue now verifies that blank space on the outer Trigger or Close does not activate the group, while pointer and keyboard activation on the inner Button, focus looping, and focus restoration after close continue to work.
• New group capabilities use the mergeGroup and getGroupEventTarget names. Deprecated route-owner aliases remain temporarily available to ease migration of existing host integrations.

Shadcn Tabs v4 default-style fidelity

• The default horizontal Shadcn Tabs surface now follows the project's pinned shadcn/ui v4 baseline: Root uses flex flex-col gap-2, while List uses inline-flex h-9 w-fit rounded-lg p-[3px] and no longer stretches to the container width by default.
• Trigger restores the v4 geometry, typography, and selected, hover, focus-visible, and disabled feedback, while removing pressed scaling, the extra ring offset, and the older oversized rounded surface that are absent from the baseline.
• Content returns to an undecorated flex-1 outline-none content carrier. Tabs no longer imposes a border, background, padding, or shadow; consumers that need card-like panels compose that surface inside the content explicitly.
• The Proto style CSS compiler now supports w-fit, h-fit, flex-1, shadow-sm, and the required outline tokens so the aligned prototype styles reach Web output without degrading into unsupported tokens.
• This pass intentionally covers the default variant's horizontal primary path. The line variant, vertical layout, explicit dark branch, SVG descendant rules, and complete native API/data forwarding remain tracked parity gaps.

Passive focus and documentation runtime behavior

• Web Component, React, and Vue now write tabindex="0" only when a prototype declares an actual focus surface. Disabled native controls retain tabindex="-1", while passive non-native hosts omit the attribute instead of becoming click-focusable through cleanup or nested-trigger projection.
• The documentation ThemeProvider installs the Starlight picker bridge before built-in mobile pickers can call it, keeps explicit preferences stable across system-theme changes, and no longer raises the previous fresh-load ReferenceError.
• The Base Textarea demo logger records only normalized exposed CustomEvent payloads; a bubbling native change event no longer replaces the projected event record with a duplicate, unnormalized entry.

Added and expanded

Scroll domain and Scroll Area

• A draft Scroll knowledge, decision, contract, module, host-capability, and test chain establishes that the host owns the scrolling engine, physics, inertia, and input integration, while Proto UI owns logical surfaces, facts, requests, and chrome-projection negotiation.
• Base Scroll Area catalogs Root, Viewport, Scrollbar, and a feedback-only Thumb. Web supports system and composed chrome; the family host session binds the actual Thumb as a bounded Move Gesture hit subregion and maps movement to normalized control-drag requests without creating a second scroll-state owner.
• Web Component, React, and Vue share the Scroll runtime, while Brutalist adds a Scroll Area visual projection and a cross-adapter journey. The rc.7 Scroll catalog remains draft and is not a completed stable cross-host guarantee.

Base Tooltip and Tooltip Group

• Draft Base Tooltip Root, Trigger, Content, and Group cover delayed open, hover/focus coordination, the Escape owner bridge, anchored overlay/portal projection, and group warm/cold delay windows with active-tooltip coordination.
• Accessibility relation projection is additive, so Tooltip can append its own aria-describedby token without overwriting host-authored IDREF relations.
• The first pass intentionally omits an empty Portal prototype and Arrow without a governed arrow-geometry channel. Touch long-press and input-modality suppression remain explicit deferred gaps.

CLI Brutalist preset and public prototype package

• proto-ui init --prototypes brutalist is a first-class CSS-only style preset. It writes a Brutalist theme (brutalist-theme.css with light/dark variables and the flat canary/mint/lavender/coral/sky accent palette) plus a generated Proto UI token closure scanned from official Brutalist prototype sources.
• @proto.ui/prototypes-brutalist is a public 0.2.0-rc.7 package in the 40-package BOM, published on npm under next outside the launch-commitment tier. Its exported family subpaths and generated proto-ui add entries cover the admitted Button, Badge, Card, Toggle, Switch, Tabs, Hover Card, Dropdown, Select, Dialog, Scroll Area, Separator, Skeleton, and Textarea surfaces.

Separator protocol and Skeleton visual prototype

• Base Separator now has explicit horizontal/vertical orientation, decorative-versus-semantic accessibility behavior, live post-mount projection, and no semantic-only orientation in decorative mode.
• The public Brutalist release candidate includes a Separator projection and a direct styled-only Skeleton subpath. Skeleton is passive, contentless, aria-hidden, and consumer-sized; the parent loading region retains busy state, announcements, replacement timing, and focus continuity.

Direct Badge and Card visual prototypes

• Brutalist Badge is a direct styled-only passive label with no Base counterpart. Its public accent | info | danger tones pair flat fills with their intended foregrounds, while the structural ink border and hard shadow remain invariant. It owns no status announcement, activation, pressed, selected, event, state, command, or method channel.
• Brutalist Card is a direct styled-only passive grouping surface with only Root, Header, Content, and Footer parts. Titles and descriptions remain ordinary content, while actions compose Button or Link so those children retain their own protocols.

Native Textarea protocol and Brutalist projection

• A typed static module-declaration substrate now lets a prototype declare adapter-owned host-infrastructure requirements before render without widening Template v0; authored asHooks may publish frozen requirements for explicit caller-definition reuse. The public @proto.ui/module-text-control package uses a host-neutral plain-text/multiline declaration whose current Web profile leases one native textarea across Web Component, React, and Vue.
• Base Textarea owns one contentless logical multiline editor with stable controlled or uncontrolled value ownership, normalized input/change/IME payloads, composition-safe controlled restoration, selection/cursor-preserving Web property projection, accessibility, and physical focus/blur methods. Current verification is cross-adapter evidence on one Web host and does not claim multi-host conformance.
• Brutalist Textarea inherits the complete Base protocol on that same target and adds only square lavender/ink, monospace, hard-shadow styling. It does not own form workflow, validation messaging, auto-resize, rich text, live-region announcements, or a second control.

Live Region and Async Region accessibility boundaries

• Base Live Region adds a content-preserving status/alert boundary with governed politeness and atomic props. It synchronizes role, aria-live, and aria-atomic without owning focus, events, commands, announcement timing, or replacement behavior.
• Base Async Region adds a content- and focus-preserving busy boundary. It projects aria-busy, exposes only the governed busy state, and leaves loading visuals, announcements, replacement state, and chat semantics to consumers.
• The Web accessibility projection now maps live, atomic, and busy state keys to their ARIA attributes. Both Base families have public package subpaths and proto-ui add entries; they add no package to the current rc.7 BOM.

Build and release

Executable artifacts for all 40 public packages

• All 40 public @proto.ui/* packages now produce dist/*.js and dist/*.d.ts before publication. Package exports point separately to the JavaScript runtime and declaration outputs instead of publishing .ts source as an npm runtime entry that requires a TypeScript loader.
• Every public package now has a package-local build and prepack contract. The root build:packages command builds selected packages and their upstream closure in production-dependency order, validates every export target, and runs import smoke tests in native Node ESM without loading TypeScript.
• Release staging now reuses and copies the same locally verified dist output used by development and CI instead of maintaining a second temporary compilation path that could drift.
• A generator maintains public manifest dist exports, files allowlists, and build scripts consistently. Source and tests remain repository inputs but are excluded from the default npm payload; release rehearsal validates the complete 40-package set.

Bundle, documentation, and CI feedback

• The fixed Lucide icon entry is decoupled from the full icon-registry renderer. The representative icons/x entry decreased from 119,273 B to 1,560 B gzip, preventing a single icon from transitively including the complete registry.
• Lucide Gallery now server-renders a limited initial set, reducing its English page's raw HTML by approximately 63%. The internal Demo Matrix again mounts Web Component, React, and Vue side by side for every demo to preserve fast cross-adapter acceptance; its English and Chinese routes are development-only drafts and no longer enter production documentation output or the sitemap.
• CI now computes affected public packages from the workspace production-dependency graph and enforces gzip budgets for representative package entries. main and manually triggered workflows continue to run the complete public-package validation.
• A repeatable monorepo analysis snapshot now records builds, tests, tarballs, bundles, documentation output, and package update frequency so these improvements can be audited under the same measurement method.

Documentation discovery and contributor governance

• The bilingual documentation search is now a keyboard-operable Pagefind dialog with localized idle, loading, empty, pagination, and retryable failure states; timeouts prevent index or runtime failures from leaving an endless spinner.
• The UI-library landing page is now a card-based showcase. Base, Shadcn, and Brutalist have lazy single-column component overviews, while Lucide has a searchable icon grid; the post-Badge/Card Brutalist overview contains all 14 admitted previews.
• The information-flow whitepaper includes one shared User/Maker/Other Component diagram with localized surrounding explanation, responsive presentation, and no redundant outer image frame. The shared documentation GitHub link now targets the canonical Proto-UI/Proto-UI repository.
• Repository contribution intake now records the Developer Certificate of Origin 1.1, per-commit sign-off, source provenance, AI-assistance disclosure, and a governed individual-remediation path for otherwise valid unsigned commits.
• Release metadata synchronization preserves reviewed package READMEs while verifying their exact install version and documented production dependencies, preventing curated package guidance from silently drifting from the public rc.7 graph.

Validation

• The complete workspace suite passes with 280 test files and 1,244 tests, plus 3 intentionally skipped files and 34 todo cases. Workspace and documentation type checks cover 134 Astro files with zero errors, warnings, or hints; the catalog reports 117 declarations, 160 static authoring entries, 116 cataloged P entities, zero known debt files, and one dynamic factory file.
• All 40 public packages pass production build, export-target validation, native Node ESM import smoke, staging, and npm publish --dry-run. The React tarball consumer uses 36/40 packed packages, the CLI multi-host consumer uses 38/40, and the production documentation build emits 190 pages with 188 indexed by Pagefind.
• The built Brutalist Textarea showcase was exercised in a browser across Web Component, React, and Vue. Each adapter mounts one native textarea; the route preserves native properties and accessible label/help relations, accepts uncontrolled editing, and renders the square lavender/ink, vertical-resize, hard-shadow surface.
• The protected publish-all workflow published all 40 public packages from the reviewed 692a6cfa30eae3049017d3c2b9e86d7f216e2176 commit through npm Trusted Publishing. Registry verification confirms all 40 exact versions, next tags, and integrity records; the workflow then created the Git tag, GitHub prerelease, and immutable snapshot assets.
• The development Demo Matrix was verified with 45 demos and 135 simultaneously mounted previewers, 45 each for Web Component, React, and Vue. Its English and Chinese routes are absent from the 190-page production build, sitemap, and Pagefind index; the development-only and three-adapter side-by-side policies are now covered by the 41 release tests.
• The public Brutalist library overview was exercised in real Chromium with 14/14 previews initialized, including Badge and Card, with no console, page, or request errors.

Upgrade notes

• Consumers that use public package exports do not need to change their imports, but runtime resolution now targets compiled .js and type resolution targets .d.ts. Non-public usage that imports package-internal src/*.ts paths or assumes source/tests are present in the npm payload is not a compatibility guarantee.
• Custom host integrations should migrate to the trigger-group capability names. Deprecated route-owner aliases are transitional only.

Still under validation

• Additional installation, runtime, CSS, accessibility, bundle, composition, and API findings from post-publication 0.2.0-rc.7 trials will enter a later release train.