ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

3.8.43

May 25, 2026 · 2 packages · 4 unique changes · 2 release entries

appsbundles

This release affects the solutions family.

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

Release summaries

  • full-docs-markdown-coverage

    Serve substantive markdown for every static web-landing docs route registered through the API markdown endpoint.

    maintainer

    Static web-landing docs routes now have markdown overrides when the presentation registry would otherwise fall back to placeholder coverage.

    integrator

    `/mdx/docs/**` consumers receive substantive route markdown for docs pages such as the Drizzle database guide.

    customer

    AI and markdown readers can load full docs pages instead of placeholder links back to the interactive site.

  • mobile-expo-landing-companion

    Add a shared marketing content/navigation surface and convert the Expo demo into a native public-nav companion for the ContractSpec OSS-first story.

    maintainer

    Marketing now exposes React-free landing story, page, navigation, and CTA data through `@lssm-tech/bundle.marketing/content`, and the Expo demo consumes that content through mobile-native components and ContractSpec handlers.

    integrator

    Integrators can import shared ContractSpec landing copy, public navigation, page content, and CTA metadata from `@lssm-tech/bundle.marketing/content` without pulling web-only React components into native shells.

    customer

    The Expo demo now presents native Home, Product, Templates, Pricing, Docs, and Changelog companion routes instead of the previous task-list demo.

Upgrade steps

  • Prefer `/mdx/docs/**` for agent-readable docs context

    auto

    Existing markdown URLs continue to work and now return substantive markdown for static docs pages.

    Packages: @lssm-tech/bundle.marketing, @lssm-tech/app.api-library

    1. Keep using existing `/mdx/docs/**` URLs.
    2. Refresh cached markdown if an agent previously stored placeholder-only docs output.

  • Prefer the platform-neutral content export for native or non-web shells

    assisted

    Use `@lssm-tech/bundle.marketing/content` when a shell needs landing story, navigation, or public page data without importing web components.

    Packages: @lssm-tech/bundle.marketing

    1. Import `contractspecLandingStory`, `contractspecPublicNavigation`, or `contractspecLandingPages` from `@lssm-tech/bundle.marketing/content`.
    2. Map the exported `iconKey` strings to platform-specific icon components.
    3. Resolve CTA targets with `resolveContractspecLandingCtaUrl` when opening links outside the web app.

Unique release changes

  • - Existing markdown URLs continue to work and now return substantive markdown for static docs pages.

    2 packages · 2 occurrences

  • - Serve substantive markdown for every static web-landing docs route registered through the API markdown endpoint.

    2 packages · 2 occurrences

  • - Add a shared marketing content/navigation surface and convert the Expo demo into a native public-nav companion for the ContractSpec OSS-first story.

    1 packages · 1 occurrences

  • - Use `@lssm-tech/bundle.marketing/content` when a shell needs landing story, navigation, or public page data without importing web components.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.api-library

    Layer: apps · 2 changes

  • @lssm-tech/bundle.marketing

    Layer: bundles · 2 changes