ContractSpecContractSpec

Start with OSS

Back to changelog index

1.0.3

Aug 05, 2026 · 8 packages · 3 unique changes · 1 release entry

libsmodulesBreaking changes

This release affects the contracts, sharedLibs, solutions familyies.

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

Release summaries

  • economic-evidence-first-class-adoption

    Make usage, cost, budget, replay, and projection evidence first-class across cost tracking, contract operations, AI provider/model/agent/chat runs, Builder workflow replay packets, and safe observability sinks.

    maintainer

    Economic evidence is now the required neutral helper/seam spine for usage-based AI-native workflows. AI chat, AI-agent lifecycle, contract/database runtime, Builder workflow replay, and observability sinks are automatically wired by safe refs instead of direct cross-package execution dependencies.

    integrator

    Persist and forward economic evidence refs emitted by helper/seam surfaces from AI chat, AI-agent runs, contract operations, database mutations, cost tracking, Builder workflow replay packets, and observability sinks. Projection refs are safe review/display inputs only.

Migration guide

  • Adopt neutral economic evidence refs

    Required

    Replace direct billing/finance/provider coupling in runtime surfaces with refs emitted by @lssm-tech/lib.economic-evidence and package-specific bridge helpers.

    1. Use cost-tracking economic evidence bridge helpers for existing cost samples and budgets.
    2. Attach contract operation/database economicEvidenceRefs when runtime work emits usage or cost evidence.
    3. Use ai-providers and ai-agent economic evidence helpers for provider/model/token/tool run evidence.
    4. Use ai-chat route callbacks/message metadata and builder-runtime replay sink serializers to aggregate chat usage and workflow replay packets.
    5. Treat billing, finance, observability, and replay projections as review/display refs, not execution commands.

Upgrade steps

  • Review economic evidence adoption

    manual

    Verify consumers persist evidence refs from the helper/seam surfaces and do not bypass the neutral economic evidence spine.

    Packages: @lssm-tech/lib.economic-evidence, @lssm-tech/lib.cost-tracking, @lssm-tech/lib.ai-agent, @lssm-tech/module.ai-chat, @lssm-tech/lib.builder-runtime

    1. Run package tests/typecheck/build for affected surfaces.
    2. Run `bun run check:automatic-economic-evidence-wiring` to enforce the automatic three-lane vertical proof.
    3. Review migration paths for any consumer persisting provider receipts, invoices, or raw prompts directly.

Unique release changes

  • - Make usage, cost, budget, replay, and projection evidence first-class across cost tracking, contract operations, AI provider/model/agent/chat runs, Builder workflow replay packets, and safe observability sinks.

    8 packages · 8 occurrences

  • - Replace direct billing/finance/provider coupling in runtime surfaces with refs emitted by @lssm-tech/lib.economic-evidence and package-specific bridge helpers.

    8 packages · 8 occurrences

  • - Verify consumers persist evidence refs from the helper/seam surfaces and do not bypass the neutral economic evidence spine.

    8 packages · 8 occurrences

Impacted packages

  • @lssm-tech/lib.ai-agent

    Layer: libs · 3 changes

  • @lssm-tech/lib.ai-providers

    Layer: libs · 3 changes

  • @lssm-tech/lib.builder-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.contracts-runtime-core

    Layer: libs · 3 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 3 changes

  • @lssm-tech/lib.cost-tracking

    Layer: libs · 3 changes

  • @lssm-tech/lib.economic-evidence

    Layer: libs · 3 changes

  • @lssm-tech/module.ai-chat

    Layer: modules · 3 changes