[qeude]

Problem

Source installs (script/build_and_run.sh) moved the installed bundle to .Defi-install.XXXX/previous.app before replacing it. LaunchServices follows moved bundles, so System Settings could list Defi's Accessibility and Screen Recording entries as previous, permanently so when a failed install retained its recovery bundle.

Fix

Keep the Defi.app file name for both transaction bundles: previous/Defi.app and candidate/Defi.app. Bundle identifier and code signature are unchanged, so existing permissions stay valid.

Release installs (Homebrew, ZIP) are unaffected: packaging only uses --stage.

Verification

• python3 script/verify.py local passed, including the failed-install recovery workflow test.
• Desktop installation not run.

Note

Keep Defi bundle name during install transaction

The installer previously staged bundles under generic names, which broke the .app naming during install. This change stages previous and candidate bundles at paths that include the application name and .app suffix.

• Creates separate previous and candidate directories inside the transaction before install proceeds in build_and_run.sh
• Rollback restores the previous bundle from the new filename-preserving path
• Candidate copy, code-signature verification, and the replacement moves all use the new named paths
• Risk: rollback detection now depends on the previous-bundle path in finish_install; check that path matches the new layout

^{Macroscope summarized 3d3c5ad.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[macroscopeapp]

Approvability

Verdict: Approved at 3d3c5ad

Macroscope's review found this PR approvable — This narrowly fixes the temporary bundle paths used during installation so macOS preserves the Defi bundle name, while leaving the final install location and service lifecycle unchanged. The change is localized to the installer transaction and is straightforward to verify.

^{You can add or adjust custom eligibility rules. Learn more.}