0.4.20

Jul 16, 2026 · 11 packages · 8 unique changes · 4 release entries

appsbundlesintegrationslibsmodules

This release affects the integrations, sharedLibs, solutions familyies.

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

Release summaries

builder-delivery-loop
Add the first canonical Builder customer-delivery-loop ref and evidence slice.
maintainer
Builder now has typed delivery-loop refs and validators that connect commercial intent, scope, implementation planning, Connect/replay, acceptance, release capsules, and customer handoff evidence.
integrator
Hosts can project customer-delivery readiness and handoff evidence without enabling Builder-side provider execution or customer sends.
agent
Agents get a fail-closed handoff surface that requires BillingOS, CompanyOS, Connect, replay, acceptance, and release evidence before customer-facing delivery is considered ready.
builder-intelligence-artifacts
Add Builder Intelligence artifact contracts plus pure runtime indexing/retrieval, memory projection, stale invalidation, trajectory capture, ReasoningBank, SONA-lite routing, GraphRAG summary, and neural readiness helpers with dry-run CLI/docs surfaces.
maintainer
Builder Intelligence schemas are additive compatibility surfaces in builder-spec, with validators that fail closed on stale refs, snippet redaction, missing deterministic refs, and raw hidden reasoning fields.
integrator
Pure builder-runtime helpers build deterministic indexes, identify changed chunks, filter stale chunks, rerank explainable retrieval matches, pack context packets, project reviewed memory, report stale memory, capture observable trajectories, propose draft strategy cards/routes, build non-authoritative graph summaries, and evaluate neural readiness without writes.
maintainer
Builder CLI can now emit dry-run JSON for index build/query, memory inspect/consolidate, trajectory learning, context build, and route explanation without writing stores or policies.
customer
Public docs describe the first Builder Intelligence slice and the reviewable generated layout for graph, index, memory, trajectory, drift, and generation artifacts.
builder-next-wave-hardening
Harden the Builder rollout with canonical bootstrap presets, channel-heavy mobile review flows, local-daemon runtime registration, and richer operator status surfaces.
maintainer
Builder bootstrap presets, local-daemon registration, and mobile/operator status views now move together as one governed rollout surface.
integrator
Integrators can adopt canonical bootstrap presets, register trusted local daemons, and consume richer snapshot-backed mobile review and operator posture data.
customer
Builder operators get clearer local runtime trust, lease, and channel-action status when reviewing rollouts away from the desktop workbench.
builder-specs-pack-connect-apply
Add governed Builder specs-pack task ledgers and fail-closed Connect-gated apply evidence.
maintainer
Maintainers get typed specs-pack task-ledger contracts, runtime helpers, and targeted regression tests for Connect-gated apply.
customer
Builder pack users can request apply with a Connect decision id, read the public specs-pack guide, and receive structured fail-closed JSON evidence instead of repository mutation without proof.

Upgrade steps

