v0.4.2

v0.4.2: Codex installation with inactive profiles and native caches

Semctx 0.4.2 packages the Codex installation correction integrated by
PR #303. The npm CLI and both host plugins keep one
release identity. Bun >=1.4.0, Codex 0.147.0 and Claude Code 2.1.229 remain the declared baseline.

What changes

Valid inactive profiles containing execution settings can coexist with installation metadata.
A selected profile, unknown authority or discovery fields, malformed values, unsupported
reasoning-summary or verbosity values, and an empty reasoning effort still refuse. Model and
service-tier strings retain the native open domains; this admission does not prove provider
execution compatibility.

The selected cache follows native Codex: a direct regular local directory takes priority;
otherwise the native directory-name comparison selects a version. An unselected residual cache
does not supply the installed identity. The selected payload must be complete and coherent.
Only the reserved, stable latest alias directly targeting that selected directory is admitted.
Raw traversal segments refuse before following a link; unsupported or changing links still fail.

On Windows, installation and both deferred cleanup helpers resolve standard Codex .cmd/.bat
launchers to verified Node and adjacent JavaScript entries with the original argument vector.
Existing native executables, safety deadlines and trust checks retain their contracts.

Install or upgrade

After the canonical release workflow publishes and attests this version:

bunx semctx@0.4.2 install

Installation does not reload an active session. Open a new Codex task or reload the Claude plugin
before attributing observed behavior to this runtime. For rollback, install the previously
published 0.4.1 through the native host mechanism instead of editing a locked cache.

The host baseline delivery proof
supports the retained host pins; it is not a delivery receipt for 0.4.2. Oh My Pi remains an
experimental consumer without the two-host delivery attestation.

Evidence and limits

The correction's candidate CI and
merged-source CI passed on their
original subjects. They establish source integration, not a release receipt for this versioned
candidate. Its lockstep metadata, generated payloads, package and delivery require their own
checks through the unchanged release workflow.

The GitHub Release and
npm package are publication targets until registry
read-back succeeds. The public demonstration retains
its own package and artifact identity; its historical evidence is not relabelled as 0.4.2.
Semantic coverage, freshness and authority refusals stay explicit. Transport recovery in an
already-open Codex session is not guaranteed by this installation correction. Live-session
activation and untested hosts remain UNKNOWN until observed. Adoption, retention and human
contribution time remain NOT_MEASURED.