Back to changelog index

0.0.0

Aug 05, 2026 · 6 packages · 45 unique changes · 24 release entries

appslibsBreaking changes

This release affects the sharedLibs, solutions familyies.

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

Release summaries

  • company-intelligence-continuous-ingestion

    Add durable multi-source Company Intelligence ingestion, replay-safe checkpoints, bounded retries and quotas, truthful credential failure, and deletion/ACL propagation.

    maintainer

    Upload, webhook, polling, and representative connector classes now share app-owned durable jobs, deterministic retry/checkpoint behavior, redacted receipts, and immutable propagation.

    integrator

    Existing 0022/0023 tables are reused without a migration. Bind provider-neutral adapters to their existing package owners and resolve credentials outside durable payloads.

  • company-intelligence-tenant-persistence

    Add app-owned PostgreSQL persistence, FORCE RLS, durable work state, resumable backfill, and recovery qualification for canonical Company Intelligence records.

    maintainer

    The API monolith owns canonical Company Intelligence records, normalized references, append-only receipts/events, tombstone purge controls, jobs, outbox, DLQ, and checkpointed backfill state in PostgreSQL with FORCE RLS.

    integrator

    G002 public identities remain unchanged. Apply additive migrations 0022 and 0023, use a NOSUPERUSER NOBYPASSRLS runtime role, and qualify clean/upgrade/recovery paths on PostgreSQL 15 before admitting tenant data.

  • companyos-auth-opa-migration-ledger

    Track Better Auth and OPA schema state transactionally, safely evolve partial Better Auth schemas, and preserve the supported idempotent first-admin server-API bootstrap.

    maintainer

    The first-admin command now requires an explicit canonical workspace identifier and derives its tenant exclusively from the Better Auth organization ID used by sessions. It creates credentials through Better Auth only when absent, reconciles enterprise-admin and owner authority, transactionally binds the Better Auth user and organization to exactly one Managed CompanyOS tenant/workspace/operator, and sends the normal verification email without marking email ownership verified.

  • companyos-managed-runtime-domain-migration

    Move managed CompanyOS runtime, auth, CORS, cookie, profile, booking, and OAuth origins from the retired companyos.lssm.tech topology to www.companyos.run and api.companyos.run.

    integrator

    Configure the managed web origin as https://www.companyos.run, API/auth origin as https://api.companyos.run, and cookie parent as .companyos.run. Retired origins fail closed.

    customer

    Managed CompanyOS now uses the live www.companyos.run browser origin while gtm.companyos.run remains a separate public destination.

  • cross-platform-mobile-demo-f7

    F7 — Final deliverable of the 37-task cross-platform plan. Add F3/F6 sections to AGENTS.md, create public/llms.txt, and add cross-platform ADR for the CompanyOS + CommunicationOS migration.

    maintainer

    AGENTS.md gains F3 (cross-platform analytics stitching) and F6 (performance budgets) sections documenting the FNV-1a hash contract, BSP constants parity, cold-start budget enforcement, and Maestro/view-model validation approach. public/llms.txt is a new AI-consumable reference file covering all v1 surfaces, personas, capability gating, PostHog schema, and privacy invariants. docs/adr/2026-05-19-cross-platform-companyos-communicationos-pillars.md records D1-D6 architectural decisions with rationale and alternatives considered.

    integrator

    Agents and LLMs working in this package should consult public/llms.txt as the primary orientation file. AGENTS.md is the full developer guide.

  • data-transmission-crdt-v0

    Add protocol-neutral data transmission contracts, deterministic runtime proofs, and guarded WebSocket worker/demo evidence while holding CRDT/Loro promotion behind the baseline gate.

    maintainer

    Maintainers now have a contract-first package family for standard fetch/RPC, realtime guardrails, invalidation, presence, idempotency, collaboration seams, and worker/demo proof evidence; CRDT/Loro promotion remains disabled until the baseline gate is green.

    integrator

    Integrators can execute protocol-neutral operations through the standard fetch proof, test realtime semantics in memory, and use the private Bun worker as a deployment-shape reference; Loro CRDT adoption remains a deferred proof lane.

  • docs-example-runtime-preview

    Wrap UI-backed docs example previews in the template runtime provider so public example pages prerender with the same runtime boundary as sandbox and template previews.

    maintainer

    The `/docs/examples/<key>` inline preview section now initializes `TemplateRuntimeProvider` for examples with inline runtime UI while preserving lightweight fallback previews for non-UI examples.

    customer

    Public docs pages for UI-backed examples, including `analytics-dashboard`, now prerender successfully instead of failing on missing template runtime context.

  • integration-hub-uplift-phase-1-app

    Internal `force-dynamic` flip + session-resolved persona for `/companyos/integrations/**` carried into Phase 1.

    integrator

    All `/companyos/integrations/**` pages are now `force-dynamic` and resolve `RoleMorphProjection` per-request from the auth session; client-side persona switching is removed.

    maintainer

    New `runtime/role-morph-resolver.ts` + `role-morph-cache-key.ts` (with `hashRoleMorph` PII-exclusion guarantee) own per-request persona projection. SSR catalog uses `unstable_cache` keyed by the hash with `revalidateTag('integrations')` invalidation.

  • integration-hub-uplift-phase-2-app

    Add new per-integration tab routes and update existing integration routes in web-application-monolith.

    integrator

    Seven new route pages under /companyos/integrations/[integrationId]/ (connections, syncs, credentials, secrets, config, audit, and the tab layout shell). All pages use force-dynamic with session-resolved RoleMorphProjection. No route removals or renames.

    maintainer

    Credentials and secrets pages are security-class (uncached, streaming via Suspense). All new pages emit surface_viewed + role_morph_resolved signals. No DEFAULT_ROLE / TENANT_ID / CORRELATION_ID hardcoding in any integration route — all session-derived.

  • managed-companyos-booking-reschedule-empty-state

    Show a usable empty and retry state when public booking reschedule availability has no slots.

    customer

    Visitors rescheduling a booking can distinguish no current slots from a pending availability request and can retry without leaving the page.

    maintainer

    The reschedule state projection makes loading, failure, empty, and ready availability outcomes explicit and independently testable.

  • managed-companyos-four-context-product-canary

    Add a read-only production canary for Personal, LSSM, CompanyOS, and ND Consulting profile, booking, and Google-derived availability.

    integrator

    A strict four-context matrix configures non-mutating production checks for published profiles, booking links, current availability, and public web routes.

    maintainer

    The operations workflow advances its migration inventory through 0033 and runs the product canary only for the reviewed canary-smoke action.

  • managed-companyos-google-calendar-topology-selection

    Make protected Google Calendar topology selection usable without manual internal identifiers.

    customer

    Calendar administrators select an eligible owned-live booking event and start from valid scheduling defaults instead of copying opaque references.

  • managed-companyos-production-env-activation

    Make the Managed CompanyOS production environment contract explicit for profile authority, booking, and Google Workspace Calendar activation.

    integrator

    Deployment templates and the runbook identify the exact server-only variables required before profile editing, Google Calendar OAuth, and Postgres-backed booking effects can be enabled.

    maintainer

    Inventory checks can distinguish required authority configuration from optional fail-closed booking notifications and approval-gated rollout posture.

  • managed-companyos-public-booking-json-datetime

    Let JSON public-booking availability requests cross the DateTime contract boundary without weakening link scope or validation.

    customer

    Public booking pages can load link-scoped availability from their ISO date-time request window instead of failing before link resolution.

    maintainer

    The HTTP adapter converts only valid ISO date-time strings to the ContractSpec-native Date input while invalid values retain the existing fail-closed validation result.

  • managed-companyos-public-booking-runtime-truth

    Make the public booking page honor request-time adapter readiness and fail closed without selectable slots for missing or sandbox-only posture.

    integrator

    Public booking now reflects MANAGED_COMPANYOS_PUBLIC_BOOKING_ADAPTER_STATUS at request time; only adapter_ready enables selectable lifecycle slots.

    maintainer

    The browser receives only the serializable adapter status, while provider operations and manage bearers remain behind existing server boundaries.

  • managed-companyos-public-profile-not-found-locale

    Localize public profile not-found content and metadata through the shared request locale contract.

    customer

    Visitors reaching an unknown public profile see localized recovery copy and page metadata in the same language as the rest of the web app.

  • managed-companyos-smart-meeting-bff-locale

    Localize authenticated Organization Planning readiness snapshots to the request locale.

    customer

    French and Spanish users receive localized smart-meeting readiness and setup copy from the authenticated planning API.

    integrator

    Organization Planning BFF consumers can rely on the resolved request locale instead of translating an English-only readiness payload.

  • managed-companyos-web-theme-hardening

    Wire app-shell runtime (globals.css + cockpit tokens, providers, layout rewrite, global state routes) and add three enforcement tests for the managed-companyos web monolith.

    maintainer

    App shell now has a full CSS pipeline (tailwind + tw-animate-css + cockpit slate/cyan/amber tokens in globals.css), env-gated PostHogProvider (no-op when NEXT_PUBLIC_POSTHOG_KEY is unset, SSR-safe), ThemeProvider (dark-only S1 — defaultTheme="dark", no enableSystem, dark class applied by next-themes at hydration; :root tokens are already cockpit-dark to minimise flash), global state routes (error.tsx Client Component + loading.tsx + not-found.tsx using design-system primitives), and three enforcement tests. AGENTS.md and README.md updated with Theme & runtime wiring section. No public-surface change; bundle untouched.

    integrator

    No bundle or public-surface change. The app renders with full Tailwind CSS theme. PostHog instrumentation is active only when NEXT_PUBLIC_POSTHOG_KEY is set. S2/S3 follow-ups (design-system CSS token export, enableSystem re-enable, CSP, page-color rewrites) documented in AGENTS.md.

  • mobile-monolith-app-submission-readiness

    Add App Store / Google Play submission-readiness metadata and evidence for the mobile monolith proof shell.

    maintainer

    The Expo mobile proof now records bundle identifiers, legal review links, iOS privacy manifest posture, Android permission boundaries, and credential-free EAS submit expectations in source-controlled readiness evidence.

    integrator

    Store submission metadata is read-first and deterministic; production App Store Connect / Google Play credentials remain external to the repository.

  • opa-v2-reset-evidence-repair

    Harden OPA v2 reset and restore evidence validation without authorizing or executing a reset.

    maintainer

    Reset evidence now rejects reordered migration ledgers, invented or misaligned Connect artifacts, incomplete approval authority, incomplete passed rehearsals, and grants that do not match the shipped OPA migration sources.

  • reviewready-web-proof

    Add the /companyos/app-submission-readiness web product proof rendering a runtime-driven readiness report.

    customer

    A new /companyos/app-submission-readiness route demonstrates the ReviewReady readiness report end-to-end. The rendered report (findings, score, decision, per-store checklists) is produced by the runReadinessAudit engine, not hardcoded.

    maintainer

    The route is a thin App Router shell composing @lssm-tech/module.app-submission-readiness with runtime-driven fixtures, statically rendered, emitting CompanyOS behavior signals for the new app_submission_readiness surface with no secret leakage.

  • special-ops-capability-db-schema

    Add Special Ops capability graph and workspace DB tables (additive)

    maintainer

    Add Special Ops capability graph and workspace DB tables (additive)

    integrator

    Add Special Ops capability graph and workspace DB tables (additive)

  • special-ops-workspace-capability-repositories

    Add WorkspaceCapabilityRepository interface + drizzle and in-memory adapters for workspace and capability graph tables

    maintainer

    Add WorkspaceCapabilityRepository interface + drizzle and in-memory adapters for workspace and capability graph tables

    integrator

    Add WorkspaceCapabilityRepository interface + drizzle and in-memory adapters for workspace and capability graph tables

  • web-landing-loop-d-e2e

    Playwright E2E infrastructure + CommunicationOS draft-approve flow test (Loop D / D3).

    maintainer

    Web landing now has Playwright E2E infrastructure with a CommunicationOS draft-approve flow test.

