Claudexor 2.1.2
Claudexor 2.1.2
(2026-07-18) — the credential-profiles release, published as
2.1.2 after two npm-infrastructure burns: the v2.1.0 flight died on npm's
post-publish indexing lag (the publisher's exposure window was too small),
and the v2.1.1 flight on two more npm realities — the attestation endpoint
lags like the version listing, and package builds are not byte-reproducible
across CI runs, so retries demanding local byte-identity could never pass.
Both partial version sets are orphaned on the registry (npm forbids
re-publishing a version); nothing user-visible shipped as 2.1.0 or 2.1.1.
The publisher now waits out both npm endpoints (bounded 10-minute polls)
and anchors retry skips on npm's signed SLSA provenance (same repo/
workflow/tag/candidate commit + published-bytes digest) instead of
impossible byte-identity. On top of the 2.1.0 scope below, this release
adds account deletion
end-to-end (DELETE /v2/credential-profiles/:harness/:id with a
delete-grade confinement fence and disclosed cleanup, claudexor profiles remove, delete on account rows) and ONE shared accounts surface
(AccountsSurface) reused by the bottom-left popover and the Settings
Harness Doctor's Manage sheet, plus the owner-review release protocol
constitutionalized as INV-125.
The 2.1.0 scope: credential profiles (INV-135) and the honest-UI
finish of the 2.x cycle. Multiple subscriptions per harness: durable
non-secret credential_profiles registry, isolated vendor config dirs
(claudexor profiles login), namespaced secret slots, strict per-turn /
thread-sticky selection, profile-isolated native-session resume, and
per-profile doctor probes (GET /v2/credential-profiles). Subscription
quota is now read proactively per profile from the vendor oauth/usage
endpoint (token transient-only, never persisted or logged) with per-profile
chips in the quota footer, plus the live-verified codex
rateLimitResetCredits balance. One typed profile_policy per harness
(fail|ask|rotate): preflight headroom breaches and typed vendor-limit
rejections rotate with full provenance — never on plain network errors,
never mid-spawn, each profile at most once per attempt. Also in 2.0.1/2.0.2
(unpublished patch steps folded into this release): the honest-engine pass
(shutdown state-machine with an uncancellable drain sweep, daemon-owned
retention with tombstones, typed final-answer assembly, harness-stream
reference + manifest-declared stream conformance) and the simple-UI pass
(messenger chat cards, flat one-row-per-tool transcripts, RunFacts SSOT,
daemon-normalized readiness rows, cause-driven single-CTA auth sheet,
typed budget.cash disclosure; INV-134 presentation discipline). Claude
api_retry error prose now classifies onto the documented retry categories.
Signed, notarized, stapled, SBOM-backed and provenance-attested.