ContractSpecContractSpec

Start with OSS

Back to changelog index

0.4.5

Aug 01, 2026 · 2 packages · 11 unique changes · 3 release entries

appsmodules

This release affects the solutions family.

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

Release summaries

  • companyos-ai-solutions-engineer-poc-live-hardening

    Harden the CompanyOS Request-to-Verified-Proof POC for truthful live and recorded customer-call use without broadening its single-profile loopback scope.

    customer

    Arkia and Théo can present one adaptive Understand-to-Verify journey with explicit live, validated-recording, prepared-simulation, failed, and blocked labels plus a concrete four-input commercial handoff.

    integrator

    Application hosts can override one generic inline preview with app-owned composition, inject the same-origin runtime client, and keep provider and Playwright dependencies server-only.

    maintainer

    Proof execution is reconstructed from an allowlisted prepared profile, live evidence is projected from the Harness receipt, recording artifacts are SHA-256 validated, and bounded session/idempotency state prevents duplicate or stale execution.

  • companyos-call-ready-dual-framing

    Make the CompanyOS proof demo call-ready with dual framing, explicit result sources, privacy-safe presenter controls, and a thin allowlisted web host route.

    customer

    Presenters can run a plain-language six-step Call Mode or the preserved technical Expert Mode with explicit prepared, live, or validated-recording disclosures.

    integrator

    Hosts can inject the result-returning browser-safe runtime contract or use the web landing operation route without importing Node or Playwright code into the client graph.

  • companyos-visual-first-adaptive-experience

    Replace the visible CompanyOS Call/Expert split with one visual-first adaptive journey and contextual evidence inspection.

    customer

    The demo communicates request understanding, bounded action, and verified proof through one adaptive visual journey with exact evidence available from each relevant object.

    integrator

    The primary preview, safe export, and presentation telemetry identify the surface as adaptive while legacy Call/Expert types and named UI exports remain import-compatible.

Deprecations

  • - DemoSurfaceMode and named Call/Expert stage exports remain available for compatibility but no longer select the primary preview presentation.
  • - DemoSurfaceMode and named Call/Expert stage exports remain compatibility-only; the primary experience is the single adaptive journey.
  • - Notification-only generation and proof callbacks remain observers and no longer define progression; inject a DemoRuntime through the browser-safe runtime-contract export instead.

Migration guide

  • Inject the host runtime through the preview override seam

    Hosts that require live preflight or proof should register an app-owned preview wrapper and inject a browser-safe same-origin DemoRuntime client.

    When: When rendering the POC inside an application host.

    1. Keep the generic examples module application-agnostic.
    2. Compose provider and deployment dependencies in the host only.
    3. Keep runtime and Playwright imports on Node/Bun server entrypoints.
    4. Preserve the prepared/recorded package preview when no host runtime exists.

  • Adopt the result-returning demo runtime

    Use DemoRuntime results and explicit sources instead of callback notifications.

    When: When a host needs live generation or browser proof.

    1. Import DemoRuntime types from the runtime-contract subpath.
    2. Import host composition helpers from the server-only runtime/server subpath.
    3. Keep Node and Playwright imports in server-only route adapters; browser clients call the allowlisted same-origin operation route.
    4. Preserve explicit fallback acceptance in auto mode.
    5. Treat DemoRuntimeResult.data as the authoritative rendered proof result.
    6. Treat operation_timed_out and session_operation_in_progress as fail-closed runtime outcomes.

  • Recognize the adaptive presentation value

    Treat adaptive as the primary preview, safe-export, and telemetry presentation value.

    When: When a consumer filters CompanyOS demo sessions by presentation surface.

    1. Accept the serialized presentation value adaptive.
    2. Stop depending on an audience-facing Call/Expert selector.
    3. Continue importing deprecated named stage exports only during compatibility migration.

Upgrade steps

  • Validate the supported recorded and local-live call paths

    assisted

    Use the consolidated pre-call command and require truthful source labels before presenting.

    Packages: @lssm-tech/example.companyos-ai-solutions-engineer-poc, @lssm-tech/module.examples, @lssm-tech/app.web-landing

    1. Run bun run --cwd packages/examples/companyos-ai-solutions-engineer-poc precall.
    2. Use validated-recording for the reliable public or hosted call.
    3. Enable local live mode only when Chromium launches and preflight reports ready-live.
    4. Accept a recording fallback explicitly after a live failure.

  • Rehearse the call-ready paths

    assisted

    Validate both framings, reset, export, and live-unavailable fallback.

    Packages: @lssm-tech/example.companyos-ai-solutions-engineer-poc, @lssm-tech/app.web-landing

    1. Follow CALL_RUNBOOK.md in the example package.
    2. Verify the default export contains no raw request text.

Unique release changes

  • - DemoSurfaceMode and named Call/Expert stage exports remain compatibility-only; the primary experience is the single adaptive journey.

    2 packages · 2 occurrences

  • - Harden the CompanyOS Request-to-Verified-Proof POC for truthful live and recorded customer-call use without broadening its single-profile loopback scope.

    2 packages · 2 occurrences

  • - Hosts that require live preflight or proof should register an app-owned preview wrapper and inject a browser-safe same-origin DemoRuntime client.

    2 packages · 2 occurrences

  • - Use the consolidated pre-call command and require truthful source labels before presenting.

    2 packages · 2 occurrences

  • - DemoSurfaceMode and named Call/Expert stage exports remain available for compatibility but no longer select the primary preview presentation.

    1 packages · 1 occurrences

  • - Make the CompanyOS proof demo call-ready with dual framing, explicit result sources, privacy-safe presenter controls, and a thin allowlisted web host route.

    1 packages · 1 occurrences

  • - Notification-only generation and proof callbacks remain observers and no longer define progression; inject a DemoRuntime through the browser-safe runtime-contract export instead.

    1 packages · 1 occurrences

  • - Replace the visible CompanyOS Call/Expert split with one visual-first adaptive journey and contextual evidence inspection.

    1 packages · 1 occurrences

  • - Treat adaptive as the primary preview, safe-export, and telemetry presentation value.

    1 packages · 1 occurrences

  • - Use DemoRuntime results and explicit sources instead of callback notifications.

    1 packages · 1 occurrences

  • - Validate both framings, reset, export, and live-unavailable fallback.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.web-landing

    Layer: apps · 3 changes

  • @lssm-tech/module.examples

    Layer: modules · 4 changes