Skip to content

Code UX 0.9.11

Latest
Latest

Choose a tag to compare

View all tags
@numnx numnx released this 17 Jul 04:31
v0.9.11
90742f1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Code UX 0.9.11

Code UX 0.9.11 is a hotfix release for Task QA. It fixes the Task QA → coding failure where Codex could resume a native thread against the wrong persisted rollout/runtime home, and it hardens session continuation across the local CLI provider boundary. It is promoted through release PR #3167.

Release Snapshot

Item Details
Version 0.9.11
Release commit 90742f142851e3a0aee68f90d06b3003a1e28bf8
Release PR #3167
Included dev sync #3164, #3166
Scope 26 files changed; 824 additions and 106 deletions across provider continuation, QA orchestration, tests, documentation, and package metadata

What’s New

Provider Session Continuation Integrity

Provider-native conversation identity is now kept aligned with the exact durable runtime state used for continuation.

  • Treats the current Codex thread.started event as authoritative instead of allowing an unrelated rollout discovered by telemetry to replace it.
  • Reads the exact rollout-*-<native-thread-id>.jsonl file from the paired isolated runtime volume when a native Codex thread is known.
  • Selects Task QA continuation invocations across logical and durable workspace identities, preferring the invocation associated with the workspace-binding task run.
  • Audits continuation behavior across Claude Code, OpenCode, Gemini, Qwen, Antigravity, and Jules, and adds provider-specific regression coverage.

Fixes

Codex Task QA Follow-Ups

  • Fixed Task QA coding follow-ups failing with thread/resume failed: no rollout found for thread id when a valid native thread ID was paired with the wrong persisted runtime home.
  • Fixed incremental Codex telemetry allowing the newest unrelated rollout in a reused runtime home to overwrite the current invocation’s native thread identity.
  • Keeps a single bounded fresh-conversation retry for legacy or already-corrupt Codex records while preserving the existing code workspace and task context.

Provider Continuation Safety

  • Fixed QA resolving provider conversation identity independently from durable workspace ownership, a provider-generic mismatch risk.
  • Fixed Antigravity logical/workspace IDs being eligible for use as native --conversation IDs; workspace-local continuation is used when no native ID was captured.
  • Preserves exact native-session continuation for providers whose persisted identity is available.

Validation

Check Result
Typecheck & Lint Passed locally and in GitHub CI
Backend Tests & Coverage Passed locally: 467 files, 6,167 passed, 12 skipped; 84.66% lines, 84.32% functions, 73.36% branches, 83.41% statements; GitHub CI passed
Dashboard Tests Passed locally: 272 files, 2,537 passed, 1 skipped; GitHub CI passed
Security Audit Passed locally and in GitHub CI; no known vulnerabilities
Production Build Passed locally and in GitHub CI
Playwright E2E Passed across Linux, macOS, and Windows
Electron Release Candidates Passed for Linux and Windows release packages
CodeQL Analysis Passed for Actions and JavaScript/TypeScript

Additional local validation:

pnpm run ci
git diff --check origin/main

Risk and Rollback

Risk is limited to provider session identity discovery and Task QA continuation selection. No database migration or persisted-data rewrite is included. If a post-publication problem appears, revert the release merge from main and publish a corrective patch; npm versions are immutable, so do not attempt to reuse 0.9.11.

Known Follow-Up

  • Existing legacy records whose Codex rollout was already deleted cannot recover the lost conversation transcript; the bounded fallback continues in a fresh conversation while retaining the code workspace.
  • Exact native continuation still depends on retaining the paired provider runtime volume and its provider-owned session artifacts.
Assets 8
Loading