Skip to content
← Back to changelog index

14.0.6

Oct 28, 2026 · 4 packages · 15 unique changes · 9 release entries

bundlesintegrationslibsmodules

This release affects the integrations, sharedLibs, solutions families.

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

Release summaries

  • authos-polish-pass

    Accessible AuthOS account forms, a robust code input, redirect-preserving sign-in, and context resolution without reloads.

    integrator

    PasswordField gains an optional placeholder (default none) and DS PasswordInput no longer shows the new-password placeholder on current-password fields. OrganizationWorkspaceSwitcher accepts onInitialSelection for soft first-load reconciliation. organizationGuardrails now returns Better Auth's 401/403 before any profile validation error.

    customer

    Verification codes no longer lose digits, account fields are properly labelled, signing in returns you to the page you asked for, and CompanyOS opens directly in your active context without a reload.

  • cmp-dataview-shell-delegation

    DataViewManagementShell works as an EntityWorkspace adapter and the Agent Fleet example runs fully through EntityWorkspace

    integrator

    DataViewManagementShell keeps its props and delegates to EntityWorkspace. Its edit panel for renderFormSlot, the narrow-screen detail drawer, and the filter and sort controls now respond: the shell owns that state because its props cannot control it. Hosts that pass search keep controlling it; hosts that omit it get a working search box. The detail empty state shows the spec title and description again.

    maintainer

    The shell entry is a facade over private data-view/internal/management-shell-* modules (types, state, view-mode switcher), and the shadcn registry lssm-data-views block lists them. DataViewManagementShell.delegation.test.tsx proves the delegation in a DOM; AgentFleetScreen.workspace.test.tsx proves search, filters, detail actions, delete, bulk pause and agents-prop reconciliation, and AgentFleetScreen.forms.test.tsx submits the create, edit and clone forms in the Agent Fleet example.

  • cmp-design-system-marketing-types

    Type the design-system marketing contract renderers with structural props and drop the lib.contracts-spec facade dependency

    integrator

    Source-compatible: MarketingContractLandingPage, MarketingContractDescriptorPage, MarketingContractBoundary, adaptMarketingPageContractToSections and adaptMarketingPageContractToDescriptors accept the same growth marketing page and site contracts as before. Their props are now the structural types MarketingPageContractLike and MarketingSiteContractLike (with MarketingSectionContractLike, MarketingSectionCardContractLike, MarketingCtaContractLike, MarketingPresentationBindingContractLike, MarketingContractPriority and MarketingContractSectionKind), exported from the root barrel, ./components/marketing and ./components/marketing/MarketingContractPage. They require only the fields the renderers read; section disclosure, presentation binding, priorities and the page density budget are optional. A section kind the renderers do not know renders as prose and maps to the marketing.prose descriptor primitive. The page and site fields of the exported prop interfaces (MarketingContractLandingPageProps, MarketingContractDescriptorPageProps, MarketingContractBoundaryProps) are now these structural types, so code that read growth-only fields through them (for example MarketingContractLandingPageProps['page']['narrative']) should type those values as MarketingPageContract or MarketingSiteContract from @lssm-tech/lib.growth-spec/marketing (or the facade ./marketing forward) instead. @lssm-tech/lib.design-system no longer installs @lssm-tech/lib.contracts-spec: a host that imports the facade must declare it itself.

    maintainer

    The contract prop types live in marketing/internal/contract/contract-types.ts and the known section kinds in section-kinds.ts; both mappers resolve the kind there and group unknown kinds with prose, which keeps the exhaustive switches. The emitted declarations reference neither the facade nor the growth domain, so the design-system-marketing-contract-types boundary bridge is deleted (B065, owner decision B062 item 2: structural props, no component move). bundle.marketing holds the type-level check that every growth section kind has a design-system layout and that its shipped site contracts render through registered renderers. @lssm-tech/lib.schema stays a runtime dependency (B182): the declarations of renderers/form-contract/renderer and its native twin infer FormSpec<AnySchemaModel> from @lssm-tech/lib.schema.

  • cmp-entity-workspace-interactions-a11y

    Native EntityWorkspace emits selection_changed and action_invoked through onInteraction, and the relation switcher exposes its selected option on web and native (B095, B101)

    integrator

    Optional. A native EntityWorkspace host that passes onInteraction now receives the same evidence as on web: renderer interactions, selection_changed (selectedCount and selectionScope only, never row ids or row data) and action_invoked (actionKey, actionPlacement, actionIntent) for row, header, toolbar and workbench actions. Wire it to useAdaptiveDataView's dataViewRendererProps.onInteraction to record them as data_view_interaction behavior events, as on web. Screen readers now announce the selected relation switcher option (aria-pressed on web, accessibilityState.selected on native).

    maintainer

    The native model (use-entity-workspace-model.native) now passes onInteraction to the shared selection hook and composes the shared use-entity-workspace-actions hook, which the web model already used. It returns handleInteraction (forwarded to the native DataViewRenderer by EntityWorkspace.native) and invokeAction (the placed-action handler that the native header and toolbar action bars and the workbench runAction use). handleRowAction emits action_invoked with the row placement before it opens detail for an Open action and before the host onAction runs. It stays native-only because an Open action runs even without onAction. The native RelationSwitcher imports atoms/Button.native, whose types carry the RN Pressable accessibilityState prop; the web-resolved atoms/Button types, which the .native lane otherwise typechecks against, do not.

  • cmp-entity-workspace-splits

    EntityWorkspace and DataViewDetail split into private leaves with unchanged exports, markup and behavior (B109)

    integrator

    No action. EntityWorkspace (web and native), DataViewDetail and every root and subpath export keep their names, props and rendered markup. The new modules live under internal/ directories, which tsdown excludes from the export map.

    maintainer

    The web EntityWorkspace entry renders private header, results and custom-renderer leaves. The web orchestrator mirrors the native lane: use-entity-workspace composes use-entity-workspace-model (paired with use-entity-workspace-model.native), the workbench hook and the node hook, whose regions are private row-action, result-action and header-region components. Both models compose the shared use-entity-workspace-query, -selection and -detail-state hooks (*.shared.ts); the web model adds use-entity-workspace-actions (action_invoked, sort routing, workbench runAction) and passes onInteraction to the selection hook, while the native model keeps its Open row-action routing and does not pass onInteraction yet, so native selection still emits no selection_changed evidence. DataViewDetail delegates to data-view/internal/detail/ (detail-header, detail-section, detail-relations). Every touched source file is now within the limits: the largest are use-entity-workspace-nodes.tsx (145 lines), workspace-header-regions.tsx (149) and EntityWorkspace.tsx (135).

  • cmp-fix-w9-visible-workspace-custom-renderers

    Restore visible governed custom content in canonical entity workspace regions

    integrator

    Optional projected-record content callbacks render once in canonical result and detail regions. Legacy full-entity callback signatures remain, with canonical fallback when full visibility cannot be proved. Presentation denial, hidden/depth-limited fields and action gates still narrow rendering.

    maintainer

    Agent Fleet status controls are declared actions, custom bodies are display content, and editing/cloning/deletion stay behind canonical action routing and the existing manual confirmation dialogs.

  • cmp-i18n-ui-packages-and-plan

    The design-system and auth-os built-in defaults resolve from their en/fr/es catalogs, both packages and the identity runtime, spec and rbac packages leave the hardcoded-string allowlist with their residue classified per file, and a sequenced plan covers the largest packages still listed.

    integrator

    Source-compatible. FormConfigMenuBar (landmark label) and FormConfigPanel (title, description, empty state) take their defaults from the new designSystem.organisms.formConfig.* catalog keys in the active locale, and fall back to the design-system catalog when the mounted LocaleProvider runtime lacks them, so English output is unchanged; explicit ariaLabel, title, description and emptyState props still win, and an explicit null emptyState still renders an empty box. MarketingContractLandingPage and MarketingContractDescriptorPage accept an optional locale prop, and adaptMarketingPageContractToSections(page, locale?) and adaptMarketingPageContractToDescriptors(page, bindings?, locale?) an optional locale, used only to label a disclosure link the contract leaves unlabelled (designSystem.organisms.marketingContract.disclosureCta: Learn more, En savoir plus, Más información); without it the label stays Learn more. resolveDesignSystemDefault(t, locale, key) is a new export of ./i18n/catalogs/messages. InputPassword's default reveal and conceal labels now follow the provider locale when the host runtime lacks the design-system keys (they used to fall back to English). The DataViewManagementShell delegation marker gains aria-hidden.

    integrator

    WaitlistJoinForm resolves each label the host omits, and the honeypot input's accessible name, from the authOs.organisms.waitlistJoinForm.* catalog keys for the active locale, falling back to the auth-os catalog when the mounted LocaleProvider does not carry it; hosts that pass every label (lssm-ecosystem-web, web-founder-suite-monolith, web-application-monolith) see no change except a localized honeypot name. The LSSM Passport resolveScopeCopy describes an unknown scope as Autorisation supplémentaire de l’application (fr) and Permiso adicional de la aplicación (es) instead of the English sentence; en is unchanged.

    maintainer

    scripts/i18n-allowlist.json drops packages/platform/ui/design-system and the identity module, runtime, spec and identity-rbac packages from unmigratedPackages (271 to 266) and SEEDED_BASELINE_COUNT follows. Their residue is classified per file: the designSystemFinalizeJsDocAndDevErrors category gains five files, and the new designSystemStorybookShowcase, identityPassportLocaleCopyModules, identityContractMetadata, identityDomainAndDeveloperDiagnostics and identityPendingServerRenderedCopy categories hold the rest; authOsPreviewDefaults gains the Ada Lovelace and Grace Hopper demo names. The 32 design-system paths patterns.filePaths duplicated from those categories are removed, as are the migrated WaitlistJoinForm.tsx and the AuthOsPreview.tsx entry that matched no flagged string. docs/refactoring/lssm-ecosystem/I18N-HIGH-VOLUME-PLAN.md classifies every flagged file of the seven largest unmigrated packages and sequences their migration (B143), for owner acknowledgement; its execution is follow-up work.

  • design-system-submit-form

    SubmitForm primitive for onSubmit forms that keep field values; accept-invitation form adopts it

    integrator

    Use SubmitForm from @lssm-tech/lib.design-system/components/forms for forms submitted through onSubmit (Enter submits) whose fields must survive a failed submission; ActionForm remains for React form actions.

  • design-system-template-marketing-splits

    Split persona graph templates and marketing renderers into private modules without changing public exports.

    integrator

    Existing persona template and marketing imports keep the same components, registries, surface specs, types and rendered markup.

