Skip to content
← Back to changelog index

11.0.4

Oct 27, 2026 · 8 packages · 16 unique changes · 9 release entries

bundlesintegrationslibs

This release affects the integrations, sharedLibs, solutions families.

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

Release summaries

  • api-monolith-owner-extractions

    Managed CompanyOS API host behavior moves to its domain owners

    integrator

    New owner subpaths expose public booking availability policy derivation and DST-safe zoned wall-clock helpers that the API host previously implemented locally.

  • cmp-companyos-db-authority-hardening

    CompanyOS authority hardening: RLS policies ignore an empty tenant or actor setting (0179, with the non-empty constraints validated by 0183), the capture-processing, bot and recorder crons run on their own restricted logins (0181), the owner recap address lookup has a tracked grant (0182), the recorder-binding projection is insert-only (its 0173 update grant is revoked by 0184 in a later release), and a late owner-recap requeue cannot send twice.

    maintainer

    Migration 0179 rewrites the tenant isolation policies of the managed CompanyOS RLS inventory (0001-0027, including the 0009 evidence bus, the 0015 auth authority binding and the 0026 brain objects), of the four 0038 AuthOS self-service tables (USING and WITH CHECK) and of the 0006 channel/builder runtime schemas to compare NULLIF(current_setting('app.tenant_id', true), ''), scopes the 0007 private-draft visibility to a non-empty app.actor_ref, defaults the 0006 runtime tenant_id to the NULLIF form and adds CHECK (tenant_id <> '') NOT VALID. It takes only brief metadata locks under a 5 s lock_timeout, and a missing policy aborts the apply. Migration 0183 validates those constraints in its own transaction (SHARE UPDATE EXCLUSIVE, 5 s lock_timeout); a table with legacy empty rows keeps its constraint NOT VALID with a WARNING. Out of scope, with the raw comparison kept for a follow-up hardening migration: the 0017 and 0064/0066 topology split policies, the tenant policies created after 0027 (0029, 0030, 0034, 0035, 0042, 0049, 0052, 0072, 0110, 0142, 0180, 0190-0192 and the TypeScript-built calendar, planning, billing and economics migrations) and the OPA owner-scope policies. The Drizzle schema declares the live 0015 policy name and the 0038 WITH CHECK.

    maintainer

    Migration 0181 adds NOLOGIN roles companyos_capture_runtime, companyos_bot_runtime and companyos_recorder_runtime (hardened like 0173: an INHERIT member of opa_app plus the background authority grants only). /api/cron/opa-capture-processing reads MANAGED_COMPANYOS_CAPTURE_RUNTIME_DATABASE_URL, both bot crons MANAGED_COMPANYOS_BOT_RUNTIME_DATABASE_URL and /api/cron/opa-recorder-sync MANAGED_COMPANYOS_RECORDER_RUNTIME_DATABASE_URL instead of LSSM_STUDIO_DATABASE_URL, and each refuses any other current_user, a superuser, BYPASSRLS or an opa_migrator member with CAPTURE_RUNTIME_ROLE_INVALID, BOT_RUNTIME_ROLE_INVALID or RECORDER_RUNTIME_ROLE_INVALID. Without the capture runtime URL the capture cron answers 200 stoppedBy unprovisioned, new recordings and live capture are not admitted, and notetaker bots fall back to the provider transcript or recording-only path; the bot readiness verdict checks the bot runtime URL. The recorder webhook route lookup needs only the dispatcher login. A failing bot or recorder cron logs a sanitized code.

    maintainer

    Migration 0182 revokes any table or column select on managed_auth_email_addresses from companyos_opa_runtime and grants exactly the five owner-recap columns. The OPA runtime writes the recorder-binding projection insert-only (on conflict do nothing; only a source rebind runs a revision-guarded update, and a binding a concurrent writer committed is re-read rather than skipped). Revoking update on opa_meeting_recorder_bindings from companyos_opa_runtime is the contract phase: it is not in this release's catalog, because the previous image still upserts with that grant, and a later release registers it as 0184. The owner recap refuses (provider_rejected, dead-lettered) an already attempted effect whose outbox row is older than 22 h, unless its only earlier attempt failed before sending; an operator resends on purpose by requeueing with attempt_count = 0.

    customer

    Recording processing, notetaker bots and recorder imports no longer run on the operator database login, and an owner recap cannot arrive twice after a late retry.

  • opa-api-monolith-extractions-x1

    Managed CompanyOS API host OPA behavior moves to organization-planning and calendar-bridge owners

    integrator

    New owner subpaths expose the smart-meeting preparation and approval lifecycle services, work proposal publication contract and suggestion-policy guard, personal plan placement predicates, private-draft command evidence, profile and profile SEO services, support destination resolution, automatic meeting preparation, the governed meeting AI artifact generator, the meeting preparation job port, the calendar topology lock and Google topology writer, and the Google OAuth state and protected booking resolver adapters, all behind explicit ports.

  • opa-host-extractions-x6

    Meeting workspace, smart-meeting, capture, transcript, task projection, conflict, Work planning, profile seed and private-meeting behavior moves from hosts to the organization-planning owners

    integrator

    New owner subpaths expose the shared SQL meeting-workspace ports and public share resolver, the smart-meeting availability rules and approval-packet store, the durable capture-processing cycle, the private transcript read service, the reviewed meeting task projection, the scheduling-conflict resolution workflow, the Work-to-OPA planning projection and revision digests, the organization seed profile projection, and a platform-neutral private-meeting create hook, all behind explicit ports.

  • opa-meeting-effects-cron

    Approved meeting follow-ups deliver from a CompanyOS API cron (Work tasks, draft follow-up meetings) without a separate worker host

    integrator

    Additive runtime exports from @lssm-tech/lib.organization-planning-runtime/meeting-workspace: processMeetingEffectLease, MeetingEffectLeaseProcessorPorts, meetingEffectLeaseOutcome, sameMeetingEffectScope, staticMeetingEffectRollout, meetingEffectScopeDigestInput, summarizeMeetingEffectCycle and MeetingEffectCycleSnapshot; from ./database: opaMeetingEffectDispatchMigrationStatements and OPA_MEETING_EFFECT_DISPATCHER_ROLE. The worker composition still exports meetingEffectScopeDigestInput (now re-exported). No operation, event or delivery-envelope contract changes.

    maintainer

    Migration 0172 adds NOLOGIN role companyos_meeting_effect_dispatcher and SECURITY DEFINER companyos_meeting_effect_due_scopes(integer), owned by opa_migrator, execute granted only to the dispatcher. The API adds the cron /api/cron/opa-meeting-effects (vercel.json, every minute). It needs MANAGED_COMPANYOS_MEETING_EFFECTS_DATABASE_URL (dispatcher login), LSSM_STUDIO_DATABASE_URL (RLS-bound runtime role), OPA_BYOK_KEY_VERSION/OPA_BYOK_MASTER_KEY_v1, OPA_MEETING_EFFECT_ROLLOUTS_JSON (one strict companyos entry), OPA_MEETING_FOLLOWUP_TARGETS, OPA_MEETING_FOLLOWUP_DELIVERY_ENABLED=1 and OPA_MEETING_EFFECTS_CRON_ENABLED=1. Run exactly one effect host per database (this cron or the standalone worker).

    customer

    After a meeting owner approves a follow-up plan, the Work tasks (with the reviewed assignee and due date) and the draft follow-up meeting are created automatically within about a minute. Nothing is sent to attendees.

  • opa-public-booking-manage-recovery

    Idempotent, recoverable public booking cancellation with an honest manage-link recovery page.

    customer

    Visitors who cancel a booking get one clear outcome even when the network drops, and an unavailable manage link explains what to do with a way back to the booking page.

    integrator

    opa.booking.public_cancel replays the cancellation lifecycle for a retried request on the same live manage session; other post-consumption mutations still fail closed.

  • opa-runtime-injected-outbox-authz

    OPA runtime uses the Jobs outbox dispatcher and an injected permission-engine port instead of CompanyOS and identity RBAC runtimes

    integrator

    The generic outbox dispatcher and backoff now live in @lssm-tech/lib.jobs (./outbox/dispatcher, ./outbox/backoff); CompanyOS outbox paths re-export the identical objects. The OPA runtime no longer depends on lib.companyos-runtime or lib.identity-rbac; hosts bind the identity RBAC engine into the OpaPermissionEngine port through OpaRbacDeps, exactly as before.

  • w6-latent-sql-binds-outbox

    JSON-text list binds for postgres.js and opa_outbox writers that run on the production and canonical OPA v2 outbox shapes

    maintainer

    Bind SQL lists as JSON text (any(array(select jsonb_array_elements_text($n::text::jsonb)))) and aggregate result lists with jsonb_agg: the shared postgres.js client neither serializes JS arrays nor parses text[] results. postgres-array-bind-guard.test.ts has no allow-list. Write opa_outbox rows through opaOutboxInsertSql so one statement runs on both outbox shapes; owner columns come from the owning row or app.product_ref/app.workspace_ref/app.owner_kind/app.owner_ref.

  • w7-opa-v2-owner-activation

    Activation-gated in-place OPA v2 owner activation (0175) superseding 0037, with schema-tolerant OPA writers

    maintainer

    0037 is superseded and never scheduled; the activation-gated 0175 converts the 28 OPA owner tables in place (backfill from owning rows, hints or the sole tenant owner; owner-scoped keys; owner row security; session-owner defaults). Classify every new opa_* table in src/db/opa-v2-owner-activation/inventory.ts. Writers on owner tables bind the owner of the row they act for (bindOpaOwnerFromRow) and never use on conflict (id) or tenant-scoped conflict targets: use a target-less on conflict do nothing or opaTolerantUpsertSql, and cover the writer with a both-shapes test (migratedOpaDatabase 'production' and 'owner-v2'). Deploys never apply 0175; activation is a future owner-approved operation that follows docs/evidence/opa/opa-v2-owner-schema-activation-runbook.md (preflight, restore rehearsal and dry run, signed evidence bound to the ledger head, apply, verify, reversal).

