3.11.10

May 25, 2026 · 6 packages · 20 unique changes · 9 release entries

appsbundleslibsmodules

This release affects the sharedLibs, solutions familyies.

Run contractspec connect adoption resolve --family sharedLibs to see how it impacts your project.

Release summaries

application-shell-notification-docs
Document AppShell in-app notification adoption and refresh shell implementation prompts.
integrator
App developers now have public guidance for wiring in-app notifications through AppShell without coupling the design system to notification runtime behavior.
maintainer
Maintainers get updated copy-ready AI prompts that include library-first notification imports, shell notification props, and migration from legacy notification module imports.
byok-env-ui-kit
Add reusable BYOK and environment alias UI helpers for integration setup.
integrator
OSS consumers can render managed/BYOK credential setup blocks and monorepo-aware env alias previews from integration manifests.
maintainer
Integration UI helpers preserve redaction guarantees by displaying secret references and required status without serializing raw secret values.
cross-platform-ui-docs
Add a dedicated cross-platform UI docs page and AGENTS/rules guidance that explain how the React, React Native, runtime, primitive UI, and design-system layers stay compatible.
maintainer
Maintainers now have a dedicated website docs page, exported bundle-library docs component, and package/rule guidance for explaining the React and React Native UI layering model.
integrator
Integrators can follow one architecture-first explanation and matching agent guidance for when to use presentation-runtime-core, the React bindings, ui-kit-web, ui-kit, and the design-system layer.
customer
Website readers and AI-agent users now have a direct cross-platform UI guide instead of piecing the React and React Native compatibility story together from several separate library pages.
docs-learning-path-spec-packs
Expand the spec-pack docs into a fuller learning path across the public docs site.
maintainer
The docs bundle and web app now expose Connect, module-bundle, and Builder workbench guides as one linked learning path instead of isolated pages.
customer
Public docs readers can follow a clearer spec-pack learning path from overview pages into Connect, module bundles, and Builder workbench hosting guides.
document-object-reference-adoption
Document and link object-reference adoption and adaptive panel guidance in the public docs bundle.
maintainer
The design-system docs now cover ObjectReferenceHandler descriptors, rich properties and sections, action handlers, safe hrefs, AdaptivePanel behavior, adoption prompts, and sidebar discovery.
integrator
Downstream apps have concrete guidance for replacing inert references with ObjectReferenceHandler and using AdaptivePanel instead of direct Sheet/Drawer branching.
customer
Product teams get clearer guidance for making addresses, phone numbers, users, customers, files, and URLs actionable in responsive panels.
mobile-web-example-parity
Promote the Expo demo Examples surface to first-class navigation and reuse shared preview components so mobile and web example previews stay aligned.
maintainer
Example preview routing now uses shared catalog helpers and a reusable Agent Console preview component instead of platform-specific allowlists or bespoke mobile summaries.
integrator
Consumers can use the example preview surface metadata to provide docs, sandbox, source, LLMS, and native preview actions from one catalog.
customer
The mobile demo now shows Examples as a normal product surface and renders Agent Console with the same shared preview structure used by web.
web-landing-data-exchange-import-template-docs
Add public website docs and prompts for flexible data-exchange import templates and user column mapping review.
maintainer
Maintainers can point developers at a canonical website guide for import templates, alias matching, format profiles, codec options, and verification.
integrator
Integrators can use the public guide and prompts to accept partner CSV, JSON, or XML imports with alternate headers and localized value formats.
customer
Import-review flows can now be explained from the public docs with matched columns, required gaps, ignored source columns, and user remapping actions.
web-landing-data-view-personalization-docs
Add public docs and LLM guidance for preference-aware DataViews.
integrator
Public docs now show how to wire DataViewRenderer with resolveDataViewPreferences and trackDataViewInteraction.
maintainer
DataView personalization docs are registered in the docs manifest and mirrored into /llms package guides.
web-landing-translation-runtime-docs
Add public web docs and agent guidance for the ContractSpec translation runtime and optional i18next adapter.
maintainer
The shared docs bundle now registers a translation-runtime library guide and primary-nav entry so the public web shell can expose ContractSpec i18n guidance consistently.
integrator
Integrators can find ContractSpec-first i18n runtime, SSR/hydration, and optional i18next adapter guidance from the website docs and `/llms*` surfaces.
customer
Public docs now explain how to keep ContractSpec translations canonical while using the optional i18next adapter for downstream app interoperability.

