Skip to content
← Back to changelog index

12.0.4

Oct 27, 2026 · 46 packages · 43 unique changes · 22 release entries

appsbundlesintegrationslibsmodules

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

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

Release summaries

  • canonical-opa-automation-policy

    Canonical OPA policy ownership with compatible runtime and module imports

    integrator

    Existing policy imports remain supported while runtime authorization depends on the canonical domain policy leaf.

  • cmp-i18n-guard-scan-and-catalogs

    The en catalogs stop falling back to themselves, the video-gen LLM prompts become ICU-valid so their placeholders validate, and the last low-count hardcoded copy in the OPA bridges, the OPA booking widget and the self-improvement controllers moves to catalogs. i18n:check reports 0 warnings and the hardcoded-string allowlist shrinks from 319 to 273 packages.

    integrator

    resolveGoogleProtectedBooking (opa-calendar-bridge) and resolveOpaAdaptiveSurface (opa-personalization-bridge) accept an optional locale (en, fr or es). The default Google event title of a booking without its own summary and the surface reasons trace now resolve from the OPA catalog keys calendar.booking.defaultSummary and experience.personalization.reason.*; without a locale they stay English and identical to before. createSelfImprovementControllersV1(dataSource, { locale }) titles each operator panel from the new self-improving-system.messages catalog; without options the titles are unchanged. The OPA catalog organization-planning.messages moves to version 1.2.0 with the four new keys, and CALENDAR_KEYS is a new export of ./translations/keys.

    integrator

    The en catalogs of these packages no longer declare fallback: 'en'; resolution is unchanged because a base locale never needed a fallback. The video-gen script and scene planner system prompts describe the JSON response object in prose (same field names and types) instead of a literal JSON skeleton, so the LLM receives slightly different wording while the parsed response shape is unchanged. The OPA booking widget's frame title moved into a package-local message table with the same values.

    maintainer

    The hardcoded-string guard excludes **/*.test-support.{ts,tsx} structurally and gains the packageDeclarationMetadata (app blueprints and integration specs), protocolText (HTTP reason phrases, the JSON-RPC internal error message and the Bearer prefix) and developerErrorMessages (thrown developer errors, problem details and log lines in packages with no user locale) allowlist categories, plus two brand names. unmigratedPackages drops from 319 to 273: four entries outside the scan, 37 packages those categories clear and five packages whose copy moved to catalogs. SEEDED_BASELINE_COUNT is lowered to 273 and a new guard test fails on any entry that names no scanned file. The private marketing-operations app now logs MARKETING_APP_READY at startup instead of an English sentence, like its other log codes.

  • cmp-meeting-context-oauth-connect

    Personal OAuth connect flows for the Drive, Notion, Slack and HubSpot meeting-context sources

    customer

    In Settings → Personal briefings you can connect Google Drive, Notion, Slack and HubSpot so OPA may read them when it prepares your meetings. Each connection is yours, read-only, and used only for the sources you select; disconnecting erases the stored access.

    integrator

    OPA_MEETING_CONTEXT_CONNECTIONS_CONTRACT 1.0.0 describes the connections, connect, callback and disconnect routes. Responses carry secret-free states and stable codes only; the callback always returns to /companyos/opa-os/settings with meetingContext, provider and, on failure, reason (denied, state_invalid, exchange_failed, scope_missing, session_required, unavailable).

    maintainer

    Grants live in opa_oauth_tokens under individual:<authority segment(userId)> in the owner's personal tenant. The live connect attempt is the row meeting-context-oauth-state:<provider> (nonce digest only), consumed in one transaction under a row lock before the code exchange; one inert row per owner and provider remains until the personal context is deleted. opa_app holds no DELETE policy on that table, so disconnect overwrites the grant with an inert token and deletes only where the role may. Drive uses its own Google client for connect and refresh. No migration.

  • cmp-opa-bots-repair-and-attendee

    Operator repair of dead-lettered notetaker bot work with a reviewed path past the recovery window, and Attendee adapter field verification

    customer

    Workspace administrators can see the work of the notetaker bots they sent themselves that failed five times, and requeue it at once instead of waiting for the automatic retry. Other members' failed bot work is not shown: inside the recovery window CompanyOS still retries it on its own, and past the window it still needs an operator data change. Work that failed more than 14 days after its retention deadline can only be requeued with the reference of an approved change; that reference is recorded, not checked, and such a repair can only stop or delete data. Every applied repair is recorded.

    integrator

    Two OPA v2 operations, opa.bot_capture.dead_letter_list and opa.bot_capture.dead_letter_repair (capability opa.meeting_policy.manage; hosts also reprove organization.admin and recording access on the owner scope). Both run in the operator's individual owner scope, so they cover only the bots that operator dispatched; a workspace-wide repair would need a workspace-axis read and repair path. They come with OpaBotDeadLetterOverviewSchema, OpaBotDeadLetterRepairRequestSchema and OpaBotDeadLetterRepairReceiptSchema. The repair request names a closed reason code, the expected revision, an idempotency key and, past the recovery window, a review reference, which is recorded for traceability and not verified. Applied repairs and refused dead dispatches are audited; precondition refusals are not. The audit row's owner axes identify the operator, and the actor digest is a separate binding, not a pseudonym. The OPA v2 catalog now declares 155 operations. OpaBotDeadLetterPanel, exported from @lssm-tech/bundle.managed-companyos/ui/organization-planning, renders the operator surface. The Attendee adapter now refuses astral-plane characters in the bot name and the join announcement, and control characters in the bot name, as invalid_input.

    maintainer

    The CompanyOS API host owns the repair service, store, 0187 audit writes and the Elysia handler under organization-planning/companyos-bot-dead-letter-repair-*; the host mounts the handler inside the opa-capture-integration-routes group (a direct mount on the host chain hits TS2589), and a composed-host test proves both routes reach it. The web OPA proxy does not forward the two routes yet. Attendee field evidence is in docs/evidence/opa/attendee-field-verification-2026-10.md.

  • cmp-opa-handler-ctx-bridge

    OpaV2OperationHandler and OpaV2HandlerRegistry take an explicit host-context type parameter, and the organization-planning spec drops the compatibility facade

    integrator

    OpaV2OperationHandler<Key, TCtx> and OpaV2HandlerRegistry<TCtx> take the host execution context as an explicit type parameter (owner decision B062 (3)). The default is the kernel DefaultOperationHandlerCtx, which every host context extends, so a handler that reads only kernel fields installs in any host. Handlers that read fields only the runtime-core HandlerCtx declares bind it explicitly. The spec no longer depends on @lssm-tech/lib.contracts-spec; it depends on @lssm-tech/lib.contracts-runtime-kernel for type-only operation IO and handler-context types. The change is type-only and has no runtime effect.

    maintainer

    The OPA runtime binds HandlerCtx explicitly in buildOpaV2ProfileHandlers, the public-profile handlers, buildPublicBookingV2Handlers, buildOpaV2Handlers and the meeting-workspace handler registry and service port, so their effective public types are unchanged. listUnavailableOpaV2OperationKeys reads only keys and accepts a registry bound to any host context. The domain-spec-handler-type boundary bridge is deleted.

  • companyos-profile-link-sections

    Public profile links gain social icon placement, section headings, descriptions and mailto URLs

    customer

    In the public profile editor, choose "Social icon" to show a link in the icon row under your name, or keep "Link button" and add an optional section heading and description. Email links use mailto: addresses.

    integrator

    OpaPublicProfileLinkSchema adds optional kind, section and description and accepts mailto URLs; consumers of the public lookup projection may now receive mailto links and should not open them in a new tab.

  • opa-background-replanner

    Governed background re-planning publishes refreshed OPA plan proposals and shows its real status

    maintainer

    Migration 0130 adds run bookkeeping and a dispatcher-only due-job claim function. The planner cron is scheduled every ten minutes and stays a no-op until OPA_REOPTIMIZATION_ENABLED=1 and the dedicated dispatcher credential are configured.

    customer

    Plans refresh in the background when tasks, focus time or preferences change. Refreshed plans are proposals only; Automation controls show whether background planning is active, paused or off, and an added plan session can be undone.

  • opa-booking-instant-time-math

    OPA availability treats offset-bearing ISO strings as instants, fixing public booking slots offset by the host UTC offset

    integrator

    toZonedInstant is an identity for ISO strings with Z or an explicit offset and only resolves floating wall-clock strings in the policy zone. Public booking slots and smart-meeting availability now stay inside the host's local working hours on every side of a DST transition.

    maintainer

    Producers that built windows with a deliberately stale offset and relied on availability to re-derive it must emit correct instants (zonedWallTimeToInstant / formatInstantInZone). No in-repo producer did; weekly-rule and smart-meeting producers already emit instants.

  • opa-booking-slot-grid

    Public booking slots start on clean local boundaries; the minimum-notice cutoff rounds up to the next slot interval

    integrator

    resolvePublicAvailability aligns slot starts to OpaSchedulingLink.slot_interval_minutes (new, optional) counted from local midnight in the policy zone, falling back to the coarsest of 60/30/20/15 minutes that divides the duration. The minimum-notice cutoff, buffers and busy events round up to the next boundary. Starts advance by the interval, so durations longer than the interval yield overlapping candidate starts.

    maintainer

    Tests that asserted a slot at an unrounded instant (busy end, notice cutoff) now expect the next grid boundary. Event types with a duration no standard grid divides (for example 45 min) now offer starts every 15 min, which fills OPA_MAX_PUBLIC_SLOTS sooner.

  • opa-booking-whole-day-pages

    Public booking availability arrives in whole-day pages with a continuation cursor, and the booking page offers later dates

    integrator

    opa.booking.public_availability adds optional hasMore and nextRangeStart output fields. A response holds at most 100 slots and always ends on a whole local day of the visitor time zone. To load later dates, repeat the query with rangeStart = nextRangeStart and the same rangeEnd. Ranges longer than 180 days now fail with RANGE_INVALID. Clients that ignore the new fields keep working and see the first page only. Minimum notice and the booking horizon are measured from the server clock: a past rangeStart is clamped to server now, and confirming a slot inside the notice window is rejected as slot unavailable.

    maintainer

    OPA_MAX_PUBLIC_SLOTS rises from 60 to 100. resolvePublicAvailability accepts max_slots and day_time_zone and returns has_more and next_range_start. The runtime public availability handler anchors notice and horizon to server now (now() dependency for tests) and clamps a past rangeStart. isPublicSlotStillBookable accepts now (default: process clock) and enforces notice and horizon from it; makePublicConfirmHandler takes a now() dependency and createManagedPublicBookingRequest a now input. Tests that re-check fixed-date slots must pass now. PublicBookingAvailabilityDto gains hasMore, nextRangeStart and rangeEnd, and PublicBookingLifecycleConfig gains laterDates.

  • opa-calendar-reauthorization-health

    Public availability declares CALENDAR_REAUTHORIZATION_REQUIRED and booking pages show an honest reconnecting state with a public contact route

    integrator

    Public availability can now fail with the declared code CALENDAR_REAUTHORIZATION_REQUIRED (503, retryable) when the host calendar grant lapsed. The body may include a public contact route (profile URL, display name, up to four https/mailto profile links) and never tenant, workspace, resource or provider references. PublicBookingApiError carries the error body as details.

  • opa-execution-owner

    OPA execution authorization, adapter ports, fake adapters, command persistence and the manual loop move to their spec and runtime owners

    integrator

    Existing module subpaths and names are unchanged and resolve to the same objects; new code can import the canonical spec and runtime subpaths directly.

  • opa-live-meeting-capture

    Add live meeting capture to OPA: a consented live session beside the durable recording, a host-side streaming transcription relay gated to EU-qualified Gateway models, rolling transcript, highlights, and a finalize handoff into the reviewed transcript flow.

    integrator

    Seven additive opa.live_capture.* operations (configuration, start, get, transition, append_audio, add_highlight, finalize) and four content-free live-capture events. The OPA v2 catalog grows from 136 to 143 operations; existing operations are unchanged. Sessions run in live_transcription, record_only or notes_only mode and report why live transcription is unavailable.

    maintainer

    Live transcription is off unless OPA_LIVE_TRANSCRIPTION_ENABLED=1, both OPA_LIVE_TRANSCRIPTION_PROCESSING_APPROVAL_REF and OPA_LIVE_TRANSCRIPTION_GATEWAY_TRANSIT_APPROVAL_REF are set, Gateway auth is present and the shared EU streaming catalog lists a model. The catalog is empty today (no Gateway streaming endpoint lists an EU region), so production reports no_eu_model and the panel runs record-only or notes-only. Migration 0167 adds the live-capture tables.

    maintainer

    The session state machine, window admission, relay against a fake streaming Gateway, encrypted persistence and the React panel have deterministic tests.

  • opa-meeting-context-production-sources

    Budgeted, consent- and grant-checked production context sources for OPA meeting preparation and AI briefings

    integrator

    MeetingContextSourcePort hosts can wrap any source with withMeetingContextSourceBudget and resolve attendees with createMeetingParticipantIdentityReader against MeetingParticipantDirectoryPort implementations (the bridge ships a HubSpot contact directory). The bridge adds read-only Notion and Slack search providers.

    maintainer

    CompanyOS meeting preparation and AI briefings read optional sources only when the owner selected them in the AI briefing settings AND the deployment lists them in OPA_MEETING_CONTEXT_SOURCES (communication-history, participants, drive, notion, slack, hubspot). Default: none, so deploying changes nothing. External grants are read from opa_oauth_tokens under provider keys google-drive, notion, slack, hubspot and accountRef individual:<authority segment of the user id>.

  • opa-meeting-follow-up-delivery

    Governed post-meeting analysis and owner-approved follow-up delivery (email, Work tasks, thread, HubSpot, draft calendar proposal)

    integrator

    New OPA operations opa.meeting_dispatch.approve (POST /api/v2/opa/meeting-dispatch-plans/:ref/approve) and opa.meeting_dispatch.list (GET /api/v2/opa/smart-meetings/:meetingRef/dispatch-plans). opa.meeting_dispatch.plan 2.1.0 accepts optional digest-bound recipients per target and now rejects unapproved artifacts, missing recipients for email/thread/HubSpot, and incompatible artifact kinds. opa.meeting_outcome.analyze 3.2.0 accepts sourceKind transcript|notes. Dispatch targets add hubspot_crm and calendar_follow_up_proposal; effects carry receipts and failure codes; artifacts carry cited insights (decisions, open questions, risks); actions carry quoted owner/due hints and human-only assigneeRef/dueDate.

    maintainer

    Migration 0168 adds the outbox dead_letter state, failure/receipt columns and the opa_meeting_follow_up_deliveries ledger. The API host exposes bearer-only /api/internal/opa/meeting-effects/{authority,deliver}; the worker speaks the v2 delivery envelope, supports OPA_MEETING_EFFECT_KILL_SWITCH and serves /metrics. Delivery stays off until OPA_MEETING_FOLLOWUP_DELIVERY_ENABLED=1 and OPA_MEETING_FOLLOWUP_TARGETS name enabled targets.

    customer

    Meeting owners review the follow-up pack in the OPA meeting detail, choose channels and recipients, confirm every recipient, and see per-channel delivery receipts. Nothing is sent without that approval.

  • opa-meeting-intake-owner-opt-in

    Calendar meeting intake derives jobs from owner opt-ins and connected calendars; OPA_MEETING_INTAKE_ENABLED=1 is the only switch

    customer

    OPA settings has a Meeting intake switch. When on, meetings from the calendars you choose (primary by default, up to ten) appear in OPA as private meetings and feed preparation; recordings imported later attach to them. No recorder is needed. The panel shows the last sync and asks you to reconnect when the calendar grant lapses.

    integrator

    New v2 operations opa.meeting_intake.settings_get and opa.meeting_intake.settings_update on /api/v2/opa/meeting-intake-settings (private owner scope, opa.meeting_work_session.manage, compare-and-set revision with idempotency replay). The OPA v2 catalog grows from 146 to 148 operations. The meeting intake cron result gains state idle and an owners count per state (contract 1.1.0).

    maintainer

    Owner-derived jobs use refs meeting-intake-job:auto:<hex>; the operator JSON pair is optional and serves its scopes as operator_managed. Calendar-only executions materialize private meeting workspaces and occurrence mappings (previously never written in production), which recorder imports, meeting context and briefing context read.

  • opa-meeting-owner-recap-email

    Meeting owners can email the approved recap to their own verified address (owner:self), behind its own flag

    integrator

    Additive: OPA_MEETING_OWNER_RECIPIENT_REF ('owner:self') in @lssm-tech/lib.organization-planning-spec and OPA_MEETING_FOLLOW_UP_CONTRACT 1.1.0. Existing recipient refs, digests and operations are unchanged; 'owner:self' already matched the opaque-ref format. The React follow-up panel (FollowUpPackPanel) offers it; no new React export.

    maintainer

    verified_email now routes owner:self to an owner-only Resend adapter (CompanyOS Briefings purpose sender) gated by OPA_MEETING_FOLLOWUP_OWNER_RECAP_ENABLED=1 and RESEND_API_KEY, inside the existing OPA_MEETING_FOLLOWUP_DELIVERY_ENABLED and OPA_MEETING_FOLLOWUP_TARGETS gates. The runtime database login needs select on managed_auth_email_addresses. It does not write CommunicationOS journal or outbox evidence (owner decision 2026-10-20).

    customer

    When sending a meeting follow-up, owners can tick "Email the recap to me" to receive the approved recap at their verified account address. Nothing is sent to attendees by this option.

  • opa-meeting-recorders-bots-share

    Owner-connected recorder imports, consent-announcing Attendee bots and fragment-token meeting sharing for OPA

    integrator

    Connect recorders through /api/v2/opa/recorder-connections (owner/admin, origin + CSRF). API keys are write-only. Fathom and Fireflies webhooks post to the per-connection /api/webhooks/opa-recorders/:routeToken URL. Granola and tl;dv are polling-only. Public meeting links carry the bearer in the URL fragment, and the viewer resolves them through POST /api/share/meeting.

    maintainer

    Apply migration 0169 (recorder imports) and provision the companyos_recorder_dispatcher login. Imports stay off until OPA_RECORDER_IMPORTS_ENABLED=1, MANAGED_COMPANYOS_RECORDER_DISPATCH_DATABASE_URL, OPA_RECORDER_WEBHOOK_ROUTE_SECRET and OPA_RECORDER_WEBHOOK_BASE_URL are set. Bots stay off until the Attendee DPA and EU approval references exist and resolveCompanyBotReadiness returns ready.

  • opa-meeting-share-list-access-receipts

    List governed meeting shares and audit every public-link resolution with append-only access receipts

    integrator

    Call opa.meeting_share.list (GET /api/v2/opa/meeting-artifacts/:artifactRef/shares) for share inventory with state, expiry, recipient count and access statistics. Only issue returns the public bearer token (share.accessRef), and only once. Resolve public links with Authorization: Bearer meeting-access:<token>, never with a URL parameter.

    maintainer

    Apply the 0170 opa_meeting_share_access_receipts migration (hCircle 0042, Pactena 0010) before you deploy. Public resolve and share listing read and write this table, and they fail closed when it is missing.

  • opa-recorder-connection-ui

    Recorder connections join the OPA v2 manifest, get a read-only weak-match review list, and are reachable through the web proxy

    integrator

    opa.recorder_connection.list/connect/disconnect/sync_now are now part of the frozen OPA v2 catalog (opaV2OperationSpecs, manifest 151 operations). New query opa.recorder_connection.review_list (GET /api/v2/opa/recorder-connections/reviews) returns content-free review items; there is no decision operation yet.

    customer

    Owners and admins can connect Fathom, Fireflies, Granola or tl;dv from Settings once recorder imports are enabled, and see recordings that could not be matched to a meeting. Before enablement the section says imports are not enabled yet.

    maintainer

    The web /api/v2/opa catch-all proxy allowlists recorder-connections routes with a 16 KiB body bound; the production-readiness guard checks the allowlist entry.

  • opa-work-planning-enrollment

    Users are enrolled in work-aware OPA planning automatically or with one click, so the background re-planner can reach them

    customer

    Selecting a company workspace turns on work planning for it. Planner, Focus and Today show an "Enable work planning" action when a workspace is not enrolled yet. Plans stay suggestions; nothing is placed on a calendar without the user.

    maintainer

    Work identity bindings (migration 0034/0081) were created only by a successful plan generation or a Work mutation, so production had none and the re-planner scanned no owners. Enrollment is now explicit, automatic and backfillable, with audit events. Background planning also requires opa.plan_run.manage on the owner's company and personal grants; new owners get it, existing owners need the reconcile below.

  • w5-opa-finish

    OPA Wave 5 gaps: re-plans stop duplicating added sessions, persisted transcription model choice with an honest empty state, optional deletion of recording outcomes, server-side cross-device home mode, booking admin in the user's language, member self-planning by default, and RLS-enforced daily operations.

    integrator

    Additive contracts: companyos.opaHomeMode.get|set, opa.transcription.settings.get|save, an optional deleteDerivedOutcomes input and derivedErasure output on opa.capture.transition (opa.capture-session 1.4.0), and work-planning/applied-placements in the organization-planning runtime. The frontline_staff role template gains opa.plan_run.manage (additive capability).

    maintainer

    Apply migrations 0160 (opa_home_modes on managed_companyos_user_shell_preferences), 0161 (opa_transcription_model_preferences, RLS to opa_app) and 0162 (owner-bounded definer function public.opa_erase_derived_meeting_records owned by opa_migrator, executable by opa_app). Existing members keep their stored grant until re-granted; run the authority repair or reassign the role to give them opa.plan_run.manage. Daily-operations reads/writes now require the personal context row to be visible under RLS for the bound personal tenant.

    customer

    Re-planning no longer suggests work you already added to your calendar. OPA OS opens on the view you chose on any device. Booking settings appear in your language. Members can plan their own work. Settings show which transcription model would be used and say plainly that no EU model is available yet. When deleting a recording you can choose to delete the notes generated from it too.

Migration guide

  • Pass the host context to OPA handler types that read host-specific fields

    Required

    OpaV2OperationHandler<Key> and OpaV2HandlerRegistry previously typed ctx as the runtime-core HandlerCtx. They now default to the kernel DefaultOperationHandlerCtx. Code that reads only kernel fields (userId, tenantId, workspaceId, actor, decide, eventPublisher and the other OperationHandlerCtx members) needs no change.

    When: Before upgrading a host that annotates OPA handlers or handler registries without a context type argument and reads HandlerCtx-only fields or stores runtime-built registries in the default type.

    1. Replace OpaV2OperationHandler<Key> with OpaV2OperationHandler<Key, HandlerCtx> where the handler reads appConfig, integrations, knowledge, queryEnvelope or the HandlerCtx telemetry tracker.
    2. Replace OpaV2HandlerRegistry with OpaV2HandlerRegistry<HandlerCtx> where it holds the result of buildOpaV2Handlers or other HandlerCtx-bound handlers.
    3. Import HandlerCtx from @lssm-tech/lib.contracts-runtime-core.
  • Mount the repair routes and panel

    Additive. The CompanyOS API host mounts the routes; the panel does nothing until a web host forwards them and renders it. Repairs need migration 0187 applied (companyos_opa_bot_repair_audit).

    1. Forward bot-dead-letters and bot-dead-letters/<captureRef>/repair in the web OPA proxy and render OpaBotDeadLetterPanel on an operator page; the CompanyOS API host already mounts opaBotDeadLetterRepairHandler.
    2. Apply migration 0187 before enabling the repair route in an environment.
  • Apply migration 0130 before enabling the dispatcher

    Required

    Additive columns and a SECURITY DEFINER function executable only by companyos_planning_dispatcher.

    1. Apply migrations 0086, 0087 and 0130 through the application migration catalog.
    2. Provision MANAGED_COMPANYOS_PLANNING_DISPATCH_DATABASE_URL for the companyos_planning_dispatcher role (function execution only, distinct from LSSM_STUDIO_DATABASE_URL).
    3. Set OPA_REOPTIMIZATION_ENABLED=1 to activate; unset it to stop all background planning immediately. OPA_PLANNING_SUGGESTIONS_ENABLED is no longer read.
  • Optionally render the reconnecting state for custom public booking hosts

    Additive only. Hosts using PublicBookingTemplateClient get the state automatically when their transport passes the JSON error body as the second PublicBookingApiError argument.

    1. Pass the parsed error body as details when constructing PublicBookingApiError in a custom transport.
    2. Treat CALENDAR_REAUTHORIZATION_REQUIRED as retryable later; do not retry in a tight loop.
  • Optionally mount the live capture panel

    Additive. Hosts that proxy /api/v2/opa must allow the live-capture routes (the web monolith proxy does) and a 660 kB body for audio windows.

    1. Apply migration 0167 before enabling the routes.
    2. Render OpaLiveCapturePanel in the meeting view; it degrades by itself when transcription or recording is not admitted.
  • Optionally enable meeting context sources

    Additive. No schema migration. Set OPA_MEETING_CONTEXT_SOURCES to the kinds to offer; Google Drive and HubSpot token refresh reuse MANAGED_COMPANYOS_GOOGLE_CALENDAR_CLIENT_ID/SECRET and HUBSPOT_OAUTH_CLIENT_ID/SECRET.

    1. Set OPA_MEETING_CONTEXT_SOURCES=communication-history to start with the CommunicationOS source.
  • Apply migration 0168 before deploying the worker

    Required

    The worker settles leases with the new dead_letter state and receipt/error columns. Run the API migration catalog (0168 organization-planning-runtime/opa-meeting-follow-up-0168) as opa_migrator before rolling out the new worker image.

    1. Run the API application migrations so contract 0168 is applied.
    2. Deploy the API host, then the meeting effect worker.
  • Delivery receivers move to the v2 envelope

    Required

    The worker no longer posts artifact content (v1). Any custom OPA_MEETING_EFFECT_DELIVERY_URL receiver must implement OpaMeetingEffectDeliveryRequestSchema / OpaMeetingEffectDeliveryResponseSchema. No v1 receiver was deployed.

    1. Point OPA_MEETING_EFFECT_DELIVERY_URL at the API host's /api/internal/opa/meeting-effects/deliver.
  • Apply the recorder imports migration

    Required

    Additive tables opa_recorder_connections, opa_recorder_imports and opa_recorder_webhook_receipts with forced owner RLS, plus the identifier-only dispatcher role functions.

    1. Apply companyos/opa-recorder-imports-0169 through the app migration ledger before you deploy.
    2. Provision a login for companyos_recorder_dispatcher and set MANAGED_COMPANYOS_RECORDER_DISPATCH_DATABASE_URL.
  • Apply the meeting-share access receipt migration

    Required

    Additive table with forced owner RLS and select/insert grants for opa_app. It references opa_meeting_shares.

    1. Apply opaMeetingShareAccessMigrationStatements() through the host migration ledger before you roll out the runtime.
  • Enroll existing users

    Required

    Idempotent; creates bindings only for active memberships with an enabled grant on an active company workspace.

    1. Back up managed_companyos_work_identity_bindings and managed_companyos_audit_events.
    2. Run COMPANYOS_WORK_PLANNING_BACKFILL=dry-run bun run companyos:opa:backfill-work-planning and review the per-organization counts.
    3. Run it again with COMPANYOS_WORK_PLANNING_BACKFILL=1; a re-run reports every binding as existing.
  • Grant background planning to existing owners

    Additive owner capability reconcile (company workspaces and the owner's personal context).

    1. Run COMPANYOS_OPA_MEETING_AUTHORITY_RECONCILE=dry-run bun run companyos:opa:reconcile-meeting-authority and check that only opa.plan_run.manage is missing.
    2. Apply with COMPANYOS_OPA_MEETING_AUTHORITY_RECONCILE=1 after the owner approves the grant.
  • Apply migrations 0160–0162

    Required

    Additive schema; existing rows default to no preference.

    1. Run the tracked CompanyOS migration runner so 0160, 0161 and 0162 are applied in order.
    2. Verify public.opa_erase_derived_meeting_records(jsonb) is owned by opa_migrator and executable by opa_app.
  • Give existing members self-planning

    Optional; new joins and new frontline_staff assignments already receive it.

    1. Dry-run the authority repair that adds the joined-member template, then apply it, or reassign the role in AuthOS.
  • Apply the meeting intake owner settings migration

    Required

    Apply app migration 0174 (companyos/opa-meeting-intake-settings-0174) with the tracked runner as opa_migrator before deploying the API; the settings routes and the cron owner listing fail closed without it.

    1. Apply app migration 0174 with the tracked runner before deploying the CompanyOS API.
  • Count recorder operations in the v2 catalog

    Additive. Consumers that pin the OPA v2 operation count or iterate opaV2Operations now see five more operations; existing operations are unchanged.

    1. Update any local snapshot of the OPA v2 operation count from 146 to 151.

Upgrade steps

  • Register the meeting-context OAuth clients

    manual

    Each provider needs an app, the API callback as redirect URI and its client credentials before owners can connect it.

    Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/bundle.managed-companyos

    1. Register https://api.companyos.run/api/companyos/opa/briefings/meeting-context/<provider>/callback for google-drive, notion, slack and hubspot with the matching provider app.
    2. Set GOOGLE_DRIVE_OAUTH_CLIENT_ID/SECRET to a Google OAuth client of Drive's own, in a Google Cloud project other than the calendar one, with the restricted scope drive.metadata.readonly; never reuse MANAGED_COMPANYOS_GOOGLE_CALENDAR_CLIENT_ID/SECRET (an equal client id is refused), because Google revocation drops every scope a user granted a client. Drive grants no longer refresh with the calendar client.
    3. Set NOTION_OAUTH_CLIENT_ID/SECRET, SLACK_OAUTH_CLIENT_ID/SECRET (user scope search:read, token rotation off) and HUBSPOT_OAUTH_CLIENT_ID/SECRET (scopes oauth crm.objects.contacts.read).
    4. Open each prepared provider in OPA_MEETING_CONTEXT_CONNECT_SOURCES (drive, notion, slack, hubspot); unlisted providers stay "not available" even when their client is set.
    5. Run the connect canary per provider, then add the kind to OPA_MEETING_CONTEXT_SOURCES; never list a kind before its connect canary passed.
  • Verify OPA handler host-context binding

    auto

    Run the organization-planning spec and runtime typechecks and the handler-type tests.

    Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/lib.organization-planning-runtime

    1. Run bun run typecheck in packages/domains/organization-planning/spec and packages/domains/organization-planning/runtime.
    2. Run bun test src/operations/opa-v2-handler-types.test.ts src/operations/opa-v2-handler-context.test.ts in the organization-planning spec.
    3. Run bun test src/ops-registry-v2.test.ts in the organization-planning runtime.
  • Pause background planning per workspace or user

    manual

    Background planning follows the "Plan work" automation policy.

    Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/lib.organization-planning-runtime, @lssm-tech/bundle.managed-companyos

    1. Set the workspace ceiling for "Plan work" to "Manual only" (or "Disabled") to pause it for a workspace; users can do the same for themselves.
    2. Repair a dead-lettered owner with PlanningReoptimizationJobs.repair after reproving authority.
  • Switch on calendar meeting intake

    manual

    Set the flag, then owners opt in from OPA settings; no JSON is needed.

    Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/lib.organization-planning-runtime, @lssm-tech/bundle.managed-companyos

    1. Set OPA_MEETING_INTAKE_ENABLED=1 on the CompanyOS API.
    2. Each owner turns on Meeting intake in OPA settings for each workspace.
    3. Watch one cron cycle; idle with owner counts or completed with provisioned and completed counts is expected.
  • Enable the owner recap email

    manual

    Optional. Without the flag, owner:self effects dead-letter as adapter_unavailable, so enable it before offering the option or keep verified_email out of the targets.

    Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/lib.organization-planning-react

    1. Grant select on managed_auth_email_addresses to the runtime login if it is not the table owner.
    2. Set OPA_MEETING_FOLLOWUP_OWNER_RECAP_ENABLED=1 (RESEND_API_KEY and the Resend purpose senders are already set for briefings).
    3. Add verified_email to OPA_MEETING_FOLLOWUP_TARGETS.

Unique release changes

  • The en catalogs stop falling back to themselves, the video-gen LLM prompts become ICU-valid so their placeholders validate, and the last low-count hardcoded copy in the OPA bridges, the OPA booking widget and the self-improvement controllers moves to catalogs. i18n:check reports 0 warnings and the hardcoded-string allowlist shrinks from 319 to 273 packages.

    35 packages · 35 occurrences

  • Additive schema; existing rows default to no preference.

    7 packages · 7 occurrences

  • Additive tables opa_recorder_connections, opa_recorder_imports and opa_recorder_webhook_receipts with forced owner RLS, plus the identifier-only dispatcher role functions.

    7 packages · 7 occurrences

  • OPA Wave 5 gaps: re-plans stop duplicating added sessions, persisted transcription model choice with an honest empty state, optional deletion of recording outcomes, server-side cross-device home mode, booking admin in the user's language, member self-planning by default, and RLS-enforced daily operations.

    7 packages · 7 occurrences

  • Optional; new joins and new frontline_staff assignments already receive it.

    7 packages · 7 occurrences

  • Owner-connected recorder imports, consent-announcing Attendee bots and fragment-token meeting sharing for OPA

    7 packages · 7 occurrences

  • Additive. No schema migration. Set OPA_MEETING_CONTEXT_SOURCES to the kinds to offer; Google Drive and HubSpot token refresh reuse MANAGED_COMPANYOS_GOOGLE_CALENDAR_CLIENT_ID/SECRET and HUBSPOT_OAUTH_CLIENT_ID/SECRET.

    6 packages · 6 occurrences

  • Budgeted, consent- and grant-checked production context sources for OPA meeting preparation and AI briefings

    6 packages · 6 occurrences

  • Add live meeting capture to OPA: a consented live session beside the durable recording, a host-side streaming transcription relay gated to EU-qualified Gateway models, rolling transcript, highlights, and a finalize handoff into the reviewed transcript flow.

    5 packages · 5 occurrences

  • Additive. Hosts that proxy /api/v2/opa must allow the live-capture routes (the web monolith proxy does) and a 660 kB body for audio windows.

    5 packages · 5 occurrences

  • Public booking availability arrives in whole-day pages with a continuation cursor, and the booking page offers later dates

    4 packages · 4 occurrences

  • Additive columns and a SECURITY DEFINER function executable only by companyos_planning_dispatcher.

    3 packages · 3 occurrences

  • Additive only. Hosts using PublicBookingTemplateClient get the state automatically when their transport passes the JSON error body as the second PublicBookingApiError argument.

    3 packages · 3 occurrences

  • Additive. Consumers that pin the OPA v2 operation count or iterate opaV2Operations now see five more operations; existing operations are unchanged.

    3 packages · 3 occurrences

  • Additive. The CompanyOS API host mounts the routes; the panel does nothing until a web host forwards them and renders it. Repairs need migration 0187 applied (companyos_opa_bot_repair_audit).

    3 packages · 3 occurrences

  • Apply app migration 0174 (companyos/opa-meeting-intake-settings-0174) with the tracked runner as opa_migrator before deploying the API; the settings routes and the cron owner listing fail closed without it.

    3 packages · 3 occurrences

  • Background planning follows the "Plan work" automation policy.

    3 packages · 3 occurrences

  • Calendar meeting intake derives jobs from owner opt-ins and connected calendars; OPA_MEETING_INTAKE_ENABLED=1 is the only switch

    3 packages · 3 occurrences

  • Canonical OPA policy ownership with compatible runtime and module imports

    3 packages · 3 occurrences

  • Governed background re-planning publishes refreshed OPA plan proposals and shows its real status

    3 packages · 3 occurrences

  • Governed post-meeting analysis and owner-approved follow-up delivery (email, Work tasks, thread, HubSpot, draft calendar proposal)

    3 packages · 3 occurrences

  • OPA execution authorization, adapter ports, fake adapters, command persistence and the manual loop move to their spec and runtime owners

    3 packages · 3 occurrences

  • Operator repair of dead-lettered notetaker bot work with a reviewed path past the recovery window, and Attendee adapter field verification

    3 packages · 3 occurrences

  • Public availability declares CALENDAR_REAUTHORIZATION_REQUIRED and booking pages show an honest reconnecting state with a public contact route

    3 packages · 3 occurrences

  • Public profile links gain social icon placement, section headings, descriptions and mailto URLs

    3 packages · 3 occurrences

  • Recorder connections join the OPA v2 manifest, get a read-only weak-match review list, and are reachable through the web proxy

    3 packages · 3 occurrences

  • Set the flag, then owners opt in from OPA settings; no JSON is needed.

    3 packages · 3 occurrences

  • The worker no longer posts artifact content (v1). Any custom OPA_MEETING_EFFECT_DELIVERY_URL receiver must implement OpaMeetingEffectDeliveryRequestSchema / OpaMeetingEffectDeliveryResponseSchema. No v1 receiver was deployed.

    3 packages · 3 occurrences

  • The worker settles leases with the new dead_letter state and receipt/error columns. Run the API migration catalog (0168 organization-planning-runtime/opa-meeting-follow-up-0168) as opa_migrator before rolling out the new worker image.

    3 packages · 3 occurrences

  • Additive owner capability reconcile (company workspaces and the owner's personal context).

    2 packages · 2 occurrences

  • Additive table with forced owner RLS and select/insert grants for opa_app. It references opa_meeting_shares.

    2 packages · 2 occurrences

  • Each provider needs an app, the API callback as redirect URI and its client credentials before owners can connect it.

    2 packages · 2 occurrences

  • Idempotent; creates bindings only for active memberships with an enabled grant on an active company workspace.

    2 packages · 2 occurrences

  • List governed meeting shares and audit every public-link resolution with append-only access receipts

    2 packages · 2 occurrences

  • Meeting owners can email the approved recap to their own verified address (owner:self), behind its own flag

    2 packages · 2 occurrences

  • OpaV2OperationHandler and OpaV2HandlerRegistry take an explicit host-context type parameter, and the organization-planning spec drops the compatibility facade

    2 packages · 2 occurrences

  • OpaV2OperationHandler<Key> and OpaV2HandlerRegistry previously typed ctx as the runtime-core HandlerCtx. They now default to the kernel DefaultOperationHandlerCtx. Code that reads only kernel fields (userId, tenantId, workspaceId, actor, decide, eventPublisher and the other OperationHandlerCtx members) needs no change.

    2 packages · 2 occurrences

  • Optional. Without the flag, owner:self effects dead-letter as adapter_unavailable, so enable it before offering the option or keep verified_email out of the targets.

    2 packages · 2 occurrences

  • Personal OAuth connect flows for the Drive, Notion, Slack and HubSpot meeting-context sources

    2 packages · 2 occurrences

  • Run the organization-planning spec and runtime typechecks and the handler-type tests.

    2 packages · 2 occurrences

  • Users are enrolled in work-aware OPA planning automatically or with one click, so the background re-planner can reach them

    2 packages · 2 occurrences

  • OPA availability treats offset-bearing ISO strings as instants, fixing public booking slots offset by the host UTC offset

    1 package · 1 occurrence

  • Public booking slots start on clean local boundaries; the minimum-notice cutoff rounds up to the next slot interval

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/app.communicationos-api

    Layer: apps · 2 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 1 change

  • @lssm-tech/bundle.self-improving-system

    Layer: bundles · 1 change

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

    Layer: integrations · 1 change

  • @lssm-tech/integration.opa-meeting-context-bridge

    Layer: integrations · 2 changes

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

    Layer: integrations · 1 change

  • @lssm-tech/integration.provider-meeting-recorder

    Layer: integrations · 2 changes

  • @lssm-tech/lib.accessibility

    Layer: libs · 1 change

  • @lssm-tech/lib.authos-spec

    Layer: libs · 3 changes

  • @lssm-tech/lib.companyos-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.companyos-spec

    Layer: libs · 3 changes

  • @lssm-tech/lib.content-gen

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-integrations

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-runtime-client-react

    Layer: libs · 1 change

  • @lssm-tech/lib.data-exchange-client

    Layer: libs · 1 change

  • @lssm-tech/lib.design-system

    Layer: libs · 1 change

  • @lssm-tech/lib.example-shared-ui

    Layer: libs · 1 change

  • @lssm-tech/lib.image-gen

    Layer: libs · 1 change

  • @lssm-tech/lib.knowledge

    Layer: libs · 1 change

  • @lssm-tech/lib.lifecycle

    Layer: libs · 1 change

  • @lssm-tech/lib.notification

    Layer: libs · 1 change

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

    Layer: libs · 2 changes

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

    Layer: libs · 1 change

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

    Layer: libs · 1 change

  • @lssm-tech/lib.presentation-runtime-react

    Layer: libs · 1 change

  • @lssm-tech/lib.provider-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.support-bot

    Layer: libs · 1 change

  • @lssm-tech/lib.surface-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.video-gen

    Layer: libs · 1 change

  • @lssm-tech/lib.voice

    Layer: libs · 1 change

  • @lssm-tech/module.agent-fleet

    Layer: modules · 1 change

  • @lssm-tech/module.ai-chat

    Layer: modules · 1 change

  • @lssm-tech/module.auth-os

    Layer: modules · 3 changes

  • @lssm-tech/module.billing-os

    Layer: modules · 1 change

  • @lssm-tech/module.builder-workbench

    Layer: modules · 1 change

  • @lssm-tech/module.communication-os

    Layer: modules · 1 change

  • @lssm-tech/module.companyos

    Layer: modules · 1 change

  • @lssm-tech/module.execution-console

    Layer: modules · 1 change

  • @lssm-tech/module.governance-suite

    Layer: modules · 1 change

  • @lssm-tech/module.learning-journey

    Layer: modules · 1 change

  • @lssm-tech/module.lifecycle-advisor

    Layer: modules · 1 change

  • @lssm-tech/module.lifecycle-core

    Layer: modules · 1 change

  • @lssm-tech/module.organization-planning

    Layer: modules · 1 change

  • @lssm-tech/module.review-queue

    Layer: modules · 1 change

  • @lssm-tech/module.workflow-orchestration

    Layer: modules · 1 change

  • @lssm-tech/opa-booking-react

    Layer: libs · 1 change