[Gaebabi]

Home keeps its quota tanks, active-account wave, large percentages and direct Switch/Recover actions while consolidating global settings behind one titlebar gear. Add account and Refresh remain visible. Secondary metadata is quieter, unknown subscription dates omit empty rows, and larger Windows account collections scroll without compressing the cards.

Prepare1.44.0 with the already merged image routing and concurrent large-request corrections. Refs #151; close only after source, native verification, package/public delivery and authorized installation are complete. Existing provider, controller and Linux support issues keep their separate acceptance scope.

Validation:54production WPF component checks cover0/1/4/8accounts, long names, warnings, persisted settings and busy restart refusal. Hosted Windows and both Mac architectures pass actual native application/menu checks, Settings keyboard focus and bounded language scrollbars. Windows runtime-recovery assertions observe real success/warning clearance while retaining the original baseline failure. The ordinary Linux session now follows Add/cancel and Settings > Start Codex/appearance with original ownership, ciphertext, theme and lifecycle assertions. Final six protected checks/packages/public downloads and owner installation remain required.

Actual application baseline with fictional accounts:

Original Windows/Mac PNGs include exact capture source, workflow/artifact digests and dimensions in the evidence receipt. Earlier local component renders remain explicitly labeled. Home contract / release gates. No private accounts, chats, generated product images or raw personal diagnostics are published. Owner Codex remains running during verification and Switch installation waits for an idle gateway.

[Gaebabi]

Author self-review, not independent approval. Review the exact final head supplied to the normal merge helper against current protected main.

The tank-fill/active wave, large quota percentage, account grid and direct Switch/Recover actions remain. Titlebar global controls are Add, Refresh and one Settings gear. Models, automatic/credit controls, restart, language/appearance, current import and drive settings retain production handlers and persisted state. Unknown subscription dates omit empty card rows; account details retain the unavailable explanation. Status/error/recovery guards remain, with quieter secondary metadata. More than four Windows accounts use reachable vertical overflow rather than compressed rows.

54windowless production UI checks cover settings persistence, busy restart refusal,0/1/4/8accounts, long names, warnings, On-state visibility and last-account scrolling. The normal native Windows runtime-recovery harness now observes real account success/warning clearance instead of a removed redundant current-login label; its unchanged baseline still demonstrates the failure. Native settings/language/automatic/credit captures and visible-scrollbar checks exercise the real popup path. Submenu scrollers override Fluent's local arrow-only theme after creation, preserve the original scrollbar theme and retain overflow assertions. The ordinary Linux desktop harness follows the new Add/cancel and Settings > Start Codex/appearance paths using actual pointer/keyboard input while retaining the ciphertext, original child identity, rendered light/dark and normal lifecycle checks. No trust/fixture identity or expected behavior is relaxed.

Package delivery requires all six protected final-head checks and matching base, source/artifact/PNG hashes, full runtime/license/payload checks, Mac signing/staged install and normal expected-head squash with matching trees. Public screenshots use fictional profiles only. Provider/gateway behavior from merged PR146/148/150 remains covered; larger request bounds are not unlimited throughput or external-provider guarantees. Owner installation uses the verified anonymous public Windows package with normal Switch IPC at active/queued0, preserving provider/account/configuration and live Codex. Existing public and Linux/provider/controller limitations remain explicit. No independent approval is claimed.