Skip to content
← Back to changelog index

2.1.5

Nov 05, 2026 · 3 packages · 5 unique changes · 3 release entries

integrationslibsmodules

This release affects the integrations, sharedLibs, solutions families.

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

Release summaries

  • control-plane-canonical-owners

    Separate canonical generic scheduling from Builder composition while preserving every existing ControlPlane entry.

  • ts-01-comments-rls

    Per-actor restrictive RLS with a host membership predicate and growth_steward paths for audience comments (TS-01-COMMENTS-RLS).

    integrator

    Hosts that compose the audience comment store must pass the same actorMembershipPredicate on every applyGrowthRowLevelSecurity call; without it the comment tables read nothing (fail-closed). The predicate is a host-owned schema-qualified (tenant, workspace, brand, actor text) RETURNS boolean function: STABLE, SECURITY DEFINER with a pinned search_path, owned by a NOSUPERUSER NOBYPASSRLS role, EXECUTE revoked from PUBLIC and granted to growth_app, with USAGE on its schema for growth_app and the owner. Mount the comment store on createScopedGrowthSqlClient with the acting actorId. Scope erasure works without an actor; authorize it above persistence. The owner now also needs to create or administer growth_steward.

    maintainer

    Donor lineage: tellshift-monorepo@eefc58b 0094_fp_20_comments.sql (comment_grant_private, comment_observation_private), 0028_v1_d_team_coordination.sql (workspace_actor_active) and tests/comments-db.test.ts. Adaptation: the actor check is a restrictive layer over growth_app_scope instead of the only permissive policy. The donor erase_workspace_content requires an active owner actor; that check now sits above persistence. The product membership adapter (for example over tellshift.is_member) is a later wiring slice. Evidence is PGlite-only under a NOSUPERUSER owner with fixture readers and a fixture predicate (D-094).

  • ts-01-rls

    FORCE row-level security, scoped client, due-scope discovery and scope erasure for growth persistence (TS-01-RLS).

    integrator

    Run migrateAllGrowthStores, then applyGrowthRowLevelSecurity on the NOSUPERUSER owner client, then grantGrowthAppMembership for each product role. Runtime stores receive createScopedGrowthSqlClient(pool, scope, { role }) instead of the owner client: under FORCE RLS the owner reads nothing. Workers discover due work through discoverGrowthDueScopes or forEachGrowthDueScope, which return scope tuples only. Tenant ids must not contain ':' because lease ids are '<tenantId>:<intentId>'. eraseMarketingScope erases one (tenant, workspace, brand) scope; a multi-brand workspace is erased by one call per brand.

    maintainer

    Semantics reference: tellshift-monorepo@eefc58b packages/integrations/postgres/migrations/0001_tenant_policies.sql (NOSUPERUSER NOBYPASSRLS roles, ENABLE plus FORCE RLS, setting-scoped policies); target precedent communication-os-persistence rls.ts and tenant-scope.ts. Evidence is PGlite-only under a NOSUPERUSER owner role; no managed Postgres rehearsal was run.

Migration guide

  • Reapply growth RLS with the membership predicate

    Adds growth_steward, the actor-private policies and the steward functions; no table changes.

    When: When the audience comment store is mounted.

    1. Create the host membership predicate and grant EXECUTE on it (and USAGE on its schema) to growth_app.
    2. Rerun applyGrowthRowLevelSecurity(owner, { actorMembershipPredicate }) and pass the same option on every later apply.
    3. Bind each comment request to createScopedGrowthSqlClient(pool, { ...scope, actorId }, { role }).
  • Apply growth row-level security

    The owner role needs CREATEROLE (or pre-created safe roles on which it holds ADMIN), CREATE on the database and on schema public, and must not be a superuser for FORCE RLS to bind it.

    When: After migrateAllGrowthStores and before any runtime store is mounted on a scoped client.

    1. Run applyGrowthRowLevelSecurity(ownerClient); it is idempotent and rerunnable after later migrations.
    2. Grant growth_app to each product role with grantGrowthAppMembership(ownerClient, role).
    3. Replace owner-client store wiring with createScopedGrowthSqlClient per request or worker scope.

Unique release changes

  • Separate canonical generic scheduling from Builder composition while preserving every existing ControlPlane entry.

    2 packages · 2 occurrences

  • Adds growth_steward, the actor-private policies and the steward functions; no table changes.

    1 package · 1 occurrence

  • FORCE row-level security, scoped client, due-scope discovery and scope erasure for growth persistence (TS-01-RLS).

    1 package · 1 occurrence

  • Per-actor restrictive RLS with a host membership predicate and growth_steward paths for audience comments (TS-01-COMMENTS-RLS).

    1 package · 1 occurrence

  • The owner role needs CREATEROLE (or pre-created safe roles on which it holds ADMIN), CREATE on the database and on schema public, and must not be a superuser for FORCE RLS to bind it.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/integration.growth-persistence

    Layer: integrations · 2 changes

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

    Layer: libs · 1 change

  • @lssm-tech/module.lssm-os-control-plane

    Layer: modules · 1 change