Release summaries
adaptive-dataview-command-center
Add adaptive DataView management-shell contracts and command-center proof metadata.
maintainer
DataView specs can now declare management-shell header, toolbar, selection, row-card, detail-panel, pagination, action placement/boundary, field-role, personalization, and RoleMorph references.
integrator
Host applications receive additive metadata for command-center DataView layouts while retaining ownership of CRUD side effects, modal state, validation, and destructive confirmations.
adaptive-dataview-management-contract
Add optional DataView management-shell metadata for adaptive command-center layouts.
maintainer
DataView contracts now include additive management-shell metadata for semantic field roles, action placement, toolbar/header/selection/detail-panel, and adaptive binding hints.
integrator
Integrators can describe command-center layouts and action boundaries in metadata while keeping application behavior host-owned.
adoption-aware-release-pipeline
Adoption-aware release pipeline with accumulating release index, per-version detail files, CLI changelog list/view commands, and web changelog version pages.
maintainer
Release build now syncs adoption catalogs, writes pending upgrades, and produces an accumulating release index with per-version detail files. CLI changelog commands (list/view) consume the generated index.
integrator
The `after-release-build` adoption hook is available in CI and local builds. Adoption catalog entries are now enriched from release index data.
customer
Web changelog now supports per-version detail pages with package breakdown, migration instructions, upgrade steps, and deprecation notices.
agentic-communication-command-inbox
Add fail-closed agentic interaction and CommunicationOS command-inbox release evidence across contracts, runtime, module, examples, and agent-facing docs.
maintainer
Maintainers get a validation matrix for the subpath-only AIP safety surface, command-inbox runtime projection, module facade, focused CommunicationOS proof, and Operating Cockpit CompanyOS bridge proof.
integrator
Integrators can adopt message-originated command evidence without granting send, credential, shell, or high-impact CompanyOS execution authority.
agent
Agents must treat command-inbox items as non-executing evidence and keep blocked signals fail-closed until an external approval path acts.
contracts-spec-loop-d-operation-aliases
Loop D D4 — `@lssm-tech/lib.contracts-spec` now supports `meta.aliases?: readonly string[]` on operations. `OperationSpecRegistry.get()` falls back to alias lookup when the canonical key misses. Future namespace migrations can ship as additive instead of BREAKING.
maintainer
Added `aliases?: readonly string[]` to `OperationSpecMeta`. Overrode `OperationSpecRegistry.get()` to fall back to alias lookup on canonical-key miss. Direct matches retain precedence — aliases never shadow registered operations. 6 new tests in `operations/operation-aliases.test.ts` cover the regression baseline, alias resolution, version filtering, and the precedence rule. Full pre-existing test sweep across 1715 tests is zero-regression.
integrator
To soften a future namespace migration, list the legacy keys in `meta.aliases` on the new contract. Registry lookups by the legacy key will resolve to the new operation, letting downstream consumers migrate at their own pace. No changes required for operations that don't migrate.
contractspec-i18n-runtime
Add a ContractSpec-native production-grade translation runtime and optional i18next adapter.
maintainer
Translation specs now keep stable bundle identity separate from locale variants while the runtime owns formatter-backed ICU resolution, fallback chains, overrides, diagnostics, async loading, SSR snapshots, and optional downstream i18next projection.
integrator
Integrators should use the production translation runtime for server, React, React Native, and CLI resolution, and use the i18next subpath only as a downstream adapter with caller-owned ICU formatting configuration.
customer
Multilingual surfaces can now rely on BCP 47 locale variants, ICU formatting, deterministic SSR snapshots, and safer migration away from locale-suffixed translation bundle keys.
database-mutation-docs-llms
Align database mutation docs, release-capsule guidance, and LLM-facing surfaces around governed domain-command writes.
maintainer
Release authors now have an explicit database mutation checklist covering contract/provider separation, domain-command authority, managed/BYOK posture, and LLM regeneration evidence.
integrator
Contracts-spec docs identify portable governed mutation descriptors while provider-database docs identify the adapter-owned SQL/Drizzle execution boundary.
customer
Database write guidance now emphasizes approved domain-command envelopes, idempotency, audit/replay evidence, and managed/BYOK production posture before adapters execute writes.
pioneer-ai-self-improvement
Add vendor-neutral AI self-improvement contracts and a mock-first Pioneer adapter.
maintainer
Maintainers get a thin AI-improvement evidence/policy envelope, package-owned bridge helpers, Connect evidence, and a targeted Pioneer adapter boundary.
integrator
Integrators can connect AI-improvement routes, evidence, policy decisions, promotion gates, rollback, and Pioneer job receipts without taking a dependency on Pioneer-specific core types.
customer
AI improvement workflows are safer by default because vendor export, auto-apply, and learning are controlled by explicit gates and replay evidence.
rich-code-diff-surfaces
Add governed rich code/diff surfaces with references, redaction, RoleMorph, and personalization support. Historical wave-0 entry; the legacy CodeBlock/DiffBlock/ObjectReferenceHandler surfaces are superseded by the rich-reference foundation (see `rich-reference-breaking-release`).
maintainer
Historical wave-0 introduction of `rich-content`, `CodeBlock`, `DiffBlock`, `surface-runtime/rolemorph`, and `personalization/rich-code-preferences`. Superseded by the rich-reference foundation (this is kept for release-history continuity).
rich-reference-foundation
Canonical RichReference subpath + ReferenceRuntime (split) + canonical serializer + detector + reference.resolve/detail queries + REST/GraphQL/MCP adapter wirings + S-9 agent surface (markdown envelope, agent-export passthrough, MCP tool descriptors, delegated/agent subject modes).
maintainer
Schema-first `defineReferenceKind` API (required `sensitiveFields`), process-global `ReferenceKindRegistry`, HMAC-signed `DenialToken`, four governance ports, six built-in kinds, canonical serializer, server-side detector with idempotent SHA-256 cache, strict-passthrough `toAgentJson`, symmetric markdown envelope. No runtime side-effects on import.
integrator
Import `@lssm-tech/lib.contracts-spec/rich-reference` for the foundation, `@lssm-tech/integration.runtime/rich-reference/{wire-rest,wire-graphql,wire-mcp}` for composition roots, and `@lssm-tech/lib.authos-runtime/subject/{agent,delegated}` for subject modes.