Back to changelog index

14.4.1

Aug 05, 2026 · 17 packages · 9 unique changes · 2 release entries

appsbundlesintegrationslibsmodules

This release affects the contracts, integrations, sharedLibs, solutions familyies.

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

Release summaries

  • adaptive-operations-v2

    Add a governed adaptive-operations V2 surface for sanitized signals, observed canaries, durable repair work, bounded patch generation, and low-risk GitHub-native auto-merge.

    maintainer

    Maintainers get replay-grade V2 contracts, durable observing work orders, strict risk classification, isolated patch receipts, and tests for stale or malformed evidence.

    integrator

    Integrators can map allowlisted PostHog metadata into operational signals and observations, then schedule branch-protection-aware native auto-merge for exact-SHA low-risk patches.

    customer

    Agent and workflow systems can recover and improve from operational evidence while keeping protected contracts, data authorities, effects, security, and delivery changes in review.

  • companyos-live-booking-intelligence

    Make CompanyOS profiles, shared and personal booking, morning recaps, and meeting-preparation email operational for the three canonical workspaces.

    customer

    Workspace members receive personal and shared booking links, a morning agenda recap, and preparation before meetings.

    maintainer

    Operators migrate and bootstrap the core-workspaces profile, reconnect Google Calendar, then activate all six booking surfaces.

Migration guide

  • Apply migration 0042 from a restorable baseline

    Required

    Take a restorable database backup, apply the additive calendar-intelligence migration, and verify the migration ledger reaches 0042.

  • Bootstrap the canonical workspaces and members

    Required

    Run the administrative bootstrap with MANAGED_COMPANYOS_SEED_PROFILE=core-workspaces to reconcile LSSM, CompanyOS, Hirly, and their owner/admin memberships.

  • Reauthorize all three Google Calendar connections

    Required

    Reauthorize each workspace calendar connection so its grant includes the read-only event scope required for recaps and meeting preparation.

  • Use the canonical CompanyOS web origin for authentication callbacks

    Required

    Set APP_WEB_BASE_URL to https://www.companyos.run and redeploy the API and web applications so credential and OAuth callbacks return to the browser app.

  • Activate the shared and personal booking surfaces

    Required

    After all three calendar topologies are connected, run companyos:booking-surfaces:activate to publish the three workspace and three personal booking links.

Upgrade steps

  • Adopt adaptive operations incrementally

    assisted

    Keep V1 running, deploy the additive V2 tables and readers, then enable repair and native auto-merge lanes behind consumer-owned kill switches.

    Packages: @lssm-tech/lib.contracts-spec, @lssm-tech/lib.ai-agent, @lssm-tech/lib.observability, @lssm-tech/lib.builder-runtime, @lssm-tech/integration.agent-durable-store, @lssm-tech/integration.provider-github, @lssm-tech/module.workspace, @lssm-tech/bundle.workspace, @lssm-tech/bundle.library, @lssm-tech/app.action-validation

    1. Run the additive Postgres migration before starting a V2 improvement worker.
    2. Emit only sanitized metadata that validates as OperationalImprovementSignalV1.
    3. Bind every patch receipt to exact base/head revisions, Connect decisions, and checks.
    4. Enable GitHub-native auto-merge only for low-risk decisions; retain human review for medium, high, unknown, stale, or failed-check changes.
  • Configure privacy-bounded daily intelligence

    assisted

    Configure the briefing sender, Resend, optional Mistral composition, and the protected five-minute Vercel cron.

    Packages: @lssm-tech/lib.contracts-spec, @lssm-tech/lib.organization-planning-runtime, @lssm-tech/lib.contracts-integrations, @lssm-tech/integration.provider-calendar, @lssm-tech/integration.provider-llm, @lssm-tech/app.api-application-monolith, @lssm-tech/app.web-application-monolith, @lssm-tech/bundle.managed-companyos

    1. Set RESEND_CALENDAR_INTELLIGENCE_FROM to the verified briefing identity.
    2. Keep RESEND_REPLY_TO explicit and monitored.
    3. Set MISTRAL_API_KEY for smart composition or use the deterministic fallback.
    4. Keep CRON_SECRET enabled for the calendar-intelligence route.

Unique release changes

  • - Add a governed adaptive-operations V2 surface for sanitized signals, observed canaries, durable repair work, bounded patch generation, and low-risk GitHub-native auto-merge.

    10 packages · 10 occurrences

  • - Keep V1 running, deploy the additive V2 tables and readers, then enable repair and native auto-merge lanes behind consumer-owned kill switches.

    10 packages · 10 occurrences

  • - After all three calendar topologies are connected, run companyos:booking-surfaces:activate to publish the three workspace and three personal booking links.

    8 packages · 8 occurrences

  • - Configure the briefing sender, Resend, optional Mistral composition, and the protected five-minute Vercel cron.

    8 packages · 8 occurrences

  • - Make CompanyOS profiles, shared and personal booking, morning recaps, and meeting-preparation email operational for the three canonical workspaces.

    8 packages · 8 occurrences

  • - Reauthorize each workspace calendar connection so its grant includes the read-only event scope required for recaps and meeting preparation.

    8 packages · 8 occurrences

  • - Run the administrative bootstrap with MANAGED_COMPANYOS_SEED_PROFILE=core-workspaces to reconcile LSSM, CompanyOS, Hirly, and their owner/admin memberships.

    8 packages · 8 occurrences

  • - Set APP_WEB_BASE_URL to https://www.companyos.run and redeploy the API and web applications so credential and OAuth callbacks return to the browser app.

    8 packages · 8 occurrences

  • - Take a restorable database backup, apply the additive calendar-intelligence migration, and verify the migration ledger reaches 0042.

    8 packages · 8 occurrences

Impacted packages

  • @lssm-tech/app.action-validation

    Layer: apps · 2 changes

  • @lssm-tech/app.api-application-monolith

    Layer: apps · 7 changes

  • @lssm-tech/app.web-application-monolith

    Layer: apps · 7 changes

  • @lssm-tech/bundle.library

    Layer: bundles · 2 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 7 changes

  • @lssm-tech/bundle.workspace

    Layer: bundles · 2 changes

  • @lssm-tech/integration.agent-durable-store

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-calendar

    Layer: integrations · 7 changes

  • @lssm-tech/integration.provider-github

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-llm

    Layer: integrations · 7 changes

  • @lssm-tech/lib.ai-agent

    Layer: libs · 2 changes

  • @lssm-tech/lib.builder-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-integrations

    Layer: libs · 7 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 7 changes

  • @lssm-tech/lib.observability

    Layer: libs · 2 changes

  • @lssm-tech/lib.organization-planning-runtime

    Layer: libs · 7 changes

  • @lssm-tech/module.workspace

    Layer: modules · 2 changes