[lynnswap]

Summary

Crash sync now uses Organizer in an already running Xcode, preserving that application's account session. It no longer launches, restarts, or terminates a separate Xcode for acquisition.

Details

• Wait for Xcode to leave the foreground before opening an Organizer route, then use the standard Reload Organizer command and retain exact-query freshness checks.
• Request the terminal page of short lists with a scroll gesture directed to the Organizer window, without resizing windows or moving the pointer.
• Keep borrowed process identities out of legacy termination records and protect running Xcode instances during recovery of older jobs.
• Preserve readable saved sample scopes after preparation or reload failures, while keeping cancellation observable.
• Update usage, migration, architecture, and MCP tool descriptions for the running-Xcode requirement. Organizer content and selection can change during collection.

Testing

• 132 focused macOS tests passed, including borrowed lifecycle, legacy recovery, foreground waiting, and saved-scope recovery.
• The saved-scope regression failed before the recovery fix and passed afterward; cancellation still propagates.
• Using the existing Xcode process, acquired a one-issue page and its empty terminal page, repeated the query with fresh data, and downloaded 25 detail samples. Each acquisition completed without errors and reused the same Xcode PID.
• During the first live acquisition, the foreground application and all four Xcode window frames remained unchanged; Organizer stayed behind the active application. No Xcode activation was recorded in the subsequent live checks. Xcode remained running after the test hosts exited.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T11:39:00.801066Z	61df9b1	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.