Deprecations

  • - @lssm-tech/integration.crdt-loro promotion is disabled until the root baseline and focused CRDT checks pass together.
  • - GraphQL remains available but is optional/legacy for new data transmission work; new transmission packages do not import @lssm-tech/lib.graphql-prisma.
  • - The previous managed CompanyOS web, API, and cookie topology is retired and rejected by the production contract; use www.companyos.run, api.companyos.run, and .companyos.run respectively.

Migration guide

  • Apply Company Intelligence tenant persistence

    Required

    Apply 0022_company_intelligence_records.sql followed by 0023_company_intelligence_work_state.sql using the digest migration ledger.

    1. Back up and checkpoint the target before any approved live migration.
    2. Verify the runtime role is NOSUPERUSER NOBYPASSRLS.
    3. Run clean, 0021-upgrade, recovery, idempotency, backfill, and RLS qualification locally.
  • Configure canonical bootstrap authority

    Required

    Configure the canonical Managed CompanyOS authority binding before bootstrap.

    When: Before running the first-admin bootstrap after this upgrade.

    1. Set MANAGED_COMPANYOS_BOOTSTRAP_WORKSPACE_ID to the canonical workspace identifier.
    2. Apply tracked migrations through version 0016 before running companyos:bootstrap-admin.
  • Configure the exact managed CompanyOS production topology

    Required

    Update managed runtime and provider allowlists before activating the new domains.

    1. Set APP_WEB_BASE_URL to https://www.companyos.run.
    2. Set BETTER_AUTH_BASE_URL and browser API/auth variables to https://api.companyos.run.
    3. Set BETTER_AUTH_COOKIE_DOMAIN to .companyos.run.
    4. Update DNS, deployment aliases, and OAuth redirect allowlists only through an authorized external-production change.
    5. Keep www.companyos.run marketing and gtm.companyos.run unchanged.
  • Keep transport and CRDT engines outside core transmission packages

    Add adapter metadata instead of protocol-specific fields when connecting HTTP, WebSocket, database, or CRDT providers.

    When: When implementing new data access, realtime, or collaboration adapters.

    1. Import contracts from @lssm-tech/lib.data-transmission-spec.
    2. Use @lssm-tech/lib.data-transmission-runtime for in-memory operation, presence, subscription, invalidation, idempotency, and production-harness semantics.
    3. Do not import loro-crdt from promoted packages; keep Loro usage isolated in the deferred @lssm-tech/integration.crdt-loro lane until its promotion gate passes.
    4. Use @lssm-tech/app.worker-data-transmission-realtime only as a guarded deployment-shape proof unless you add durable persistence, auth, observability, and operating guarantees.
  • Regenerate pending reset evidence

    Required

    Recreate pending or completed evidence against the hardened schemas and validator.

    When: Before relying on an OPA v2 reset authorization or restore rehearsal.

    1. Preserve migration versions 0001 through 0036 in exact order.
    2. Record the exact 56 direct table-grant records described by the repository inventory.
    3. Supply non-null approval authority and decision timestamps only when authorization is complete.
    4. Supply stored, mutually aligned Connect context, plan, verify, review, and replay evidence.
    5. Reject unrelated task lineages and store replay provenance with a valid trace identifier separately from verify decisions.
    6. Supply every operator, rehearsal, snapshot, target, verifier, and cleanup reference for a passed restore rehearsal.