Migration guide

  • Prefer projected record content

    Use visible field keys and stable item identity without assuming a full entity.

    1. Prefer renderResultContent/renderDetailContent for projected records.
    2. Leave complex/reference bodies absent or return nullish content for canonical fallback.
    3. Keep mutations in declared actions and recheck host authority at confirmation and commit.
  • Preserve safe legacy callbacks

    Existing full-entity signatures remain with default rendering when full visibility cannot be established.

    1. Legacy callbacks require every own entity property to be safely visible.
    2. Migrate narrowed records to projected content callbacks rather than casting partial records.
  • Declare lib.contracts-spec yourself if you relied on it through the design system

    The design system no longer depends on the @lssm-tech/lib.contracts-spec compatibility facade. Hosts that import the facade without declaring it resolved it only through hoisting.

    1. If your package imports @lssm-tech/lib.contracts-spec without listing it, add it as a dependency, or import the canonical owner instead (@lssm-tech/lib.contracts-spec-core, @lssm-tech/lib.growth-spec/marketing or @lssm-tech/lib.design-catalog/themes).
  • Optionally replace raw onSubmit forms with SubmitForm

    Additive only. Application surfaces that render a raw <form onSubmit> can adopt SubmitForm to satisfy the design-system element rule without React form-action reset semantics.

    1. Import SubmitForm from @lssm-tech/lib.design-system/components/forms and pass the existing onSubmit handler.

