Release summaries
cmp-fix-w9-adaptive-authority-binding
Bind asynchronous authority verification and writing to the same isolated intent.
integrator
Authority requests, nested origins and payloads are captured before the first asynchronous digester or verifier call. The writer receives isolated frozen data with the approved tenant, target, actor, decision and payload; mutating the caller's object cannot redirect authority. Existing caller payload drift refusal remains. Plain data, arrays, Date values and JSON key order are preserved without requiring structuredClone or Node-only facilities.
cmp-personalization-platform
Data-view interaction tracking records selection count/scope and invoked actions, and usePersonalizedVariants resolves cockpit-kit variants through the schema bridge and role overrides
integrator
BehaviorTracker.trackDataViewInteraction accepts and records selectedCount and selectionScope for selection_changed, and actionKey, actionPlacement and actionIntent for action_invoked, so renderer interactions forwarded from useAdaptiveDataView keep their selection and action evidence. Only declared fields are copied; never pass row ids. usePersonalizedVariants(componentKey) now returns resolved { density, expansion } variants instead of an empty record: cockpit components that spread its result render the personalized variants. Pass the optional roleVariants prop to PersonalizedSurfaceProvider to override variants per role, surface-wide or per component key.
maintainer
TrackDataViewInteractionInput extends the presentation-runtime-core DataViewSelectionInteractionFields and DataViewActionInteractionFields instead of redeclaring them. personalized-presentation owns mapPreferencesToVariants in the schema bridge and resolvePersonalizedVariants in the new ./variant-resolution entry; the hook has no unchecked cast. The NavRail proof (2 roles x 2 preference profiles) and the cockpit example proof (CockpitFrame + NavRail + MetricPanel under 3 role profiles) compare personalized markup with directly rendered markup and keep bun snapshots under src/__tests__/__snapshots__. The package gains @lssm-tech/lib.cockpit-kit-web and react-dom as devDependencies for those proofs. README and AGENTS guidance in both packages describe the new fields and the resolution order.
commos-behavior-signals
CommunicationOS emits inbox_viewed, thread_opened and handoff_accepted behavior signals from web and native, registered with a privacy classification and stitched by tenant_ref.
integrator
Additive. BEHAVIOR_SIGNAL_EVENTS gains the
communication-oscategory with inbox_viewed and thread_opened (non-decision, 0.25 sampling, operational retention) and handoff_accepted (decision, 1.0 sampling, regulatory retention). Import the keys from COMMUNICATION_OS_BEHAVIOR_SIGNAL_KEYS. Payload fields are pseudonymized ids or theplatformenum only. CompanyOsBehaviorSignal accepts the three keys, and the guarded recorder emits them with the hashed tenant_ref. Code that switches exhaustively over BehaviorSignalCategory or CompanyOsBehaviorSignal must handle the new members.maintainer
Mobile emits inbox_viewed from (persona)/inbox.tsx and thread_opened from threads/[id].tsx. It does not emit handoff_accepted: its handoff list is demo data with no confirmed transition, and a mobile guardrail test fails if native source names the decision signal before one exists. Web emits inbox_viewed and thread_opened from renderCommunicationOsScreen, and handoff_accepted only after the API confirms an approved handoff transition (reportConfirmedHandoffAcceptance observing withConfirmedWorkTransitions in the live room controller). The module controller's action wrapper resolves even on failure, so the signal is never wired to the click. PRIVACY_SIGNALS.md lists the call sites. The new source export ./ui/agents/CommsAiPanel.native is workspace-only for the in-repo Expo app and is intentionally absent from publishConfig.exports until the bundle has a native build lane. The bundle declares it with a reason in contractspec.workspaceOnlyExports, the explicit allowlist (scripts/workspace-only-exports.mjs) that entrypoint-rollout.mjs excludes from key parity and entry selection and that audit-publish-tarballs.mjs rejects if the key is also published. The adoption catalog already describes publishConfig.exports, so the subpath never enters it.