Skip to content
← Back to changelog index

2.1.4

Nov 05, 2026 · 40 packages · 75 unique changes · 40 release entries

appsbundlesintegrationslibsmodulesBreaking changes

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

  • authos-better-auth-schema-check-identity

    The canonical-email adapter wrapper keeps the adapter's identity so Better Auth's schema self-check can find it.

    integrator

    withCanonicalEmailDatabaseLookup returns the adapter object the database factory built, with findOne replaced as an own property, instead of a Proxy. Better Auth's schema self-check, keyed by adapter identity, is therefore registered for compositions that only add canonical-email lookups. Once it is registered, Better Auth awaits it before handling auth requests and logs a mismatch at startup.

    maintainer

    withSsoSecretEncryption still wraps the adapter in a Proxy, so compositions with the sso plugin (such as the CompanyOS API) keep the schema check disabled until that wrapper also preserves the adapter's identity.

  • authos-better-auth-server-entry

    authos-better-auth adds an explicit server-only ./server entry; the root barrel stays compatible

    integrator

    Server hosts may import @lssm-tech/integration.authos-better-auth/server; browser and native code imports ./client or ./native-session-client. Existing root imports keep working.

  • authos-idp-oauth-provider-1-7-schema

    Better Auth 1.7.5 OAuth-provider schema (migration 0176) and back-channel origin handling for the central LSSM IdP

    maintainer

    Apply tracked migration 0176 before promoting an lssm-identity-api build on Better Auth 1.7.5. Without it, /api/auth/jwks and /api/auth/oauth2/authorize answer 500 on the production database.

  • authos-oauth-second-factor

    AuthOS: OAuth/social sign-ins of TOTP-enrolled identities are challenged for the second factor unless the device is trusted, and the CompanyOS client registration ceremony on the central IdP uses central-only env names.

    integrator

    Hosts that enable the two-factor bridge plugin now challenge OAuth sign-ins too. Set the new optional twoFactorChallengePage bridge config to the page that renders the pending MFA challenge; it receives the original destination as ?callback=. Without it, the callback URL is reused with twoFactorRedirect=true and no session.

    maintainer

    To register companyos-web on id.lssm.co, set LSSM_IDP_COMPANYOS_RP_ENABLED, LSSM_IDP_COMPANYOS_RP_SECURITY_REVIEW_REF, LSSM_IDP_COMPANYOS_RP_CLIENT_SECRET and LSSM_IDP_RP_RECONCILE_TOKEN on the identity API (never LSSM_RP_*), redeploy, reconcile, then remove them.

    customer

    If you turned on an authenticator app, signing in with LSSM, Google, Microsoft, LinkedIn or GitHub now asks for your code too, unless you trusted this browser.

  • authos-product-admission-adapters

    Brand-neutral verified-identity and reviewed-membership product admission adapters with monolith wiring.

    integrator

    New server-only subpaths under ./product-admission/*; no existing export or behavior changes. Hosts supply binding rows {productApplicationId, relyingPartyId, mode, accessTier} and inject session, operator and revocation ports.

  • authos-shared-oidc-subject-binding-20261102

    Bind strict relying-party profile and account subjects to the verified ID token.

    maintainer

    Strict OIDC fallback cannot replace the verified subject or share claim state across callbacks.

  • authos-sso-adapter-schema-check

    The SSO client-secret adapter wrapper forwards Better Auth's schema self-check, so compositions with the sso plugin detect schema drift.

    integrator

    withSsoSecretEncryption registers each wrapper with the schema check of the adapter it wraps, so $context.checkSchema is defined when the sso plugin is enabled (it was undefined before). Encryption of SSO OIDC client secrets at rest is unchanged, and the wrapped adapter is not modified. Behaviour tightening: Better Auth awaits the check before every auth request, and a schema mismatch fails the request with SchemaMismatchError.

    maintainer

    The package declares @better-auth/core 1.7.5 (already a peer of its Better Auth plugin dependencies) as a direct dependency for registerSchemaCheck and schemaCheckFor. Keep it pinned to the better-auth version.

  • builder-existing-control-plane-build

    Build existing Builder control-plane leaves and preserve export manifests

    integrator

    Existing advertised control-plane leaves produce their canonical build outputs without rewriting the explicit manifest.

  • canonical-control-plane-operations

    Preserve ControlPlane operation identity through canonical Builder declarations

    integrator

    Historical execution approval, rejection and trace imports forward to the same canonical Builder declarations.

  • cmp-auth-and-product-schema-rehearsals

    Better Auth schema check helpers and local schema rehearsal scripts for CompanyOS, hCircle and Pactena

    integrator

    runBetterAuthSchemaCheck(await auth.$context) reports whether the composed instance still has its schema check (unregistered means an adapter wrapper dropped it) and returns mismatch findings as data. findBetterAuthStoreSchemaProblems(options, tables) compares the tables the plugins write with introspected tables given in the adapter's logical names. Both are read-only.

    maintainer

    Three operator scripts rehearse schema work on loopback test databases: the CompanyOS Better Auth check per production profile, the hCircle meeting host provisioning and migrations, and the Pactena 0007-0010 apply at boot. Evidence and the provisioning steps are in docs/evidence/authos/better-auth-schema-rehearsal-2026-10-27.md and docs/evidence/opa/rehearsals/.

  • cmp-fix-lssm-runtime-portable-declarations

    Preserve portable claimed queue envelope and fixture declarations

    integrator

    Queue envelope declarations retain their canonical inferred types and runtime behavior.

  • cmp-meeting-intake-sync-and-titles

    Meeting intake gets calendar push channels and delta sync, retires meetings whose event moved or was cancelled, names materialized meetings, and exposes its readiness to operators

    customer

    Once the operator turns them on, meetings OPA creates from your calendar show the event title in your private recent meetings (filterable by title or note), a meeting whose event moved or was cancelled no longer lingers there unless you wrote in it, and calendar changes reach OPA within minutes instead of at the next poll.

    integrator

    @lssm-tech/integration.provider-calendar adds push channels and delta sync: ./impls/calendar-sync (calendarPushChannelToken, constant-time verifyCalendarPushChannelToken, CalendarSyncSession, CalendarDeltaResult), Google events.watch channels, header parsing and syncToken sync (./impls/google-calendar-push, ./impls/google-calendar-delta, createGoogleCalendarSyncSessionWithTokens), and Microsoft Graph subscriptions, validation handshake, notification parsing and calendarView/delta (./impls/microsoft-graph-push, ./impls/microsoft-graph-delta, createMicrosoftCalendarSyncSession). The Graph transport now admits /subscriptions and calendarView/delta paths. OpaPrivateMeetingRecentItemSchema (opa.meeting_workspace.recent) gains an optional plain-text title (1-200 characters); the schema stays strict, so a client built before this change rejects a response that carries a title.

    maintainer

    The CompanyOS API owns migrations 0185-0189 (B242): 0185 calendar push channels and encrypted delta cursors, 0186 encrypted intake titles and retirements, 0187 the append-only bot repair audit (B164), 0188 the live-capture retention index, discovery function and capture-runtime deletes (B175), and 0189 the OPA service price table (seeded unpriced) and usage records (B170). The API host mounts the guarded readiness route GET /api/opa/meeting-intake/readiness (key names only), POST /api/webhooks/calendar-push/google and /microsoft, and the cron GET /api/cron/meeting-intake-push-channels, which vercel.json and the deploy/lssm-ecosystem CompanyOS API profile schedule every 30 minutes.

  • control-plane-skills-owner

    Canonical owners for messaging policy and signed control-plane skill contracts

    integrator

    Import skill schemas from lssm-os-spec, signing and verification from lssm-os-runtime/control-plane/skills, and messaging policy from builder-spec.

  • current-growth-model-form-owner

    Own complete marketing model and FormSpec families in Growth.

    maintainer

    Preserve full marketing types, canonical FormSpec identity and compatibility paths.

  • current-growth-operation-owner

    Canonicalize complete marketing operations and remove the Growth Legacy return.

    maintainer

    Preserve operation objects, schemas, policies and compatibility exports.

  • cving-01a-host

    The job-application API and MCP hosts inject CV original custody over the existing candidate S3 configuration with a distinct CV prefix, failing closed when it is absent.

    maintainer

    The API and MCP from-environment compositions build cvOriginalCustody with createRailwayCvOriginalCustodyV1 over JOB_APPLICATION_S3_* and the new JOB_APPLICATION_CV_S3_PREFIX (default candidate-cv-originals/, must not overlap the document, inbox or export prefixes) and pass cvImageTranscriptionEnabled false, only together with profileEvidenceKey. A missing bucket or incomplete endpoint, region or credential set composes no custody and the CV ingestion operations stay JOB_APPLICATION_OPERATION_UNSUPPORTED; invalid present values fail at startup with a code and no value. The worker host composes no profileEvidenceKey and does not run CV operations, so it is unchanged.

    integrator

    Both apps depend on @lssm-tech/integration.job-application-effects-dependencies-railway, which exposes the ./cv-original-custody subpath. Set JOB_APPLICATION_CV_S3_PREFIX per deployment if the default prefix is not wanted.

  • fo2-s04-knowledge-live-stack

    Live evidence ingestion and grounded answers run on Supabase Storage, pgvector in the evidence database and the Vercel AI Gateway; no S3 vendor account, Qdrant or embedding/OCR vendor key is needed

    integrator

    New adapters: supabaseStorageS3ClientConfig with S3ObjectWriter conditionalWrite head-verify for Supabase Storage, GatewayEmbeddingProvider for Vercel AI Gateway embeddings, SupabaseVectorProvider extensionSchema, and createCompanyIntelligenceEvidenceVectorStore for tenant-isolated pgvector evidence. Knowledge evidence vector requests carry an additional tenantId field; vector stores without tenancy ignore it, tenant-isolated stores require it.

    maintainer

    The CompanyOS API document evidence composition now defaults to pgvector (migration 0180, managed_companyos_ci_evidence_vectors, vector(1536) in the extensions schema, RLS on app.tenant_id) unless COMPANY_INTELLIGENCE_QDRANT_URL is set; Gateway embedding and OCR routes use AI_GATEWAY_API_KEY or VERCEL_OIDC_TOKEN; COMPANY_INTELLIGENCE_EMBEDDING_API_KEY is required only for direct openai/mistral routes. Health capabilities gain an ocr entry. Composition never throws while the API module loads: invalid Gateway inferenceProviders, a malformed Supabase region or https URL, an OCR model outside the EU Gateway catalog and a provider constructor refusal are all reported by name as configuration_required. health.get reports the vector dependency unavailable when pgvector is selected and the 0180 table is absent. docs/operations/founder-ops-v2/knowledge-stack.md lists the bucket, route and variable names an operator must set.

  • fo2-s06-meeting-evidence-briefings

    Account-scoped Granola/calendar meeting evidence, private meeting preparation, durable briefing occurrences and approval-gated follow-through

    integrator

    Granola reads are exact-identity, bounded and fail with redacted typed codes; hosts persist evidence through MeetingEvidenceStorePort and read explicit freshness. @lssm-tech/bundle.managed-companyos/meeting-intelligence-founder-ops exposes DailyBriefModel, MeetingPreparationPack, MEETING_PREPARATION_RECIPE and services whose ports bind to the existing occurrence claim store, grounded knowledge, Work and CommunicationOS delivery owners.

  • fo2-s06-meetings-live-readiness

    Notetaker bot live-readiness (readiness names and a disabled state, cron gating, reauthorization alerts, dead-letter recovery through migration 0195); production stays off.

    maintainer

    AttendeeCaptureError gains the unauthorized code for HTTP 401 (other 4xx stay rejected); exhaustive switches over the code union must handle it. resolveCompanyBotReadiness keeps its signature and output fields; its verdict union gains disabled (OPA_BOTS_ENABLED is not 1), the BOTS_DISABLED blocker code is retired, and the new codes are ENV_INVALID (with the key name) and CAPTURE_STORAGE_REGION_NOT_EU. OPA_CAPTURE_STORAGE_REGION is now a required readiness key.

    integrator

    Nothing changes while OPA_BOTS_ENABLED is unset. To go live follow section 4 of docs/operations/founder-ops-v2/meetings-enable.md: Attendee DPA and EU evidence, migrations 0165 and 0195, the dispatcher login and the OPA_BOTS_* values. No route exposes the readiness verdict, so check the key names against the deployment's environment listing first; after the switch is set, any gap makes both bot crons answer 503 and log opa-bots.configuration_required with blocker codes and key names. Rollback is unsetting OPA_BOTS_ENABLED.

  • fo2-s08-founder-coding-improvement

    Agent fleet adds durable coding-agent supervision, proactive proposals, governed workflow improvement and use-case proposals for founder operations

    integrator

    @lssm-tech/module.agent-fleet/core exports SupervisedCodingSessionService, ProactiveProposalService, WorkflowImprovementService with createWorkflowImprovementAdapter, reviewUseCaseProposals and the shared FounderProposalV1 contract. Hosts bind durable stores, provider control (Agent Host, Runtime Node, Claude Code or Codex adapters), notification, authority, quiet-hours and Work-creation ports. Workflow improvement uses GovernedAiImprovementRuntimeV2, so failed evaluations are rejected and production promotion needs a human approval.

  • growth-marketing-tail-ownership

    Move marketing validation, forms and sample handlers to canonical Growth owners

    integrator

    Legacy marketing paths preserve fixture objects, form schemas and deterministic handler behavior through Growth packages.

  • hook-authority-runtime-owner

    Canonical Hook Authority runtime ownership with preserved private packaging and compatibility

    integrator

    Use lssm-os-runtime/control-plane/hook-authority and the digest, validation and reference-adapter leaves.

  • job-application-fact-revised-consumer-2

    Store migration 0019, key-dispatched invalidation recording with the sibling rule, and revised-event consumption in the managed-runtime consumer and worker.

    integrator

    JobApplicationProfileFactInvalidationEventV1 gains an optional key (no-longer-confirmed when omitted, or job-application.profile.fact.revised; any other key is refused with JOB_APPLICATION_PROFILE_FACT_INVALIDATION_EVENT_INVALID) and JobApplicationProfileFactInvalidationResultV1 gains siblings. The invalidation consumer now records streamed revised events instead of ignoring them, so exact packet submits refuse on dependents invalidated by any material fact revision, not only a withdrawal.

    customer

    Apply job-application-store migration 0019 after 0018 before running a worker of this release with JOB_APPLICATION_PROFILE_FACT_INVALIDATION_ENABLED; without it recording a revised invalidation fails the reason check and that candidate's drain stops at the event. Then run the store conformance.

    maintainer

    A withdrawn confirmed fact appends revised then no-longer-confirmed with one receipt and the same dependents; the first event stored in sequence order keeps its reason (normally revised), the other is a sibling and writes nothing. Real-Postgres conformance of 0019 has not been run.

  • job-application-inbox-subject-sealed

    Inbox message subjects are sealed under the per-candidate data key behind an opaque subject_ref (store migration 0029 drops the plaintext column); the managed Resend webhook requires the deployment material key.

    integrator

    PostgresJobApplicationInboxStoreV1(client, scope, objects, keys, now) takes a candidate data-key strategy (inboxSubjectKeysV1; the legacy key form is refused with APPLICATION_INBOX_SUBJECT_KEY_STRATEGY_INVALID); readApplicationInboxV1 message rows carry subject_ref (sealed reference, null for legacy rows, or deleted) and no subject; openInboxSubjectV1 opens a reference of its own scope; store() can now refuse with JOB_APPLICATION_CANDIDATE_ERASED and refuses a different subject for the same provider message as APPLICATION_INBOX_MESSAGE_COLLISION; the candidate-key PostgresCandidateMaterialVaultV1 handles inbox-subject references; createManagedApplicationResendWebhookCompositionV1 requires materialKey.

    customer

    Apply store migration 0029 before deploying a runtime or webhook built from this release, and give the webhook service JOB_APPLICATION_MATERIAL_KEY_BASE64 (the same deployment material key the effects dependencies use); without it the webhook refuses to start (JOB_APPLICATION_MATERIAL_KEY_REQUIRED or JOB_APPLICATION_MATERIAL_KEY_INVALID). Existing plaintext subjects are dropped by 0029 (fresh schema under D-088/D-112b); those rows keep a null subject_ref.

    maintainer

    The webhook role now holds the deployment material key and route-scoped SELECT/INSERT on candidate_material_keys and inbox-subject vault rows (key_version > 0), never UPDATE/DELETE; the vault policy does not verify that a reference's scope fingerprint matches its row scope (the store computes it). No unkeyed subject digest is stored.

  • job-application-invalidation-quarantine

    Store migration 0020, bounded retry and quarantine of permanently invalid invalidation events, typed worker signals and a fail-closed submit gate until operator resolution.

    integrator

    ManagedJobApplicationProfileFactInvalidationOutcomeV1 gains a quarantined variant (sourceEventId, eventKey, typed reason, attempts, replayed); the consumer and ProfileFactInvalidationRunnerV1 accept maxPermanentAttempts (1..100, default 3); ProfileFactInvalidationRunResultV1 gains optional quarantined signals and the host loop an onQuarantine callback. listProfileFactInvalidations (and so every exact packet binding and disclosure read) now throws APPLICATION_PACKET_INVALIDATION_QUARANTINED while the candidate has an unresolved quarantine entry; submit refuses before any reservation and the pre-dispatch recheck reports capacity_requeued. consume() of a streamed event is unchanged.

    customer

    Apply job-application-store migration 0020 after 0019 before running this release; without it every exact packet submit fails closed because the unresolved-quarantine read is missing. Watch for JOB_APPLICATION_PROFILE_FACT_INVALIDATION_QUARANTINED signals and resolve each entry with PostgresJobApplicationProfileFactInvalidationQuarantineStoreV1.resolve (dependents_reviewed or not_applicable, opaque operator and evidence refs) to reopen that candidate's submits.

    maintainer

    Only typed recording refusals are permanent; database, connection, lock, timeout and unknown errors are transient and never quarantine. Attempt rows are counted per candidate scope, consumer and event and survive restarts; a replay of a quarantined event counts nothing. Quarantine rows are value-free and retained through candidate deletion like cursors. Real-Postgres conformance of 0020 has not been run.

  • job-application-profile-interview-store

    Candidate-private profile interview store (migration 0024), atomic fact correction with value and brand-configured managed composition.

    maintainer

    PostgresJobApplicationProfileInterviewStoreV1 implements the runtime interview store port; the managed operation handler passes interview deps as the ninth handler argument only when profileEvidenceKey and profileInterview (consentRevision, model, optional emit) are both set, otherwise the job-application.profile.interview.* operations stay JOB_APPLICATION_OPERATION_UNSUPPORTED. The API and MCP environment factories accept an optional brand argument with profileInterview; no consent text, prompt or model default ships in the shared owners (D-117). Deploy store migration 0024 before the runtime.

  • job-application-verification-effect-ledger

    Fenced verification effect ledger (migration 0028) with in-doubt reconciliation and lease-gated challenge claims (E-01n)

    integrator

    Apply migration 0028 before deploying; pass claimDigest from reserve() to complete, handoff and release; verification replay now completes instead of handing off, an effect that may have been dispatched is handed off as ambiguous, and missing or blank work claims are refused with APPLICATION_EFFECT_CLAIM_REQUIRED.

  • job-application-verification-effect-reconcile

    Lease-checked verification transitions and audited operator reconcile of in-doubt verification effects (migration 0030, E-01p)

    integrator

    Apply migration 0030 after 0029; pass the full work claim (workItemId, leaseOwner, fencingToken) with claimDigest to complete, handoff and release; compose the operator reconcile port as the runtime role and bind the operator_verification_read/reconcile grants in AuthOS.

  • meeting-recorder-provider-normalization

    Normalized transcript segments, per-provider webhook verification and bounded retries for meeting recorder providers

    integrator

    Read transcript timing from startMs/endMs (or startTimeMs/endTimeMs) and speakers from the speaker object, not from startTime. Verify webhooks with verifyMeetingRecorderWebhook and reject providers whose meetingRecorderCapabilities entry says webhook 'unsupported' (Granola, tl;dv). A verified event names one record to re-fetch; payload content is never trusted.

    maintainer

    withRecorderRetry wraps the transport for all four HTTP providers. Fathom and Fireflies verifyWebhook fail closed without a secret. Fathom SDK list pages are read from result.items.

  • microsoft-calendar-reauthorization

    Personal Microsoft calendar requests least-privilege Graph scopes and surfaces, alerts and restores lapsed grants like Google

    customer

    When Microsoft stops accepting CompanyOS access to your Outlook calendar (password change, expired sign-in, revoked consent), you get one email and a "Reconnect Microsoft" banner on every OPA page; one click reconnects. CompanyOS now only asks Microsoft for read access to your calendars.

    integrator

    MicrosoftCalendarOAuthClient requires Calendars.Read (Calendars.ReadWrite is no longer allowed in the config) and throws MicrosoftOAuthError with sanitized codes, AADSTS numbers and Retry-After. Personal Microsoft reads declare CALENDAR_REAUTHORIZATION_REQUIRED (409); a new health query reports the stored connection state without contacting Microsoft.

    maintainer

    The shared transition/outbox/relay used for Google now carries providerKind; Microsoft transitions run in a fresh transaction after the failed read rolls back. invalid_client is logged as microsoft_calendar_connection.client_rejected and never flips owners.

  • ts-01-comments

    Audience comment grants, observations, cursor and redaction lineage under FORCE RLS (TS-01-COMMENTS).

    integrator

    Run SqlMarketingAudienceCommentStore.migrate() on the owner client before applyGrowthRowLevelSecurity, then mount the store on createScopedGrowthSqlClient. Compose MarketingAudienceCommentService with a real authority, a targets port that resolves the actor's current connection and owned object and returns SOCIAL_COMMENT_SCOPES for requiredScopes, a credentials port, a lineage port answered by the content, publication and results owners, and a provider reader (the integrations comment readers are structurally compatible). Call redact after a publication, content or result deletion. Mapping a comment to an account or contact, reply holds and results recording are not part of this release.

    maintainer

    Donor lineage: tellshift-monorepo@eefc58b packages/libs/contracts/comments.ts, packages/modules/workspace/comments{,-collect,-ports}.ts and migrations 0094-0096 (reference only). Actor privacy is enforced by the store and service; FORCE RLS binds tenant, workspace and brand. Evidence is PGlite-only under a NOSUPERUSER owner with fixture readers (D-094).

  • ts-01-deps

    Tellshift Studio subpath exports, browser-layer dependencies and verbatim typecheck split; provider-x static twitter-text import (TS-01-DEPS).

    maintainer

    Import the studio through ./engine, ./react, ./hosts-public or ./hosts-public/runtime; the embed entry stays free of the engine. A host rendering ./react must import src/react/index.css and provide Tailwind 4. The verbatim folders and the two public-host files that import them are typechecked by tsconfig.verbatim.json until parity.

  • ts-01-edcore

    Editorial core v2 with native content kinds, field-addressed claims, policy-fingerprinted review and consented scheduling.

    integrator

    Editorial records, content and operation IO are v2 (operations 2.0.0). Hosts must supply an EditorialPolicyEvaluator (or accept the refusal-by-default double that refuses submit, review approval, scheduling and publication), and the due runner needs EditorialStore.listDueScopes.

    maintainer

    growth-persistence replaces EDITORIAL_DDL with EDITORIAL_V2_DDL (editorial_record and editorial_record_history). This is a reset: v1 editorial rows are neither read nor migrated.

  • ts-01-edcore-fu

    Editorial record v2 documentation and repository script follow-up; no package behavior change.

    maintainer

    Package READMEs describe editorial record v2 (editorial_record tables, operations 2.0.0, required policy evaluator, admission bridge). The preview, packed-consumer, Hirly compiler and GitHub qualification scripts build schemaVersion 2 records; the packed lifecycle also checks a policy-change review refusal.

  • ts-01-edgov

    Editorial governance with exact-revision assigned review, authorized export with receipts, clipboard confirmation and self-reported feedback.

    integrator

    Compose EditorialAssignmentService, EditorialExportService and EditorialFeedbackService with real stores, an EditorialReviewerPolicy and EditorialReviewRules, then call registerEditorialGovernanceOperations next to registerEditorialOperations. Pass assignments.gate(authority) as the editorial authority so approval honors an open assignment. Use createProductionEditorialPolicyEvaluator over the knowledge stores and authority instead of a fixture policy; there is no permissive default.

    maintainer

    growth-persistence adds three fully scoped marketing_execution tables through SqlEditorialAssignmentStore, SqlEditorialExportStore and SqlEditorialFeedbackStore. They are registered as editorial-assignments, editorial-export-receipts and editorial-feedback after evidence-sources, with package exports and the marketing barrel.

    integrator

    Breaking (D-088, donor parity): evaluateEditorialPolicy now returns EDITORIAL_POLICY_CHANGED instead of EDITORIAL_NEEDS_EVIDENCE when the evaluator refuses after a fingerprint was bound, so a profile, source or brief change after submit refuses review, schedule and the due runner with POLICY_CHANGED (409) and the invalidation code is EDITORIAL_POLICY_CHANGED; a refusal at submit stays NEEDS_EVIDENCE. The review error catalog declares ASSIGNED_REVIEW_REQUIRED, ASSIGNED_REVIEW_STALE, ASSIGNED_REVIEW_BLOCKED, ASSIGNED_REVIEWER_UNAVAILABLE and SELF_REVIEW_FORBIDDEN (403). Clients that branched on NEEDS_EVIDENCE for post-submit changes must handle POLICY_CHANGED.

    customer

    EditorialReviewActions now shows the assigned review panel while in review and the export action once approved. Ready is labelled as a reviewer signal, copying as not publication, and feedback as self-reported.

  • ts-01-gen

    Durable fenced marketing copy runs over a strict task generator, with Tellshift generation configuration and wiring.

    integrator

    Hosts compose MarketingCopyRunService with a MarketingCopyGeneratorPort, a usage-reservation port, a draft port and the copy run store, then mount registerMarketingCopyRuns. Start, retry and resume are cost-bearing and need an operation approval receipt over an exact quote; a run never confirms, approves or publishes. The existing growth.marketing.copy.generate operation is unchanged.

    maintainer

    growth-persistence adds SqlMarketingCopyRunStore with two fully scoped marketing_execution tables (copy_runs, copy_run_attempts) under FORCE RLS; its store-registry step and package exports are added by the integration owner. bundle.tellshift-studio server/generation needs the content-gen and provider-llm dependencies and a ./server subpath.

  • ts-01-int0-shared

    Marketing content kinds, the growth store migration registry and pre-declared Tellshift dependencies.

    maintainer

    lib.growth-spec exports ./marketing/content-kind (8 content kinds, 11 brief formats; legacy linkedin/x values refused). integration.growth-persistence exports ./store-registry with 20 ordered idempotent migration steps run by migrateAllGrowthStores. provider-x and app.marketing-operations pre-declare dependencies used by later Tellshift slices.

  • ts-01-know

    Marketing knowledge convergence with revisioned evidence, scoped search, intake candidates, confirmed brand revisions and campaign briefs.

    integrator

    MarketingBrandRevision and MarketingBrief are schemaVersion 2. Brand revisions carry draft|confirmed status and company-brief fields; briefs are revisioned campaign context that pin a confirmed brand revision. Copy generation refuses unconfirmed brands and the retired linkedin/x formats. Hosts must supply a real MarketingKnowledgeAuthority; there is no permissive default.

    maintainer

    growth-persistence adds six fully scoped marketing_execution tables through SqlMarketingEvidenceSourceStore, SqlMarketingEvidenceCandidateStore, SqlMarketingBrandStore and SqlMarketingBriefStore. Their store-registry steps are added by the integration owner.

  • ts-01-results

    Results with provenance and publication binding, reviewed CSV import, learning decisions with autoApply false and draft next-cycle revisions.

    integrator

    Hosts compose MarketingResultService and MarketingLearningService with a real MarketingResultsAuthority, the CSV adapter (parseResultsCsv) and a learning context (briefLearningContext over the brief store plus the campaign revision reader), then call registerMarketingResults. There is no permissive default. Decisions are never applied: operators submit the draft through the owning brief or campaign revise command.

    maintainer

    growth-persistence adds SqlMarketingResultStore and SqlMarketingLearningStore with four fully scoped marketing_execution tables under FORCE RLS. Their store-registry steps are added by the integration owner. normalizeAdvertisingObservation takes a seventh connectionRef argument.

  • ts-01-soc

    Owner-only member-approved LinkedIn, X and Instagram scheduling and publish-now on module.social-media (TS-01-SOC).

    integrator

    Compose scheduling with createMarketingSocialScheduling and supply an account binding port (AuthOS connection projection with CAS), per-kind qualification, a content reader, policy and the SqlSocialPublisherStore. Owners submit acknowledgements, an exact kind and the reviewed bindingHash per target; the runtime mints one member approval per target. Adapters receive publicationKind, actorId, connectionId and connectionVersion and should be given currentConnectionVersion. Run workers through createMarketingSocialScopedWorker with discoverGrowthDueScopes and scope-bound runtimes.

    maintainer

    Ported from tellshift-monorepo@eefc58b (public-scheduling contract, workspace public-scheduling and public-scheduling-run, linkedin/x/x-thread/instagram publishing blockers, scheduled LinkedIn provider, public worker and the public-scheduling, linkedin-publishing, x-publishing, x-thread and instagram-publishing test cases). Breaking: the grant union, schedule record schema 2, the extended SocialScheduleStore port (count, peers, forAccount) and operation versions 2.0.0. Fixture-only evidence.

Migration guide

  • Apply job-application-store migration 0019

    Required

    Widens profile_fact_invalidations_reason_check to rejected, superseded and revised, re-creates the worker-only pending-candidates function for both event keys and adds a partial outbox index for both keys.

    When: Before enabling JOB_APPLICATION_PROFILE_FACT_INVALIDATION_ENABLED on this release.

    1. Apply packages/integrations/job-application-store/migrations/0019_candidate_profile_fact_revised_invalidations.sql after 0018.
    2. Run the store conformance; security.sql asserts the widened reason check and the worker-only discovery grant.
  • Apply job-application-store migration 0029

    Required

    Adds inbox_messages.subject_ref with its check constraint, drops inbox_messages.subject, adds the route-scoped webhook SELECT/INSERT policies on candidate_material_keys and candidate_material_vault (inbox-subject references only) and grants the webhook role the erasure guard and the vault check helper.

    When: Before deploying a runtime, worker or webhook built from this release.

    1. Apply packages/integrations/job-application-store/migrations/0029_inbox_subject_sealed.sql (generated verbatim from inboxSubjectSealingMigrationSqlV1) after 0028; it is idempotent.
    2. Set JOB_APPLICATION_MATERIAL_KEY_BASE64 on the managed Resend webhook service (brand deployment configuration).
    3. Run the store conformance; security.sql asserts the 0029 grants, policies and the absent subject column.
  • Apply job-application-store migration 0020

    Required

    Adds profile_fact_invalidation_failures, profile_fact_invalidation_quarantine and profile_fact_invalidation_quarantine_resolutions (FORCE RLS, worker select/insert only), profile_fact_invalidation_quarantine_unresolved() for runtime and worker, and the worker-only profile_fact_invalidation_unresolved_quarantine(text, integer).

    When: Before deploying a runtime or worker of this release.

    1. Apply packages/integrations/job-application-store/migrations/0020_candidate_profile_fact_invalidation_quarantine.sql after 0019.
    2. Run the store conformance; security.sql asserts the three tables, their insert-only worker grants and the function grants.
  • Apply migration 0028 before the runtime

    Required

    job-application-store migrations/0028_verification_effect_ledger.sql adds the append-only verification_effect_events ledger (FORCE RLS) and its SECURITY DEFINER worker functions; the function owner must bypass RLS (superuser or BYPASSRLS), as for reserve_work_effect.

    1. Apply job-application-store migrations/0028_verification_effect_ledger.sql after 0027.
  • Apply migration 0030 before the runtime

    Required

    job-application-store migrations/0030_verification_effect_reconcile.sql adds the append-only verification_effect_reconciliations table (FORCE RLS) and runtime-only SECURITY DEFINER list/load/reconcile functions; the function owner must bypass RLS, as for 0028.

    1. Apply job-application-store migrations/0030_verification_effect_reconcile.sql after 0029.
  • Create the audience comment tables

    Three new tables in marketing_execution; no existing table changes.

    When: Before mounting the audience comment service.

    1. Run SqlMarketingAudienceCommentStore.migrate() on the owner client (or through migrateAllGrowthStores once registered).
    2. Rerun applyGrowthRowLevelSecurity so the new tables get ENABLE and FORCE RLS and the growth_app policy.
  • Recreate editorial content under v2

    Required

    v1 editorial records, payloads and the linkedin/x formats are rejected; there is no upgrade path.

    When: When a deployment holds v1 marketing_execution.editorial rows.

    1. Run the v2 editorial store migration (EDITORIAL_V2_DDL) and recreate drafts with content v2 payloads.
    2. Supply a production EditorialPolicyEvaluator, EditorialContextPort and EditorialAuthorPolicy before enabling review.
    3. Schedule with publishAt, an IANA timeZone and the three mandatory acknowledgements.
  • Handle POLICY_CHANGED for post-submit policy changes

    Required

    Review, schedule and the due runner now refuse a profile, source or brief change after submit with POLICY_CHANGED instead of NEEDS_EVIDENCE.

    When: When a client or host branches on the editorial NEEDS_EVIDENCE refusal or on the EDITORIAL_NEEDS_EVIDENCE invalidation code.

    1. Treat POLICY_CHANGED (409) at review and schedule, and the EDITORIAL_POLICY_CHANGED invalidation code from the due runner, as a request for a new review of the current policy.
    2. Keep NEEDS_EVIDENCE (422) handling for submit, where no policy fingerprint is bound yet.
  • Create the copy run tables

    Required

    Run the copy run store migration as the growth owner, then reapply growth row-level security.

    When: When a host enables durable copy runs.

    1. Run SqlMarketingCopyRunStore.migrate on the owner client (inline DDL, no migration number).
    2. Run applyGrowthRowLevelSecurity so copy_runs and copy_run_attempts get FORCE RLS and the scope policy.
    3. Give runtime stores only scoped growth clients.
  • Recreate brand and brief knowledge under v2

    Required

    v1 brand revisions and briefs, and the linkedin/x copy formats, are rejected; there is no upgrade path.

    When: When a host stores v1 MarketingBrandRevision or MarketingBrief snapshots.

    1. Run the knowledge store migrations and record evidence sources for the facts a brand relies on.
    2. Save brand drafts with the company-brief fields and confirm them; confirmation requires current factual evidence.
    3. Recreate campaign briefs pinning the confirmed brand revision digest and using linkedin_post or x_post formats.
  • Pass the connection ref to normalizeAdvertisingObservation

    Required

    Direct callers must pass the request connection ref so the row carries provider_authenticated provenance.

    When: When code calls normalizeAdvertisingObservation outside AdvertisingCampaignObserver.

    1. Add the observation request connectionRef as the seventh argument.
  • Close or drain schema 1 social schedules before upgrading

    Required

    SqlSocialScheduleStore reads only schema 2 records; schema 1 rows are refused rather than reinterpreted.

    When: Before mounting the upgraded store on a database that holds schema 1 social schedules.

    1. Let pending schema 1 schedules finish or cancel them, then remove or archive their rows.
    2. Recreate future schedules through create or publish-now with member acknowledgements.
  • Create the social_publishers table

    Required

    marketing_execution.social_publishers is created by SqlSocialPublisherStore.migrate(), or by migrateAllGrowthStores once its registry entry lands; row-level security classifies it as full.

    When: Before mounting publisher reservations with the SQL store.

    1. Run the store migration on the owner (migrator) client, then re-apply growth row-level security.
  • Enable intake titles only after the web host that accepts them is live

    Required

    The recent-meetings schema is strict. An API that returns title to a web build from before this change makes that page show "unavailable". The API returns titles only while OPA_MEETING_INTAKE_TITLES_ENABLED=1.

    When: When a deployment turns on OPA_MEETING_INTAKE_TITLES_ENABLED.

    1. Apply migrations 0185-0189, deploy the API with the switch unset, then deploy the web host.
    2. Set OPA_MEETING_INTAKE_TITLES_ENABLED=1 on the API; titles appear for meetings in the next intake window.
  • Optionally turn on calendar push channels and delta sync

    Additive and off by default. With OPA_MEETING_INTAKE_SYNC_ENABLED unset nothing changes: the webhooks answer 404 and the channel cron answers disabled.

    When: When a deployment wants calendar changes to reach intake within minutes.

    1. Deploy the API build that mounts the readiness route, both calendar push webhooks and the push-channel cron; a host without Vercel Cron calls GET /api/cron/meeting-intake-push-channels every 30 minutes with the cron secret.
    2. Set OPA_MEETING_INTAKE_PUSH_SECRET (at least 32 bytes, from the secret store) and OPA_MEETING_INTAKE_PUSH_BASE_URL (the public https origin of the API), then OPA_MEETING_INTAKE_SYNC_ENABLED=1.
    3. Check GET /api/opa/meeting-intake/readiness reports sync ready, then confirm a channel opens on the next cron pass.
  • Adapt to Granola recorder surface changes

    Required

    The experimental Granola recorder no longer fabricates identities, attendees or dates.

    When: Consuming the Granola meeting recorder adapter

    1. Granola MCP getMeeting now throws granola_not_found instead of returning another meeting when the requested ID is missing.
    2. Granola transcript segments no longer populate speakerName from speaker.source; read metadata.audioChannel.
    3. Granola records no longer copy known attendees into invitees/participants; read metadata.knownParticipants (unverified).
    4. Granola types created_at, owner, summary_text and transcript times are nullable; absent values are no longer fabricated.
  • Read normalized transcript segment fields

    Additive. Legacy segment fields keep working. Consumers that read segment.startTime for Fireflies or tl;dv timing got null before; read startMs instead.

    1. Replace segment.startTime / endTime reads with segment.startMs / endMs, or call normalizeMeetingTranscriptSegments(record).
  • Configure webhook secrets before relying on verifyWebhook

    FathomMeetingRecorderProvider and FirefliesMeetingRecorderProvider verifyWebhook now return false when no webhookSecret is configured.

    1. Pass webhookSecret, or call verifyMeetingRecorderWebhook with the connection secret.
  • Reduce the Entra app registration to read-only calendar permissions

    Existing grants consented with Calendars.ReadWrite keep working (refresh returns the consented superset). The app registration can drop Calendars.ReadWrite; no owner action is needed.

    1. In the Entra app used by MANAGED_COMPANYOS_MICROSOFT_CALENDAR_CLIENT_ID keep delegated offline_access, User.Read and Calendars.Read.
    2. Callers constructing MicrosoftCalendarOAuthClient must list https://graph.microsoft.com/Calendars.Read instead of Calendars.ReadWrite.
  • Apply migration 0176 before the identity API deployment

    Required

    Additive and idempotent. The running Better Auth 1.6 identity deployment ignores the new columns and tables, so the migration can run ahead of the deploy. Existing jwks rows get the alg/crv of their own public key.

    1. Run the tracked live migration runner (bun scripts/companyos-live-db.ts migrate in packages/apps/api-application-monolith) with approval and backup evidence; the only pending version must be 0176.
    2. Verify jwks.alg/crv are set on the existing key (EdDSA/Ed25519), oauth_client.client_credentials_scopes exists, and oauth_resource, oauth_client_resource and oauth_client_assertion exist.
    3. Build and deploy lssm-identity-api, then smoke /api/auth/jwks (200) and /api/auth/oauth2/authorize (302) before promotion.
  • Auth requests now wait on the schema check

    Required

    Once deployed, every auth request in a composition with the sso plugin (such as the CompanyOS API) awaits Better Auth's schema check, and a schema that does not match Better Auth's expected tables fails auth instead of proceeding.

    When: Before deploying a composition that enables the sso plugin to production.

    1. Run await (await auth.$context).checkSchema?.() in a preview built with the production environment flags and confirm it resolves without findings.
    2. Apply any pending auth schema migration through the reviewed migration process before the deploy.
    3. Set advanced.database.validateSchema to false only as a deliberate, reviewed exception.
  • Apply migration 0180 before enabling pgvector evidence search

    Required

    Migration 0180 installs pgvector in the extensions schema (when the server offers it) and creates the tenant-isolated evidence vector table. It fails if pgvector is already installed in another schema and skips the table with a NOTICE on servers without pgvector; health.get then reports the vector dependency unavailable, and installing pgvector later needs a follow-up migration because the ledger records 0180 as applied.

    1. Ensure pgvector is enabled in the extensions schema (Supabase default) or not installed yet.
    2. Apply api-application-monolith migration 0180 with the migration owner role.
    3. Reindex existing evidence by re-running document ingestion; the projection is rebuildable from the ledger.
  • Apply the bot dead-letter discovery function

    Migration 0195 adds the identifier-only function public.companyos_bot_dead_letters(integer), executable by companyos_bot_dispatcher only.

    When: Before or after enabling notetaker bots (requires 0165)

    1. Apply app migration 0195 (companyos/opa-bot-dead-letter-recovery-0195) after 0165. Until then the dispatcher logs opa-bots.dead_letter_recovery_unavailable and runs without recovery.
  • Legacy contracts-spec subpaths continue forwarding the canonical objects

    Legacy contracts-spec subpaths continue forwarding the canonical objects; existing consumers require no migration.

    1. Legacy contracts-spec subpaths continue forwarding the canonical objects; existing consumers require no migration.
  • Existing contracts-spec paths continue forwarding identical canonical objects

    Existing contracts-spec paths continue forwarding identical canonical objects. Supplied verifiers, clocks, lease bindings and effect authority remain required.

    1. Existing contracts-spec paths continue forwarding identical canonical objects. Supplied verifiers, clocks, lease bindings and effect authority remain required.

Upgrade steps

  • Qualify the relying-party callback after deploying the bridge fix

    assisted

    Preserve official token verification and exact identity binding before local authority.

    Packages: @lssm-tech/integration.authos-better-auth

    1. Retain strict issuer, ID-token, server nonce and PKCE requirements for reviewed web consumers.
    2. Verify same-subject email-less userinfo succeeds and substituted identity proof fails closed.
    3. Require explicit owner-reviewed reconciliation for any historical account key that differs from the signed subject; never merge by email.
    4. Repeat real hosted callback and local authorization journeys before claiming production qualification.
  • Apply job-application-store migration 0024 before the runtime

    manual

    The profile interview operations need the eight tables and the erasure trigger created by 0024_profile_interview.sql.

    Packages: @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-managed-runtime

    1. Apply packages/integrations/job-application-store/migrations/0024_profile_interview.sql.
    2. Deploy the API and MCP hosts with JOB_APPLICATION_MATERIAL_KEY_BASE64 and a brand host profileInterview configuration to enable the interview.
  • Pass the verification claim digest to transitions

    manual

    PostgresApplicationVerificationExecutionStoreV1 complete, handoff and release now require the claimDigest returned by reserve.

    Packages: @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-effects-managed

    1. Direct callers of PostgresApplicationVerificationExecutionStoreV1 pass the returned claimDigest to complete, handoff and release.
  • Pass the full claim to verification transitions

    manual

    PostgresApplicationVerificationExecutionStoreV1 complete, handoff and release now require workItemId, leaseOwner and fencingToken as well as claimDigest; an expired or reclaimed lease gets APPLICATION_EFFECT_STALE_FENCE.

    Packages: @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-effects-managed, @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-managed-runtime

    1. Direct callers spread the work claim into every transition input.
  • Wire editorial governance in a host

    manual

    Register the governance operations and gate approval through the assignment service.

    Packages: @lssm-tech/lib.growth-spec, @lssm-tech/lib.growth-runtime, @lssm-tech/integration.growth-persistence, @lssm-tech/module.editorial, @lssm-tech/bundle.marketing-operations

    1. Run the three governance store migrations with the owner client and use the scoped client at runtime.
    2. Build the services and register them with registerEditorialGovernanceOperations.
    3. Replace the editorial authority with assignments.gate(authority).
  • Verify migrations, push channels, delta cursors, retirement and titles

    auto

    Run the provider, API and recent-meetings tests.

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

    1. Run bun test src/impls in provider-calendar.
    2. Run the meeting-intake tests in api-application-monolith (W9 migrations, push, delta, reconcile, readiness, webhooks, cron).
    3. Run bun test src/ui/organization-planning/OpaRecentPrivateMeetings.test.tsx in managed-companyos.
  • Confirm the auth schema before the check becomes active

    manual

    Where the schema check becomes active, a Drizzle schema that does not match Better Auth's expected tables makes auth requests fail with SchemaMismatchError instead of proceeding.

    Packages: @lssm-tech/integration.authos-better-auth

    1. Build the composition locally and confirm await (await auth.$context).checkSchema?.() resolves without findings.
    2. Set advanced.database.validateSchema to false only as a deliberate, reviewed exception.
  • Confirm the auth schema in a preview before production

    manual

    A Drizzle schema missing tables or columns Better Auth expects for the enabled plugins makes auth requests fail with SchemaMismatchError.

    Packages: @lssm-tech/integration.authos-better-auth

    1. Deploy a preview with the production environment flags and verify await (await auth.$context).checkSchema?.() resolves.
  • Enable notetaker bots

    manual

    Bots stay off until the legal, database and configuration steps are complete; the global switch comes last.

    Packages: @lssm-tech/integration.provider-meeting-recorder

    1. Complete the Attendee DPA and the EU-processing confirmation and record both approval references.
    2. Apply 0165 and 0195 and create a login that is a member of companyos_bot_dispatcher only.
    3. Set the OPA_BOTS_* values and deploy; confirm every readiness key name is present in the deployment's environment listing (values are never printed).
    4. Set OPA_BOTS_ENABLED=1 and deploy; confirm the next bot cron runs log no opa-bots.configuration_required (otherwise unset the switch and fix the named keys), then let workspace administrators opt in.
  • Import server code from the explicit server entry

    manual

    The root barrel keeps working; the explicit entries keep client bundles away from server-only code.

    Packages: @lssm-tech/integration.authos-better-auth

    1. Optionally replace server-side root imports with @lssm-tech/integration.authos-better-auth/server.
    2. Keep browser code on @lssm-tech/integration.authos-better-auth/client (all workspace client consumers already use it).

Unique release changes

  • marketing_execution.social_publishers is created by SqlSocialPublisherStore.migrate(), or by migrateAllGrowthStores once its registry entry lands; row-level security classifies it as full.

    7 packages · 7 occurrences

  • Owner-only member-approved LinkedIn, X and Instagram scheduling and publish-now on module.social-media (TS-01-SOC).

    7 packages · 7 occurrences

  • SqlSocialScheduleStore reads only schema 2 records; schema 1 rows are refused rather than reinterpreted.

    7 packages · 7 occurrences

  • Direct callers must pass the request connection ref so the row carries provider_authenticated provenance.

    6 packages · 6 occurrences

  • Results with provenance and publication binding, reviewed CSV import, learning decisions with autoApply false and draft next-cycle revisions.

    6 packages · 6 occurrences

  • Canonical owners for messaging policy and signed control-plane skill contracts

    5 packages · 5 occurrences

  • Durable fenced marketing copy runs over a strict task generator, with Tellshift generation configuration and wiring.

    5 packages · 5 occurrences

  • Editorial core v2 with native content kinds, field-addressed claims, policy-fingerprinted review and consented scheduling.

    5 packages · 5 occurrences

  • Editorial governance with exact-revision assigned review, authorized export with receipts, clipboard confirmation and self-reported feedback.

    5 packages · 5 occurrences

  • Legacy contracts-spec subpaths continue forwarding the canonical objects; existing consumers require no migration.

    5 packages · 5 occurrences

  • Live evidence ingestion and grounded answers run on Supabase Storage, pgvector in the evidence database and the Vercel AI Gateway; no S3 vendor account, Qdrant or embedding/OCR vendor key is needed

    5 packages · 5 occurrences

  • Migration 0180 installs pgvector in the extensions schema (when the server offers it) and creates the tenant-isolated evidence vector table. It fails if pgvector is already installed in another schema and skips the table with a NOTICE on servers without pgvector; health.get then reports the vector dependency unavailable, and installing pgvector later needs a follow-up migration because the ledger records 0180 as applied.

    5 packages · 5 occurrences

  • Register the governance operations and gate approval through the assignment service.

    5 packages · 5 occurrences

  • Review, schedule and the due runner now refuse a profile, source or brief change after submit with POLICY_CHANGED instead of NEEDS_EVIDENCE.

    5 packages · 5 occurrences

  • Run the copy run store migration as the growth owner, then reapply growth row-level security.

    5 packages · 5 occurrences

  • v1 editorial records, payloads and the linkedin/x formats are rejected; there is no upgrade path.

    5 packages · 5 occurrences

  • job-application-store migrations/0030_verification_effect_reconcile.sql adds the append-only verification_effect_reconciliations table (FORCE RLS) and runtime-only SECURITY DEFINER list/load/reconcile functions; the function owner must bypass RLS, as for 0028.

    4 packages · 4 occurrences

  • Lease-checked verification transitions and audited operator reconcile of in-doubt verification effects (migration 0030, E-01p)

    4 packages · 4 occurrences

  • Marketing knowledge convergence with revisioned evidence, scoped search, intake candidates, confirmed brand revisions and campaign briefs.

    4 packages · 4 occurrences

  • PostgresApplicationVerificationExecutionStoreV1 complete, handoff and release now require workItemId, leaseOwner and fencingToken as well as claimDigest; an expired or reclaimed lease gets APPLICATION_EFFECT_STALE_FENCE.

    4 packages · 4 occurrences

  • v1 brand revisions and briefs, and the linkedin/x copy formats, are rejected; there is no upgrade path.

    4 packages · 4 occurrences

  • Account-scoped Granola/calendar meeting evidence, private meeting preparation, durable briefing occurrences and approval-gated follow-through

    3 packages · 3 occurrences

  • Additive and off by default. With OPA_MEETING_INTAKE_SYNC_ENABLED unset nothing changes: the webhooks answer 404 and the channel cron answers disabled.

    3 packages · 3 occurrences

  • Audience comment grants, observations, cursor and redaction lineage under FORCE RLS (TS-01-COMMENTS).

    3 packages · 3 occurrences

  • Canonical Hook Authority runtime ownership with preserved private packaging and compatibility

    3 packages · 3 occurrences

  • Editorial record v2 documentation and repository script follow-up; no package behavior change.

    3 packages · 3 occurrences

  • Existing contracts-spec paths continue forwarding identical canonical objects. Supplied verifiers, clocks, lease bindings and effect authority remain required.

    3 packages · 3 occurrences

  • Existing grants consented with Calendars.ReadWrite keep working (refresh returns the consented superset). The app registration can drop Calendars.ReadWrite; no owner action is needed.

    3 packages · 3 occurrences

  • Marketing content kinds, the growth store migration registry and pre-declared Tellshift dependencies.

    3 packages · 3 occurrences

  • Meeting intake gets calendar push channels and delta sync, retires meetings whose event moved or was cancelled, names materialized meetings, and exposes its readiness to operators

    3 packages · 3 occurrences

  • Move marketing validation, forms and sample handlers to canonical Growth owners

    3 packages · 3 occurrences

  • Personal Microsoft calendar requests least-privilege Graph scopes and surfaces, alerts and restores lapsed grants like Google

    3 packages · 3 occurrences

  • Preserve ControlPlane operation identity through canonical Builder declarations

    3 packages · 3 occurrences

  • Run the provider, API and recent-meetings tests.

    3 packages · 3 occurrences

  • The experimental Granola recorder no longer fabricates identities, attendees or dates.

    3 packages · 3 occurrences

  • The recent-meetings schema is strict. An API that returns title to a web build from before this change makes that page show "unavailable". The API returns titles only while OPA_MEETING_INTAKE_TITLES_ENABLED=1.

    3 packages · 3 occurrences

  • Three new tables in marketing_execution; no existing table changes.

    3 packages · 3 occurrences

  • Additive. Legacy segment fields keep working. Consumers that read segment.startTime for Fireflies or tl;dv timing got null before; read startMs instead.

    2 packages · 2 occurrences

  • Adds inbox_messages.subject_ref with its check constraint, drops inbox_messages.subject, adds the route-scoped webhook SELECT/INSERT policies on candidate_material_keys and candidate_material_vault (inbox-subject references only) and grants the webhook role the erasure guard and the vault check helper.

    2 packages · 2 occurrences

  • Adds profile_fact_invalidation_failures, profile_fact_invalidation_quarantine and profile_fact_invalidation_quarantine_resolutions (FORCE RLS, worker select/insert only), profile_fact_invalidation_quarantine_unresolved() for runtime and worker, and the worker-only profile_fact_invalidation_unresolved_quarantine(text, integer).

    2 packages · 2 occurrences

  • AuthOS: OAuth/social sign-ins of TOTP-enrolled identities are challenged for the second factor unless the device is trusted, and the CompanyOS client registration ceremony on the central IdP uses central-only env names.

    2 packages · 2 occurrences

  • Better Auth schema check helpers and local schema rehearsal scripts for CompanyOS, hCircle and Pactena

    2 packages · 2 occurrences

  • Candidate-private profile interview store (migration 0024), atomic fact correction with value and brand-configured managed composition.

    2 packages · 2 occurrences

  • Canonicalize complete marketing operations and remove the Growth Legacy return.

    2 packages · 2 occurrences

  • FathomMeetingRecorderProvider and FirefliesMeetingRecorderProvider verifyWebhook now return false when no webhookSecret is configured.

    2 packages · 2 occurrences

  • Fenced verification effect ledger (migration 0028) with in-doubt reconciliation and lease-gated challenge claims (E-01n)

    2 packages · 2 occurrences

  • Inbox message subjects are sealed under the per-candidate data key behind an opaque subject_ref (store migration 0029 drops the plaintext column); the managed Resend webhook requires the deployment material key.

    2 packages · 2 occurrences

  • job-application-store migrations/0028_verification_effect_ledger.sql adds the append-only verification_effect_events ledger (FORCE RLS) and its SECURITY DEFINER worker functions; the function owner must bypass RLS (superuser or BYPASSRLS), as for reserve_work_effect.

    2 packages · 2 occurrences

  • Normalized transcript segments, per-provider webhook verification and bounded retries for meeting recorder providers

    2 packages · 2 occurrences

  • Own complete marketing model and FormSpec families in Growth.

    2 packages · 2 occurrences

  • PostgresApplicationVerificationExecutionStoreV1 complete, handoff and release now require the claimDigest returned by reserve.

    2 packages · 2 occurrences

  • Store migration 0019, key-dispatched invalidation recording with the sibling rule, and revised-event consumption in the managed-runtime consumer and worker.

    2 packages · 2 occurrences

  • Store migration 0020, bounded retry and quarantine of permanently invalid invalidation events, typed worker signals and a fail-closed submit gate until operator resolution.

    2 packages · 2 occurrences

  • The profile interview operations need the eight tables and the erasure trigger created by 0024_profile_interview.sql.

    2 packages · 2 occurrences

  • Widens profile_fact_invalidations_reason_check to rejected, superseded and revised, re-creates the worker-only pending-candidates function for both event keys and adds a partial outbox index for both keys.

    2 packages · 2 occurrences

  • A Drizzle schema missing tables or columns Better Auth expects for the enabled plugins makes auth requests fail with SchemaMismatchError.

    1 package · 1 occurrence

  • Additive and idempotent. The running Better Auth 1.6 identity deployment ignores the new columns and tables, so the migration can run ahead of the deploy. Existing jwks rows get the alg/crv of their own public key.

    1 package · 1 occurrence

  • Agent fleet adds durable coding-agent supervision, proactive proposals, governed workflow improvement and use-case proposals for founder operations

    1 package · 1 occurrence

  • authos-better-auth adds an explicit server-only ./server entry; the root barrel stays compatible

    1 package · 1 occurrence

  • Better Auth 1.7.5 OAuth-provider schema (migration 0176) and back-channel origin handling for the central LSSM IdP

    1 package · 1 occurrence

  • Bind strict relying-party profile and account subjects to the verified ID token.

    1 package · 1 occurrence

  • Bots stay off until the legal, database and configuration steps are complete; the global switch comes last.

    1 package · 1 occurrence

  • Brand-neutral verified-identity and reviewed-membership product admission adapters with monolith wiring.

    1 package · 1 occurrence

  • Build existing Builder control-plane leaves and preserve export manifests

    1 package · 1 occurrence

  • Migration 0195 adds the identifier-only function public.companyos_bot_dead_letters(integer), executable by companyos_bot_dispatcher only.

    1 package · 1 occurrence

  • Notetaker bot live-readiness (readiness names and a disabled state, cron gating, reauthorization alerts, dead-letter recovery through migration 0195); production stays off.

    1 package · 1 occurrence

  • Once deployed, every auth request in a composition with the sso plugin (such as the CompanyOS API) awaits Better Auth's schema check, and a schema that does not match Better Auth's expected tables fails auth instead of proceeding.

    1 package · 1 occurrence

  • Preserve official token verification and exact identity binding before local authority.

    1 package · 1 occurrence

  • Preserve portable claimed queue envelope and fixture declarations

    1 package · 1 occurrence

  • Tellshift Studio subpath exports, browser-layer dependencies and verbatim typecheck split; provider-x static twitter-text import (TS-01-DEPS).

    1 package · 1 occurrence

  • The canonical-email adapter wrapper keeps the adapter's identity so Better Auth's schema self-check can find it.

    1 package · 1 occurrence

  • The job-application API and MCP hosts inject CV original custody over the existing candidate S3 configuration with a distinct CV prefix, failing closed when it is absent.

    1 package · 1 occurrence

  • The root barrel keeps working; the explicit entries keep client bundles away from server-only code.

    1 package · 1 occurrence

  • The SSO client-secret adapter wrapper forwards Better Auth's schema self-check, so compositions with the sso plugin detect schema drift.

    1 package · 1 occurrence

  • Where the schema check becomes active, a Drizzle schema that does not match Better Auth's expected tables makes auth requests fail with SchemaMismatchError instead of proceeding.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/app.communicationos-api

    Layer: apps · 1 change

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 2 changes

  • @lssm-tech/bundle.marketing-operations

    Layer: bundles · 3 changes

  • @lssm-tech/integration.authos-better-auth

    Layer: integrations · 2 changes

  • @lssm-tech/integration.company-intelligence-postgres

    Layer: integrations · 2 changes

  • @lssm-tech/integration.growth-persistence

    Layer: integrations · 3 changes

  • @lssm-tech/integration.job-application-effects-dependencies-railway

    Layer: integrations · 1 change

  • @lssm-tech/integration.job-application-effects-managed

    Layer: integrations · 3 changes

  • @lssm-tech/integration.job-application-managed-runtime

    Layer: integrations · 3 changes

  • @lssm-tech/integration.job-application-store

    Layer: integrations · 3 changes

  • @lssm-tech/integration.job-application-webhook-resend-managed

    Layer: integrations · 2 changes

  • @lssm-tech/integration.lssm-os-state-sqlite

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-calendar

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-embedding

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-instagram

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-linkedin

    Layer: integrations · 3 changes

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

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-storage

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-vector-store

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-x

    Layer: integrations · 3 changes

  • @lssm-tech/integration.runtime

    Layer: integrations · 2 changes

  • @lssm-tech/integration.social-tracking-runtime

    Layer: integrations · 2 changes

  • @lssm-tech/lib.advertising-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.authos-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.builder-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.companyos-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.content-gen

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-integrations

    Layer: libs · 3 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.growth-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.growth-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.job-application-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.knowledge

    Layer: libs · 2 changes

  • @lssm-tech/lib.lssm-os-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.lssm-os-spec

    Layer: libs · 2 changes

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

    Layer: libs · 4 changes

  • @lssm-tech/module.agent-fleet

    Layer: modules · 1 change

  • @lssm-tech/module.editorial

    Layer: modules · 3 changes

  • @lssm-tech/module.growth-os

    Layer: modules · 2 changes

  • @lssm-tech/module.social-media

    Layer: modules · 3 changes