Upgrade steps

  • Record native selection and action evidence

    manual

    Optional. Native hosts that already record DataView interactions can add selection and action evidence.

    Packages: @lssm-tech/lib.design-system

    1. Pass onInteraction={adaptive.dataViewRendererProps.onInteraction} (or your own sink) to the native EntityWorkspace.
    2. Do not rely on onAction being called with exactly one argument from native header, toolbar or workbench actions; it now receives (action, undefined), as on web.
  • Soft-refresh after first-load context reconciliation

    manual

    Hosts of OrganizationWorkspaceSwitcher should pass onInitialSelection.

    Packages: @lssm-tech/lib.design-system, @lssm-tech/module.auth-os, @lssm-tech/bundle.managed-companyos, @lssm-tech/integration.authos-better-auth

    1. Pass onInitialSelection={router.refresh} so first-load workspace completion does not hard-reload the page.

Unique release changes

  • Accessible AuthOS account forms, a robust code input, redirect-preserving sign-in, and context resolution without reloads.

    4 packages · 4 occurrences

  • Hosts of OrganizationWorkspaceSwitcher should pass onInitialSelection.

    4 packages · 4 occurrences

  • Additive only. Application surfaces that render a raw <form onSubmit> can adopt SubmitForm to satisfy the design-system element rule without React form-action reset semantics.

    2 packages · 2 occurrences

  • SubmitForm primitive for onSubmit forms that keep field values; accept-invitation form adopts it

    2 packages · 2 occurrences

  • The design-system and auth-os built-in defaults resolve from their en/fr/es catalogs, both packages and the identity runtime, spec and rbac packages leave the hardcoded-string allowlist with their residue classified per file, and a sequenced plan covers the largest packages still listed.

    2 packages · 2 occurrences

  • DataViewManagementShell works as an EntityWorkspace adapter and the Agent Fleet example runs fully through EntityWorkspace

    1 package · 1 occurrence

  • EntityWorkspace and DataViewDetail split into private leaves with unchanged exports, markup and behavior (B109)

    1 package · 1 occurrence

  • Existing full-entity signatures remain with default rendering when full visibility cannot be established.

    1 package · 1 occurrence

  • Native EntityWorkspace emits selection_changed and action_invoked through onInteraction, and the relation switcher exposes its selected option on web and native (B095, B101)

    1 package · 1 occurrence

  • Optional. Native hosts that already record DataView interactions can add selection and action evidence.

    1 package · 1 occurrence

  • Restore visible governed custom content in canonical entity workspace regions

    1 package · 1 occurrence

  • Split persona graph templates and marketing renderers into private modules without changing public exports.

    1 package · 1 occurrence

  • The design system no longer depends on the @lssm-tech/lib.contracts-spec compatibility facade. Hosts that import the facade without declaring it resolved it only through hoisting.

    1 package · 1 occurrence

  • Type the design-system marketing contract renderers with structural props and drop the lib.contracts-spec facade dependency

    1 package · 1 occurrence

  • Use visible field keys and stable item identity without assuming a full entity.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 2 changes

  • @lssm-tech/integration.authos-better-auth

    Layer: integrations · 2 changes

  • @lssm-tech/lib.design-system

    Layer: libs · 2 changes

  • @lssm-tech/module.auth-os

    Layer: modules · 2 changes