Migration guide

Use the shell notification boundary for app integrations
Keep notification contracts and runtime helpers outside the design system, then pass render-ready notification center state into AppShell.
1. Use `@lssm-tech/lib.contracts-spec/notifications` for canonical notification contracts.
2. Use `@lssm-tech/lib.notification` for reusable schema, channel, template, and i18n helpers.
3. Keep persistence, subscriptions, delivery, and mutation logic in the host app or runtime layer.
4. Pass `ShellNotificationCenter` state to `AppShell.notifications`.
Prefer shared preview components for web/mobile example parity
Rich example previews should reuse cross-platform components through the UI kit alias layer before falling back to app-local native summaries.
When: When adding a rich mobile preview for an example package that already has a reusable React preview surface.
1. Export a focused preview subpath that does not pull web-only modules into Expo.
2. Import UI primitives through the shared UI kit boundary so Metro can map web imports to native components.
3. Keep mobile generic fallbacks only for examples without stable shared data or reusable components.
Use the import-template guide for flexible ingestion flows
Start from `/docs/guides/data-exchange-import-templates` when adding a recommended import template that still accepts partner-specific files.
1. Define a reusable template with target fields, required columns, aliases, and value-format rules.
2. Dry-run CSV, JSON, or XML files with codec options before execution.
3. Show the client mapping-review state so users can remap columns or adjust formats before import.
4. Use `/llms/lib.data-exchange-core`, `/llms/lib.data-exchange-client`, and `/llms/lib.data-exchange-server` for package-specific agent context.
Use the translation runtime guide for production i18n adoption
Start from `/docs/libraries/translation-runtime` when wiring ContractSpec translations into server, React, React Native, or i18next-backed app surfaces.
1. Open `/docs/libraries/translation-runtime` from the docs sidebar or libraries overview.
2. Use `/llms/lib.translation-runtime` when prompting agents for package-specific implementation context.
3. Keep `TranslationSpec` catalogs canonical and treat i18next resources as generated downstream adapter data.

Upgrade steps

Use the reusable credential setup block
assisted
Replace bespoke integration credential setup panels with the shared setup model and components when rendering managed/BYOK flows.
Packages: @lssm-tech/bundle.library
1. Import `IntegrationCredentialSetupBlock` or `buildIntegrationCredentialSetupModel` from `@lssm-tech/bundle.library/components/integrations`.
2. Pass credential manifests and optional workspace environment config to render requirements and target-specific aliases.
3. Pass secret references, not raw secret values, when displaying configured BYOK credentials.
Review the updated spec-pack learning path
manual
Confirm the new guide pages and cross-links appear in the expected docs navigation flow.
Packages: @lssm-tech/bundle.library, @lssm-tech/app.web-landing
1. Open the public docs overview and verify the new learning-path entries for Connect, module bundles, and hosting the Builder workbench.
2. Follow the related-page links between the spec overview, architecture references, and Studio/Builder guides to confirm the intended navigation loop.
Replace inert references with ObjectReferenceHandler
assisted
Use the documented adoption prompt and examples to find plain object references and wrap them with the shared handler.
Packages: @lssm-tech/bundle.library
1. Start with address, phone, email, user, customer, file, and URL text rendered in product workflows.
2. Model each reference as a data-only descriptor and put runtime behavior in handler props.
3. Use rich properties and sections when one object should expose multiple interaction targets.
4. Keep responsive overlays on AdaptivePanel or ObjectReferenceHandler panel props.
Verify web and mobile example preview parity
assisted
Re-run catalog, web preview, mobile preview, and Expo export checks after changing example preview wiring.
Packages: @lssm-tech/app.expo-demo, @lssm-tech/app.web-landing, @lssm-tech/bundle.library, @lssm-tech/bundle.marketing, @lssm-tech/example.agent-console, @lssm-tech/module.examples
1. Run the module examples runtime preview tests.
2. Run mobile example registry and landing handler tests.
3. Run Agent Console preview smoke tests.
4. Run an Expo export smoke check for the mobile demo.
Keep website docs and LLM guides aligned for data-exchange imports
manual
When data-exchange template behavior changes, update the package READMEs, public guide, web-landing README, and generated `/llms*` package guides together.
Packages: @lssm-tech/bundle.library, @lssm-tech/app.web-landing
1. Update the data-exchange package READMEs for package-level API behavior.
2. Update `/docs/guides/data-exchange-import-templates` for end-to-end website guidance.
3. Regenerate or verify `/llms*` package guides before release.
Use the linked DataViews and personalization docs for collection screens
manual
Follow the DataViews tutorial or runtime guide, then apply the personalization bridge from the personalization library page.
Packages: @lssm-tech/app.web-landing, @lssm-tech/bundle.library, @lssm-tech/lib.personalization
1. Open `/docs/getting-started/dataviews` for the end-to-end query/spec/render flow.
2. Open `/docs/libraries/data-views` for collection config, data depth, and renderer props.
3. Open `/docs/libraries/personalization` for preference resolution, interaction tracking, analyzer output, and agent prompts.
Keep website docs and LLM guides aligned for translation runtime work
manual
When translation runtime behavior changes, update the web docs route, package README, `/llms.txt`, and package-specific `/llms` guide together.
Packages: @lssm-tech/bundle.library, @lssm-tech/app.web-landing
1. Update `@lssm-tech/lib.translation-runtime` README for package-level API behavior.
2. Update the shared library docs page for website readers.
3. Regenerate or verify `/llms*` package guides before release.

