Back to changelog index

0.4.5

Aug 05, 2026 · 2 packages · 2 unique changes · 1 release entry

appsbundles

This release affects the solutions family.

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

Release summaries

  • agent-all-in-one-reference-examples

    Add complete Release Steward and Company Intelligence Scout examples with multi-agent execution, governed self-improvement, durable loops, replaceable provider ports, candidate qualification, and public all-in-one guides.

    integrator

    Consumers can start from two complete, credential-free agent scenarios and replace discovery, rendering, outreach, repository, data, worker, and deployment ports according to infrastructure, budget, security, and residency requirements.

    maintainer

    Maintainers can exercise deterministic lifecycle, replay, approval, safety, privacy, rollback, and candidate-qualification evidence before running live suites against an exact environment.

Upgrade steps

  • Choose and adapt an all-in-one reference agent

    manual

    Start with the release migration or public-web intelligence scenario, then bind only the provider ports and autonomy allowed by the consumer's policy.

    Packages: @lssm-tech/example.agent-application-foundation, @lssm-tech/bundle.library, @lssm-tech/app.web-landing

    1. Run the deterministic fixture command before adding provider adapters.
    2. Keep repository mutation, outreach, and other effects approval-bound by default.
    3. Supply tenant-scoped durable storage, secrets, audit, observability, and kill switches.
    4. Run every required live suite against the exact deployment composition.
    5. Retain the resulting plan digest, declared losses, and evidence bundle.

Unique release changes

  • - Add complete Release Steward and Company Intelligence Scout examples with multi-agent execution, governed self-improvement, durable loops, replaceable provider ports, candidate qualification, and public all-in-one guides.

    2 packages · 2 occurrences

  • - Start with the release migration or public-web intelligence scenario, then bind only the provider ports and autonomy allowed by the consumer's policy.

    2 packages · 2 occurrences

Impacted packages

  • @lssm-tech/app.web-landing

    Layer: apps · 2 changes

  • @lssm-tech/bundle.library

    Layer: bundles · 2 changes