Skip to content
← Back to changelog index

3.0.4

Nov 05, 2026 · 33 packages · 51 unique changes · 33 release entries

appsbundlesintegrationslibsmodulestools

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

  • agentpacks-canonical-rtk-sections

    Agentpacks applies pack-owned canonical RTK sections after generation instead of the installed rtk init templates.

    maintainer

    Edit packs/workspace-specific/rtk/claude-instructions.md and packs/workspace-specific/rtk/RTK.md to change the root RTK guidance; agentpacks generation applies them and no longer lets the local rtk init template overwrite the committed CLAUDE.md and RTK.md sections.

  • agentpacks-claude-model-precedence

    Claude Code agents keep an explicit claudecode.model, model guidance loads only for model configuration files, Fable and Mythos IDs are recognised, and pack validate flags rules Claude would always load.

    maintainer

    Regenerated Claude agents that set claudecode.model: inherit now render model: inherit even when models.json assigns them a model; agents without an override still render the profile model. .claude/rules/model-config.md gains paths frontmatter and Cursor model-config.mdc switches to alwaysApply: false with globs **/models.json and agentpacks.jsonc, so model routing guidance no longer loads in every session.

    integrator

    pack validate prints a warning for a detail rule with no globs, no claudecode.paths, and Cursor alwaysApply: false. Add globs to scope it, or set claudecode.paths: ['**/*'] to keep it always loaded in Claude Code. The warning does not fail validation.

    maintainer

    The software-best-practices pack routes to claude-opus-5-5 (default) and claude-haiku-5-5 (small), drops all temperature fields, and lets planner, test-writer and documenter inherit. security-scanner and ai-auditor move from openai/o3 to anthropic/claude-opus-5-5; this is a recorded decision the owner may revisit.

  • agentpacks-complete-skills-and-focused-guidance

    Preserve complete skill bundles across agentpacks targets and rebuild repository guidance around current ContractSpec workflows.

    maintainer

    Canonical skills, commands, role prompts, and AGENTS source templates use focused triggers, current APIs, and task-appropriate completion checks.

    integrator

    Generated and imported skills retain nested references, scripts, binary assets, metadata, permissions, and exact provenance. Text-only adapters remain compatible with single-file skills.

  • agentpacks-frontmatter-first-scoped-rules

    Keep YAML frontmatter on the first line of generated markdown, give Claude Code agents and commands their metadata, and scope Claude Code rules with paths from rule globs.

    maintainer

    Skills, agents, commands, and Cursor rules are parsed with their descriptions again because the generated-by header now follows the frontmatter. Claude Code rules with globs load only for matching files; rules without globs or with **/* stay always loaded.

    integrator

    Claude Code agents emit name, description, and a Claude-compatible model; non-Anthropic profile models fall back to claudecode.model or the session model. claudecode.paths overrides rule globs for Claude Code.

  • app-extraction-lane-x5

    Work, privacy, Builder candidate, design authoring, booking, membership and Resend ledger behavior moves from apps to owner packages

    integrator

    New owner subpaths expose the task status transition, governed privacy-rights commands, local Builder candidate planning and admission, managed tenant design authoring, typed OPA v2 public booking projections, the hCircle product membership store and a pg-compatible Resend webhook ledger. Hosts keep authority, storage, migrations and transport bindings.

  • canonical-test-contract-fixtures

    Complete canonical test contract and reference fixture ownership

    integrator

    Existing test contracts and reference fixtures retain canonical identity through compatibility imports.

  • canonical-translation-factory-runtime

    Preserve translation factory identity through canonical TranslationRuntime ownership

    integrator

    Historical translation factory imports forward the same implementations; explicit contract subpaths avoid runtime locale name collisions.

  • canonical-visual-registry-owners

    Canonical owners for visual scenario and visualization registries

    integrator

    Legacy visual registry and platform imports preserve canonical identity.

  • cli-ai-integration-closure

    Move canonical AI commands and reusable authoring runtimes to their approved owners while preserving public registration.

    integrator

    Existing optional AI packs preserve synchronous automatic commands and core AI extensions; bundle paths forward to the same canonical modules.

  • cli-builder-integration-owner

    Give Builder CLI adapters their canonical integration owner while preserving existing Commander behavior.

    integrator

    Existing Builder registrations keep their original command objects and automatic handlers.

  • cmp-cli-closure-reduction

    The Builder command pack loads its harness, channel and provider adapters only inside the command actions that run them, and the cli-runtime adoption catalog loader splits into private leaves

    customer

    No change in what the Builder, builder-delivery, control-plane, execution-lanes, harness and intelligence commands do or print. Starting the CLI with the Builder pack installed, or running a command that needs no adapter, no longer loads the harness runtime, the channel runtime or the Codex and OpenCode Go providers.

    integrator

    The four adapters stay regular dependencies of integration.cli-contractspec-builder, so installs are unchanged. They load through literal dynamic imports: harness eval loads the harness runtime, control-plane commands load the channel runtime, and Builder production commands, preflight and doctor load both providers; settings resolution loads the Codex provider only to default the model of a quality gate that names none. An adapter package that cannot be resolved fails the command with BuilderAdapterUnavailableError (code builderAdapterUnavailable) naming the package and the command. The mapping matches only the unresolved specifier (Bun's specifier field, or the quoted name at the start of the Node message) against the package or one of its subpaths, so a missing dependency of an installed adapter, a package that merely shares the name prefix, and every other load error propagate unchanged. ./commands/builder/production/provider keeps createCodexOpenCodeProviderPort synchronous with the 3.0.4 contract: that entry imports both providers, so a fresh port serves every method, including createCompletionReceipt. The new ./commands/builder/production/provider-port entry adds loadCodexOpenCodeProviderPort, which the Builder commands use, and createCodexOpenCodeProviderPortWithAdapters for callers that already hold the adapters. resolveOpenCodeCliModel is exported from ./commands/builder/production/preflight. The cli-runtime adoption catalog-loader entry keeps exactly DEFAULT_ADOPTION_CATALOG_URL and loadAdoptionCatalog.

    maintainer

    src/lazy-adapters.ts in the Builder pack owns the four literal adapter imports and the typed resolution error. lazy-adapters.test.ts walks the static module graph of command-pack, index and register across workspace sources and fails if it reaches harness-runtime, integration.runtime, provider-codex, provider-opencode-go, contractspec-catalog, contracts-runtime-server-mcp or logger; it fails on the previous code. builder/production/provider-port.ts owns the provider port without importing either provider; provider.ts is the only module that imports them statically, and nothing in the pack imports it. cli-runtime catalog-loader.ts delegates to catalog-loader-candidates, -selection, -legacy and -overrides, none of which is a package export. The published-consumer manifest closure is unchanged by design (86 raw packages, 70 ledger units for the current case), so the B045 exit condition is not met and the budget exception stays with its owner review. The emitted declarations still reference the four adapter packages through typeof import aliases; moving them to optional dependencies would also need those types decoupled.

  • cmp-fix-w8-realtime-reconnect-isolation

    Isolate WebSocket callback failures and retain reconnect resync through temporary unsubscription

    integrator

    Synchronous throws and asynchronous rejections from onStatus, onConnectionError and invalidation handlers reach onHandlerError without interrupting transitions, handshake completion, subscription flushing, resync or lifecycle timers. A throwing or rejecting error reporter is surfaced asynchronously. Node and Bun hosts continue supplying a reliable onHandlerError because uncaught errors may terminate their process. A temporarily empty subscription set retains lost-session resync debt until the actual idle close or replacement invalidation, including reconnect timers, offline recovery and asynchronous replacement handshakes. The callback signatures, contractspec.realtime.v1 frames and configured budgets are unchanged. No host activation or server protocol adoption is implied.

  • cmp-realtime-transport-client

    Transport.subscribe gets WebSocket delivery with bounded reconnect and backpressure, a React subscription hook, and ContractDataEngineProvider can build its engine from transport, mode and offline props

    integrator

    createWebSocketTransport({ transport, url }) from @lssm-tech/lib.contracts-runtime-core returns a canonical Transport. execute stays on the supplied request transport (REST, MCP, in-memory), and subscribe(tags, handler) runs over one shared WebSocket that speaks the contractspec.realtime.v1 subprotocol: the client sends init (from connectionParams, never the URL), subscribe and unsubscribe frames, and the server pushes invalidate {tags, versionToken?}. connectionParams may be async; no subscribe frame is written before init, and the status reads open only after it. A throw, a rejection, an unencodable result or a promise still pending after handshakeTimeoutMs (default 10000, RealtimeHandshakeTimeoutError) closes the socket with code 4000 (REALTIME_CLOSE_HANDSHAKE_FAILED), retries within the reconnect budget and reports to onConnectionError. A host callback that throws once an async connectionParams settles goes to onHandlerError instead of becoming an unhandled rejection. A server adopting contractspec.realtime.v1 must authenticate init before any subscribe, authorise every subscribe's tags for that principal and tenant (deny by default) and push only tags that connection may see, because tags carry no tenant. Reconnects back off exponentially with jitter and stop after reconnect.maxAttempts (default 6) until a connection stays open for stableAfterMs. The status then becomes failed until reconnect() or a reachability recovery, and offline periods do not spend attempts. A pending reconnect or reachability recovery that finds no subscription settles the status to idle, so a later subscription always gets a socket. A reconnect after a lost connection resends every subscription and delivers each one its own tags; a connection opened after an idle close does not resync. Outbound writes pause while bufferedAmount exceeds maxBufferedBytes. Inbound pushes are merged per coalesceWindowMs and coarsen to entity tags, then to a full refresh, past maxPendingTags; a broadened batch carries no versionToken. Hosts running on Node or Bun pass onHandlerError, because the default asynchronous rethrow can end the process. In @lssm-tech/lib.contracts-runtime-client-react, ContractDataEngineProvider also accepts transport with optional mode and offline props and builds the engine itself. Without mode, offline.storage selects offline-capable, otherwise online-only. offline is passed as the engine's advanced options, with offline.storage and offline.cacheStore forwarded only in offline-capable mode, so one offline object works while mode toggles. The engine is rebuilt only when transport, the resolved mode, the forwarded offline.storage or offline.reachability changes. The explicit engine prop keeps working and can take an optional transport for subscriptions. useContractSubscription(tags, options) subscribes through the provider transport, marks the pushed tags' cached reads stale, runs the engine's maintenance.revalidateStale() pass, which refetches every stale entry, sends a failed invalidation or revalidation to onError, and reports { supported, active, lastEvent, eventCount }. It is also exported from ./subscriptions/use-contract-subscription.

    maintainer

    ContractDataEngineProviderProps is now a union of ContractDataEngineExplicitProps and ContractDataEngineBuildProps. Every existing <ContractDataEngineProvider engine={...}> call still typechecks; only an interface that extends ContractDataEngineProviderProps would need to extend one branch instead, and no workspace package does. The provider forwards the host reachability source through a gate that is active only while it is mounted, so engines created during discarded renders or replaced by a mode toggle stop draining the offline queue. The realtime worker (worker-data-transmission-realtime) still speaks its own room protocol; serving contractspec.realtime.v1 there is a follow-up. All realtime tests use a fake socket and a manual scheduler; no network is opened.

  • communication-os-tenant-erasure-definer

    CommunicationOS tenant erasure runs only through a SECURITY DEFINER function; the app role loses the erasure flag and personal-device DELETE

    integrator

    Tenant erasure now needs a connection role that is a member of communication_os_tenant_erasure_caller. The migration grants it to the migrating role; a host that separates its API login from its erasure worker login should grant the caller role only to the erasure login. communication_os_app can no longer delete support notes or personal device records, and setting communication_os.tenant_erasure has no effect.

    maintainer

    A migration that adds a communication_os table with tenant_id must append communicationOsTenantErasureAccess(table); otherwise erase_tenant refuses with TENANT_ERASURE_CATALOG_INVALID instead of silently skipping the table.

  • compat-docblock-owner-leaves

    The contracts-spec facade barrels hold no DocBlock arrays; the workspace-config DocBlock moves to its contracts-runtime-core owner and four facade DocBlocks move to private leaves, with names, ids, routes and bodies unchanged.

    integrator

    @lssm-tech/lib.contracts-runtime-core/workspace-config/contractsrc-schema additionally exports tech_workspace_config_DocBlocks; @lssm-tech/lib.contracts-spec/workspace-config forwards that same value, and the facade subpath @lssm-tech/lib.contracts-spec/workspace-config/contractsrc-schema (an export * forwarder to that runtime-core module) gains the same additive export. The facade keeps every existing export name, and every DocBlock id, route and body is unchanged.

    maintainer

    contracts-spec-compat src/workspace-config/index.ts, src/examples/index.ts, src/rich-reference/index.ts and src/features/types.ts are pure forwarders in the facade source audit. The remaining facade-owned DocBlocks live in src/docs/private/*-docs.ts. The packed forward-chain allowlist drops the workspace-config entry, which is now owner-forwarded. Against a manifest regenerated from release sources, only sourceModule changes, for the five moved blocks. This change does not commit the generated surface-runtime manifest: the one on release is stale, and a regeneration also carries release drift (4 new DocBlocks, 4 body updates from other packages), so the integration regenerates it once with docs:manifest instead of merging it by hand.

  • connect-hook-run-modes

    Host-aware Connect hook run modes so bypass and auto agent sessions stop prompting on every governed action.

    integrator

    Host hooks read the agent host permission_mode. Claude Code bypassPermissions and dontAsk sessions run autonomous and are no longer asked for governed contracts-spec/LSSM edits and shell commands; critical (destructive or immutable) actions are denied with a reason, and Connect policy deny/rewrite still block. default sessions keep asking. .contractsrc.json connect.runModes tunes the defaults, host mapping, maxLevel, and extra high-criticality paths.

    maintainer

    Operators grant bounded autonomy with contractspec connect mode set <level> --for 8h [--scope <paths>], inspect it with connect mode show, and remove it with connect mode clear. Agent writes to .claude/settings*.json, .codex/hooks.json, .cursor/hooks.json, the grant file, and agent-run connect mode set|clear are operator-only. Decisions made without asking are appended to .contractspec/connect/run-mode-decisions.ndjson.

  • consumer-canonical-harness-dataview

    Use canonical Harness registries and Core DataView types in existing consumers.

    maintainer

    Preserve nominal registries and full web/native DataView contracts while removing the Builder command pack's direct compatibility-facade dependency.

  • d117-ds-01

    Family base design packs, brand packs as family patches and composition design-pack selection in design-catalog.

    maintainer

    lssmBrandDesignPackRegistry.list() grows from 3 to 10 because it now also holds the seven family bases; get() is unchanged. The 30 built-ins, the 960/480 visual matrix and the Storybook hash are unchanged.

  • designcatalog-rich-field-form-fixture

    Canonical rich-field form fixture ownership in DesignCatalog

    integrator

    Existing rich-field showcase consumers retain one canonical model and form singleton.

  • examples-validate-catalog-alignment

    examples validate checks the formatted generated catalog and skips catalog rules for private examples.

    maintainer

    contractspec examples validate no longer reports every cataloged example as missing from the formatted builtins.ts, and no longer asks private example packages for ./example, ./docs or an EXAMPLE_REGISTRY entry that the generator never produces for them. DocBlock rules still apply to private packages. A ./docs export may point at any DocBlock owner module; the validator checks that its target exists instead of requiring src/docs/index.ts.

  • fo2-s09-personal-device-persistence

    Personal device pairing, heartbeat and revocation state persist as tenant-isolated CommunicationOS connection records

    integrator

    Run the CommunicationOS migration ledger to 0014, then bind createPostgresCommunicationPersonalDeviceStore (with a tenant-scoped provider) as the PersonalDeviceRegistry store.

  • fo2-s12-design-authority

    Measured design contrast, SSR-safe design hydration, and preference-versus-authority guards for founder surfaces

    integrator

    Design selection can be hydrated on the server without a colour-mode dependent flash, built-in themes now pass measured WCAG contrast for text and focus pairs, RoleMorph presentation preferences cannot widen server authority, and private projection caches purge on authority changes. Built-in dark focusRing values, two Creator secondary-foreground values and the Editorial light ring change.

  • fo2-s12-ui-defect-repro

    Reproduced founder UI defects fixed - Editorial dark primary contrast, native shell translations, scoped preference replacement and StrictMode-safe accessibility preferences

    integrator

    The Editorial dark primary colour changes slightly to meet WCAG AA as text, native shell chrome follows the active locale, preference stores gain a scope-safe replace, and accessibility preference events fire once per change under StrictMode.

  • hirly-consumer-closure-hygiene

    Narrow published runtime dependencies so consumers install fewer LSSM packages.

    integrator

    The Builder command pack installs only the Codex and OpenCode Go providers it uses instead of the whole provider collection; exports and behavior are unchanged.

    maintainer

    Test-only workspace dependencies are devDependencies and unused ones are removed; published declarations do not reference them.

  • release-capsule-known-gaps

    Release capsules accept an optional knownGaps list that release builds copy and render.

    maintainer

    Record open limitations of a release in knownGaps instead of a quarantine sidecar. release check no longer flags the key, and patch notes list the gaps.

    integrator

    ReleaseCapsule and GeneratedReleaseManifestEntry carry an optional knownGaps string list. The change is additive; code that reads capsules or manifests can ignore it.

  • runtime-core-portable-primitives

    Direct portable primitive adoption with unchanged runtime defaults and exports

    integrator

    Existing execution, Forms and observability imports retain behavior while primitive references resolve to the canonical Core owner.

  • runtimecore-complete-host-model-current

    Preserve the complete existing host/configuration model families at RuntimeCore with precise original Legacy forwarding types and implementations.

    integrator

    Complete original model bodies, schemas, defaults and Legacy forwarding identity are retained.

  • stt-gateway-rounded-duration

    Gateway transcription no longer rejects results whose reported duration is rounded below the last segment end

    maintainer

    gateway-stt-mapping.ts allows DURATION_ROUNDING_TOLERANCE_MS (1000 ms) between the reported duration and the last segment end and returns the longer value as durationMs. Found by the first real call to microsoft/mai-transcribe-2 (durationInSeconds 15.3, last segment end 15.305 s).

  • stt-gateway-webm-ogg-remux

    Gateway transcription remuxes browser WebM/Opus recordings to Ogg/Opus, which Azure MAI accepts

    maintainer

    gatewaySttWireMedia (gateway-stt-request.ts) converts audio/webm with remuxWebmOpusToOgg (webm-opus-demux.ts, matroska-block.ts, ogg-page.ts, webm-ogg-opus.ts): an EBML demuxer that tolerates unknown-size Segment/Cluster elements and a truncated tail, supports Xiph, fixed and EBML lacing, and an RFC 7845 Ogg writer whose granule positions count 48 kHz samples from each Opus TOC byte. Other media types are forwarded unchanged. Callers that classify errors should treat STT_MEDIA_REMUX_FAILED as terminal.

  • translation-adapter-export-workflow

    Preserve Translation compatibility exports through canonical prebuild.

    maintainer

    Prebuild retains all 17 public paths while compiling the four adapter implementation files without exposing new paths.

  • translation-runtime-catalog-models

    Canonical translation catalog model ownership in TranslationRuntime

    integrator

    Existing translation catalog consumers retain all six original declarations.

  • w4-themes-designpack-owner

    Move complete theme and design-pack families and the pure visual-scenario model to DesignCatalog.

    integrator

    Adopt canonical reusable design definitions without a legacy return dependency.

  • web-01-ds

    LSSM atlas, Tellshift and Patio brand packs and brand font manifests in lib.design-catalog (WEB-01-DS, D-100, D-103).

    maintainer

    Hosts can select contractspec.design.lssm-atlas, contractspec.design.tellshift and contractspec.design.patio from LSSM_BRAND_CATALOG_DATA; the 30 generic built-ins, their visual matrix and the Storybook manifest are unchanged.

Migration guide

  • Recreate local databases that applied the earlier 0016

    0016_tellshift_sequences_rls was rewritten before release and its digest changed. A local or disposable database that applied the earlier 0016 fails with communication_os_migration_digest_mismatch and must be recreated; no deployed database carries it.

    When: When a development database applied 0016_tellshift_sequences_rls before this change.

  • Apply CommunicationOS migrations 0013 and 0014

    Required

    Additive table plus RLS; deploy schema before enabling device pairing.

    1. Run migrateCommunicationOsSchema; environments that manage roles out of band skip 0014 with applyRls false and apply equivalent policies.
  • Optionally adopt SSR-safe design hydration

    Additive. Server-rendered web hosts that already pass designHydration may set cssVariablesStrategy="stylesheet" on DesignSystemThemeProvider instead of gating applyCssVariables on mount.

    1. Pass cssVariablesStrategy="stylesheet" to DesignSystemThemeProvider and drop the mounted gate on applyCssVariables.
    2. Keep the next-themes (or equivalent) dark class on an ancestor element.
  • Optionally bind design selection to the rendered scope

    Additive. Pass scope { tenantId, userId, appId } to resolveDesignSelection so a stale private selection from another workspace or account is ignored.

    1. Pass the request tenant, user and app as scope when resolving design selection.
  • Replace preference dimensions on identity or workspace change

    Additive. Hosts that hydrate a shared PreferenceDimensionsStore per workspace should call replace(snapshot) when the tenant, workspace or user changes and keep hydrate(snapshot) for refreshes within the same scope.

    1. Track the tenant/workspace/user key in the personalization provider and call replace when it changes.
  • Regenerate configured targets

    Regenerate so Claude agents, model-config rules, and OpenCode agent settings reflect the new precedence and scoping. Review pack validate warnings and either add globs or an explicit claudecode.paths to each flagged rule.

    1. Run bun run agentpacks:validate and resolve or accept each unscoped-rule warning.
    2. Run bun packages/tools/agentpacks/src/index.ts generate.
    3. Run bun run agentpacks:diff and confirm no changes remain.
  • Optionally call the new owner subpaths

    Additive; existing imports keep working. Hosts may compose the owner subpaths instead of application-local copies.

    1. Import the behavior from the owner subpath listed in the changeset instead of an app-local copy.
  • Review callers of the in-memory design authoring store

    InMemoryDesignAuthoringStore now lists drafts newest first, rejects updates whose tenant, app or owner differ from the stored draft, uses the message Design draft revision conflict, and returns false for a stale deleteDraft instead of throwing, matching the SQL adapter.

    1. If a test expected deleteDraft to throw on a stale revision, assert a false result instead.
  • Regenerate configured targets

    Regenerate so existing outputs move the generated header after frontmatter and Claude rules receive path scopes. Add globs to canonical rules that only apply to specific paths.

    1. Run bun run agentpacks:validate.
    2. Run bun packages/tools/agentpacks/src/index.ts generate.
    3. Run bun run agentpacks:diff and confirm no changes remain.
  • Build the canonical AI integration

    Existing consumers require no registration migration; producer ownership follows the relocated implementations.

    1. Build the AI integration to refresh its owning static offline MCP knowledge corpus.
    2. Use the existing transpilation workflow to retain canonical module identity across command-pack and compatibility subpaths.
  • Use DesignCatalog themes and design-packs entries with their exact leaves

    Use DesignCatalog themes and design-packs entries with their exact leaves.

    1. Use DesignCatalog themes and design-packs entries with their exact leaves.
  • Use DesignCatalog visual-scenario-spec for the pure visual-case model

    Use DesignCatalog visual-scenario-spec for the pure visual-case model.

    1. Use DesignCatalog visual-scenario-spec for the pure visual-case model.
  • Legacy imports remain supported with original defaults and nominal registry identities

    Legacy imports remain supported with original defaults and nominal registry identities.

    1. Legacy imports remain supported with original defaults and nominal registry identities.
  • Regenerate from canonical pack sources

    Regenerate configured targets to include supporting skill files and refreshed guidance. Gemini now emits .gemini/skills. Replace symlink or non-regular resources with contained regular files.

    1. Run bun run agentpacks:validate.
    2. Run bun packages/tools/agentpacks/src/index.ts generate.
    3. Run bun run agentpacks:diff and verify skill discovery in the selected host.
  • Add byte and permission support to custom adapters

    Adapters generating resource-bearing skills implement optional readBytes, writeBytes with mode, and statMode operations. Missing capabilities fail before mutation; single-file skills retain the text-only path.

Upgrade steps

  • Review built-in token contrast fixes before regenerating baselines

    manual

    Built-in dark focusRing values, Creator Arcade and Creator Signal light secondaryForeground and the Editorial light ring changed to reach measured WCAG contrast.

    Packages: @lssm-tech/lib.design-catalog, @lssm-tech/lib.design-system, @lssm-tech/lib.personalization, @lssm-tech/lib.surface-runtime, @lssm-tech/lib.accessibility

    1. Review the changed packages/platform/ui/design-catalog/css values against the source palettes.
    2. Regenerate screenshot baselines only after the reviewed change is accepted.
  • Review the Editorial dark primary change before regenerating baselines

    manual

    Editorial dark primary moved from #c46c43 to #c57049 (HSL 19 52% 53%); copies outside the design catalog should follow.

    Packages: @lssm-tech/lib.design-catalog, @lssm-tech/lib.design-system, @lssm-tech/lib.personalization, @lssm-tech/lib.accessibility

    1. Update host stylesheets or docs that copied the Editorial dark primary value.
    2. Regenerate screenshot baselines only after reviewing the change.
  • Review run-mode defaults for your hosts

    manual

    Sessions in bypass or auto permission modes now proceed on governed actions without an operator prompt; cap them if your workspace requires supervision.

    Packages: @lssm-tech/lib.contracts-runtime-core, @lssm-tech/lib.cli-runtime, @lssm-tech/bundle.workspace, @lssm-tech/app.cli-contractspec

    1. Set connect.runModes.maxLevel to supervised or connect.durableAuthorityRequired to true to keep every governed action supervised.
    2. Run contractspec connect mode show to inspect the effective mapping and any grant.

Unique release changes

  • Additive; existing imports keep working. Hosts may compose the owner subpaths instead of application-local copies.

    7 packages · 7 occurrences

  • InMemoryDesignAuthoringStore now lists drafts newest first, rejects updates whose tenant, app or owner differ from the stored draft, uses the message Design draft revision conflict, and returns false for a stale deleteDraft instead of throwing, matching the SQL adapter.

    7 packages · 7 occurrences

  • Work, privacy, Builder candidate, design authoring, booking, membership and Resend ledger behavior moves from apps to owner packages

    7 packages · 7 occurrences

  • Narrow published runtime dependencies so consumers install fewer LSSM packages.

    6 packages · 6 occurrences

  • Additive. Pass scope { tenantId, userId, appId } to resolveDesignSelection so a stale private selection from another workspace or account is ignored.

    5 packages · 5 occurrences

  • Additive. Server-rendered web hosts that already pass designHydration may set cssVariablesStrategy="stylesheet" on DesignSystemThemeProvider instead of gating applyCssVariables on mount.

    5 packages · 5 occurrences

  • Built-in dark focusRing values, Creator Arcade and Creator Signal light secondaryForeground and the Editorial light ring changed to reach measured WCAG contrast.

    5 packages · 5 occurrences

  • Measured design contrast, SSR-safe design hydration, and preference-versus-authority guards for founder surfaces

    5 packages · 5 occurrences

  • Additive. Hosts that hydrate a shared PreferenceDimensionsStore per workspace should call replace(snapshot) when the tenant, workspace or user changes and keep hydrate(snapshot) for refreshes within the same scope.

    4 packages · 4 occurrences

  • Complete canonical test contract and reference fixture ownership

    4 packages · 4 occurrences

  • Editorial dark primary moved from #c46c43 to #c57049 (HSL 19 52% 53%); copies outside the design catalog should follow.

    4 packages · 4 occurrences

  • Existing consumers require no registration migration; producer ownership follows the relocated implementations.

    4 packages · 4 occurrences

  • Host-aware Connect hook run modes so bypass and auto agent sessions stop prompting on every governed action.

    4 packages · 4 occurrences

  • Move canonical AI commands and reusable authoring runtimes to their approved owners while preserving public registration.

    4 packages · 4 occurrences

  • Reproduced founder UI defects fixed - Editorial dark primary contrast, native shell translations, scoped preference replacement and StrictMode-safe accessibility preferences

    4 packages · 4 occurrences

  • Sessions in bypass or auto permission modes now proceed on governed actions without an operator prompt; cap them if your workspace requires supervision.

    4 packages · 4 occurrences

  • Adapters generating resource-bearing skills implement optional readBytes, writeBytes with mode, and statMode operations. Missing capabilities fail before mutation; single-file skills retain the text-only path.

    3 packages · 3 occurrences

  • Canonical owners for visual scenario and visualization registries

    3 packages · 3 occurrences

  • Give Builder CLI adapters their canonical integration owner while preserving existing Commander behavior.

    3 packages · 3 occurrences

  • Preserve complete skill bundles across agentpacks targets and rebuild repository guidance around current ContractSpec workflows.

    3 packages · 3 occurrences

  • Regenerate configured targets to include supporting skill files and refreshed guidance. Gemini now emits .gemini/skills. Replace symlink or non-regular resources with contained regular files.

    3 packages · 3 occurrences

  • Canonical rich-field form fixture ownership in DesignCatalog

    2 packages · 2 occurrences

  • Canonical translation catalog model ownership in TranslationRuntime

    2 packages · 2 occurrences

  • Legacy imports remain supported with original defaults and nominal registry identities.

    2 packages · 2 occurrences

  • Move complete theme and design-pack families and the pure visual-scenario model to DesignCatalog.

    2 packages · 2 occurrences

  • Preserve the complete existing host/configuration model families at RuntimeCore with precise original Legacy forwarding types and implementations.

    2 packages · 2 occurrences

  • Preserve translation factory identity through canonical TranslationRuntime ownership

    2 packages · 2 occurrences

  • Release capsules accept an optional knownGaps list that release builds copy and render.

    2 packages · 2 occurrences

  • The Builder command pack loads its harness, channel and provider adapters only inside the command actions that run them, and the cli-runtime adoption catalog loader splits into private leaves

    2 packages · 2 occurrences

  • The contracts-spec facade barrels hold no DocBlock arrays; the workspace-config DocBlock moves to its contracts-runtime-core owner and four facade DocBlocks move to private leaves, with names, ids, routes and bodies unchanged.

    2 packages · 2 occurrences

  • Transport.subscribe gets WebSocket delivery with bounded reconnect and backpressure, a React subscription hook, and ContractDataEngineProvider can build its engine from transport, mode and offline props

    2 packages · 2 occurrences

  • Use canonical Harness registries and Core DataView types in existing consumers.

    2 packages · 2 occurrences

  • Use DesignCatalog themes and design-packs entries with their exact leaves.

    2 packages · 2 occurrences

  • Use DesignCatalog visual-scenario-spec for the pure visual-case model.

    2 packages · 2 occurrences

  • 0016_tellshift_sequences_rls was rewritten before release and its digest changed. A local or disposable database that applied the earlier 0016 fails with communication_os_migration_digest_mismatch and must be recreated; no deployed database carries it.

    1 package · 1 occurrence

  • Additive table plus RLS; deploy schema before enabling device pairing.

    1 package · 1 occurrence

  • Agentpacks applies pack-owned canonical RTK sections after generation instead of the installed rtk init templates.

    1 package · 1 occurrence

  • Claude Code agents keep an explicit claudecode.model, model guidance loads only for model configuration files, Fable and Mythos IDs are recognised, and pack validate flags rules Claude would always load.

    1 package · 1 occurrence

  • CommunicationOS tenant erasure runs only through a SECURITY DEFINER function; the app role loses the erasure flag and personal-device DELETE

    1 package · 1 occurrence

  • Direct portable primitive adoption with unchanged runtime defaults and exports

    1 package · 1 occurrence

  • examples validate checks the formatted generated catalog and skips catalog rules for private examples.

    1 package · 1 occurrence

  • Family base design packs, brand packs as family patches and composition design-pack selection in design-catalog.

    1 package · 1 occurrence

  • Gateway transcription no longer rejects results whose reported duration is rounded below the last segment end

    1 package · 1 occurrence

  • Gateway transcription remuxes browser WebM/Opus recordings to Ogg/Opus, which Azure MAI accepts

    1 package · 1 occurrence

  • Isolate WebSocket callback failures and retain reconnect resync through temporary unsubscription

    1 package · 1 occurrence

  • Keep YAML frontmatter on the first line of generated markdown, give Claude Code agents and commands their metadata, and scope Claude Code rules with paths from rule globs.

    1 package · 1 occurrence

  • LSSM atlas, Tellshift and Patio brand packs and brand font manifests in lib.design-catalog (WEB-01-DS, D-100, D-103).

    1 package · 1 occurrence

  • Personal device pairing, heartbeat and revocation state persist as tenant-isolated CommunicationOS connection records

    1 package · 1 occurrence

  • Preserve Translation compatibility exports through canonical prebuild.

    1 package · 1 occurrence

  • Regenerate so Claude agents, model-config rules, and OpenCode agent settings reflect the new precedence and scoping. Review pack validate warnings and either add globs or an explicit claudecode.paths to each flagged rule.

    1 package · 1 occurrence

  • Regenerate so existing outputs move the generated header after frontmatter and Claude rules receive path scopes. Add globs to canonical rules that only apply to specific paths.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/agentpack.contractspec

    Layer: tools · 3 changes

  • @lssm-tech/agentpacks

    Layer: tools · 3 changes

  • @lssm-tech/app.cli-contractspec

    Layer: apps · 2 changes

  • @lssm-tech/bundle.library

    Layer: bundles · 2 changes

  • @lssm-tech/bundle.workspace

    Layer: bundles · 3 changes

  • @lssm-tech/integration.agent-durable-store

    Layer: integrations · 1 change

  • @lssm-tech/integration.cli-contractspec-ai

    Layer: integrations · 2 changes

  • @lssm-tech/integration.cli-contractspec-builder

    Layer: integrations · 1 change

  • @lssm-tech/integration.cli-contractspec-examples

    Layer: integrations · 1 change

  • @lssm-tech/integration.communication-os-persistence

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-email

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-voice

    Layer: integrations · 1 change

  • @lssm-tech/integration.providers-impls

    Layer: integrations · 1 change

  • @lssm-tech/integration.runtime

    Layer: integrations · 1 change

  • @lssm-tech/lib.accessibility

    Layer: libs · 3 changes

  • @lssm-tech/lib.cli-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-runtime-client-react

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-runtime-core

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-runtime-server-mcp

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 4 changes

  • @lssm-tech/lib.data-exchange-core

    Layer: libs · 3 changes

  • @lssm-tech/lib.design-catalog

    Layer: libs · 4 changes

  • @lssm-tech/lib.design-system

    Layer: libs · 1 change

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

    Layer: libs · 1 change

  • @lssm-tech/lib.observability

    Layer: libs · 1 change

  • @lssm-tech/lib.personalization

    Layer: libs · 3 changes

  • @lssm-tech/lib.surface-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.translation-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.work-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.workflow-composer

    Layer: libs · 1 change

  • @lssm-tech/module.design-studio

    Layer: modules · 3 changes

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

    Layer: modules · 3 changes

  • @lssm-tech/opa-booking-react

    Layer: libs · 3 changes