The second fixed package train was published on October 13, 2026, in
registry workflow run 38341350489
from source commit 9ed1b4b2c1a523e44e7fd35b545b9d3dec7f9f03.
These notes summarize the changes since the beta 1 publication; they do not
describe later same-version local builds or prove deployed provider readiness.
Identity maintenance and recipient previews
Auth adds capability-selective credential maintenance so partial installations need not create optional staff or authorization-code tables just to run cleanup. Trusted origin-scoped password-breach request hints are explicit configuration, not permission to forward arbitrary credentials.
Accounts adds read-only invitation and ownership-transfer recipient inspection, with acceptance still reauthorizing current state. Active-actor checks are reordered before lifecycle transaction locks. API Keys rejects malformed credential time bounds. Mature/partial identity adoption guidance documents the fail-closed boundaries and application-owned persistence choices.
Transactional events and Prisma runtime
Events preserves concrete caller transaction types and validates required consumer readiness. Events Prisma adds admitted-publication draining, bounded cleanup and fenced terminal-failure handling. Prisma Runtime classifies qualified transaction aborts; Devices accepts physical Prisma 7 transaction handles. Exact-runtime fixtures cover identity and outbox compositions, rather than assuming all Prisma errors prove rollback.
Storage, Audit and licensing
The Memory Storage testing provider evaluates conditional writes atomically after asynchronous work, fixing concurrent create/replace fixtures. Audit adds an explicit complete-snapshot row budget; bounded prefix deletion alone is not a bounded-memory guarantee.
Licensing Issuer serializes concurrent source issuance, canonicalizes persisted grant metadata and documents concurrent persistence requirements. Remote activation release joins transactional authorization. Host adapters must still meet the locking and lifecycle contracts.
Tooling and release limits
The fixed version train, internal dependency pins, integration/artifact manifests, Skills metadata and package references are synchronized. Core/Prisma Runtime build ordering and version-sensitive CLI tests are corrected. Compatible dependency refreshes and production-origin discovery accompany the release.
Registry diagnostic hooks and cold-install fixtures help investigate metadata failures; publication success is not a fresh-builder availability check. The beta 2 Audiences archive did not include the confirmation producer exports and schema described in its documentation. That packaging gap requires a new immutable version; do not overwrite beta 2 or deep-import unpublished source. The beta 3 checklist covers the corrected artifacts and subsequent adoption work.
