v0.4.1
dsh-lcx-codex 0.4.1
0.4.1 is the current stable release (npm latest). It is a zero-functional-change stable promotion of the fully QA-passed 0.4.1-pre.1 runtime.
What's new since 0.4.0
- Alpha stateful Web Actions are hardened. URL-based continuation now supports the intended
search → open → find / click → screenshotflow while preserving strict opaque-ref/session/route boundaries. Unsupported deployments fail closed instead of advertising capabilities they cannot actually execute. - DSH compatibility seams are isolated. Route resolution, SearchProvider selection, AgentPresets services, compaction/pruner integration, and session/request-header access are contained behind a narrower compatibility boundary instead of leaking host-version assumptions through the runtime.
- Typed protocol hardening. High-risk Responses paths for routing, Native V2 compaction/replay, checkpoint handling, SSE validation, generation controls, and provider-machine diagnostics gained stronger type/runtime validation.
- Conservative token budgeting is unified. Native retained-history budgeting and portable migration use the same conservative estimator, including CJK/code/JSON-heavy content and atomic tool-call/result groups, while preserving the existing 64K / 24K / ~3K retention policy.
- Installed Settings lifecycle is fixed. The plugin now initializes and re-enables cleanly when installed through the normal DSH plugin path, including late-mounted Settings/configuration-card behavior.
Existing core behavior retained
- Ordinary search still uses DSH's existing
web_searchentry and follows the active GPTopenai-responsesroute. websearch_gpt_advancedremains opt-in for Hosted Search controls.- Native V2 remains integrated through DSH's existing compaction lifecycle: Native-first at the configured threshold, emergency DSH pruning only in the higher-pressure zone, and DSH session transactions/recovery remain authoritative.
- Native opaque checkpoints remain source-session bound; forks and model/route migrations use portable history rather than replaying a parent's opaque state.
Install / upgrade
dsh plugin --profile web add dsh-lcx-codex
dsh webTo pin this release explicitly:
dsh plugin --profile web add dsh-lcx-codex@0.4.1Do not delete DSH sessions or $DSH_HOME/storages/lcx-codex/ as part of a normal upgrade.
Compatibility
Formally verified stable stack:
| Plugin | DSH | DSH host Pi | Plugin Pi |
|---|---|---|---|
0.4.1 |
0.1.1-rc.2 |
0.82.1 |
0.82.1 |
New DSH versions are not assumed compatible automatically.
Validation
Stable promotion was gated on the exact release runtime:
- TypeScript typed-core check: PASS
- unit/regression suite: 111/111 PASS
- DSH schema validation: 4/4 PASS
- npm package dry-run: 28 files PASS
- runtime/source parity vs
v0.4.1-pre.1: PASS - trusted npm publication with provenance: PASS
Because 0.4.1 is a zero-functional-change promotion, the Installed Candidate + Cross-feature QA already completed for 0.4.1-pre.1 is the runtime acceptance basis for this stable release.
Next line
Cache-prefix low-reuse anomaly diagnostics are continuing separately for the 0.4.2 development line. They were not a release blocker for the already accepted 0.4.1 runtime.
See CHANGELOG.md for the detailed history.