BYOK SDK 0.30.1 · keys 0.30.1

0.30.1 publication record

Date: 2026-10-24 (UTC).
Status: all nine packages are published on npm latest. The complete registry readback passed.

Changes

0.30.1 is a PATCH release under a one-release exception to the pre-1.0 policy. By that policy it would be a MINOR: it adds public API, gated wire additions and Postgres migration 0028, and it has breaking changes in cloud, client and cloud-do. The owner chose 0.30.x on 2026-10-24 (#872).

• Client: a daemon paired as an E2EE member uses real member keys. byok-agent pair --e2ee enrolls the member (#861). The daemon handles the e2ee.key_package.available notice (#863), seals with the member keyring (#866) and rotates a scope epoch before it seals (#877). The device can rotate its own member KEM key, as an interim step before E5b-2 (#885). The daemon advertises sealed-payload-v1 only while its member is verified and the deployment declares e2ee.member (#654 E2d).
• Cloud and cloud-dataplane (breaking): the Host shreds a sealed scope. Postgres needs migration 0028_e2ee_scope_shred.sql (#857). The three E2EE member writes take a single-use proof requestId of at most 120 characters (#860, #901). TenantStores gets the required member objects (#859).
• Cloud and client: the cloud accepts a sealed terminal or artifact by ciphertextRef and advertises sealed-output-ciphertext-ref. The daemon uploads a sealed output that is larger than the inline frame and sends it by reference (#859, #867, #908).
• Client, protocol, server and cloud: a failed task carries failure.class and failure.resetsAt when the server advertises runtime-failure-class (#869, #894, #900).
• Client: an ordinary Agent offer can select agentMemory: 'read-write-if-admitted' (#833, #880). Claude, Codex, Grok and Hermes send message drafts (#870, #893). The opt-in Claude option agentUserContext: 'excluded' keeps the user's own MCP servers, CLAUDE.md files, rules and auto memory out of an Agent task (#871, #873, #887, #904).
• Client (breaking): the Claude, Codex and Grok adapters now always yield message_draft_delta items on Session.events. The CHANGELOG calls this a type change, but a consumer that rejects unknown event types fails at run time, even when it compiles. Accept or skip these items (#870).
• Client, cloud-do and keys (breaking): the nine official Pi packages are pinned to exactly 1.4.0, and the private OAR source moves to 0.71.0. pi-durable 1.4.0 migrates SQLite stores to schema version 2, so there is no rollback to Pi 1.3.0 past this release (#909).
• Examples: K8 closes the downstream gaps #879, #881, #882, #884 and #886. The Host owns persona projections in external team mode (#898, #903). The Host narrows the outcome offer of new Turns, with at most 16 confirmable actions (#892, #895, #914). Host intents have named handlers, and the owner call failStuckIntent ends a stuck intent (#891, #914). K8 rules import from the I/O-free K4 ./canonical entry (#905), and a vendor contract is checked against the import graph (#888). The changes of #882 and #884 are breaking for a Host that copies K8. Seat ContextPacks read room messages from a Host authority (#899, part of #883). The hosted reference H adds S1 to S8 and stays unreleased (#793).

See the CHANGELOG and the release notes for the full scope and the upgrade notes. The release tracker is #872.

Source and accepted artifacts

• Source commit: 142acbe24e4c7bb453f5bbd29cbfe6c60a7e0670 on main, the merge of #916.
• Push CI: run 40118464326 completed with success.
• Release matrix: run 40118500872, dispatched with release_sha equal to the source. It completed with success: 33 jobs passed and 1 job was skipped as expected.
• Artifact: release-pack-142acbe24e4c7bb453f5bbd29cbfe6c60a7e0670, id 12570192890. Manifest SHA-256: 35920114cc7091d2bf6ebd4008c0c90f0080c46bccd67a04730e77add4450f5a.
• Downstream acceptance (AiphaBee) passed on macOS with the nine CI tarballs from this artifact. Their SHA-256 and SHA-512 values match the manifest.
• After publication, the npm dist.integrity of all nine packages was compared with the SHA-512 values in the manifest. All nine are equal.

npm execution

The account is ancienttwo, with auth-and-writes 2FA. Uploads used npm browser authentication. This local route has no provenance attestation. The dist-tag is latest.

One run uploaded all nine packages. The registry records them from 19:08:59 to 19:12:31 UTC. The run waited for registry propagation, read back all nine packages and created the tag. No package was on the registry before this run, and no upload was repeated. The dry run before it uploaded nothing.

Tag

The annotated tag v0.30.1 points to 142acbe2. The tag object is 3a353111e902a1984335fe42a9b27252474b6868. Its message is v0.30.1, a blank line, then sourceGitSha 142acbe24e4c7bb453f5bbd29cbfe6c60a7e0670. It was created after the readback passed, on 2026-10-24 at 19:13:29 UTC.

Accepted tarballs

Package	Version	SHA-256
@byok-sdk/core	0.30.1	af414ea089617a1e408137597a9837c7a2c6aff1c90ed3d2634a221d6e1d10c0
@byok-sdk/protocol	0.30.1	f0e80e6f611de81333e9b65f44ced2fe08097d6c6f61ee933d025bf1e159d8b0
@byok-sdk/server	0.30.1	ac03038d0dd10ed647626454afca4430ccd5554994d85065a8b2043fa11c424b
@byok-sdk/cloud	0.30.1	588fa1c8a710ca220fa5fde0a4ac5155ab3533842c4b9e9295a0632623b298db
@byok-sdk/client	0.30.1	ea3c3562690a3e2980f362b27178693d5252241f5ee7033424ae9df80ed9d64a
@byok-sdk/cloud-dataplane	0.30.1	21350063ca141578f5b16d747852e22d8be49f4da68bb249bbd30cc581461c5d
@byok-sdk/cloud-do	0.30.1	78128cae022f03c359faeaa743952da082efbcf37210b9d26505114ddfb3aec4
@byok-sdk/ui-runtime	0.30.1	c1eb068d5f943db8a365bb079094a3383195a235f259b22d1f9ed9c51ca064f2
@byok-sdk/keys	0.30.1	26fc3ecae193ffdac7cf8ca35c5ffb929602fc7edb96dd87525a7dca13512d30

Release boundary

AiphaBee accepted this release on macOS only. Windows code relies on the required windows-latest CI. The E2EE member flows were not run on two physical devices (#794), and no browser tests ran (#654 E6). A terminal sent by ciphertextRef that the Host refuses for good reaches the Host as no terminal; the journal replace operation comes in a later release. Live provider runs were not part of this release: real Windows runs of Hermes (#608, #712), the submit_result success rate (#610) and a live Pi provider turn on 1.4.0 (#909). On Windows, Agent memory makes no claim for an OS crash or a power loss (#605). #883 and #793 are only partly done and stay open. The hosted example H is unreleased and has no migrations (#793). npm publication does not deploy a Host.