Migration guide

  • Apply 0179 and 0181-0183, enable the three cron logins, then deploy

    Required

    The capture-processing and recorder crons are live in production and stop until their restricted logins exist, and the logins need the 0181 roles, so every migration and login comes before the deploy. All four migrations are safe under the previous code. The recorder-binding grant revoke is not in this release (it ships as 0184 later), so a rollback needs no re-grant. Production applies and login creation stay with the operator (B217).

    1. Record whether production already holds a manual grant on managed_auth_email_addresses (0182 replaces it with the five tracked columns).
    2. As opa_migrator through the guarded wrapper (0179 and 0183 alter the managed tenant tables, which needs their owner), run the tracked API application migrations: contracts 0179_rls_empty_setting_nullif.sql, companyos/opa-cron-runtime-roles-0181, companyos/opa-owner-recap-address-grant-0182 and 0183_rls_nonempty_constraint_validation.sql. If 0179 or 0183 aborts with 55P03 lock_not_available, nothing changed; rerun later. Note any WARNING naming a table with legacy empty tenant rows.
    3. Enable LOGIN on companyos_capture_runtime, companyos_bot_runtime and companyos_recorder_runtime with offline-computed SCRAM-SHA-256 verifiers, and set MANAGED_COMPANYOS_CAPTURE_RUNTIME_DATABASE_URL, MANAGED_COMPANYOS_BOT_RUNTIME_DATABASE_URL and MANAGED_COMPANYOS_RECORDER_RUNTIME_DATABASE_URL to the transaction pooler.
    4. Deploy the API.
  • Apply migration 0172 and give the dispatcher a login before enabling the cron

    Required

    The cron discovers due owner scopes only through companyos_meeting_effect_due_scopes as companyos_meeting_effect_dispatcher and refuses any other database user. Old code never calls the function, so 0172 can be applied before or after the API deploy.

    1. Run the API application migrations as opa_migrator so contract 0172 (organization-planning-runtime/opa-meeting-effect-dispatch-0172) is applied after 0168.
    2. Give companyos_meeting_effect_dispatcher a LOGIN with a secret from the secret store and set MANAGED_COMPANYOS_MEETING_EFFECTS_DATABASE_URL to it.
    3. Set OPA_MEETING_EFFECT_ROLLOUTS_JSON and OPA_MEETING_FOLLOWUP_TARGETS=companyos_work_graph,calendar_follow_up_proposal, then OPA_MEETING_FOLLOWUP_DELIVERY_ENABLED=1, then OPA_MEETING_EFFECTS_CRON_ENABLED=1.
    4. Do not run the standalone meeting effect worker against the same database.
  • Optionally call the new owner subpaths

    Additive only; existing imports are unchanged. Hosts may call the new owner subpaths instead of reimplementing host-local policy.

    1. Import availabilityPolicyFromEventConfig from @lssm-tech/lib.organization-planning-runtime/public-booking-availability-policy instead of a host-local copy.
  • Optionally call the new OPA owner subpaths

    Additive only; existing exports are unchanged. Hosts may call the new owner subpaths instead of reimplementing host-local OPA policy, binding their own persistence, environment, role model and transport.

    1. Import smart-meeting contracts and services from @lssm-tech/lib.organization-planning-runtime/smart-meeting/* and bind host persistence, booking saga and RBAC.
    2. Import WorkProposalPublicationSchema from @lssm-tech/lib.organization-planning-spec/work-proposal-publication and the guard port and suggestion guard from @lssm-tech/lib.organization-planning-runtime/work-proposal/*.
    3. Use PostgresGoogleOAuthStateStore and resolveGoogleProtectedBooking from @lssm-tech/integration.opa-calendar-bridge/google-oauth-state and ./google-protected-booking instead of host copies.
  • Optionally call the new organization-planning owner subpaths

    Additive only; existing exports are unchanged. Hosts may compose the new owner subpaths instead of keeping host copies, binding their own environment, pools, key custody, session authority, host-migration SQL and provider adapters.

    1. Compose createSqlMeetingWorkspacePorts and resolveOpaMeetingShare from @lssm-tech/lib.organization-planning-runtime/database/meeting-workspace-sql-ports, passing a readDocumentText binding for the Loro provider.
    2. Bind the Work reducer (replayWorkEvents) into projectWorkOpaPlanningSnapshot and a Work commit into projectOpaMeetingTask; the runtime has no Work runtime dependency.
    3. Use usePrivateMeetings from @lssm-tech/lib.organization-planning-react/usePrivateMeetings with module-scope openSession, openIntentStore and createKey ports.
  • Optionally import the outbox dispatcher and backoff from lib.jobs

    Additive only; @lssm-tech/lib.companyos-runtime/outbox, ./outbox/dispatcher and ./outbox/backoff keep working and export the same objects.

    1. Replace @lssm-tech/lib.companyos-runtime/outbox dispatcher or backoff imports with @lssm-tech/lib.jobs/outbox/dispatcher or @lssm-tech/lib.jobs/outbox/backoff.
  • Keep binding the identity RBAC engine in OPA host composition roots

    No code change is required: OpaRbacDeps.engine accepts any OpaPermissionEngine and identity RBAC's RBACPolicyEngine satisfies it. Code that read OpaRbacDeps.engine expecting RBACPolicyEngine-only methods must keep its own RBACPolicyEngine reference.

    1. Construct new RBACPolicyEngine() from @lssm-tech/lib.identity-rbac/policies in the host and pass it as rbac.engine to createOpaRuntime or the OPA handlers.
    2. Use createLocalOpaPermissionEngine() from @lssm-tech/lib.organization-planning-runtime/install/local-permission-engine only for local, demo and test wiring.

Unique release changes

  • Additive only; @lssm-tech/lib.companyos-runtime/outbox, ./outbox/dispatcher and ./outbox/backoff keep working and export the same objects.

    3 packages · 3 occurrences

  • Additive only; existing exports are unchanged. Hosts may call the new owner subpaths instead of reimplementing host-local OPA policy, binding their own persistence, environment, role model and transport.

    3 packages · 3 occurrences

  • Managed CompanyOS API host OPA behavior moves to organization-planning and calendar-bridge owners

    3 packages · 3 occurrences

  • No code change is required: OpaRbacDeps.engine accepts any OpaPermissionEngine and identity RBAC's RBACPolicyEngine satisfies it. Code that read OpaRbacDeps.engine expecting RBACPolicyEngine-only methods must keep its own RBACPolicyEngine reference.

    3 packages · 3 occurrences

  • OPA runtime uses the Jobs outbox dispatcher and an injected permission-engine port instead of CompanyOS and identity RBAC runtimes

    3 packages · 3 occurrences

  • Activation-gated in-place OPA v2 owner activation (0175) superseding 0037, with schema-tolerant OPA writers

    2 packages · 2 occurrences

  • Additive only; existing exports are unchanged. Hosts may compose the new owner subpaths instead of keeping host copies, binding their own environment, pools, key custody, session authority, host-migration SQL and provider adapters.

    2 packages · 2 occurrences

  • Idempotent, recoverable public booking cancellation with an honest manage-link recovery page.

    2 packages · 2 occurrences

  • JSON-text list binds for postgres.js and opa_outbox writers that run on the production and canonical OPA v2 outbox shapes

    2 packages · 2 occurrences

  • Meeting workspace, smart-meeting, capture, transcript, task projection, conflict, Work planning, profile seed and private-meeting behavior moves from hosts to the organization-planning owners

    2 packages · 2 occurrences

  • Additive only; existing imports are unchanged. Hosts may call the new owner subpaths instead of reimplementing host-local policy.

    1 package · 1 occurrence

  • Approved meeting follow-ups deliver from a CompanyOS API cron (Work tasks, draft follow-up meetings) without a separate worker host

    1 package · 1 occurrence

  • CompanyOS authority hardening: RLS policies ignore an empty tenant or actor setting (0179, with the non-empty constraints validated by 0183), the capture-processing, bot and recorder crons run on their own restricted logins (0181), the owner recap address lookup has a tracked grant (0182), the recorder-binding projection is insert-only (its 0173 update grant is revoked by 0184 in a later release), and a late owner-recap requeue cannot send twice.

    1 package · 1 occurrence

  • Managed CompanyOS API host behavior moves to its domain owners

    1 package · 1 occurrence

  • The capture-processing and recorder crons are live in production and stop until their restricted logins exist, and the logins need the 0181 roles, so every migration and login comes before the deploy. All four migrations are safe under the previous code. The recorder-binding grant revoke is not in this release (it ships as 0184 later), so a rollback needs no re-grant. Production applies and login creation stay with the operator (B217).

    1 package · 1 occurrence

  • The cron discovers due owner scopes only through companyos_meeting_effect_due_scopes as companyos_meeting_effect_dispatcher and refuses any other database user. Old code never calls the function, so 0172 can be applied before or after the API deploy.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 1 change

  • @lssm-tech/integration.opa-calendar-bridge

    Layer: integrations · 2 changes

  • @lssm-tech/integration.opa-notification-bridge

    Layer: integrations · 1 change

  • @lssm-tech/lib.companyos-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.jobs

    Layer: libs · 3 changes

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

    Layer: libs · 2 changes

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

    Layer: libs · 3 changes

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

    Layer: libs · 2 changes