Release summaries
adaptive-object-reference-panel
Promote object-reference detail panels to a reusable adaptive sheet/drawer surface.
maintainer
Design-system now exposes AdaptivePanel as the shared responsive sheet/drawer primitive and wires object-reference details through it.
integrator
ObjectReferenceHandler supports same-page vs new-page detail opening, rich nested properties, and configurable sheet/drawer behavior with responsive defaults.
customer
Reference interactions can show richer details in a desktop sheet or mobile drawer without custom per-screen logic.
adaptive-panel-menu-migration
Route design-system mobile menu overlays through the shared AdaptivePanel primitive.
maintainer
Header and marketing header mobile menus now use AdaptivePanel instead of direct sheet composition, leaving sheet/drawer primitives behind the shared overlay adapter.
integrator
Design-system overlay behavior is more consistent because mobile menu panels and object references share the AdaptivePanel boundary.
customer
Mobile menus keep the same behavior while using the shared responsive panel implementation.
agent-workflow-ui-enhancements
Enhanced agent-workflow-command-center with comprehensive UI interactions
maintainer
Enhanced agent-workflow-command-center with comprehensive UI interactions including CRUD operations, workflow builder, review queue, and real-time dashboard.
customer
Users get enhanced UI with full CRUD operations for agents, workflow builder with templates, review queue with actions, and real-time dashboard with widgets.
application-shell-navigation
Add design-system application shell primitives with typed navigation, command search, breadcrumbs, native bottom-tab adaptation, and PageOutline support.
maintainer
Design-system maintainers now have a focused shell API for application frames, navigation sections, breadcrumbs, commands, and page outlines.
integrator
Web and Expo app developers can adopt AppShell and PageOutline from the shell subpath while existing AppLayout, AppSidebar, AppHeader, NavLink, and NavSection imports remain supported.
customer
Documentation readers get public library docs with copy-ready AI prompts for fresh application shell implementation and existing-app refactors.
appshell-notification-layout
Fix AppShell desktop sidebar collapse/layout and web notification dismissal behavior.
integrator
AppShell now keeps the desktop topbar inset beside the sidebar, exposes a shared sidebar collapse trigger, and dismisses the web notification panel on outside click, Escape, or trigger toggle.
atomic-marketing-design-components
Add design-system-owned marketing CTA, hero, prose, icon-grid, proof, CTA-band, and landing-page section sequence components; keep bundle.marketing section subpaths as compatibility shims.
integrator
Consumers can import full-page marketing composition primitives from the design-system root or focused marketing subpaths. Existing bundle.marketing section subpaths continue to render via thin wrappers.
agent
Marketing story/copy stays in bundle.marketing; generic atoms, molecules, sections, and the closed landing-page section union now belong in lib.design-system. Do not add runtime personalization or bundle imports to DS marketing components.
atomic-marketing-design-foundation
Add design-system-owned full-page marketing sections and route CompanyOS landing composition through bundle compatibility shims.
maintainer
Generic marketing page primitives, sections, and a typed landing-page renderer now live in the design system while bundle.marketing retains content ownership.
integrator
Existing bundle marketing section subpaths remain compatible while new pages can compose design-system MarketingPageSection objects.
atomic-marketing-design-system-foundation
Add a design-system-owned full-page marketing component foundation and keep bundle.marketing CompanyOS section imports compatible through thin adapters.
maintainer
lib.design-system now owns generic marketing CTA, hero, prose, icon-grid, proof-strip, CTA-band, and typed landing page section composition exports. bundle.marketing keeps public section subpaths available as compatibility adapters from LandingCta/content models into generic DS models.
integrator
Existing bundle.marketing section imports continue to resolve. New DS marketing exports are additive and should be used for product-neutral full marketing page composition.
billing-os-ui-uplift
Add BillingOS UI uplift — Cluster A + B ports, presenter seam, atoms, molecules, and templates.
maintainer
Seven new DS atoms (MoneyInput, PercentInput, AutocompleteCombobox, FieldLabel, FieldHint, FieldError, UndoToast) are exported from the lib.design-system root. billing-spec gains a ./contracts subpath with two search query contracts and a registry (8 entries total after Phase 3 status-transition contracts: InvoiceStatusTransitionContract, PaymentReconcileContract, ReviewDecisionContract). billing-runtime gains a ./fixtures-rich subpath with rich test fixtures. billing-os gains ports interfaces, a PortsProvider/usePorts React API, a spec→view-model presenter seam with documented losses, money/validator utilities, 6 new molecules, 4 new templates, atomic-layer barrel re-exports, QuoteEditor uplift (Phase 2), and Phase 3 other-surfaces uplift: 3 new state hooks (useInvoiceCard, usePaymentCard, useReviewItemCard), 2 new JSX-only organisms (InvoiceLineItemsSection, PaymentReconciliationPanel), refactored JSX-only organisms (InvoiceCard, PaymentCard, ReviewItemCard), all 6 workspace screens wrapped in BillingPageShell + WorkspaceHeader, and extended presenter losses for invoice and payment surfaces.
integrator
All existing consumer imports continue to resolve unchanged. New molecules, templates, hooks, and organisms are additive. The presenter seam documents which spec fields are dropped (losses array) so integrators can decide whether to map them in a later phase. Port interfaces must be wired through PortsProvider before the new autocomplete pickers operate. Status-transition actions (invoice, payment, review) are now contract-backed via billingContracts.
comm-os-cross-surface-consolidation
Move CommunicationOS composite presentational components from lib.design-system to module.communication-os (CommOsLegacyComposites).
maintainer
The design-system no longer owns CommunicationOS composite components. They live in the module layer where they have domain context. CI lint now enforces the old path is not re-imported.
integrator
Import CommunicationWorkQueue, CommunicationThreadTimeline, SourceEvidenceList, ReplyDraftReviewPanel, PolicyDecisionBanner, HandoffPacketCard, ActionCandidateList, IdentityLinkReviewCard, and ChannelCapabilityMatrixView from @lssm-tech/module.communication-os/ui instead of @lssm-tech/lib.design-system/components/communication-os.
commos-design-system-overlap
Migrate CommOS composite components out of lib.design-system into module.communication-os/ui (G010)
maintainer
The nine CommOS composite components previously under @lssm-tech/lib.design-system/components/communication-os are migrating to their canonical home in @lssm-tech/module.communication-os/ui. This changeset records the library-level impact. The G010 changeset records the module-level additions. Import from @lssm-tech/module.communication-os/ui for all new and migrated consumers. PENDING: If G010 removes the design-system subpath without a shim, this changeset must be reclassified as major/breaking and this release.yaml updated (isBreaking: true, releaseType: major) before the release is cut.
customer
CommOS UI components should be imported from @lssm-tech/module.communication-os/ui. The @lssm-tech/lib.design-system/components/communication-os import path is being deprecated and will be removed in an upcoming release.
companyos-marketing-narrative-atomic
Improve the CompanyOS marketing surface with clearer governed-execution positioning and a reusable atomic, prop-driven section component set for hero, CTA, button row, and prose sections. CompanyOsLandingPage now composes those shared sections and renders the previously hidden built-on/studio block with Vision and Platform up-links.
maintainer
design-system owns the prop-driven marketing section primitives: CtaButtonRow, MarketingHero, MarketingCtaBand, ProseSection, and IconGridSection. bundle.marketing keeps compatibility subpath re-exports from @lssm-tech/bundle.marketing/components/marketing/sections. CompanyOsLandingPage is recomposed from the shared sections and external CTAs render with target="_blank" rel="noopener noreferrer".
integrator
The change is additive. Existing bundle.marketing imports continue to resolve; the preferred neutral imports now come from @lssm-tech/lib.design-system and the bundle subpaths remain optional compatibility shims and intended for composing CompanyOS marketing surfaces with the refreshed governed-execution narrative.
data-table-ux-stability-upgrade
Harden the shared data-table stack and add a first-class composed toolbar for search, filter chips, selection summary, and hidden-column recovery.
maintainer
The shared table controller now sanitizes stale row and column state, and the design-system exports `DataTableToolbar` as the preferred composed UX layer above the primitive tables.
integrator
Integrators can adopt `DataTableToolbar` without changing the underlying `DataTable` or `useContractTable` API, and server-paginated tables now behave more defensively when data, columns, or totals change.
customer
The CRM and canonical data-grid examples now expose search, filter chips, selection summaries, safer column recovery, and less failure-prone table interactions across web and native paths.
dataview-entity-workspace-uiux-uplift
Token-correct, animated, skeleton-aware UI/UX uplift for DataViewRenderer and entity-workspace, plus a native worklet build fix.
maintainer
New theme-aware semantic status tokens (success, warning, info, each with a -foreground) are added to ContractSpecEditorialTheme in lib.contracts-spec — across the ThemeSpec light/dark token maps and all four CSS-var export objects (hex Css, dark Css, HSL, dark HSL) — and registered in the design-system v3 Tailwind config plus the web-landing, web-application-monolith (hex/@theme inline), and mobile-monolith (HSL triplet/@theme) app globals. The theme-contract tests in both monoliths enforce parity. danger continues to map to the existing destructive token. Light-mode warning (#905a18) and info (#2b6688) values are tuned to clear WCAG AA 4.5:1 on tinted (bg-*/12) card surfaces. Design-system components are migrated off raw Tailwind palette colors (emerald/amber/sky/zinc) onto these tokens: EntityEvidenceBlock, EntityMetricStrip, CopyButton, and the entity workbench-strip (web + native). CopyButton now emits an emitActionFeedback success/error toast via the canonical feedback infra. DataViewRenderer gains a view-aware loading skeleton (list/grid/table/detail, derived from the resolved view mode) on web and native; EntityMetricStrip gains an additive loading prop with placeholder cards, wired through EntityWorkspace's effectiveLoading. Motion is motion-safe/motion-reduce gated throughout (result-card hover lift, staggered skeleton entrance, copy zoom-in).
integrator
All existing imports and prop contracts resolve unchanged; the work is additive (new EntityMetricStrip `loading` prop, new DataViewLoadingState `variant`) plus a default visual restyle. Consumers using the design-system status tones inherit the new theme-aware colors automatically. Apps that maintain their own copy of the editorial CSS variables must mirror the new --success/--warning/--info (+ -foreground) vars to render the tones correctly (already applied to the three in-repo app globals). The tool.bun change makes the `native` build target ship unminified so reanimated `'worklet'` directives are preserved; rebuild any package that ships react-native worklets to benefit.
customer
Data views and entity workspaces look more consistent and polished: status colors adapt to light/dark themes with accessible contrast, copying a value shows a confirmation toast, lists/grids/tables/detail panels show shape-matched loading skeletons instead of blank space, and subtle motion respects reduced-motion preferences. On native, gesture-driven panels (swipe-to-dismiss detail panel) run smoothly on the UI thread again.
dataview-renderer-split
Split DataViewRenderer.tsx into per-kind modules for extensibility.
maintainer
DataViewRenderer.tsx (809 lines) and DataViewRenderer.native.tsx (776 lines) are replaced by 13 focused modules. All public exports, props, and runtime behavior are preserved. New DataViewRendererSwitch with fallback prop enables adding graph/timeline kinds in Phase 3 without touching the orchestrator files.
integrator
No API changes. DataViewRenderer still exports the same props interface and renders the same output. Import paths from @lssm-tech/lib.design-system are unchanged.
design-system-adaptive-panel-native-behavior
Native AdaptivePanel now honors mode/side/direction props, adds gesture swipe-to-dismiss, focus trap + accessibilityViewIsModal + dialog role, tokenized styles, and reduced-motion-gated spring/slide. Previously these props were declared but ignored.
integrator
BREAKING (native only) — the native AdaptivePanel previously ignored mode/mobileMode/desktopMode/breakpoint/sheetSide/drawerDirection (no-ops) and rendered a fixed bottom sheet with a stray always-visible, inert trigger. It now resolves the mode via useResponsive.native, slides from the resolved side/direction, supports react-native-gesture-handler swipe-to-dismiss (fires onOpenChange(false)), traps focus with accessibilityViewIsModal + a dialog role and returns focus on close, tokenizes the scrim/radius/max-height, and gates motion on reduced-motion. The `trigger` prop is now optional and, when provided, is rendered as a button that calls onOpenChange(true) on press (web Radix Sheet/Drawer parity) instead of an inert sibling; omit it for fully host-controlled panels. Any native consumer that passed these props will now see active behavior.
agent
Web AdaptivePanel is unchanged in behavior (Radix Sheet/Drawer) aside from tokenized max-height. The breaking change is scoped to the React Native lane.
design-system-codeblock-actions
Add an opt-in download action and grouped action toolbar to the design-system CodeBlock.
maintainer
CodeBlock actions are now grouped in a token-aware toolbar, with copy preserved and an additive opt-in download action.
integrator
Consumers can enable code downloads with `showDownloadButton`, customize the saved filename with `downloadFilename`, and observe initiated downloads through `onDownload`.
design-system-codeblock-dual-theme
Consolidate CodeBlock syntax highlighting on the design-system molecule with Shiki dual-theme support.
maintainer
The shared CodeBlock molecule now owns Shiki dual-theme rendering and ContractSpec/Tailwind token framing; web landing no longer carries a duplicate CodeBlock implementation.
integrator
Apps can use the design-system CodeBlock for syntax highlighting that follows the standard `.dark` application theme and can override the light/dark Shiki theme pair through props.
design-system-codeblock-metadata
Add optional description and comment metadata slots to the design-system CodeBlock.
maintainer
CodeBlock can now carry filename-adjacent descriptions and footer comments without app-local wrapper text.
integrator
Use `description` to explain what a snippet is and `comment` to attach provenance, replay, safety, or interpretation notes.
customer
Evidence receipt code samples now include their replay context directly in the code block.
design-system-core-hardening
Add focused design-system subpaths and harden ThemeSpec runtime, Tailwind bridge, form-control helpers, and form renderer internals without changing root-import compatibility.
maintainer
Maintainers now have smaller internal design-system modules and focused subpaths for theme, controls, forms, layout, and renderers.
integrator
Integrators can keep root imports or adopt focused subpaths such as `@lssm-tech/lib.design-system/theme` and `@lssm-tech/lib.design-system/forms`.
customer
Contract-rendered forms and themed controls keep the same behavior while the design-system internals become easier to maintain.
design-system-dataview-native-uplift
Restore silently-dropped native DataView render props, replace Unicode mode-switcher glyphs with real icons, honor native field actions, add renderer-level empty/loading defaults with skeletons, and route FiltersToolbar copy through i18n.
integrator
Native DataViewRenderer now forwards renderFieldValue / getFieldClassName / getFieldLabelClassName / row-selection props (previously dropped at the native switch), renders real lucide-react-native mode icons (LayoutGrid/Table/List) instead of Unicode glyphs, honors intelligent field actions via the shared resolveFieldActionsPolicy (no longer hardcoded "hidden"), and provides renderer-level empty/loading defaults with animated skeletons. FiltersToolbar search/clear/remove copy is routed through resolveTranslationString (default English, localizable) instead of hardcoded French.
agent
fieldActions.shared.ts exposes the pure resolveFieldActionsPolicy(field,value,density,hostPolicy) resolver (guard precedence hidden->blocked->destructive->approval->auto; compact density trims copy) consumed read-only by both web and native field-action paths.
design-system-diffblock
Add a ContractSpec-owned DiffBlock molecule for web and native diff review surfaces.
maintainer
DiffBlock is now owned by the design-system package, exposing a shared diff review primitive for web and native surfaces.
integrator
Consumers can import DiffBlock from the design system instead of reimplementing diff layout per surface.
design-system-entity-workspace-uplift
Split EntityWorkspace web+native into internal modules, close native tone/feature parity, unify field rendering through a shared descriptor, add reduced-motion-gated micro-interactions, and render the detail empty-state inline in the master-detail pane.
integrator
EntityWorkspace public entries are unchanged; native now reaches parity — EntityMetricStrip/EntityEvidenceBlock gain tone coloring + useThemedPrimitive, the native results toolbar (search/filters/sort), toolbarActions, personalization, and renderDetail are wired, and native cards gain a reduced-motion-gated press micro-interaction. The web detail "select a record" empty-state now renders inline beside the list (no longer hidden behind a closed drawer when nothing is selected).
agent
Web and native field rendering are unified through internal/field-render.shared resolveEntityFieldDescriptor (descriptors, not JSX); the native NativeEntityDetail/NativeDetailField/formatNativeFieldValue reimplementation is removed. denial-token/redaction handling is shared across platforms.
design-system-select-groups
Add grouped option support to design-system Select controls across web and native.
maintainer
The design-system Select wrappers now share grouped-option normalization and expose a typed grouped Select API.
integrator
Existing flat Select options keep working, while callers can opt into translated grouped option sections on web and native.
customer
Select controls can now present options in labelled groups consistently across web and native surfaces.
design-system-themed-controls
Add a ThemeSpec-aware and TranslationSpec-aware design-system form/control layer with stack primitives, exported control wrappers, and FormSpec renderer alignment.
maintainer
Maintainers now have a shared design-system control boundary for forms, stacks, themes, translations, and FormSpec rendering.
integrator
Integrators can import themed and translated controls from `@lssm-tech/lib.design-system` instead of reaching into web or native UI kit primitives directly.
customer
Product surfaces and contract-rendered forms can now share the same ThemeSpec-aware and TranslationSpec-aware design-system controls across web and React Native.
design-system-token-backed-entity-primitives
Add token-backed neutral EntityWorkspace metric and evidence primitive paths and align entity-surface docs.
integrator
Product shells can import neutral EntityMetricStrip and EntityEvidenceBlock subpaths with native-paired entrypoints while keeping domain copy in adapters.
agent
Entity-surface docs now recommend EntityWorkspace for product shells and keep DataViewRenderer positioned as the lower-level renderer path.
design-system-ux-uplift-foundation
Add motion/elevation/density token scales, wire CVA tone/density variants, animate native skeletons, add useMotion(.native), and declare lane-split animation peer deps.
integrator
New motion (duration/easing), structured elevation (web box-shadow + native shadow object), and density token scales flow tokens.ts -> web CSS vars (--ds-motion/-elevation/-density-*) and native tokenBridge. New ./platform/useMotion(.native) hook returns reduced-motion-gated transition config. dsBaseVariants tone/density now emit token-backed classes.
agent
Animation libraries are declared as split-by-lane peers — framer-motion is a non-optional web peer (resolves via @lssm-tech/lib.ui-kit-web); react-native-reanimated/-gesture-handler/-svg are OPTIONAL native peers so web-only consumers are not required to install them.
entity-workspace-appshell-explicitness
Require explicit EntityWorkspace and AppShell contracts across web and native design-system surfaces.
maintainer
EntityWorkspace and AppShell public props now enforce explicit host-owned state, callbacks, shell slots, and customization contracts at the type level.
integrator
Consumers must pass explicit nulls, empty collections, and no-op callbacks instead of relying on optional defaults for EntityWorkspace and AppShell.
entity-workspace-detail-navigation
Add standardized EntityWorkspace detail-page navigation action props.
maintainer
EntityWorkspace now has first-class detail-page navigation props and tests covering web/native detail panel rendering.
integrator
Hosts can pass `buildDetailPageLink` and `onNavigateToDetailPage` to render a standard full-page navigation action inside the detail panel without coupling design-system to a router.
customer
Entity detail panels can now include a consistent full-page open action across web and native apps.
entity-workspace-listing-workbench
Add cross-platform EntityWorkspace listing workbench controls with contract-aware intent resolution and host-owned side effects.
maintainer
Maintainers get additive public types and tests for EntityWorkspace workbench intent resolution without provider/runtime coupling.
integrator
App teams can use built-in EntityWorkspace create, refresh, force-sync, and cache status controls while executing concrete side effects in host adapters.
entity-workspace-native-fixes
Fix React Native EntityWorkspace open actions, collection mode rendering, icon switcher affordances, and scrollable panels.
maintainer
Native EntityWorkspace now has regression coverage for Open row actions, native collection renderer resolution, icon switcher affordances, and scrollable AdaptivePanel content.
integrator
React Native and Expo hosts get working Open buttons on result cards/rows, distinct list/grid/table modes, accessible icon mode switching, and scrollable detail/edit panels.
customer
Native entity workspaces now open records from the Open button, show different list/grid/table views, and allow long detail or edit sheets to scroll.
entity-workspace-ux
rendering and duplicate text within the entity workspace
field-label-nested-control-compat
Restore native nested-control association compatibility for FieldLabel.
integrator
FieldLabel continues to support explicit htmlFor/id bindings and again accepts controls nested directly in the label through native implicit association.
forms-option-surface-aliases
Add ThemeSpec Tailwind aliases for FormSpec option surface backgrounds.
maintainer
The ThemeSpec Tailwind bridge now emits shadcn-compatible color aliases for popover, card, and input surfaces.
integrator
Apps using generated design-system theme CSS get the color aliases expected by Radix/shadcn select and combobox primitives.
customer
Contract-rendered select and combobox option panels keep a proper themed surface instead of falling back to transparency when the app relies on ThemeSpec CSS.
forms-password-visibility-toggle
Fix FormSpec password visibility toggles so rendered password fields can reveal and re-mask values.
maintainer
The web password primitive now keeps its computed `type` authoritative over upstream input props from FormSpec renderers.
integrator
Design-system FormSpec renderers can pass legacy `type: "password"` hints without disabling the visibility toggle.
customer
Contract-driven password fields now reveal the password when the visibility toggle changes from closed eye to open eye.
forms-phone-ux-regression
Fix FormSpec phone country-select rendering to remove duplicated country adornments.
customer
Split FormSpec phone fields now show one clear country selector instead of duplicating the flag and calling code beside the select.
integrator
Design-system phone country options now honor the configured flag/calling-code display parts, while the selected country control owns those adornments in select mode.
m3-design-system-template-prop-shapes
M3 — Breaking template prop shape changes across all 5 graph templates (remove onAction/isLive/time-scrub M2 props; add onDrilldown(node), p6, p7 tunnels). Density-state auto-shift. M3 engineer/manager signature treatments.
maintainer
All five graph templates have updated prop shapes. Remove M2 props (onAction, isLive, liveLabel, onRestoreView, steps, snapshotCursor, snapshotTimestamps, onScrub) and add M3 equivalents (onDrilldown, p6, p7).
integrator
Any code rendering WorkflowDagView, AgentTreeView, ConversationGraphView, EngineeringLoopView, or PersonActivityView must be updated to the M3 prop surface. onAction is removed; use onDrilldown(node). Time-scrub props replaced by TimeScrubber component.
customer
Graph template surfaces now support export, annotation, story-mode (via p6) and AI interaction (via p7). Analysis-mode triggers a visual density shift for richer exploration.
managed-companyos-responsive-ux-hardening
Harden Managed CompanyOS mobile/desktop theming, localization, touch targets, accessible naming, reduced motion, production-only tooling isolation, and smart-meeting browser proof.
customer
Personal and multi-company users receive a touch-safe, localized, light/dark CompanyOS planning flow from context selection through an approved Google Meet.
integrator
Existing design-system and web UI-kit APIs remain compatible while buttons, selects, narrow shell headers, and destructive states gain safer accessibility defaults.
maintainer
A deterministic Playwright matrix covers en/fr/es, light/dark, 320/375/768/1280px, 1/3/4/20 contexts, team choices, Axe checks, target sizes, overflow, and approval-to-Meet scheduling. A production-binary suite adds keyboard-only completion, visible focus, reduced motion, and a 200%-reflow proxy through the real Better Auth branch.
marketing-rich-components
Add prop-driven marketing components (pricing calculator, pricing table, FAQ, testimonial, lead-capture, feature tabs, timeline, trust badges, video, announcement bar) with documented marketing subpath exports.
integrator
The design system exposes new prop-driven marketing components — pricing calculator, pricing table, FAQ, testimonial, lead-capture, feature tabs, timeline, trust badges, video, and announcement bar — through documented marketing subpath exports for composition in marketing and product surfaces.
maintainer
Additive, prop-driven components composed from existing design-system primitives. No existing exports change; the new surfaces are reachable via the documented marketing subpath.
mega-menu-duplicate-link-keys
Prevent duplicate React keys in design-system mega-menu panels with repeated link destinations.
maintainer
MegaMenuPanel now keys repeated destination links by column, position, href, and label fallback instead of href alone.
integrator
Marketing navigation menus can include multiple entries that intentionally route to the same page without React duplicate-key warnings.
customer
Marketing menu rendering is more stable when several solution cards link to the same page.
mobile-appshell-native-uplift
Native AppShell renders a single Expo Router NativeTabs navigator, removes the native header/notifications/menu chrome, and sources tab-bar colors from the active design-system theme.
integrator
BREAKING (native only) — AppShell.native now renders ONLY the `expo-router/unstable-native-tabs` navigator. The native header (`AppHeader`), the notification bell, the overflow menu, and the `children`/`aiPanel` slots are no longer rendered on native; this also removes the prior double-navigator mount (NativeTabs + a sibling Stack). `AppShellProps` is unchanged and all props remain accepted and crash-free, but `brand`/`logo`/`title`/`notifications`/`commands`/`userMenu`/`children`/ `aiPanel` now render nothing on native. Mount AppShell.native from an Expo Router layout whose direct child route files match the primary tab triggers, and wrap the app in `DesignSystemThemeProvider` + `SafeAreaProvider`.
maintainer
AppShell.native is reduced to a header-less single-navigator component; tab triggers come from the governed `buildNativeTabDescriptors` mapping with `{sf, md}` native icons. Tab colors derive from `useDesignSystemTheme()` (falling back to `defaultTokens`): `iconColor`/`labelStyle` use `{default: mutedForeground, selected: primary}`, Android `tintColor`/ `indicatorColor` = primary, badge colors from primary/primaryForeground. `rippleColor` was removed because the editorial `muted` token is a `color-mix()` CSS string that React Native cannot parse. Web AppShell and `AppShellProps` are untouched.
customer
The mobile app no longer shows an empty bar at the top; primary navigation is a themed bottom tab bar with visible icons and a clear active/inactive state that respects safe-area insets.
native-appshell-tabs
Replace native AppShell custom bottom tabs with Expo Router NativeTabs layout-adapter behavior as a breaking native-shell behavior change.
integrator
Native AppShell now expects Expo Router layout usage and renders primary navigation through `expo-router/unstable-native-tabs` instead of the design-system custom BottomTabs row.
maintainer
AppShell native tab mapping is governed by `AppShell.native-helpers.ts`; unsafe primary tab hrefs fail fast and the public BottomTabs export remains available for non-shell consumers.
native-design-system-platform-suffix
Migrate design-system platform implementation suffixes from `.mobile` to `.native`.
integrator
Design-system platform variants now use Metro's standard `.native` suffix and no longer publish `.mobile` subpaths.
maintainer
Package exports, registry metadata, and cross-platform UI docs now describe `.tsx` / `.native.tsx` renderer pairs.
native-entity-workspace-private-build
Emit private EntityWorkspace implementation files for Expo/React Native bundles without exposing internal package subpaths.
maintainer
Design-system internal split modules now build into dist for relative imports while the build tool can filter private files from generated exports.
integrator
Expo consumers resolving @lssm-tech/lib.design-system/components/entity-workspace no longer fail on missing native internal hook files.
native-form-renderer
Add a React Native FormSpec renderer variant for contract-driven mobile screens.
maintainer
The design-system form-contract renderer now has native conditional exports and native slot wiring while preserving the existing web renderer.
integrator
React Native hosts can import the form-contract renderer through native package conditions or explicit `.native` subpaths to render FormSpec screens with design-system native controls.
customer
Contract-driven forms can now appear in mobile/native screens using the same FormSpec surface as web forms.
notion-page-outline
Improve PageOutline desktop behavior with a Notion-like floating rail, and hide the AppShell page outline on small web screens to preserve layout stability.
integrator
AppShell consumers get a floating desktop PageOutline that no longer reserves a right content column, while small web screens hide the outline instead of rendering a compact dialog.
maintainer
Design-system maintainers can opt PageOutline into a floating variant while preserving existing rail and compact variants for direct component usage.
object-reference-handler
Add an extensible design-system object reference handler for actionable references.
maintainer
The design-system package now exposes a public object-reference component group with schema-friendly descriptors, runtime action handlers, and paired web/native implementations.
integrator
Product surfaces can replace inert addresses, phone numbers, users, customers, files, URLs, and custom references with one extensible interaction surface.
customer
Reference text can now offer quick actions such as copy, open, call, or maps navigation from a consistent interaction surface.
rich-reference-breaking-release
Rich-reference foundation — single coordinated release across 11 packages (S-0..S-13). See MIGRATION.md at the repo root.
maintainer
11-package coordinated release lands the rich-reference foundation. AC-17 release gate enforced via `.github/workflows/rich-reference-migration-gate.yml`.
integrator
Downstream consumers must run the bundled codemods (`@lssm-tech/tools.contractspec-codemods`) before bumping the 11 listed packages in lockstep. Chrome props (`filename`, `description`, `showDownloadButton`) are dropped on migrated `<CodeBlock>`/`<DiffBlock>` callsites — re-add per the patterns in `packages/tools/contractspec-codemods/MIGRATION.md`.
studio-rsc-i18n-boundary
Fix the CompanyOS /autonomous-company-studio production SSR failure by making i18n hook consumers explicit client boundaries and adding a provider-free global error fallback for App Router production rendering.
maintainer
The Autonomous Company Studio route now renders through production SSR without invoking LocaleContext hooks from a Server Component graph.
integrator
Design-system i18n hooks and marketing components that consume them now carry explicit client boundaries, making RSC misuse fail closed instead of producing a production-only useContext runtime error.
unified-design-system-tabs
Add a unified design-system Tabs primitive and migrate local tab consumers away from ui-kit leaf imports.
maintainer
Maintainers can expose tabbed product surfaces through the design-system root instead of choosing between web and native UI-kit tab APIs.
integrator
Integrators can use one `Tabs` API with optional `value`, `defaultValue`, and `onValueChange` props across web and native surfaces.
customer
Example dashboards and execution consoles keep their existing tabbed UX while using the cross-platform design-system primitive.