0.2.15

May 26, 2026 · 3 packages · 7 unique changes · 3 release entries

appsbundlesmodules

This release affects the solutions family.

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

Release summaries

agent-workflow-command-center-boil-lake
Add a deterministic Agent/Workflow Command Center scenario with policy-gated tool binding, review-required workflow state, audit/replay proof, Managed CompanyOS view-model export, mobile shell consumption, and concrete example agent lifecycle operation contracts.
maintainer
Add a deterministic Agent/Workflow Command Center scenario with policy-gated tool binding, review-required workflow state, audit/replay proof, Managed CompanyOS view-model export, mobile shell consumption, and concrete example agent lifecycle operation contracts.
integrator
Add a deterministic Agent/Workflow Command Center scenario with policy-gated tool binding, review-required workflow state, audit/replay proof, Managed CompanyOS view-model export, mobile shell consumption, and concrete example agent lifecycle operation contracts.
tool-effects-agent-fleet
Add typed ContractSpec and integration tool effects with deterministic validation, simulation, replay, and explicit execution adapter boundaries.
maintainer
Maintainers get a typed reusable effect contract and operation matrix entries for tool effect validation, simulation, and execution.
integrator
Integrators can bind tools to ContractSpec operations or already-integrated provider catalog entries while keeping real execution behind injected adapters.
customer
Command-center users can configure tool effects, validate readiness, simulate behavior, and see that execution requires an explicit host adapter.
tool-selection-workbench
Add a decision-quality operation workbench for selecting and configuring ContractSpec and integration tool effects.
maintainer
Maintainers get additive workbench metadata and helpers for richer tool-effect catalog selection without breaking existing effect entries.
integrator
Integrators can model searchable ContractSpec operations and integration calls with schemas, mappings, examples, risk/auth metadata, and explicit host-adapter boundaries.
customer
Command-center users can compare candidates, inspect schemas and boundaries, configure mappings, validate readiness, and simulate before saving a tool.

Migration guide

Enrich tool-effect catalogs for operation workbench selection
Existing catalog entries continue to work, but hosts can add optional metadata for domains, tags, risks, schemas, examples, mapping hints, and adapter boundaries.
1. Keep existing id, kind, label, credential boundary, and required input refs stable.
2. Add optional metadata fields for search, compare, schema preview, and mapping hints.
3. Continue to inject real execution adapters explicitly instead of calling providers from reusable presentation.
Adopt typed tool effects for configurable agent tools
Use `contract_effect` for ContractSpec operation selectors and `integration_effect` for already-integrated catalog operations; do not model bash, JavaScript, TypeScript, or raw code execution effects in this first pass.
1. Persist optional tool `effect` definitions on registry entries and drafts.
2. Provide an operation catalog for ContractSpec-backed tools and an integration catalog for provider-backed tools.
3. Call validate and simulate before wiring host execution adapters.
4. Inject executors explicitly when a host is ready to run real effects.

Upgrade steps

Keep default command-center behavior deterministic
manual
The example can show host adapter metadata but must not capture credentials or perform live provider/network/backend execution by default.
Packages: @lssm-tech/module.agent-fleet, @lssm-tech/example.agent-workflow-command-center
1. Review fixture catalog entries for fake provider/package refs only.
2. Keep validation and simulation deterministic.
3. Wire real adapters only in host applications outside the default example.
Keep command-center examples deterministic by default
manual
Host applications must wire execution adapters deliberately; the example remains integration-free, backend-free, secret-free, and provider/network-free by default.
Packages: @lssm-tech/module.agent-fleet, @lssm-tech/example.agent-workflow-command-center
1. Keep real credentials outside reusable presentation and example fixtures.
2. Use the adapter-missing execution state as the safe default until a host provides executors.
3. Update docs and AGENTS guidance when adding new effect kinds or host execution surfaces.
Review Agent Workflow Command Center Boil Lake adoption
manual
Add a deterministic Agent/Workflow Command Center scenario with policy-gated tool binding, review-required workflow state, audit/replay proof, Managed CompanyOS view-model export, mobile shell consumption, and concrete example agent lifecycle operation contracts.
Packages: @lssm-tech/module.agent-fleet, @lssm-tech/bundle.managed-companyos, @lssm-tech/example.agent-workflow-command-center, @lssm-tech/app.mobile-monolith
1. Review the paired changeset summary and update consumers only if they use the affected package surface.

Unique release changes

- Add a deterministic Agent/Workflow Command Center scenario with policy-gated tool binding, review-required workflow state, audit/replay proof, Managed CompanyOS view-model export, mobile shell consumption, and concrete example agent lifecycle operation contracts.
3 packages · 6 occurrences
- Add a decision-quality operation workbench for selecting and configuring ContractSpec and integration tool effects.
1 packages · 1 occurrences
- Add typed ContractSpec and integration tool effects with deterministic validation, simulation, replay, and explicit execution adapter boundaries.
1 packages · 1 occurrences
- Existing catalog entries continue to work, but hosts can add optional metadata for domains, tags, risks, schemas, examples, mapping hints, and adapter boundaries.
1 packages · 1 occurrences
- Host applications must wire execution adapters deliberately; the example remains integration-free, backend-free, secret-free, and provider/network-free by default.
1 packages · 1 occurrences
- The example can show host adapter metadata but must not capture credentials or perform live provider/network/backend execution by default.
1 packages · 1 occurrences
- Use `contract_effect` for ContractSpec operation selectors and `integration_effect` for already-integrated catalog operations; do not model bash, JavaScript, TypeScript, or raw code execution effects in this first pass.
1 packages · 1 occurrences

Impacted packages

@lssm-tech/app.mobile-monolith
Layer: apps · 2 changes
@lssm-tech/bundle.managed-companyos
Layer: bundles · 2 changes
@lssm-tech/module.agent-fleet
Layer: modules · 2 changes