Back to changelog index

1.1.16

May 26, 2026 · 5 packages · 48 unique changes · 20 release entries

appsbundlesBreaking changes

This release affects the solutions family.

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

Release summaries

  • agent-workflow-command-center-readiness-evidence

    Document the production-readiness evidence gates for the Managed CompanyOS Agent/Workflow Command Center slice.

    maintainer

    Maintainers get a release-facing checklist for command-center promotion gates, verification commands, known authority gates, and evidence packet shape.

    integrator

    Integrators get explicit guidance that examples and app hosts remain deterministic consumers while module/bundle surfaces own command-center behavior.

  • b2-operating-cockpit-bundle-promotion

    Promote OperatingCockpitPreview and all operating-cockpit screens into bundle.managed-companyos.

    maintainer

    OperatingCockpitPreview, OriginChip, COCKPIT_ORIGIN_KINDS, all ten screen components (AuditTrailScreen, CommunicationInboxScreen, DashboardScreen, DryRunConsoleScreen, EvidenceMapScreen, HomeScreen, PolicyGateScreen, StarterKitScreen, ThreadDetailScreen, WorkGraphScreen), OperatingCockpitScreen enum, state helpers (createInitialOperatingCockpitState, createInMemoryOperatingCockpitPersistence, parseOperatingCockpitState, reduceOperatingCockpitState, serializeOperatingCockpitState), EMPTY_COMMUNICATION_DATA sentinel, and navigation/href preview data are now exported from the canonical bundle.managed-companyos surface under ui/cockpit/templates/operating-cockpit.

    integrator

    Import OperatingCockpitPreview and related types from @lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit instead of the deprecated example package shim.

  • commos-bundle-provider-props

    Add personalization + rolemorph props to CommOS bundle templates (G006/G007 wiring)

    maintainer

    InboxTemplate, ThreadsTemplate, HandoffsTemplate, and ThreadDetailTemplate now accept optional `personalization?: ResolvedPreferenceProfile` and `rolemorph?: RoleMorphProjection` props. Both default to fail-closed values (empty profile, EMPTY_ROLEMORPH) when omitted. Templates converted to 'use client' to mount React context providers at the template boundary.

    customer

    CommOS screens in CompanyOS applications now respect persona preferences (density, guidance) and role-based capability gating automatically when the parent page passes the resolved personalization and rolemorph values.

  • cross-platform-managed-companyos-bundle

    Promote operating-cockpit view-model adapters as pure synchronous exports safe for both Next.js RSC and Expo React Native consumers.

    maintainer

    Four new view-model builders exported: buildMobileCockpitViewModel, buildMobileWorkGraphViewModel, buildMobileAuditLogViewModel, buildMobileInboxViewModel. All are pure synchronous functions with no server-only imports.

    integrator

    Mobile consumers (Expo / React Native) can now import mobile view-model builders directly from @lssm-tech/bundle.managed-companyos without bundler errors. Web RSC consumers are unaffected.

    customer

    CompanyOS surfaces (cockpit, work-graph, audit-log, inbox) are now available on native iOS and Android via the mobile-monolith superapp shell.

  • integration-hub-uplift-phase-1-bundle

    Additive bump for the Lane 0 integration atoms + capability projection landed in `bundle.managed-companyos`.

    integrator

    New capability atoms (`CapabilityButton`, `CapabilityLens`, `CapabilityFallback`) plus the `IntegrationCapability` enum + `useIntegrationCapabilities` hook are now consumable from the bundle for Phase 2 screen lanes.

    maintainer

    Lane 0 atoms + `integration-rolemorph.ts` carry `@frozen-until: integration-hub-uplift-phase-3 (Lane 0 owner)` markers and are CODEOWNERS-pinned for Phase 2; non-Lane-0 commits are rejected on those paths.

  • integration-hub-uplift-phase-2-screens

    Add first-class bundle-owned Integration Hub management screens and normalized catalog seams to bundle.managed-companyos.

    integrator

    Four new tab templates are now available: CredentialsTabTemplate, SecretsTabTemplate, ConfigTabTemplate, IntegrationAuditTabTemplate. Existing IntegrationHubTemplate and IntegrationDetailTemplate are updated with capability-gated actions, persona-adaptive layouts, bundle-owned health/details and Info affordances, and read-only configure states for inspect-only personas. Consumers can feed normalized records through buildIntegrationHubViewModelFromCatalog instead of rebuilding catalog behavior in apps or examples.

    maintainer

    New organisms (IntegrationAuditFeed, IntegrationConfigForm, CredentialsScreen, SecretsScreen, ConnectionsTableView, SyncConfigsTableView) and 8 view-model families landed. The reusable catalog seam now exports normalized catalog/connection records, filter state, health summary, and action descriptor contracts from the bundle. Keep future Integration Hub list/detail behavior routed through these bundle-owned VM/UI surfaces.

  • managed-companyos-app-runtime

    Add executable managed CompanyOS app-layer foundations with Next.js web/API monoliths and a VPS worker/WebSocket runtime.

    maintainer

    Managed CompanyOS now has test-backed app-layer runtime surfaces instead of PRD-only scaffolding.

    integrator

    Integrators can evaluate provider-neutral managed and BYOK flows through deterministic web, API, worker, and WebSocket surfaces while production provider choices remain approval-gated.

  • managed-companyos-bundle

    Add the provider-neutral Managed CompanyOS product-composition bundle.

    maintainer

    Maintainers get a provider-neutral bundle boundary for the managed CompanyOS app ecosystem without importing app, example, or provider SDK code.

    integrator

    Integrators can compose web/API/worker app layers from deterministic tenant, integration, approval, replay, evidence, and health readiness fixtures before selecting live providers.

    agent

    Agents can validate managed/BYOK parity, redacted credential refs, fail-closed approval gates, evidence receipts, and forbidden imports through focused tests.

  • managed-companyos-capability-graph

    Add canonical capability graph + special-ops/ops-sprint/work-graph view-models to @lssm-tech/bundle.managed-companyos.

    maintainer

    Introduces src/capability-graph/ as the production-owned shape source-of-truth for the Special Ops capability graph. Adds CapabilityNodeKind, CapabilityStatus (incl. disabled), CapabilityNode, CapabilityEdge, CapabilityGraph, pure builders (createSpecialOpsCapabilityGraph, createSpecialOpsWorkspaceProfile, createSpecialOpsSeedRunReceipt, attachSpecialOpsCapabilityGraph), read helpers, and projection selectors (selectCockpitProjection, selectOpsSprintProjection, selectWorkGraphProjection). Disabled or restricted nodes surface a [redacted-capability] label and a disabled effective status with no raw secret material. View-models for special-ops/ai-ops-sprint/work-graph carry a deterministic locale (default en) and an optional displayCopy map keyed by ManagedCompanyOsI18nKey for T7/T9 localization. Legacy Managed* type aliases remain exported for one migration cycle.

    integrator

    Import the new capability graph and projections from @lssm-tech/bundle.managed-companyos to power the Special Ops cockpit, AI Ops Sprint, and Work Graph surfaces. View-model builders accept an optional locale and displayCopy map so API/worker/web layers can hydrate localized strings without forking the builders. No new runtime dependencies; no imports from packages/apps/* or packages/examples/*.

  • managed-companyos-cockpit-ui-export

    Expose the managed CompanyOS cockpit UI subpath used by promoted operating-cockpit shims.

    integrator

    Consumers can import the promoted operating cockpit template from the managed-companyos bundle export map instead of failing package subpath resolution.

    maintainer

    The source and publish export maps now include the canonical UI barrel and nested UI subpaths needed by the B2 shim-delete path.

  • managed-companyos-composition

    Document the provider-neutral Managed CompanyOS composition bundle and managed/BYOK ownership parity surface.

    maintainer

    Maintainers get a release capsule for the composition bundle boundary, redacted-secret guardrails, and provider-neutral app-facing seams.

    integrator

    Integrators can evaluate managed and BYOK ownership modes through deterministic DTO/view-model helpers before provider approval.

    agent

    Agents can trace managed/BYOK parity and provider-neutral smoke expectations to focused bundle tests and docs.

  • managed-companyos-ecosystem

    Release the provider-neutral Managed CompanyOS ecosystem slice across web, API, worker, integration, workflow, replay, evidence, and operator readiness surfaces.

    maintainer

    Maintainers get a single release capsule for the Managed CompanyOS PRD implementation and its remaining provider/compliance caveats.

    integrator

    Integrators can exercise deterministic managed/BYOK setup, workflow, replay/evidence, health/degraded, and WebSocket proof surfaces without production provider defaults.

    agent

    Agents can follow PRD evidence through the ecosystem handoff packet, runbook, release readiness matrix, and focused tests.

  • managed-companyos-product-surface-i18n

    Add locale-aware Managed CompanyOS product-surface copy owned by the bundle translation catalogs.

    maintainer

    Managed CompanyOS product-surface route and degraded-state display copy now resolves through bundle-owned i18n catalogs instead of app-local business dictionaries.

    integrator

    App shells can request localized product-surface snapshots by passing locale preferences into bundle helpers while keeping ids, paths, evidence refs, and safety reasons stable.

    agent

    I18n work should keep Managed CompanyOS business copy in the bundle catalog and verify no app-local duplicate dictionaries are introduced for shared product surfaces.

  • managed-companyos-production-hardening

    Close Managed CompanyOS production-readiness gaps with persistence, provider wiring, deployment artifacts, live WebSocket proof, and production E2E evidence.

    maintainer

    Production-hardening artifacts now cover deployment, durable state, provider-neutral reference dispatch harness, live WebSocket proof, and E2E verification.

    integrator

    Integrators can run the production E2E proof with env-backed credentials and mounted durable state while raw secrets remain out of git.

  • managed-companyos-provider-strategy-readiness

    Document the Managed CompanyOS provider-strategy closure and release-readiness gates for broad managed/BYOK provider catalog support.

    maintainer

    Maintainers get an explicit provider matrix and release gate for catalog-ready versus live-dispatch-ready Managed CompanyOS providers.

    integrator

    Integrators can rely on managed/BYOK parity by default while treating BYOK-only, regulated, unofficial, and live-session providers as documented exceptions until dispatch evidence exists.

  • managed-companyos-s6-release-readiness

    Add Managed CompanyOS S6 release-readiness evidence helpers, docs, operator runbook, and provider-catalog parity handoff covering T1–T3 app surfaces.

    maintainer

    Maintainers get an executable S6 acceptance matrix, provider-catalog parity gate, final-evidence packet shape, and a consolidated operator runbook covering web/worker/API app surfaces.

    integrator

    Integrators get provider-neutral smoke harness guidance, managed/BYOK provider-catalog parity requirements, environment validation runbook requirements, and /llms.txt guidance without committing provider secrets.

    agent

    Agents can run release-readiness tests and docs guardrails that reject compliance, credential-custody, production-provider, and autonomous reserved-action overclaims. The /llms.txt surface provides full route inventory, role roster, redaction policy, and AI-dispatch rules.

  • managed-companyos-verification-guardrails

    Tighten Managed CompanyOS verification guardrails for explicit ownership gating and provider-neutral raw-secret scans.

    maintainer

    Maintainers get passing managed-companyos package tests/typecheck plus provider-neutral safety scan evidence for explicit managed/BYOK ownership and redacted defaults.

    integrator

    Integrators keep deterministic fail-closed provider dispatch and raw-secret scanning without false positives from Markdown paths or design-token labels.

  • next-app-tsgo-prebuild

    Move Next.js app production type validation out of `next build` and into explicit package-local `tsgo` prebuild checks, while preserving Next app build success with `typescript.ignoreBuildErrors`.

    maintainer

    Next app builds now run `bun x tsgo --project tsconfig.build.json --noEmit` before `next build`, and Next itself skips its slower built-in TypeScript validation step.

    integrator

    App package builds keep type safety through an explicit tsgo prebuild script. Consumers should continue using each app's `build` or `typecheck` script instead of invoking Next's internal type validation directly.

    customer

    Production app output is unchanged; this release only makes the build pipeline faster and more explicit about where TypeScript validation runs.

  • special-ops-monolith-production-docs

    Document the database-first Special Ops monolith production cutover, seed contract, capability graph gates, and verification evidence path.

    maintainer

    Maintainers now have an explicit Special Ops production runbook separating deterministic proof paths from approval-gated DB seed, capability graph, AI Ops Sprint, work-graph, and provider cutover work.

    integrator

    Integrators can follow the documented API, worker, and web surface map while preserving no-example-runtime-import, redaction, tenant isolation, and degraded-state honesty boundaries.

    customer

    The Special Ops production path is documented as fictive, redacted, and approval-gated before real customer data or live provider dispatch is admitted.

  • t6-i18n-managed-companyos-catalog-expansion

    expand en/fr/es catalogs to cover PRD domains (additive)

    maintainer

    expand en/fr/es catalogs to cover PRD domains (additive)

    integrator

    expand en/fr/es catalogs to cover PRD domains (additive)

Deprecations

  • - package: @lssm-tech/example.companyos-communicationos-operating-cockpit; export: OperatingCockpitPreview; replacedBy: @lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit; removeAfter: shim-delete phase (B4 CI test passing)
  • - target: src/capability-graph.ts; replacement: src/capability-graph/index.ts; removalAt: next-major; note: The flat module is replaced by a directory module exporting the new names. Managed* type aliases remain available during the migration cycle.

Migration guide

  • New consumers should import Integration Hub catalog helpers from @lssm-tech/bund

    Required

    New consumers should import Integration Hub catalog helpers from @lssm-tech/bundle.managed-companyos/view-models/integration-hub or the root bundle export, then render bundle templates instead of duplicating catalog, health, Info, or configure affordances in app-local code.

    1. New consumers should import Integration Hub catalog helpers from @lssm-tech/bundle.managed-companyos/view-models/integration-hub or the root bundle export, then render bundle templates instead of duplicating catalog, health, Info, or configure affordances in app-local code.
  • To enable persona-aware density and capability gating, resolve personalization f

    Required

    To enable persona-aware density and capability gating, resolve personalization from personalizationForActorKind(actor.kind) and rolemorph from toRoleMorphProjection(result) at the page level, then pass both props to the template.

    1. To enable persona-aware density and capability gating, resolve personalization from personalizationForActorKind(actor.kind) and rolemorph from toRoleMorphProjection(result) at the page level, then pass both props to the template.
  • Run the B4 shim-delete CI test (`cd packages/examples/__tests__ && bun test`) to

    Required

    Run the B4 shim-delete CI test (`cd packages/examples/__tests__ && bun test`) to verify all promoted symbols are importable.

    1. Run the B4 shim-delete CI test (`cd packages/examples/__tests__ && bun test`) to verify all promoted symbols are importable.
  • Pass negotiated locales into Managed CompanyOS product-surface helpers

    Host apps should forward their already-negotiated locale or preference context to bundle helpers instead of copying Managed CompanyOS route labels/descriptions locally.

    1. Keep host-specific locale detection in the app adapter layer.
    2. Pass the selected locale to `createManagedCompanyOsProductSurfaceSnapshot` or `createManagedCompanyOsProductSurfaceRoutes`.
    3. Treat localized labels, descriptions, and degraded banners as presentation copy only; keep route ids, paths, capability refs, evidence refs, policy reasons, tenant ids, and correlation ids unchanged.
  • Move browser consumers to web app surfaces

    Required

    The managed CompanyOS bundle is published for Bun/Node server-side composition only; browser consumers should import through the web application or generated view-model outputs instead of a package-level browser condition.

    1. Replace direct browser imports from @lssm-tech/bundle.managed-companyos with the web application route/view-model surfaces.
    2. Keep package-level composition in server-side Bun/Node runtime code.

Upgrade steps

  • Run the app-local tsgo typecheck before Next production builds

    auto

    Use each app's package scripts so the prebuild `tsgo` gate runs before `next build` skips built-in type validation.

    Packages: @lssm-tech/app.api-application-monolith, @lssm-tech/app.web-landing, @lssm-tech/app.web-application-monolith, @lssm-tech/bundle.managed-companyos

    1. Run `bun run --cwd packages/apps/api-application-monolith build` for the API monolith.
    2. Run `bun run --cwd packages/apps/web-landing build` for the public landing app.
    3. Run `bun run --cwd packages/apps/web-application-monolith build` for the CompanyOS web app.
    4. If invoking checks separately, run the app's `typecheck` script; it points to `bun x tsgo --project tsconfig.build.json --noEmit`.
  • Update imports to canonical bundle.managed-companyos path

    assisted

    Replace example shim imports with the promoted bundle surface.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/example.companyos-communicationos-operating-cockpit

    1. Update all imports from `@lssm-tech/example.companyos-communicationos-operating-cockpit/ui` to `@lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit`.
    2. Verify no remaining imports from the deprecated example shim.
    3. Run B4 shim-delete CI test to confirm readiness for shim deletion.
  • Wire personalization and rolemorph from page to template

    auto

    Resolve props server-side and pass to bundle templates

    Packages: @lssm-tech/bundle.managed-companyos

    1. Import personalizationForActorKind and toRoleMorphProjection from your rolemorph resolution utilities
    2. Resolve roleMorphResult at the route boundary (server component)
    3. Pass personalization={personalizationForActorKind(roleMorphResult.actor.kind)} to the template
    4. Pass rolemorph={toRoleMorphProjection(roleMorphResult)} to the template
  • Wire screens through `CapabilityButton` + `useIntegrationCapabilities`

    manual

    Phase 2 screen lanes consume the Lane 0 atoms read-only via the existing bundle barrel.

    Packages: @lssm-tech/bundle.managed-companyos

  • Replace imports of ManagedCapabilityKind/Status/Node/Edge/Graph with CapabilityN

    manual

    Replace imports of ManagedCapabilityKind/Status/Node/Edge/Graph with CapabilityNodeKind/Status/Node/Edge/Graph for new code.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Replace imports of ManagedCapabilityKind/Status/Node/Edge/Graph with CapabilityNodeKind/Status/Node/Edge/Graph for new code.
  • When building view-models, pass an optional locale and displayCopy map to forwar

    manual

    When building view-models, pass an optional locale and displayCopy map to forward localization context end-to-end.

    Packages: @lssm-tech/bundle.managed-companyos

    1. When building view-models, pass an optional locale and displayCopy map to forward localization context end-to-end.
  • Import promoted cockpit UI from the bundle subpath

    manual

    Use `@lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit` for the promoted operating-cockpit template surface.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Keep example-local cockpit files as shims only.
    2. Put new cockpit UI logic in `@lssm-tech/bundle.managed-companyos` before re-exporting through the example package.
  • Remove duplicate Managed CompanyOS business dictionaries from app shells

    manual

    Use the bundle catalogs for shared Managed CompanyOS product-surface display copy.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Search web and mobile app shells for route label/description dictionaries that duplicate Managed CompanyOS product-surface copy.
    2. Replace duplicate business copy with bundle helper output.
    3. Leave true app-shell metadata, accessibility text, and host-specific error/proof copy in app-owned catalogs.
  • Run Managed CompanyOS verification guardrails before promotion

    assisted

    Execute the managed bundle tests, typecheck, modified-file lint, provider safety scan, and production E2E check.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Run `bun test --cwd packages/bundles/managed-companyos`.
    2. Run `bun run --cwd packages/bundles/managed-companyos typecheck`.
    3. Run `bun run managed-companyos:provider-safety`.
    4. Run `bun run managed-companyos:prod-e2e`.
  • Review T6 I18n Managed Companyos Catalog Expansion adoption

    manual

    expand en/fr/es catalogs to cover PRD domains (additive)

    Packages: @lssm-tech/bundle.managed-companyos

    1. Review the paired changeset summary and update consumers only if they use the affected package surface.
  • Adopt managed CompanyOS app foundations safely

    assisted

    Compose the managed bundle through the app monoliths while keeping provider SDKs, credentials, persistence, and queues behind explicit approval.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/app.web-application-monolith, @lssm-tech/app.api-application-monolith, @lssm-tech/app.worker-application-monolith

    1. Use the Next.js web app for cockpit review and proof visibility.
    2. Use the Next.js API app for deterministic workspace, evidence, and health route handlers.
    3. Use the Bun worker/WebSocket runtime for VPS graph snapshot publication.
    4. Keep managed/BYOK provider credentials represented as redacted references only.
  • Compose managed CompanyOS apps through the bundle boundary

    assisted

    Use the new bundle for app-facing ports and deterministic readiness checks while keeping providers and runnable app entrypoints outside the bundle.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Import blueprint, readiness, boundary, port, and type helpers from `@lssm-tech/bundle.managed-companyos`.
    2. Keep runnable apps under `packages/apps/*` and compose downward through the bundle, modules, and libs.
    3. Add provider adapters only after explicit provider approval and keep credentials represented by redacted refs.
  • Compose app layers through the managed-companyos bundle

    assisted

    Import provider-neutral DTOs, ports, and view-model helpers from the bundle instead of duplicating app-local logic.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Keep apps as thin entrypoints that compose downward into bundles/modules/libs.
    2. Preserve managed/BYOK admin-affordance parity and mode-specific accountability copy.
    3. Store only redacted credential refs and keep provider SDKs out of the bundle.
  • Verify the managed CompanyOS ecosystem before release handoff

    assisted

    Run the app/bundle/worker/API checks and attach the ecosystem evidence packet before claiming release readiness.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/app.web-application-monolith, @lssm-tech/app.api-application-monolith, @lssm-tech/app.worker-application-monolith

    1. Run bundle, web, API, and worker tests plus targeted typecheck/lint/build checks where environment allows.
    2. Confirm web AuthOS revoke forms post to the governed API route and current-session revoke stays blocked.
    3. Confirm workflow/replay/evidence API routes expose tenant-scoped data and degraded state is visible.
    4. Confirm CRDT remains disabled by default until explicit promotion evidence exists.
  • Deploy Managed CompanyOS with durable state and provider-neutral reference dispatch harness

    manual

    Configure web/API external hosting, worker VPS runtime, mounted state file, and provider credentials through env/secret manager values.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/app.web-application-monolith, @lssm-tech/app.api-application-monolith, @lssm-tech/app.worker-application-monolith

    1. Review `.omx/decisions/managed-companyos-production-hardening.md` before deployment.
    2. Configure `MANAGED_COMPANYOS_STATE_FILE` on a mounted persistent volume.
    3. Configure approved provider env vars through the deployment secret manager.
    4. Run `bun run managed-companyos:prod-e2e` before promoting a release.
  • Verify provider catalog and live-dispatch gates before release handoff

    assisted

    Use the readiness matrix and runbook gate to separate catalog support from production provider dispatch.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Confirm provider SDK imports and defaults stay out of bundles, libs, and modules.
    2. Confirm provider setup surfaces expose managed and BYOK modes by default and document provider-specific exceptions.
    3. Confirm live dispatch uses app/provider-layer env or credential-manager references and fails closed when refs are missing.
  • Attach S6 evidence before Managed CompanyOS release promotion

    assisted

    Use the release-readiness packet, README checklist, and command evidence before promoting managed CompanyOS surfaces.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/app.web-application-monolith, @lssm-tech/app.worker-application-monolith, @lssm-tech/app.api-application-monolith

    1. Run package tests, typecheck, lint, build, secret/redaction scan, and static import guard.
    2. Keep bundle-level provider smoke checks deterministic until approved provider dispatch is enabled from deployment secret-manager values.
    3. For app-layer provider catalog smoke, document managed/BYOK parity or exception rationale for every provider and prove missing secret-manager values fail closed.
    4. Reject release copy that claims formal compliance certification, raw credential custody, production provider execution without approval, or autonomous reserved-human actions.
    5. Verify /llms.txt is reachable at /llms, /llms.txt, and /llms.md before promoting the web app.
    6. Confirm consolidated runbook at docs/runbooks/managed-companyos.md covers deploy, degraded triage, replay regen, and evidence verification for all three app components.
  • Attach command-center readiness evidence before promotion

    assisted

    Run targeted typecheck, tests, lint, build/smoke, redaction, import-boundary, and replay-determinism checks for changed command-center surfaces.

    Packages: @lssm-tech/bundle.managed-companyos, @lssm-tech/example.agent-workflow-command-center

    1. Use docs/agent-workflow-command-center-production-readiness.md as the evidence packet template.
    2. Record exact command output summaries and known gaps before claiming production readiness.
    3. Keep live providers, credentials, external side effects, and human-review bypasses approval-gated.
  • Use the Special Ops production cutover runbook

    assisted

    Read the new runbook before promoting deterministic Special Ops surfaces to DB-backed tenant/workspace/capability graph truth.

    Packages: @lssm-tech/bundle.managed-companyos

    1. Review docs/runbooks/special-ops-monolith-production.md before enabling DB-backed Special Ops seed execution.
    2. Attach the documented tenant/workspace isolation, import-boundary, redaction, worker correlation, and degraded-state evidence before release promotion.

Unique release changes

  • - Add executable managed CompanyOS app-layer foundations with Next.js web/API monoliths and a VPS worker/WebSocket runtime.

    4 packages · 4 occurrences

  • - Add Managed CompanyOS S6 release-readiness evidence helpers, docs, operator runbook, and provider-catalog parity handoff covering T1–T3 app surfaces.

    4 packages · 4 occurrences

  • - Close Managed CompanyOS production-readiness gaps with persistence, provider wiring, deployment artifacts, live WebSocket proof, and production E2E evidence.

    4 packages · 4 occurrences

  • - Compose the managed bundle through the app monoliths while keeping provider SDKs, credentials, persistence, and queues behind explicit approval.

    4 packages · 4 occurrences

  • - Configure web/API external hosting, worker VPS runtime, mounted state file, and provider credentials through env/secret manager values.

    4 packages · 4 occurrences

  • - Move Next.js app production type validation out of `next build` and into explicit package-local `tsgo` prebuild checks, while preserving Next app build success with `typescript.ignoreBuildErrors`.

    4 packages · 4 occurrences

  • - Release the provider-neutral Managed CompanyOS ecosystem slice across web, API, worker, integration, workflow, replay, evidence, and operator readiness surfaces.

    4 packages · 4 occurrences

  • - Run the app/bundle/worker/API checks and attach the ecosystem evidence packet before claiming release readiness.

    4 packages · 4 occurrences

  • - The managed CompanyOS bundle is published for Bun/Node server-side composition only; browser consumers should import through the web application or generated view-model outputs instead of a package-level browser condition.

    4 packages · 4 occurrences

  • - Use each app's package scripts so the prebuild `tsgo` gate runs before `next build` skips built-in type validation.

    4 packages · 4 occurrences

  • - Use the release-readiness packet, README checklist, and command evidence before promoting managed CompanyOS surfaces.

    4 packages · 4 occurrences

  • - expand en/fr/es catalogs to cover PRD domains (additive)

    1 packages · 2 occurrences

  • - Add canonical capability graph + special-ops/ops-sprint/work-graph view-models to @lssm-tech/bundle.managed-companyos.

    1 packages · 1 occurrences

  • - Add first-class bundle-owned Integration Hub management screens and normalized catalog seams to bundle.managed-companyos.

    1 packages · 1 occurrences

  • - Add locale-aware Managed CompanyOS product-surface copy owned by the bundle translation catalogs.

    1 packages · 1 occurrences

  • - Add personalization + rolemorph props to CommOS bundle templates (G006/G007 wiring)

    1 packages · 1 occurrences

  • - Add the provider-neutral Managed CompanyOS product-composition bundle.

    1 packages · 1 occurrences

  • - Additive bump for the Lane 0 integration atoms + capability projection landed in `bundle.managed-companyos`.

    1 packages · 1 occurrences

  • - Document the database-first Special Ops monolith production cutover, seed contract, capability graph gates, and verification evidence path.

    1 packages · 1 occurrences

  • - Document the Managed CompanyOS provider-strategy closure and release-readiness gates for broad managed/BYOK provider catalog support.

    1 packages · 1 occurrences

  • - Document the production-readiness evidence gates for the Managed CompanyOS Agent/Workflow Command Center slice.

    1 packages · 1 occurrences

  • - Document the provider-neutral Managed CompanyOS composition bundle and managed/BYOK ownership parity surface.

    1 packages · 1 occurrences

  • - Execute the managed bundle tests, typecheck, modified-file lint, provider safety scan, and production E2E check.

    1 packages · 1 occurrences

  • - Existing callers of InboxTemplate, ThreadsTemplate, HandoffsTemplate, ThreadDetailTemplate that do not pass personalization or rolemorph continue to work — both props are optional with fail-closed defaults. No changes required for basic usage.

    1 packages · 1 occurrences

  • - Expose the managed CompanyOS cockpit UI subpath used by promoted operating-cockpit shims.

    1 packages · 1 occurrences

  • - Host apps should forward their already-negotiated locale or preference context to bundle helpers instead of copying Managed CompanyOS route labels/descriptions locally.

    1 packages · 1 occurrences

  • - Import provider-neutral DTOs, ports, and view-model helpers from the bundle instead of duplicating app-local logic.

    1 packages · 1 occurrences

  • - New consumers should import Integration Hub catalog helpers from @lssm-tech/bundle.managed-companyos/view-models/integration-hub or the root bundle export, then render bundle templates instead of duplicating catalog, health, Info, or configure affordances in app-local code.

    1 packages · 1 occurrences

  • - package: @lssm-tech/example.companyos-communicationos-operating-cockpit; export: OperatingCockpitPreview; replacedBy: @lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit; removeAfter: shim-delete phase (B4 CI test passing)

    1 packages · 1 occurrences

  • - Phase 2 screen lanes consume the Lane 0 atoms read-only via the existing bundle barrel.

    1 packages · 1 occurrences

  • - Promote operating-cockpit view-model adapters as pure synchronous exports safe for both Next.js RSC and Expo React Native consumers.

    1 packages · 1 occurrences

  • - Promote OperatingCockpitPreview and all operating-cockpit screens into bundle.managed-companyos.

    1 packages · 1 occurrences

  • - Read the new runbook before promoting deterministic Special Ops surfaces to DB-backed tenant/workspace/capability graph truth.

    1 packages · 1 occurrences

  • - Replace example shim imports with the promoted bundle surface.

    1 packages · 1 occurrences

  • - Replace imports of `@lssm-tech/example.companyos-communicationos-operating-cockpit/ui` with `@lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit`.

    1 packages · 1 occurrences

  • - Replace imports of ManagedCapabilityKind/Status/Node/Edge/Graph with CapabilityNodeKind/Status/Node/Edge/Graph for new code.

    1 packages · 1 occurrences

  • - Resolve props server-side and pass to bundle templates

    1 packages · 1 occurrences

  • - Run targeted typecheck, tests, lint, build/smoke, redaction, import-boundary, and replay-determinism checks for changed command-center surfaces.

    1 packages · 1 occurrences

  • - Run the B4 shim-delete CI test (`cd packages/examples/__tests__ && bun test`) to verify all promoted symbols are importable.

    1 packages · 1 occurrences

  • - target: src/capability-graph.ts; replacement: src/capability-graph/index.ts; removalAt: next-major; note: The flat module is replaced by a directory module exporting the new names. Managed* type aliases remain available during the migration cycle.

    1 packages · 1 occurrences

  • - The EMPTY_COMMUNICATION_DATA sentinel and all screen/state/navigation exports are available at the canonical path.

    1 packages · 1 occurrences

  • - Tighten Managed CompanyOS verification guardrails for explicit ownership gating and provider-neutral raw-secret scans.

    1 packages · 1 occurrences

  • - To enable persona-aware density and capability gating, resolve personalization from personalizationForActorKind(actor.kind) and rolemorph from toRoleMorphProjection(result) at the page level, then pass both props to the template.

    1 packages · 1 occurrences

  • - Use `@lssm-tech/bundle.managed-companyos/ui/cockpit/templates/operating-cockpit` for the promoted operating-cockpit template surface.

    1 packages · 1 occurrences

  • - Use the bundle catalogs for shared Managed CompanyOS product-surface display copy.

    1 packages · 1 occurrences

  • - Use the new bundle for app-facing ports and deterministic readiness checks while keeping providers and runnable app entrypoints outside the bundle.

    1 packages · 1 occurrences

  • - Use the readiness matrix and runbook gate to separate catalog support from production provider dispatch.

    1 packages · 1 occurrences

  • - When building view-models, pass an optional locale and displayCopy map to forward localization context end-to-end.

    1 packages · 1 occurrences

Impacted packages

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

    Layer: apps · 2 changes

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

    Layer: apps · 2 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 2 changes

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

    Layer: apps · 2 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 2 changes