keel v0.1.2
This second public pre-alpha carrier for keel was published on npm and GitHub on 2026-08-13 after the
protected tag workflow built and attested one exact carrier, a maintainer inspected those same staged
bytes, and separate maintainer 2FA approval made the version public. The npm and GitHub tarballs are
byte-identical. Standalone Bun binaries remain excluded under ADR-0040.
This release adds three bounded, Warden-governed execution and publication paths: literal-argv
process.run; one exact human-approved non-default feature-branch git.push; and a separately
approved same-repository GitHub.com pull-request creation after exact remote-head verification.
Per-launch authenticated proxy authority, immutable configuration/credential snapshots, credential-
helper provenance controls, verified TLS, connect-time destination guarding, once-only review,
durable intent, independent outcome observation, and audit evidence constrain those paths. The
limits documented in the README, status page, ADR-0090, ADR-0091, and claim ledger still apply.
The carrier also includes the TUI completion, review, recovery, interruption, evidence, and
presentation polish delivered since 0.1.1; provider streaming-integrity and vendored TLS response-
flush fixes; dependency advisory remediation; and the subsequent lifecycle and reconciliation fixes
found by adversarial real-product testing.
Known limitations: P1-007 failed for the exact 0.1.2 carrier at 373,342,208 bytes aggregate peak
Kernel+Warden RSS against the unchanged strict <150,000,000-byte threshold. The owner accepted that
named residual for this pre-alpha version only; no packaged-performance claim is made. Issue #222's
two nondeterministic real git.push product-path failures also remain an open P0 accepted only for
this pre-alpha version; assertions, no-retry/no-force behavior, and enforcement remain unchanged.
Current source contains two later fail-closed reliability/DX fixes not present in this carrier:
actionable recovery for expected credential-broker readiness failures and exact same-repository
handling of GitHub's maintainerCanModify: false normalization. On 0.1.2, an internal or
indeterminate result in those cases requires audit/provider inspection and no automatic retry.