Unique release changes

- Promote the Expo demo Examples surface to first-class navigation and reuse shared preview components so mobile and web example previews stay aligned.
5 packages · 5 occurrences
- Re-run catalog, web preview, mobile preview, and Expo export checks after changing example preview wiring.
5 packages · 5 occurrences
- Rich example previews should reuse cross-platform components through the UI kit alias layer before falling back to app-local native summaries.
5 packages · 5 occurrences
- Add public docs and LLM guidance for preference-aware DataViews.
3 packages · 3 occurrences
- Follow the DataViews tutorial or runtime guide, then apply the personalization bridge from the personalization library page.
3 packages · 3 occurrences
- Add public web docs and agent guidance for the ContractSpec translation runtime and optional i18next adapter.
2 packages · 2 occurrences
- Add public website docs and prompts for flexible data-exchange import templates and user column mapping review.
2 packages · 2 occurrences
- Confirm the new guide pages and cross-links appear in the expected docs navigation flow.
2 packages · 2 occurrences
- Document AppShell in-app notification adoption and refresh shell implementation prompts.
2 packages · 2 occurrences
- Expand the spec-pack docs into a fuller learning path across the public docs site.
2 packages · 2 occurrences
- Keep notification contracts and runtime helpers outside the design system, then pass render-ready notification center state into AppShell.
2 packages · 2 occurrences
- Start from `/docs/guides/data-exchange-import-templates` when adding a recommended import template that still accepts partner-specific files.
2 packages · 2 occurrences
- Start from `/docs/libraries/translation-runtime` when wiring ContractSpec translations into server, React, React Native, or i18next-backed app surfaces.
2 packages · 2 occurrences
- When data-exchange template behavior changes, update the package READMEs, public guide, web-landing README, and generated `/llms*` package guides together.
2 packages · 2 occurrences
- When translation runtime behavior changes, update the web docs route, package README, `/llms.txt`, and package-specific `/llms` guide together.
2 packages · 2 occurrences
- Add a dedicated cross-platform UI docs page and AGENTS/rules guidance that explain how the React, React Native, runtime, primitive UI, and design-system layers stay compatible.
1 packages · 1 occurrences
- Add reusable BYOK and environment alias UI helpers for integration setup.
1 packages · 1 occurrences
- Document and link object-reference adoption and adaptive panel guidance in the public docs bundle.
1 packages · 1 occurrences
- Replace bespoke integration credential setup panels with the shared setup model and components when rendering managed/BYOK flows.
1 packages · 1 occurrences
- Use the documented adoption prompt and examples to find plain object references and wrap them with the shared handler.
1 packages · 1 occurrences

Impacted packages

@lssm-tech/app.expo-demo
Layer: apps · 3 changes
@lssm-tech/app.web-landing
Layer: apps · 3 changes
@lssm-tech/bundle.library
Layer: bundles · 3 changes
@lssm-tech/bundle.marketing
Layer: bundles · 3 changes
@lssm-tech/lib.personalization
Layer: libs · 2 changes
@lssm-tech/module.examples
Layer: modules · 3 changes