Release summaries
cmp-facade-manifest-builder-owner
Deprecate the facade docs/manifest-builder forward in favour of the lib.typescript-runtime owner and fix the i18n diagnostics README example
integrator
Behavior-compatible: @lssm-tech/lib.contracts-spec/docs/manifest-builder still exports buildPackageDocManifest and extractModuleDocData with the canonical function identities, and still needs the optional @lssm-tech/lib.typescript-runtime peer. Both exports are now marked @deprecated; import them from @lssm-tech/lib.typescript-runtime/docs-manifest-builder. The subpath and the optional peer are removed at the next major of @lssm-tech/lib.contracts-spec.
maintainer
The facade docs:manifest producer imports the tool owner directly, so no package tooling routes through the deprecated forward. The facade-docs-manifest-typescript-tooling boundary bridge keeps its two exact edges (optional peer and deprecated forward) and now exits only at the facade major. The translation-diagnostics README example uses a package-relative catalogDir.
compat-declaration-canonical-forwarding
Preserve historical declaration compatibility through canonical forwarding
maintainer
Reproduce historical declaration forwards and verify type augmentation and runtime parity.
explicit-contracts-spec-entries
Explicit ContractSpec build roots preserve existing compatibility surfaces
maintainer
Canonical package entries and frozen exports separate private implementation discovery from public compatibility.
facade-typescript-runtime-optional-peer
The contracts-spec facade no longer installs the TypeScript compiler; docs/manifest-builder needs an optional peer
integrator
Only consumers of
@lssm-tech/lib.contracts-spec/docs/manifest-builderare affected: they must add@lssm-tech/lib.typescript-runtimeto their own dependencies. All other subpaths behave identically and stop pulling the compiler into production installs.forms-private-module-ownership
Preserve Forms behavior and public imports through cohesive private modules
integrator
Existing Forms imports keep the same constructor, nominal registry, model signatures and runtime statements; private implementation modules add no public subpaths.
generated-compatibility-artifacts
Preserve generated compatibility export targets during production pruning
integrator
Required generated exports and declaration dependencies survive pruning.
lane-12b-facade-family-owners
Remaining facade-owned definition families move to their canonical owners with identity-preserving forwards; host, platform and domain packages stop depending on owners their layer may not use
integrator
Import the moved definitions from their owners; every former @lssm-tech/lib.contracts-spec subpath keeps working with identical objects.
legacy-model-validation-canonical-runtime
Restore Legacy model validators to their canonical runtime owner
integrator
Historical validation imports retain their optional-clock API and canonical runtime identities.
library-composition-canonical-owners
Preserve library composition and structured-data assertions through canonical ownership.
integrator
Historical composition imports retain exact handlers, schemas and registry types.
semantic-tooling-canonical-owners
Preserve semantic tooling and social publication APIs through exact canonical owner forwards.
integrator
Adopt canonical leaves while retaining historical imports and class/schema identity.
w4-ai-improvement-declaration-owner
Preserve AI-improvement contracts through a canonical orchestration declaration owner and remove the provider facade backedge.
integrator
Legacy imports retain their exact types and V2 value identities; internal provider declarations use the canonical leaf.
w4-visual-scenario-validator-owner
Preserve complete visual scenario validation through the existing canonical DesignCatalog entry.
integrator
Existing visual validator subpaths retain their exact function identities, context defaults, and ordered diagnostics; DesignCatalog provides canonical named bindings.