Skip to content
← Back to changelog index

6.1.4

Nov 05, 2026 · 1 package · 4 unique changes · 2 release entries

modules

This release affects the solutions family.

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

Release summaries

  • authos-example-registry-preflight-20261102

    Separate explicit example registry generation from package build comparison.

    maintainer

    Regenerate catalog sources explicitly, then compare them during package prebuild without managed source rewrites.

  • cmp-example-import-boundaries

    module.examples adds named host ports for native previews, the Feature Hub reference and the hosted CompanyOS demo, and apps stop importing example packages directly

    integrator

    @lssm-tech/module.examples adds five subpaths. ./runtime/native-previews re-exports native-safe example contracts, visualization specs and deterministic sample data; generic example names are re-exported under example-qualified names (CRM_PIPELINE_DEALS, POLICY_SAFE_KNOWLEDGE_ASSISTANT_FIXTURES, videoDocsTerminalTutorials). ./runtime/feature-hub-reference exposes installFeatureHubCompositionReference and FEATURE_HUB_REFERENCE_ROUTE_IDS. ./runtime/companyos-ai-solutions-engineer-poc is the isomorphic hosted-demo contract, ./runtime/companyos-ai-solutions-engineer-poc/server the Node proof runtime and ./runtime/companyos-ai-solutions-engineer-poc/ui the preview component. Existing entrypoints are unchanged. Five examples join the optional peers; a host installs the examples whose port it imports.

    maintainer

    Apps never import @lssm-tech/example.* in source. mobile-monolith reads its native preview data and Feature Hub reference through the new ports, and web-landing reads the CompanyOS demo profile, proof, runtime contract, Node runtime and preview UI through them, including the route tests and the e2e helpers. The 39 accepted no-example-import findings are retired and the package-layer baseline is empty. The route boundary test mocks the server port instead of the example runtime, and the client guard test now forbids the server port and any example import. The registry generator added the five new optional peers and their Turbo build edges.

Upgrade steps

  • Regenerate example metadata before building the registry package

    assisted

    Existing generation commands retain their writes; package prebuild verifies managed outputs.

    Packages: @lssm-tech/module.examples

    1. Run bun run examples:sync-registry from a trusted repository execution context after changing example metadata or runtime ports.
    2. Review and commit the generated CLI catalog, registry preview sources, optional peers and build graph.
    3. Run bun run --cwd examples/registry check:registry before building.
    4. Keep comparison and generation execution-authority checks because both still load trusted workspace example modules.
  • Verify the example host ports

    auto

    Run the registry host-port tests, the boundary check and the consumer typechecks.

    Packages: @lssm-tech/module.examples

    1. Run bun test examples/registry/src/runtime/host-ports.test.ts.
    2. Run bun run lint:boundaries and confirm 0 accepted legacy findings.
    3. Run bun run --cwd packages/apps/mobile-monolith typecheck and bun run --cwd packages/apps/web-landing typecheck.

Unique release changes

  • Existing generation commands retain their writes; package prebuild verifies managed outputs.

    1 package · 1 occurrence

  • module.examples adds named host ports for native previews, the Feature Hub reference and the hosted CompanyOS demo, and apps stop importing example packages directly

    1 package · 1 occurrence

  • Run the registry host-port tests, the boundary check and the consumer typechecks.

    1 package · 1 occurrence

  • Separate explicit example registry generation from package build comparison.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/module.examples

    Layer: modules · 2 changes