The release run re-invoked the Full native tests workflow and waited for it
before aggregating packages. That workflow already runs for every pull
request, merge group and main push, so the repeat added no coverage while
its macOS Intel job queued behind the Intel package build and became the
critical path (60 minutes end to end, packages done after 28). Aggregation
now depends on the packaging jobs only; each package still runs its own
runtime conformance and the aggregate still validates every report.
Align the 1.9.0 notes and CHANGELOG entry with the 1.8.2 format (prefixed
bilingual entries), record the session-breaker fix and the sponsor page,
and date the entry to the release day. Remove the ARM64 diagnostics
workflow and its two probe scripts from the release tree; the CI workaround
script stays because the release workflow runs it.
Settings → Home → Project and support gains a Sponsors row that opens an
in-app page (logo on the left, bilingual introduction on the right) with a
single sign-up link carrying the project's attribution parameters. Both
READMEs add a matching Sponsors table and the community Discord invite.
snapshot_session() pinned boot_attempts at the launch value whenever any
pane still had an unconfirmed AI restore target, so the 1 Hz autosave never
reset the crash-loop counter. A Codex conversation waiting at its startup
prompts (hook review, directory choice, "open in another app") therefore
counted every normal exit as a failed start, and the third launch moved the
whole workspace to session.crashed.json.
The breaker only answers "did this launch reach its first autosave"; the
restore target is still persisted through session_agent() and resumed on the
next launch. Drop the coupling and the recovery_boot_attempts field, and add
a GPUI regression that restores an unconfirmed Codex target on the third
attempt and asserts the snapshot reports zero attempts.
Keep the owned GUI test executable attached to its CMD or PowerShell parent, control the font layout fixture independently of host preferences, and gate the exit-prompt UI test on GPUI test support.
Include cloud settings, panel sizing, command groups, Agent integration settings and runtime input fixes from main. Bind native Codex recovery to the live pane process and preserve verified IDs; add CMD recovery choices and an explicit exit path when identity discovery fails.
The resize fixture submitted the new pane's command before its shell produced initial output. Reuse the bounded boot precondition before the first sibling probe while preserving immediate post-resize measurements and strict geometry assertions. Cover delayed and silent startup with cleanup.
Retain the merged Markdown caret, selection and popup fixes and their pinned component revision alongside the session and highlight repairs. Update bilingual release notes for the integrated changes.
Synchronize product crate versions, local dependency constraints, lockfiles, Windows resources and installer defaults. Add bilingual changes and verified contributor credits before CI packaging.
Regenerate Bash, Fish and Zsh snapshots after adding the distribution and user flags to setup-ai. This repairs the exact snapshot mismatch in Windows native CI.
Use translucent accent ink for selection and search matches, apply the resolved document palette to caret rows, and let source editors reveal the existing workspace wallpaper. Cover built-in/custom palettes and search/copy across theme changes.
Keep a validated saved conversation ID when the optional native filename does not provide a rollout UUID. Cover normalization, command generation, unsafe IDs and the queued GPUI restore path.
Native Codex hooks may identify a running session/group instead of the
rollout thread accepted by resume. Retain transcript paths, normalize the
thread identity, and share the parser with session discovery and probes.
Keep recovery paths when a matching provider acknowledgement omits them,
retain native identity metadata while reducing large SSH/WSL events, and
show the existing failure message when a saved target has no resume command.
Add regressions for Windows/guest paths and multiple CLI startup flows.
Add the working-directory action to tab and terminal-selection menus, and
reuse it in the command palette. Copy the shell-reported local/guest path,
disable unavailable paths, and show the existing clipboard feedback.
Selection copying keeps the original text, including prompt glyphs.
Move palette availability and row filtering into the existing palette
module so this change does not grow the workspace orchestrator.
GeekMr