ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

4.0.20

May 25, 2026 · 1 packages · 2 unique changes · 1 release entry

libsBreaking changes

This release affects the sharedLibs family.

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

Release summaries

  • support-bot-reliability-threshold-cleanup

    Harden support-bot runtime validation, align responder prompts with i18n, and replace the overloaded support-bot threshold config with explicit semantics.

    maintainer

    Support-bot now validates tool inputs and classifier LLM overrides more defensively, and its responder prompt/catalog wiring is aligned and covered by focused unit tests.

    integrator

    `defineSupportBot` no longer accepts `autoEscalateThreshold`; integrators must migrate to the explicit `thresholds` object and can now pass `review` directly.

Migration guide

  • Replace the old support-bot threshold field

    Required

    Migrate `defineSupportBot` calls from the overloaded `autoEscalateThreshold` field to the explicit `thresholds` object.

    When: When upgrading code that constructs `@lssm-tech/lib.support-bot` specs through `defineSupportBot`.

    1. Replace `autoEscalateThreshold` with `thresholds.autoResolveMinConfidence` when you mean the auto-response cutoff.
    2. Set `thresholds.escalationConfidenceThreshold` when you need a distinct policy escalation cutoff.
    3. Move any external review routing into the new top-level `review` field if the spec should expose queue or approval workflow metadata.

Unique release changes

  • - Harden support-bot runtime validation, align responder prompts with i18n, and replace the overloaded support-bot threshold config with explicit semantics.

    1 packages · 1 occurrences

  • - Migrate `defineSupportBot` calls from the overloaded `autoEscalateThreshold` field to the explicit `thresholds` object.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/lib.support-bot

    Layer: libs · 2 changes