BYOK SDK 0.30.2 · keys 0.30.2

0.30.2 publication record

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

This record does not say that 0.30.2, or a Host on it, is ready for production. The product loop gate (#977) is evaluated after release, against the published 0.30.2.

Changes

0.30.2 is a PATCH release under a one-release exception to the pre-1.0 policy, as 0.30.1 was. By that policy it would be a MINOR: it adds public API and Postgres migration 0029, and it has breaking changes in client, core, cloud and protocol. The owner chose 0.30.2 instead of 0.31.0 (#978, #977). The envelope wire stays v3.

• Client, core, cloud and protocol (breaking): scope key packages are version 2, the Host takes only version 2 puts, and the deployment declaration gains e2ee.member.kem-epoch. Postgres needs migration 0029_e2ee_member_kem_floor.sql. The daemon advertises sealed-payload-v1 only where the Host declares e2ee.member.kem-epoch, so the Host upgrades first. Migration 0029, and the first 0.30.2 open of a SQLite store, refuse a member chain that already holds a rotate entry (#950, #951, #654 E5b-2).
• Client (breaking): a refused sealed terminal sent by ciphertextRef is replaced by one closed-form terminal (#930). The durable journal is the only daemon mode, and a daemon config with hostedJournal is refused (#941, #924). byok-agent doctor no longer scans for pre-0.27.0 temp directories (#949, #938). The Agent home lease marker is published whole, so an Agent home root needs a filesystem with hard links (#990, #605).
• Client: AgentHomeLeaseCorruptError for a lease marker says how to recover, for example from an empty marker that a crash before 0.30.2 left. The marker is still refused (#1006). agentUserMcpServers for Codex and Grok Agent tasks (#947), ClaudeAdapterOptions.agentSessionPersistence (#946), and HermesAdapter declares Windows after a real Hermes run (#967). The Pi durable lane has a typed start contract and a run failure class (#921), and a Codex record consumer failure on an exit's own record stays runtime_exited (#920). task-runner.ts and create-daemon.ts are split into modules with no change to behavior, exports or published declarations (#964, #969).
• Cloud, cloud-dataplane and server: maintenance prunes the receipts of used device-proof request ids in the new twelfth step proofReceipts. A hosted Postgres Host passes proofReceiptRetention to createByokCloud, or the step reports not-configured (#942).
• Examples (private, not published): the hosted reference Host H adds S9 to S14 (#793), the Worker H Host adds D3, H1, H3 and H4 (#794), and the owner switch between L and H moves forward (#957, #975). Sealed executions and routines advance (#953). The changes of #793 S9, #794 H3 and #975 slice 5b are breaking for a Host that copies the hosted collaboration example.

See the CHANGELOG, the release notes and the Host upgrade checklist for the full scope and the upgrade steps. The CHANGELOG is the authority.

Source and accepted artifacts

• Source commit: b1469e5a236e99736c9a63b75fe845f102f81dc0 on main, the merge of #1006. The release preparation #1002 merged at 57a2e086; #1004 and #1006 merged after it with the owner's approval, and the owner chose to publish from b1469e5a.
• Push CI: run 40321474351 completed with success.
• Release matrix: run 40324830377, dispatched with release_sha equal to the source. It completed with success: 34 jobs passed and 1 job was skipped. An earlier matrix run on 57a2e086 (run 40318961528) was superseded and not used.
• Artifact: release-pack-b1469e5a236e99736c9a63b75fe845f102f81dc0, id 12651196205. Manifest SHA-256: bcdacba174373c3e2e995bda134c00eb415a47bab46077c4319c13700fb6542c.
• After publication, the npm dist.integrity of all nine packages was compared with the SHA-512 values in the manifest. All nine are equal.
• Downstream acceptance (AiphaBee) was not run before publication, by the owner's decision. The AiphaBee paths of #977 (macOS and Windows) and the #978 upgrade run after release, pinned to the published 0.30.2.

npm execution

The account is ancienttwo, with auth-and-writes 2FA. Uploads used npm web authentication, approved once for all nine packages. This local route has no provenance attestation. The dist-tag is latest.

One run uploaded all nine packages, in the plan order cloud-do, core, protocol, client, cloud, keys, cloud-dataplane, server, ui-runtime. The registry records them from 13:24:28 (core) to 13:28:02 (client) 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.

Tag

The annotated tag v0.30.2 points to b1469e5a. The tag object is ea8ba2f8fd035d172cf3c3179ab9160b40d4a7aa. Its message is v0.30.2, a blank line, then sourceGitSha b1469e5a236e99736c9a63b75fe845f102f81dc0. It was created after the readback passed, on 2026-10-26 at 13:29:11 UTC.

Accepted tarballs

Package	Version	SHA-256
@byok-sdk/core	0.30.2	4d81cb07e1636c520bceb66af07f802b89b8cc7d6cc0bf9bcf554014aac6ef35
@byok-sdk/protocol	0.30.2	3524e9177983128cfc86ad25f3c12ff1057527cdc28237806284fe4e99ab5233
@byok-sdk/server	0.30.2	6580e948a72b613f1af02b645474c9e646438eee639d15f8179244d1201989fd
@byok-sdk/cloud	0.30.2	79c2461f133f50bf5bfa554fa21f6aed9d36cb8201eda52da65759bf15028f7d
@byok-sdk/client	0.30.2	f521cf4af4fc24f806f10fad6d18e811434b825cd7f9ec4e9b96ce374f192533
@byok-sdk/cloud-dataplane	0.30.2	62c14009c2a75426a3a691a34f24ee2cb4689bc41e46674455ab72cdaaf3b335
@byok-sdk/cloud-do	0.30.2	bb808d9c568838e6349c07b1d3f4bd58ed476cee5fda52ac3d7a9e9cfbc94c42
@byok-sdk/ui-runtime	0.30.2	f805b3f01bb348dc21d1cfcbc3efb4df87a45d3c744bcf279f8fb81081c936d0
@byok-sdk/keys	0.30.2	7859db18dd2ca0b2ea5ff8609d7706bb25df1395fdaadb02b8c9832bd67435ac

Release boundary

No downstream acceptance ran before publication. The product loop gate (#977) is open: Pi submit_result data against the published 0.30.2, one AiphaBee structured-outcome path on macOS and on Windows pinned to 0.30.2, and the maintainer's gate conclusion. The pre-release Pi measurement (Pi 1.4.0, zai/glm-5.3-flash, 120 trials on ebcb8d96) had 73/120 valid and 63/120 exact results, with no valid result for the oneOf union case or the 64,011-byte case. It is evidence for #977, not the gate result. The #978 acceptance is AiphaBee's upgrade PR by the Host upgrade checklist, after release. Wire v4 comes after 0.30.2 (#925). The E2EE Workers canary and the two-device and browser matrix are not run (#654 E6). The Workers deployment, two physical devices and real runtime calls are not approved (#794). Agent memory W5 and W6 stay open (#605), and the submit_result validation row stays open (#610). The hosted examples are unreleased. npm publication does not deploy a Host.