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: inheritnow rendermodel: inheriteven when models.json assigns them a model; agents without an override still render the profile model..claude/rules/model-config.mdgainspathsfrontmatter and Cursormodel-config.mdcswitches toalwaysApply: falsewith globs**/models.jsonandagentpacks.jsonc, so model routing guidance no longer loads in every session.integrator
pack validateprints a warning for a detail rule with no globs, noclaudecode.paths, and CursoralwaysApply: false. Add globs to scope it, or setclaudecode.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.modelor the session model.claudecode.pathsoverrides 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 CodebypassPermissionsanddontAsksessions runautonomousand 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.defaultsessions keep asking..contractsrc.jsonconnect.runModestunes 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 withconnect mode show, and remove it withconnect mode clear. Agent writes to.claude/settings*.json,.codex/hooks.json,.cursor/hooks.json, the grant file, and agent-runconnect mode set|clearare 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.