Model customer feature delivery with Builder refs and evidence
assisted
Use Builder delivery-loop contracts to connect quote/order refs, customer commitments, implementation plans, task ledgers, acceptance evidence, release capsules, and handoff refs before production adapters act.
Packages: @lssm-tech/lib.builder-spec, @lssm-tech/lib.builder-runtime
1. Import delivery-loop types from @lssm-tech/lib.builder-spec or the root Builder spec entry point.
2. Use Builder runtime delivery-loop helpers to project readiness and handoff blockers.
3. Keep BillingOS commercial data, CompanyOS authority, durable storage, provider execution, repository writes, and customer sends in their owning packages or host layers.
Inspect Builder Intelligence dry-run artifacts
assisted
Use the new runtime helpers and `contractspec builder` dry-run JSON commands to validate integration assumptions before enabling durable stores or generated writes.
Packages: @lssm-tech/lib.builder-spec, @lssm-tech/lib.builder-runtime, @lssm-tech/app.cli-contractspec, @lssm-tech/bundle.library, @lssm-tech/app.web-landing
1. Run `contractspec builder index build --json` to inspect the runtime-produced manifest/chunk shape.
2. Run `contractspec builder context build --goal "<goal>" --json` to inspect context packet fields.
3. Keep memory writes, policy updates, vector stores, and generated artifact writes disabled until later reviewed phases.
Verify hardened Builder bootstrap and local-daemon flows
manual
Confirm the new preset, mobile-review, and local runtime registration surfaces are wired through the workbench snapshot.
Packages: @lssm-tech/lib.builder-spec, @lssm-tech/lib.builder-runtime, @lssm-tech/lib.mobile-control, @lssm-tech/lib.provider-runtime, @lssm-tech/module.builder-workbench, @lssm-tech/module.mobile-review, @lssm-tech/integration.runtime-local, @lssm-tech/integration.provider-gemini, @lssm-tech/app.cli-contractspec, @lssm-tech/bundle.library
1. Update any bootstrap orchestration to use the managed, local-daemon, or hybrid preset values exposed by the Builder contracts.
2. Register a local daemon through the runtime integration and confirm the resulting trust and lease details appear in the Builder snapshot surfaces.
3. Review the mobile-review and operator status cards to verify channel-native actions and comparison posture are rendered from the shared snapshot model.
Use Connect-gated Builder pack apply for reviewed specs packs
assisted
Continue using import/analyze/plan for dry-runs, then call apply with an explicit Connect decision id when reviewed evidence exists.
Packages: @lssm-tech/lib.builder-spec, @lssm-tech/lib.builder-runtime, @lssm-tech/app.cli-contractspec, @lssm-tech/app.web-landing, @lssm-tech/bundle.library
1. Run `contractspec builder pack plan <zip-or-folder> --dry-run --json` to inspect the task ledger shape before writes.
2. Run `contractspec builder pack apply <zip-or-folder> --connect-decision <decision-id> --json` after Connect review; the command remains blocked until required evidence is present.

Unique release changes

- Confirm the new preset, mobile-review, and local runtime registration surfaces are wired through the workbench snapshot.
10 packages · 10 occurrences
- Harden the Builder rollout with canonical bootstrap presets, channel-heavy mobile review flows, local-daemon runtime registration, and richer operator status surfaces.
10 packages · 10 occurrences
- Add Builder Intelligence artifact contracts plus pure runtime indexing/retrieval, memory projection, stale invalidation, trajectory capture, ReasoningBank, SONA-lite routing, GraphRAG summary, and neural readiness helpers with dry-run CLI/docs surfaces.
5 packages · 5 occurrences
- Add governed Builder specs-pack task ledgers and fail-closed Connect-gated apply evidence.
5 packages · 5 occurrences
- Continue using import/analyze/plan for dry-runs, then call apply with an explicit Connect decision id when reviewed evidence exists.
5 packages · 5 occurrences
- Use the new runtime helpers and `contractspec builder` dry-run JSON commands to validate integration assumptions before enabling durable stores or generated writes.
5 packages · 5 occurrences
- Add the first canonical Builder customer-delivery-loop ref and evidence slice.
2 packages · 2 occurrences
- Use Builder delivery-loop contracts to connect quote/order refs, customer commitments, implementation plans, task ledgers, acceptance evidence, release capsules, and handoff refs before production adapters act.
2 packages · 2 occurrences

Impacted packages

@lssm-tech/app.cli-contractspec
Layer: apps · 2 changes
@lssm-tech/app.web-landing
Layer: apps · 2 changes
@lssm-tech/bundle.library
Layer: bundles · 2 changes
@lssm-tech/integration.provider-gemini
Layer: integrations · 2 changes
@lssm-tech/integration.runtime-local
Layer: integrations · 2 changes
@lssm-tech/lib.builder-runtime
Layer: libs · 2 changes
@lssm-tech/lib.builder-spec
Layer: libs · 2 changes
@lssm-tech/lib.mobile-control
Layer: libs · 2 changes
@lssm-tech/lib.provider-runtime
Layer: libs · 2 changes
@lssm-tech/module.builder-workbench
Layer: modules · 2 changes
@lssm-tech/module.mobile-review
Layer: modules · 2 changes