Upgrade steps

  • Qualify durable ingestion and connector bindings

    assisted

    Run deterministic connector scenarios and the disposable PostgreSQL lease, propagation, receipt, and tenant-isolation proof before enabling source intake.

    Packages: @lssm-tech/app.api-application-monolith

    1. Run the focused continuous ingestion test.
    2. Run bun run --cwd packages/apps/api-application-monolith companyos:db:prove-disposable-postgres.
    3. Review docs/company-intelligence-persistence-runbook.md.
  • Qualify Company Intelligence persistence locally

    assisted

    Use the disposable PostgreSQL proof and follow the recovery runbook before tenant cutover.

    Packages: @lssm-tech/app.api-application-monolith

    1. Run bun run --cwd packages/apps/api-application-monolith companyos:db:prove-disposable-postgres.
    2. If PostgreSQL 15 already runs locally, use companyos:db:prove-existing-postgres.
    3. Review docs/company-intelligence-persistence-runbook.md.
  • Reconcile first-admin authority

    assisted

    Re-run the supported first-admin bootstrap to reconcile authority without rebinding.

    Packages: @lssm-tech/app.api-application-monolith

    1. Run bun run companyos:bootstrap-admin from the API package with server-only bootstrap configuration.
    2. Complete the verification email flow when the existing Better Auth user is unverified.
    3. Verify the resulting user, owner membership, tenant, workspace, operator, and authority binding counts are each exactly one.
  • Re-run focused data transmission verification

    assisted

    The V0 spans spec, runtime, private worker, and web demo boundaries; CRDT/Loro verification is documented as a promotion prerequisite, not a promoted package in this capsule.

    Packages: @lssm-tech/lib.data-transmission-spec, @lssm-tech/lib.data-transmission-runtime

    1. Run focused tests for data-transmission-spec, data-transmission-runtime, worker-data-transmission-realtime, and the web-landing realtime demo route.
    2. Run targeted typechecks and lint checks for the same packages/apps.
    3. Before re-enabling CRDT/Loro promotion, also run bun run --cwd packages/integrations/crdt-loro typecheck, lint:check, and test in the same green root-baseline run.
    4. Run build:worker, no-Prisma, release build, and release check before publishing.
  • Confirm no `/companyos/integrations` route declares `force-static`

    manual

    CI guard in Phase 3 asserts all routes under `/companyos/integrations/**` are `force-dynamic`.

    Packages: @lssm-tech/app.web-application-monolith

  • Configure the read-only four-context canary matrix

    manual

    Install the exact Personal, LSSM, CompanyOS, and ND Consulting public profile and booking projections in the reviewed environment secret.

    Packages: @lssm-tech/app.api-application-monolith, @lssm-tech/app.web-application-monolith

    1. Configure MANAGED_COMPANYOS_CANARY_MATRIX_JSON with each canonical context exactly once and no authentication, cookie, tenant, database, or provider fields.
    2. Run managed-companyos:ops:product-smoke before any live write canary.
    3. Retain target-database and live Google event/Meet approvals as separate gates; the product smoke is intentionally read-only.
  • Configure production authority and Google Calendar OAuth

    manual

    Add the documented values through the deployment secret manager and register the exact Google OAuth callback before connecting an account.

    Packages: @lssm-tech/app.api-application-monolith, @lssm-tech/app.web-application-monolith

    1. Configure the profile context keys and booking grant pepper as distinct server-only random values of at least 32 bytes.
    2. Register the exact API OAuth callback with Google before enabling a Google Workspace Calendar connection.
  • Retain the public-booking evidence gate

    manual

    Keep public booking dry-run until current provider and vault evidence permits an adapter-ready posture.

    Packages: @lssm-tech/app.api-application-monolith, @lssm-tech/app.web-application-monolith

    1. Do not infer live traffic from environment inventory alone; follow docs/runbooks/opa-public-booking.md before setting adapter_ready.
  • Qualify request-time booking posture before enabling adapter_ready

    manual

    Keep the route degraded until the approved provider, vault, outbox, route-policy, and rollout evidence are current.

    Packages: @lssm-tech/app.web-application-monolith

    1. Leave the adapter status unset for fail-closed dry-run behavior.
    2. Use sandbox_only only for provider qualification without customer writes.
    3. Set adapter_ready only after the OPA public booking runbook gates pass.
  • Set NEXT_PUBLIC_POSTHOG_KEY to enable PostHog

    auto

    PostHog initialisation is env-gated and produces no side effects when the key is absent.

    Packages: @lssm-tech/app.web-application-monolith

    1. Add NEXT_PUBLIC_POSTHOG_KEY=<your-key> to the deployment environment to enable PostHog session tracking.
    2. When enabled, add "connect-src https://eu.i.posthog.com" to your Content-Security-Policy header (S2 concern — see AGENTS.md).
    3. No action required to disable PostHog — simply omit the env var.
  • Review mobile proof submission metadata before uploading builds

    manual

    Confirm the legal pages are live, inspect generated PrivacyInfo.xcprivacy after prebuild/EAS, and keep submission credentials in EAS or CI secret stores.

    Packages: @lssm-tech/app.mobile-monolith

    1. Confirm https://contractspec.io/privacy, /terms, and /support are live.
    2. Run an Expo prebuild or EAS build and inspect the generated iOS privacy manifest.
    3. Add any App Store Connect-reported third-party SDK required-reason APIs before upload promotion.
    4. Keep App Store Connect and Google Play credentials out of source.
  • Validate the reset packet

    manual

    Run the focused validator before any reset decision.

    Packages: @lssm-tech/app.api-application-monolith

    1. Run bun test scripts/validate-opa-v2-evidence.test.ts.
    2. Run bun scripts/validate-opa-v2-evidence.ts.
  • View the app-submission-readiness product proof

    manual

    Open /companyos/app-submission-readiness to see the runtime-driven readiness report.

    Packages: @lssm-tech/app.web-application-monolith

    1. Navigate to /companyos/app-submission-readiness in the web monolith.
    2. Confirm the report findings, score, decision, and per-store checklists render.
  • Review Special Ops Capability Db Schema adoption

    manual

    Add Special Ops capability graph and workspace DB tables (additive)

    Packages: @lssm-tech/app.api-application-monolith

    1. Review the paired changeset summary and update consumers only if they use the affected package surface.
  • Review Special Ops Workspace Capability Repositories adoption

    manual

    Add WorkspaceCapabilityRepository interface + drizzle and in-memory adapters for workspace and capability graph tables

    Packages: @lssm-tech/app.api-application-monolith

    1. Review the paired changeset summary and update consumers only if they use the affected package surface.

