View Markdown source ↗

Dialog launch ownership

Baseline: TortoiseGit 7338078f8ddd924b8cddee35f512f2286072136d. TortoiseProc opens the requested operation rather than requiring a persistent repository workspace. In the pinned source, src/TortoiseProc/Commands/AboutCommand.cpp creates CAboutDlg and calls DoModal() directly; SettingsCommand.cpp similarly opens its CSettings property sheet for the captured path. TurtleGit retains a workspace as a macOS convenience; it must not be a prerequisite for each native dialog.

Entry points

Opening a dialog must preserve any existing workspace's repository, selection, window and in-flight operations. Folder registration must preserve unrelated watches and the user's background-refresh preference. A path or URL is input, not authority to read a repository. Cancelling folder authorization stops that request; failures must be visible without relying on an otherwise hidden workspace.

Implementation and verification scope

The action launch mode is selected before SwiftUI creates scenes. Finder supplies that mode explicitly when launching commands. Utility and Git preparation use a retained routing model without a repository window, with their existing permission and cancellation owners. Explicit workspace requests retain their own route.

The public Services inventory is one restricted public.item entry, Open in TurtleGit. Legacy typed handlers remain available internally; they no longer produce dozens of duplicated public menu items. See Finder Services.

The implementation batch also carries the port author credit, Jochen Kühner, and the existing green TurtleGit artwork. These identify the macOS port separately from retained upstream attribution and do not establish App Store seller identity.

The grouped checkpoint records four focused Core inventory methods, the final Debug build and six distinct native case/engine pairs cumulatively passing. It retains the earlier compiler, attribution-package and fixture-permission failures and their repairs. Native checks cover cold/warm About, Settings and Log, registration Cancel/retry and watch/recent persistence, explicit workspace/public Open, handoff flags and dirty Settings Quit refusal. Retained older launch checks additionally exposed a FIFO reentrant-delivery regression; its source repair and production-only lazy-access initialization were followed by affected launch, handoff, workspace/retirement, Merge, Unified Diff and primary-entry checks. Stale fixture option/launch expectations were corrected while retaining mutation and ownership assertions. All 18 receiver PIDs, including failed attempts, were reaped and independently absent afterward.

Native receivers use private repositories/preferences and invisible windows; they do not establish physical Finder gestures, signed permission grants or visual parity of all upstream dialogs. Installed-application acceptance and cold URL-launch limitations remain separate from injected receiver checks.

Cold links, patch documents and the workspace host

The general application uses a Settings-only SwiftUI scene on macOS 13 and later. A retained AppKit controller creates the workspace only for a default application launch, explicit Open Repository/Open Recent, the public Open Service or Dock reopen. AppKit's launchIsDefaultUserInfoKey supplies the initial launch intent; there is no timeout that guesses whether a URL will arrive. See the AppKit launch metadata.

A cold turtlegit:// action or .patch/.diff document uses the retained routing owner without creating the repository model or workspace controller. Requests received before startup are queued and delivered in order. Closing and reopening the workspace retains its model and child operation ownership. The native toolbar keeps Open, Refresh, Commit and Show log, with repository/busy eligibility. Settings drafts are settled before the shared Settings service changes to the workspace; the action owner retains a separate service afterward.

The follow-up grouped checkpoint passed Debug and nine focused native checks: cold file, late URL and workspace ownership with system/bundled Git, retained primary dialog routing with both engines, and the dedicated Merge scene/menu lifecycle. Receiver processes were reaped and independently absent. These checks inject launch metadata; they do not certify physical Launch Services delivery or migration of previously saved window state. The installed build3 acceptance below describes the preceding candidate.

Installed application acceptance — 25 October 2026

The signed universal Apple Development build3 was installed after the prior user session had closed. All 6,356 installed files match the measured candidate; app, Finder and cache identities agree, and the Finder registration was refreshed while retaining its enabled preference. The previous bundle is recoverable.

A normal-environment installed --command=about launch visibly showed the standalone About dialog, green TurtleGit banner, Jochen Kühner port credit and packaged Git2.55.0 version/path. The first private-home acceptance attempt did not complete and was cleaned up; CUA also created/exposed a normal launch that was closed before the clean retry. These attempts and all process cleanup are recorded rather than counted as successful physical checks. No acceptance app remains running. This covers application About, not physical Finder grants, all tool layouts, a live Dock-cache inspection or App Store distribution.

Follow-up installed acceptance — build4

The universal Apple Development build4 passed strict signature checks and was installed with all6,356 files matching the measured candidate. Its source input digest is fb3c59b7da7afefe72796eea54038427aacd1848a62a7621847202fcb5503f68. One enabled Finder registration points to the installed extension.

A real cold Launch Services request for turtlegit://action?command=about, with no special launch arguments or injected metadata, visibly opened the About dialog, green TurtleGit banner and version0.1.0(4); no workspace was observed. The acceptance process was closed with Command-Q, its waiting launcher exited0 and the application PID was independently absent. This complements the private receiver checks; it is not exhaustive acceptance of saved-state migration, every external action, physical Finder grants or all upstream layouts.