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) andresolveOpaAdaptiveSurface(opa-personalization-bridge) accept an optionallocale(en,frores). The default Google event title of a booking without its own summary and the surfacereasonstrace now resolve from the OPA catalog keyscalendar.booking.defaultSummaryandexperience.personalization.reason.*; without a locale they stay English and identical to before.createSelfImprovementControllersV1(dataSource, { locale })titles each operator panel from the newself-improving-system.messagescatalog; without options the titles are unchanged. The OPA catalogorganization-planning.messagesmoves to version 1.2.0 with the four new keys, andCALENDAR_KEYSis 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 thepackageDeclarationMetadata(app blueprints and integration specs),protocolText(HTTP reason phrases, the JSON-RPC internal error message and theBearerprefix) anddeveloperErrorMessages(thrown developer errors, problem details and log lines in packages with no user locale) allowlist categories, plus two brand names.unmigratedPackagesdrops from 319 to 273: four entries outside the scan, 37 packages those categories clear and five packages whose copy moved to catalogs.SEEDED_BASELINE_COUNTis lowered to 273 and a new guard test fails on any entry that names no scanned file. The private marketing-operations app now logsMARKETING_APP_READYat 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_CONTRACT1.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/settingswithmeetingContext,providerand, on failure,reason(denied,state_invalid,exchange_failed,scope_missing,session_required,unavailable).maintainer
Grants live in
opa_oauth_tokensunderindividual:<authority segment(userId)>in the owner's personal tenant. The live connect attempt is the rowmeeting-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_appholds 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.