Unique release changes

  • - @lssm-tech/integration.crdt-loro promotion is disabled until the root baseline and focused CRDT checks pass together.

    2 packages · 2 occurrences

  • - Add a read-only production canary for Personal, LSSM, CompanyOS, and ND Consulting profile, booking, and Google-derived availability.

    2 packages · 2 occurrences

  • - Add adapter metadata instead of protocol-specific fields when connecting HTTP, WebSocket, database, or CRDT providers.

    2 packages · 2 occurrences

  • - Add protocol-neutral data transmission contracts, deterministic runtime proofs, and guarded WebSocket worker/demo evidence while holding CRDT/Loro promotion behind the baseline gate.

    2 packages · 2 occurrences

  • - Add Special Ops capability graph and workspace DB tables (additive)

    1 packages · 2 occurrences

  • - Add the documented values through the deployment secret manager and register the exact Google OAuth callback before connecting an account.

    2 packages · 2 occurrences

  • - Add WorkspaceCapabilityRepository interface + drizzle and in-memory adapters for workspace and capability graph tables

    1 packages · 2 occurrences

  • - GraphQL remains available but is optional/legacy for new data transmission work; new transmission packages do not import @lssm-tech/lib.graphql-prisma.

    2 packages · 2 occurrences

  • - Install the exact Personal, LSSM, CompanyOS, and ND Consulting public profile and booking projections in the reviewed environment secret.

    2 packages · 2 occurrences

  • - Keep public booking dry-run until current provider and vault evidence permits an adapter-ready posture.

    2 packages · 2 occurrences

  • - Make the Managed CompanyOS production environment contract explicit for profile authority, booking, and Google Workspace Calendar activation.

    2 packages · 2 occurrences

  • - Move managed CompanyOS runtime, auth, CORS, cookie, profile, booking, and OAuth origins from the retired companyos.lssm.tech topology to www.companyos.run and api.companyos.run.

    2 packages · 2 occurrences

  • - The previous managed CompanyOS web, API, and cookie topology is retired and rejected by the production contract; use www.companyos.run, api.companyos.run, and .companyos.run respectively.

    2 packages · 2 occurrences

  • - The V0 spans spec, runtime, private worker, and web demo boundaries; CRDT/Loro verification is documented as a promotion prerequisite, not a promoted package in this capsule.

    2 packages · 2 occurrences

  • - Update managed runtime and provider allowlists before activating the new domains.

    2 packages · 2 occurrences

  • - Add App Store / Google Play submission-readiness metadata and evidence for the mobile monolith proof shell.

    1 packages · 1 occurrences

  • - Add app-owned PostgreSQL persistence, FORCE RLS, durable work state, resumable backfill, and recovery qualification for canonical Company Intelligence records.

    1 packages · 1 occurrences

  • - Add durable multi-source Company Intelligence ingestion, replay-safe checkpoints, bounded retries and quotas, truthful credential failure, and deletion/ACL propagation.

    1 packages · 1 occurrences

  • - Add new per-integration tab routes and update existing integration routes in web-application-monolith.

    1 packages · 1 occurrences

  • - Add the /companyos/app-submission-readiness web product proof rendering a runtime-driven readiness report.

    1 packages · 1 occurrences

  • - Apply 0022_company_intelligence_records.sql followed by 0023_company_intelligence_work_state.sql using the digest migration ledger.

    1 packages · 1 occurrences

  • - CI guard in Phase 3 asserts all routes under `/companyos/integrations/**` are `force-dynamic`.

    1 packages · 1 occurrences

  • - Configure the canonical Managed CompanyOS authority binding before bootstrap.

    1 packages · 1 occurrences

  • - Confirm the legal pages are live, inspect generated PrivacyInfo.xcprivacy after prebuild/EAS, and keep submission credentials in EAS or CI secret stores.

    1 packages · 1 occurrences

  • - F7 — Final deliverable of the 37-task cross-platform plan. Add F3/F6 sections to AGENTS.md, create public/llms.txt, and add cross-platform ADR for the CompanyOS + CommunicationOS migration.

    1 packages · 1 occurrences

  • - Harden OPA v2 reset and restore evidence validation without authorizing or executing a reset.

    1 packages · 1 occurrences

  • - Internal `force-dynamic` flip + session-resolved persona for `/companyos/integrations/**` carried into Phase 1.

    1 packages · 1 occurrences

  • - Keep the route degraded until the approved provider, vault, outbox, route-policy, and rollout evidence are current.

    1 packages · 1 occurrences

  • - Let JSON public-booking availability requests cross the DateTime contract boundary without weakening link scope or validation.

    1 packages · 1 occurrences

  • - Localize authenticated Organization Planning readiness snapshots to the request locale.

    1 packages · 1 occurrences

  • - Localize public profile not-found content and metadata through the shared request locale contract.

    1 packages · 1 occurrences

  • - Make protected Google Calendar topology selection usable without manual internal identifiers.

    1 packages · 1 occurrences

  • - Make the public booking page honor request-time adapter readiness and fail closed without selectable slots for missing or sandbox-only posture.

    1 packages · 1 occurrences

  • - Open /companyos/app-submission-readiness to see the runtime-driven readiness report.

    1 packages · 1 occurrences

  • - Playwright E2E infrastructure + CommunicationOS draft-approve flow test (Loop D / D3).

    1 packages · 1 occurrences

  • - PostHog initialisation is env-gated and produces no side effects when the key is absent.

    1 packages · 1 occurrences

  • - Re-run the supported first-admin bootstrap to reconcile authority without rebinding.

    1 packages · 1 occurrences

  • - Recreate pending or completed evidence against the hardened schemas and validator.

    1 packages · 1 occurrences

  • - Run deterministic connector scenarios and the disposable PostgreSQL lease, propagation, receipt, and tenant-isolation proof before enabling source intake.

    1 packages · 1 occurrences

  • - Run the focused validator before any reset decision.

    1 packages · 1 occurrences

  • - Show a usable empty and retry state when public booking reschedule availability has no slots.

    1 packages · 1 occurrences

  • - Track Better Auth and OPA schema state transactionally, safely evolve partial Better Auth schemas, and preserve the supported idempotent first-admin server-API bootstrap.

    1 packages · 1 occurrences

  • - Use the disposable PostgreSQL proof and follow the recovery runbook before tenant cutover.

    1 packages · 1 occurrences

  • - Wire app-shell runtime (globals.css + cockpit tokens, providers, layout rewrite, global state routes) and add three enforcement tests for the managed-companyos web monolith.

    1 packages · 1 occurrences

  • - Wrap UI-backed docs example previews in the template runtime provider so public example pages prerender with the same runtime boundary as sandbox and template previews.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.api-application-monolith

    Layer: apps · 2 changes

  • @lssm-tech/app.mobile-monolith

    Layer: apps · 2 changes

  • @lssm-tech/app.web-application-monolith

    Layer: apps · 2 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 1 changes

  • @lssm-tech/lib.data-transmission-runtime

    Layer: libs · 5 changes

  • @lssm-tech/lib.data-transmission-spec

    Layer: libs · 5 changes