ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

3.11.7

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

libs

This release affects the contracts, sharedLibs familyies.

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

Release summaries

  • knowledge-indexed-payload-hardening

    Persist canonical knowledge payload text during indexing and align the retrieval/query docs with the corrected behavior.

    maintainer

    The knowledge ingestion/query path now persists fragment text into vector payloads, package tests cover the corrected behavior, and the knowledge doc surfaces were refreshed.

    integrator

    Consumers of `@lssm-tech/lib.knowledge` no longer need to copy fragment text into metadata for retrieval and RAG queries to work.

  • knowledge-runtime-hardening

    Complete the knowledge OSS surface with stricter guardrails and an easier runtime path.

    maintainer

    Maintainers get a stricter, better-tested knowledge package and a concrete example surface that proves the OSS path end to end.

    integrator

    Integrators can compose `KnowledgeRuntime`, use per-query overrides, rely on typed retrieval filters, and see real example usage in the knowledge-canon package.

Migration guide

  • Remove custom knowledge payload text shims

    Stop copying fragment text into metadata solely to make downstream retrieval/query flows return readable content.

    When: When a consumer previously worked around missing indexed text by injecting `text` into fragment metadata before upsert.

    1. Upgrade to the patched `@lssm-tech/lib.knowledge` release.
    2. Remove any pre-upsert metadata workaround that duplicates `fragment.text` into `metadata.text`.

  • Update flows that depended on permissive automation writes

    `KnowledgeAccessGuard` now enforces `automationWritable`, so spaces or callers that relied on writes being allowed must be updated before upgrading.

    When: When a consumer previously expected automation writes to succeed even when `automationWritable` was false.

    1. Update the affected space definition to allow the required write path, or change the calling flow so it no longer attempts that write.
    2. Verify automation-triggered write operations still succeed only for explicitly writable spaces.

  • Provide explicit scoped workflow and agent bindings

    Missing workflow or agent names no longer bypass scoped bindings implicitly.

    When: When a consumer previously omitted workflow or agent binding identifiers and relied on permissive fallback behavior.

    1. Pass the correct workflow and agent binding identifiers explicitly wherever scoped bindings are required.
    2. Re-run the affected retrieval or mutation flows to confirm the intended scope still resolves.

Upgrade steps

  • Verify indexed knowledge payloads expose canonical text

    manual

    Check that vector payloads now include `payload.text` and that retrieval/query flows surface readable snippets without custom metadata shims.

    Packages: @lssm-tech/lib.knowledge, @lssm-tech/lib.contracts-spec

    1. Re-run the ingestion flow that feeds your knowledge index.
    2. Inspect the stored vector payloads or downstream references for canonical `payload.text` content.

  • Use the higher-level runtime helper when you want a simple OSS setup

    manual

    Prefer `createKnowledgeRuntime(...)` for the common ingest, retrieve, and answer flow instead of composing every low-level primitive by hand.

    Packages: @lssm-tech/lib.knowledge, @lssm-tech/example.knowledge-canon

    1. Provide embedding and vector-store providers, plus an LLM provider if you want `query(...)`.
    2. Set `collection`, `namespace`, and either `spaceKey` or `spaceCollections`.
    3. Keep using the lower-level primitives directly when you need custom orchestration.

Unique release changes

  • - Check that vector payloads now include `payload.text` and that retrieval/query flows surface readable snippets without custom metadata shims.

    2 packages · 2 occurrences

  • - Persist canonical knowledge payload text during indexing and align the retrieval/query docs with the corrected behavior.

    2 packages · 2 occurrences

  • - Stop copying fragment text into metadata solely to make downstream retrieval/query flows return readable content.

    2 packages · 2 occurrences

  • - `KnowledgeAccessGuard` now enforces `automationWritable`, so spaces or callers that relied on writes being allowed must be updated before upgrading.

    1 packages · 1 occurrences

  • - Complete the knowledge OSS surface with stricter guardrails and an easier runtime path.

    1 packages · 1 occurrences

  • - Missing workflow or agent names no longer bypass scoped bindings implicitly.

    1 packages · 1 occurrences

  • - Prefer `createKnowledgeRuntime(...)` for the common ingest, retrieve, and answer flow instead of composing every low-level primitive by hand.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 3 changes

  • @lssm-tech/lib.knowledge

    Layer: libs · 4 changes