View Markdown source ↗

TurtleGit for Mac — full port tracking

Current installed checkpoint

Build 9 is the recoverably installed Apple Development build for Intel and Apple silicon. Its 1,509 clean measured distribution inputs match commit e832798c; strict signatures, all eight universal components and the 6,362-member source/staged/installed inventories passed. Build 8 remains preserved for recovery. The installed app includes the connected Finder restart-cache recovery below, in addition to the standalone authorization, stored-decision and pane-header corrections. No user cache was reset.

The build 8 checkpoint retains the actual signed initial file-chooser cancellation: owned process exit 1, no editor or misleading permission-renewal error, and restored preferences. No new build 9 physical Finder, image or mail acceptance is claimed. All native recovery receivers were independently absent, and installation left the app closed.

The Finder registration and compact error checkpoint retains evidence for actual permission, canonical publication, visible badges and repository commands with nested untracked/ignored checkouts. The compact error controller is included in build 9: short content is 148 points high, and long selectable details scroll. The later screenshot's build is unidentified. A separate restart-cache defect has now been reproduced: invalid decoded warm status could enter live contributions and block a fresh Add. Its connected recovery batch is included in installed build 9; physical acceptance on the reported repository remains unverified.

The completed hosted macOS run at c47640a3 failed during test compilation on Swift 6.1.2, before behavioral tests ran. The subsequent typed gradient-assertion repair retains the behavioral assertion. At the latest observation, the 4b90f77a macOS run is executing Git integration tests and d89ad1f6 is pending. Pages for d89ad1f6 succeeded. These results do not establish a current complete hosted macOS pass or App Store distribution acceptance.

Latest source batches

The connected advanced Cherry Pick parent-choice family replaces whole-plan merge-parent questions with durable decisions at each reached merge occurrence. Earlier ordinary commits and empty-subject reviews run first; Cancel preserves replay progress, and Continue/reopen, Skip, Abort and pending-row edits retain their session/occurrence ownership. Parent acceptance is fenced to the captured HEAD, original parents and replay files. This source is newer than installed build 9. Its grouped checkpoint records 15 affected Core methods passing cumulatively, a Debug build and both native engine cases passing. First-leader Skip exposing an orphan Squash remains an explicit stopped-plan boundary; full source parity is not claimed.

The connected Finder restart-cache recovery validates optional saved subtrees before live admission and rebuilds malformed archives from fresh, validated status. A typed successful recovery notice allows Add to complete its paired Recent record; actual write, live-publication and child-collection failures still fail. Other live repositories survive recovery, and no global cache reset or new permission grant is used.

The connected standalone authorization family separates lexical Open roles from post-grant file validation and distinguishes normal CLI chooser cancellation, corrective selection and actual fresh-scope failure. Panels remain owned through detachment and late replies cannot revive retired preparation. Its checkpoint records the actual focused Core/native scope and compiler-bridge repair.

Stored decisions now clears exact project-hook approvals and denials, refreshes an already loaded Hook Settings page, and preserves drafts, script permissions and accepted running hooks. The reset checkpoint records eight focused Core methods, two retained hook engine cases and the native Saved Data case passing. The pane-header acceptance correction records six final native scenario/engine pairs passing after repairing the real load-title overwrite and correcting the accessibility oracle. These corrections are included in installed build 9; their focused local checks do not establish physical acceptance of every workflow or full hosted acceptance.

The patch export-to-mail family replaces lossy attachment-list filtering in Sync and Format Patch with complete verified delivery. It retains actual Git completion/output, already-written files, owner cancellation and late-child refusal. The grouped checkpoint passes 17 focused Core methods, one Debug build and four native case/engine pairs without a repair cycle; all owned receivers are absent. Installed build 7 includes this source. Pages deployment for 4b90f77a succeeded; its macOS workflow remains in progress at the observed application-build step, so full hosted acceptance remains unproven.

The Compare/Merge pane-header family adds original source comparisons, saved-target Reveal and connected Save As menus in classic and compact headers, with owner and layout replacement handling. Its affected Debug build and six cumulative native case/engine pairs pass after recorded startup and fixture repairs. The general path-gradient family extends EMF+ rendering to cubic, multiple-figure and crossing boundaries against retained Windows references; 12 focused Core methods and two actual native Compare/Conflict engine workloads pass. Installed build 7 includes these source changes. Subsequent header acceptance corrections remain newer than that candidate. Physical/full-dialog parity, current hosted CI, distribution signing and App Store submission remain open.

Earlier connected implementation checkpoints

The connected parity batch covering Commit category checking and Settings context/page handoffs. Source comparison confirmed the existing Commit checkbox layout and graph-first Log presentation, while identifying actual category-mask and asynchronous Settings request loss. Its grouped checkpoint records 13 focused Core methods, both affected bundled-Git filter cases and 16 native case/engine pairs passing after recorded repairs. Its original Commit table-reentrancy warning is followed by the later Commit report-row checkpoint, whose bounded final checks contain no reentrancy warning. That does not prove global resolution of every earlier shared-table diagnostic. Complete dialog/application parity and a current full hosted CI pass remain unproven.

The Browser Git filename family preserves raw tree identities instead of rejecting a complete directory because one name is not UTF-8. It connects tree navigation and refresh, read-only stored-blob inspection, explicit path-action admission and recursive transfer preflight. Its grouped checkpoint passed 33 focused Core methods and 14 native case/engine pairs after a recorded compile repair. Raw-byte filesystem operations, physical/signed acceptance and full Browser parity remain open. Build 6 includes this source; the Browser-specific physical acceptance was not repeated as part of the Finder registration check.

The signed viewer-family checkpoint records that earlier recoverably installed Apple Development candidate: measured 8569ede1… inputs at a955f566 with preserved dirty work, eight universal owned components, 206 runtime items and matching 6,356-member inventory. Actual signed stdin/title, native Save with exact bytes, window-local Dark Mode and Quit passed. That acceptance found duplicate Close commands; the repaired signed candidate then passed static/install checks and its actual File menu has one standard Close. Its Close exit passed; a later CUA accessibility observation reopened a workspace, which was separately quit and shell-verified absent. Final menu evidence is accessibility text only because no screenshot was returned. Existing helper functional sandbox modes were not rerun. Full source visual/physical, external signed grants, current hosted CI and App Store delivery remain open.

The standalone Unified Diff family adds explicit file, empty-document and raw stdin entry without Git or a repository workspace. It retains source titles, bounded bytes, owned cancellation and Quit drain, regular-file admission, explicit sandbox file selection and per-window Dark Mode. Existing document editing and Save/Apply workflows are reused, with Git resolved only for Apply. The checkpoint records 17 cumulative Core method passes, five native cases and a real executable pipe launch/close. The Unicode path repair and fixture compile failure remain recorded; complete viewer visual parity, signed grants and App Store deployment remain open.

The native list interaction family preserves full-row/label selection, native checks, colors and drag while deferring unsafe row-construction work and fencing delegate/client/reuse/retirement handoffs. Its checkpoint initially passed Debug and six native case/engine pairs after retained fixture-oracle repairs. A later physical Debug Log check proved duplicated label text, then early truncation. Measured primary-label geometry and direct attributed drawing now pass a fresh six-pair checkpoint plus focused consumers with both Git executables, and physical Log dark/light checks show complete labels. Failed fixture and physical attempts remain recorded. Owned receivers are reaped and final cleanup restores preferences/grants. Six original offscreen images remain diagnostic only. Full visual acceptance of all three consumers, external signed grants, full hosted CI and App Store delivery remain open.

The status refresh ownership family keeps Working Tree, Commit, Log working-tree previews and Finder display reads fresh without publishing optional index-stat updates. Busy Cancel drops older passive reloads while preserving accepted scope requests and later external changes. Its checkpoint records four distinct Core methods with each Git executable, final Debug and six native case/engine pairs passing after the recorded production and fixture repairs. All eight attempted receivers are absent. Reentrant NSTableView delegate warnings remain open. Signed build/static checks, recoverable install and focused physical refresh/close acceptance passed with raw index bytes preserved; wider Finder, App Store and full current hosted CI acceptance remain open.

The Finder comparison and delivery family adds eight selected-file Services to existing native comparison, patch/mail and repository export/request workflows. Captured document bytes/settings, independent file grants, mark ID races, fresh source admission, live cache context and actual child/worker retirement are implemented. Its grouped checkpoint passes 57 Core methods and seven distinct native scenarios across recorded fixture-only repairs. All nine receivers are independently absent. Original 47 declarations remain unchanged;55 total registrations do not imply whole-port completion. Physical/signed/full-hosted and source-dialog acceptance remain open.

The bounded metafile raster continuation implements four-corner device regions, global operand sampling, a single verified native destination checkpoint and reachable SVG snapshots without deleting live GDI objects. Existing truth matrices, cumulative limits and the 15-second decoder deadline are retained. Its grouped checkpoint records 39 distinct passing Core methods across focused repairs, the final Debug build and four native comparison/conflict case/engine pairs. All four receivers are independently absent. Both universal helper slices convert the full truth matrices locally under the unchanged deadline; complete Windows rendering identity and a current hosted pass remain open.

The classic direct bitmap and gradient family connects EMF/WMF scanline bands and full compressed direct input with classic rectangle/triangle meshes through existing native comparison and conflict panes. Its grouped checkpoint passes 16 focused Core methods, universal runtime reconstruction/conversion, Debug and four native case/engine pairs after a runtime constructor-label repair. All four receivers are absent. Format/signed/physical limits remain explicit; this does not implement Windows metafile graph writing.

The Statistics save/calculation family implements source filter groups and filename-selected encoders, captured exports, cancellable atomic publication, actual sheet/worker retirement and a consistent captured diff backend. The grouped checkpoint passes 23 focused Core methods, Debug and ten native case/engine pairs across recorded repairs. All twelve owned receivers are absent. Windows graph metafile output and physical/signed/full-hosted acceptance remain open.

The Blame embedded Log family adds captured reference/tracking/HEAD metadata, shared source-colored labels, configured fonts and adaptive rows, source column migration and fitted Reset, guarded header/activation receipts and drained ownership across File Open/closure. Its grouped checkpoint passes 25 focused Core methods, the Debug build, four functional native case/engine pairs and the native capture case after recorded fixture/capture repairs. Two complete light/dark captures were reviewed and all eight owned receivers are absent; physical and signed acceptance remain open.

The revision-list drag family connects Changed Files, Log, Rebase Revision Files and both Sync file lists to captured native file delivery. Historical hashes, exact paths, backend preferences and access leases belong to the accepted drag; working lists offer actual file URLs. Sync preserves the source base-revision rule. Its grouped checkpoint passes six focused Core methods, the Debug build and six native case/engine pairs after recorded fixture repairs. All nine owned receivers are absent. Physical gestures and signed cross-application grants remain open.

The classic bitmap-brush family adds serialized WMF patterns, EMF monochrome/DIB brushes, late palette selection/edits and live text/background state through the existing comparison/conflict paint consumers. The grouped checkpoint passes eleven focused Core methods and both native case/engine pairs on the final rebuilt universal helper, with measured embedded runtime identity. Device-dependent color layouts and full Windows rendering identity remain open.

The retained Commit staging repair preserves selected rename paths through repeated Stage/Unstage while consulting fresh conflicts, keeping copies destination-only and unrelated index content intact. Its grouped checkpoint passes 21 Core methods and four native case/engine pairs after recorded fixture repairs. Both previously failing hosted methods pass locally; a complete current hosted pass remains open.

The Export archive format and owned chooser batch implements source format choices, Git filename inference, captured save/overwrite decisions and drained native completion ownership. Ten distinct Core methods and six native case/engine pairs pass across the recorded checkpoint and focused repairs. Four complete captures were reviewed; signed destination grants and physical Finder acceptance remain open.

The Bisect source form and completion family connects sorted Good/Bad choices and native focus, exact child Log end/selection and preferences, native source-ordered completion actions, real child/question/ worker drainage, retired cache refusal and captured Submodule Update presentation. Six distinct native pairs pass across the grouped checkpoint and focused fixture repairs. All eight receivers are absent; four complete light/dark captures were reviewed. The user guide is bundled in Help. The dated checkpoint records actual checks and remaining physical, source, signed and hosted acceptance. Core was unchanged.

The Clone/Create navigation and result family connects source sticky Browse/Open, captured local/remote navigation, native form commands/tooltips and bounded fields, plus optional verified-bare folder artwork with preserved customization and nonfatal warnings. Eight distinct default native case/engine pairs pass across recorded fixture repairs and a production compact Init sizing repair. Four complete light/dark captures were reviewed; all sixteen receivers, including failed attempts, are absent. The dated checkpoint retains a separate failing accessibility probe: offscreen SwiftUI virtual help exposure is unverified. Core was unchanged and not rerun. Full source, physical, signed and hosted acceptance remain open.

The submodule dialog actions family connects sticky native Show diff/Compare actions, source action rows and colors, captured child Log/Reset preferences and exact revisions, retired cache replacement, deferred conflict handoff and real child/worker cleanup. Eight distinct native case/engine pairs pass across the grouped checkpoint and affected routing repair. Four complete light/dark captures were reviewed; all eleven receivers, including the failed fixture attempt, are absent. Dated evidence records compiler/caption/fixture repairs and retained contradictory build diagnostics. Core was unchanged and not rerun. Full source, physical, signed and hosted acceptance remain open.

The conflicted Commit family connects source checkbox selection and live staging state, current-content Stage, remembered OK/Ignore and merge hints, unchecked conflict resets, CLI command-phase effects and the distinct single-write library policy. Forty-four distinct relevant Core methods pass across the grouped checkpoint and focused repairs; all eight native case/engine pairs pass and all owned receivers are absent. Four complete light/dark captures were reviewed. Dated evidence retains compiler/fixture/mode repairs and the limits of this local checkpoint. Full source/layout, physical/signed and hosted integration acceptance remain open.

The classic region/flood family replaces silent flood omissions and per-rectangle frame approximations with destination connectivity and union-aware logical borders. It connects WMF region object lifetime, copied device clips, transforms, brush/ROP2 state and native image consumers. Seven distinct relevant Core methods and both offscreen native case/engine pairs pass across the grouped checkpoint and focused repairs. Dated evidence records actual scope, the initial clip/fixture failures, explicit native-grid/geometry policies and remaining physical, format and signed acceptance.

The classic EMF extended-pen family connects custom/alternate device and geometric strokes, cap/join/InsideFrame geometry, hatch/DIB brushes, transforms, clip/ROP2 and saved miter state. Six relevant Core methods pass across the grouped checkpoint and focused repairs. Both offscreen native case/engine pairs also pass. The checkpoint and retained build diagnostics are recorded in dated evidence; this remains a partial image rendering family, with region/flood painting and full format acceptance open.

The Synchronization commit-list family adds captured In/Out menus, source SVN metadata, scoped layouts and confirmed content-fit reset, font-sized native rows, owned root feedback and event-specific Shift comparisons. The Debug app and four native case/engine checks pass after correcting a fixture's SVN trailer assumption; production was unchanged by that correction. Core was not repeated. Four configured-font light/dark captures were reviewed and all three receivers are absent. Evidence keeps legacy installed migration, physical, signed and complete source acceptance open.

The Synchronization reference/tag result family adds fixed native source tables, captured menus and selected Log/Shift Compare/ RefLog routes, local header filters and owned tag confirmation/error retirement. The Debug build and six native case/engine checks passed on first attempts; Core was unchanged. Four light/dark captures were reviewed and both receivers are independently absent. Evidence retains actual scope and remaining physical, signed, transport and complete source gates.

The Synchronization file-list family adds native incoming/outgoing tables with source comparison and clipboard commands, historical icons/colors, exact path selection, sort/display-order dispatch and separate saved columns. Reset, tab/snapshot replacement and closure retain owned guards. The Debug app and both native groups with both Git engines pass; the affected rendering group passed after a newline-caption repair. Four final captures were reviewed and all owned receivers are absent. Evidence records failures and actual scope; Core was unchanged. Physical, signed and complete source acceptance remain open.

The native reference and transport controls connect source form menus and focus across Branch, Tag, Switch, Merge and Reset, owned Push F5 refresh, four Synchronization split controls and one-second typing coalescing. Long names retain their full menu/tooltips while fitting the native window, whose minimum survives hosting updates. TurtleGit Blame uses the fork's mascot and Git lettering. One relevant Core method, the Debug app, branding and identity checks, and both native groups with both Git engines pass. Fourteen light/dark captures were reviewed; all fifteen owned receivers are absent. Evidence retains failures and repairs. Physical, complete source and signed distribution acceptance remain open.

The connected Edit Notes lifecycle family adds the source author/committer Settings repair loop across Log, RefLog, Rebase and Synchronization, captured commit/ref saves, owned cancellation and bounded post-interruption outcome recovery. Drafts and Undo survive ordinary errors; confirmed saved-but-refresh-failed results have an owned completion warning or retained Synchronization status. Parent closures drain actual preparation, Settings, save and warning work. The Debug app, ten distinct focused Core methods (six also with bundled Git) and ten native case/engine checks passed. Evidence retains fixture failures, focused repairs, four inspected offscreen captures and owned cleanup. Full physical, multi-ref compatibility and signed acceptance remain open.

The Commit result and next-draft family connects saved-file restoration before client PostCommit, captured failed-attempt Recent messages and an editor-owned ReCommit Undo/reset boundary. It includes reset observer, raw editor/attempt buffer separation and completion cancellation ownership. The Debug app and ten native case/engine checks passed across the grouped checkpoint and focused repairs; Core was unchanged. Evidence retains the Git partial-failure discovery, exact-byte checks and owned cleanup. Full physical, signed and application parity remain separate work.

The Commit safety and draft-recovery family connects detached-HEAD Yes/Create Branch, No and Cancel, actual branch re-reading and owned child cancellation with issue-field recovery in cancelled message history. It retains explicit index-order adaptations and physical/signed/full-dialog gaps. Eight focused Core methods, the Debug app and six native case/engine checks passed across the grouped checkpoint and focused repairs. Evidence retains actual failures, private-context scope, captures and owned cleanup.

The Commit preparation and SSH signing family adds the source identity gate before status/template/Start-hook loading, owned Git Settings repair, effective author defaults and retained command/replay presets. Local SSH signing uses the existing secure helper with explicit helper precedence and cancellation. Eleven distinct focused Core methods and eighteen native case/engine checks passed across the grouped checkpoint and affected repairs. Evidence records failures, cleanup and actual scope; physical, external-agent and signed acceptance remain open.

The Open XML presentation revision family adds a bounded ZIP reader/writer, package-aware slide/shape/group decisions, dependency graph import, undo/redo and editable-copy output. Native ownership connects unresolved/dirty state, original/alias protection, Save As, cancellation and Discard/Cancel closure. An unavailable PowerPoint installation permits package metadata review for PPTX/PPTM. The legacy/result continuation adds private binary PPT normalization/Save As, explicit combined-result previews, regenerated-ID matching and classic comment remapping. The recursive group continuation described below adds independent child decisions. Complete mixed-reference combinations and physical/signed acceptance remain open. The Debug build, 28 distinct focused Core methods across the checkpoint and affected repair, native workflow checks and independent saved-output ZIP/XML checks pass. Evidence records the actual failures/repairs, captures and ownership scope.

The recursive presentation group review continuation adds sibling-scoped nested matching, independent child changes and local stacking order, with whole-group fallback for changed group shells. Editable export resolves the complete selected tree before assigning globally unique IDs and mapping connector endpoints; the native list retains full group paths and source icons and report ancestry. Twenty-eight distinct focused Core methods, the Debug app and both native review/save/lifecycle cases passed across the grouped checkpoint and affected repairs. Evidence retains the opaque-content, assertion and minimum-window layout repairs, independent saved-output verification, captures and owned cleanup. Modern threaded comments, whole-slide reference restrictions, live Office and physical/signed acceptance remain explicit gaps.

The connected Word/LibreOffice handoff family adds unavailable-Word comparison fallback, pinned outline/master/reading view gates, result-window/document exclusion checks, verified macro-security restoration, exact private-input cleanup and cooperative cancellation with worker draining. Merge remains Word-only unless LibreOffice is explicitly selected. New-window identification is conservative; concurrent user window activity and live Office, TCC, format and signed distribution acceptance remain open. The subsequent PowerPoint family above adds shape-level revision decisions and editable output while retaining explicit parity gaps. The Debug build and all eight focused native case/engine combinations pass; batch evidence records the injected Office boundary and owned-process cleanup. Core was unchanged and was not rerun.

The connected history/editor presentation batch adds the source-available three-way line-diff inspection pane, Blame incremental style/highlight/layout updates and attribution date preferences, and Revision Graph filter marks, menu artwork/shortcuts and full bounded hover metadata. The three families retain captured preferences, native input ownership and read-only inspection semantics. Three-way source editing and inline traversal remain source-disabled; Graph's existing geometry persistence is preserved. The family records distinguish these changes from complete dialog and signed acceptance. The Debug build and all three scoped native families passed with Apple and bundled Git across grouped validation and focused repairs. Evidence retains the initial failures, actual repair scope and owned cleanup; Core code was unchanged.

The list-selection presentation family ports the source FullRowSelect policy across file, reference, progress and related Settings/Find/Import lists, preserving forced-full revision history. The Core policy/store group, Debug app and grouped native checks passed across the checkpoint and focused repairs. Real light/dark captures caught and verified the source-list painting and fallback-baseline corrections; the family record retains source/platform and full-dialog acceptance gaps.

The Finder status-policy family connects all four cache choices, exact index-case policy, source stat/content thresholds and global command ownership across Settings, foreground/watched publishers, the helper and Finder. Query-only IPC preserves the separate grant endpoint, and transactional Apply fences old readers. Universal helper checks, 80 distinct Core methods, the Debug app and grouped native checks with Apple/bundled Git passed across the initial checkpoint and focused repairs. Actual light/dark page captures accompany the family record; installed signed Finder and complete source acceptance remain open.

The hosted Core repair checkpoint addresses the terminal 813fc0f5 run: process-local Unicode reference handling, explicit tree-expression fixtures, current stale-confirmation behavior and the actual post-stash inspection boundary. Its 59 affected Core tests passed; that focused result does not certify a complete current hosted CI pass.

The positioned metafile text family connects driver strings, caller-provided glyph indices and classic text displacements to native font geometry and the existing comparison/preview/conflict consumers. Its checkpoint records grouped runtime, Core and native validation alongside remaining Windows font, physical and signed acceptance.

The EMF+ custom-cap family connects versioned cap objects, native endpoint geometry and brush painting through comparison, preview and conflict panes. Default fill/stroke precedence, adjustable arrows, physical endpoints across dashes/compound paths, bounded nested decoding and world clipping share the existing image workflow. Analytic geometry evidence and remaining Windows pixel/metric limits are recorded separately.

The Rebase/Cherry Pick execution recovery family connects ordinary failed-Pick decisions, checked Retry/Skip, per-replay remembered Skip and retained cleanup intent. Empty-result, conflict and Edit/Squash recovery remain distinct. The family record separates implementation and actual validation from unsupported setup failures and remaining platform/source acceptance.

The Finder cache persistence and restart family connects source CacheSave to native Settings, foreground/watched publishers and the independent helper. Warm data, process-session live status, shutdown drain, owner-aware removal, crash fencing and persistence-failure recovery have explicit contracts and validation boundaries. Catalogue presence alone is not a completion claim for other Advanced preferences or the full Finder extension.

The EMF+ pen stroke family connects all nine stroke commands to bounded native geometry and the existing brush pipeline. Linear nib transforms, compound bands, independent caps, four joins, dashes, physical/world units and Center/Inset positioning have independent pixel oracles and explicit remaining format/Windows-metric limits. Batch evidence retains the initial failures, focused repairs and actual validation scopes.

The durable pending replay action family adds future Pick/Edit/Squash/Skip and per-row cycling while paused, with saved occurrence/mainline/message metadata, checked todo publication and journal recovery. Native drafts and ownership survive the handoff. Batch evidence records the grouped Core/native checkpoint and remaining acceptance.

The Rebase revision menu family adds source row-action eligibility/order, all merge-parent/unified mode choices, inherited icons/default comparison, native keyboard/AX entry and exact captured receipts. Batch evidence records the grouped checkpoint. The older/external session adoption family extends recognized structural recovery; arbitrary custom commands and the remaining shared Log menu commands remain open.

The captured Settings sheet family repairs real Close/OK/Cancel across Rebase, Git Properties and Unified Diff. It preserves captured preferences, property drafts and queued dirty-document decisions through actual sheet detachment. Batch evidence records grouped native checks and remaining physical, hosted and signed gates.

The connected Resolve review/automation family adds all four silent/noquestion entry modes, literal force-staging with first failure/cancellation semantics, source side-file cleanup, retained reviews and captured permission/adoption/preferences. Silent work owns cancellation and Quit through actual drain; source noquestion-only Skip behavior stays explicit. Batch evidence records checks and remaining Windows protocol, physical, hosted and signed acceptance.

The connected LFS completion and native-readiness family retains reported server effects through incomplete/cancelled terminal replies, refuses false success/Pull, preserves captured Force targets, settings and exact window ownership, and addresses the next hosted native-header settlement failure. Batch evidence records focused validation and remaining physical, hosted and signed acceptance.

The connected conflict editor entry/routing family adds standalone normal/alternative command entry, captured working-tree/metadata authorization and adoption, original preference inheritance across all four specialized editors, and exact preparation/Delete/Submodule window identities. Duplicate native drafts survive entry; owner/retirement cancellation holds pending work through actual drain. Batch evidence records actual checks and remaining external, physical, source and signed gates.

The connected service utility command family adds Daemon normal/bare entry, visible/quiet/forced update behavior and download visibility, owned no-Git Autotext entry, and a native launch explanation with Help/Documents actions. Utilities preserve their existing drafts/workers and preferences; update checks coalesce without interrupting accepted downloads. Batch evidence retains actual validation and public-network, physical, source and signed acceptance gaps.

The connected dropped-file command family adds source Move, Move/Rename and Copy/Add command routes, source/target separation, owned destination authorization/adoption, automatic explicit operation startup and captured preferences. Existing name/collision/error/metadata prompts, Git actions, source icons and cancellation counters remain shared with native transfers. Batch evidence records actual checks and remaining physical Finder, complete source and signed acceptance.

The connected application utility entry family adds source Settings page selection/defaults, About/Help routes without repository requirements, and explicit First Start page/bootstrap ownership. Native Settings retains its transaction through idle page navigation, suppresses Remote Fetch for source command entry, and uses captured context adoption. Supplied handoff owners remain authoritative through drain. Evidence records actual validation and remaining platform/source acceptance.

The connected Request Pull/Send Mail entry family adds source presets and ordered duplicate file inputs, captured native permissions/inspection, linked sender metadata grants, independent global sender contexts and owning preferences. Competing Request Pull entry preserves its existing draft/progress; opening mail options does not deliver. Existing forms, icons and delivery remain shared. Batch evidence separates local checks from physical, public-service and signed acceptance.

The connected Worktree entry and destination family adds Create/List/drop command routes, source destination presets, inherited settings, retained drafts/progress, captured native destination authorization, compound Submodule Update grants and deferred manager refresh. Existing forms, source icons and Git operations remain shared. Batch evidence separates actual validation from physical/signed and remaining source parity.

The connected historical output/comparison entry batch adds ShowCompare, filtered Cat, standalone containing references and normal/hidden Revision Graph entry. Outputs retain separate grants, staged atomic publication and owner/Quit cancellation; historical virtual paths use authorized ancestors. Existing source windows, icons and native renderers remain the consumers. Batch evidence records actual checks and remaining source/platform acceptance; no complete-port claim follows.

The Revision Graph save continuation connects Pictures, Graphs and All Files to filename-driven encoders, source extension defaults and JPEG fallback. Native acceptance and CLI output authorization use the final destination; graph preferences, cancellation, Quit and retired save replies remain owned across the handoff. Windows metafile graph writing, physical/signed save grants and complete graph parity remain open.

The Compare/Merge input-encoding family ports per-pane decoder reload independently from output-format conversion. Raw source bytes, read-only/historical input choices, regeneration through the current comparison/merge engine and owned dirty Save/Discard/Cancel decisions remain connected. Source copies and replaced editors retain their own input identity; full editor, physical/signed and distribution acceptance remain open.

The connected Synchronization/SVN command batch adds Sync, SVN Fetch/Rebase/DCommit/Ignore entry paths, source sequence placement, owning settings and preserved SVN options/questions through competing commands. It reuses the native transport forms, progress and Git workflows. Batch evidence retains actual checks and source/platform limits; no whole dialog or application certification is implied.

The connected Submodule entry batch adds Add, Update and Sync command routes, source parent/bkpath superproject lookup, Update filtering/preselection, preserved reviews, active-progress refusal and owning preferences throughout forms/progress. File-only Sync remains empty rather than expanding to whole-project work. Existing source forms/icons and Git operations remain the consumers. Batch evidence retains validation scope and source/platform gaps.

The connected Bisect command family adds fresh-state source routing, optional Good/Bad Start presets, active custom-term classification, Skip/Reset, preserved native reviews and captured progress/picker preferences. Conflicting-state errors retain recovered session ownership and Reset availability. Batch evidence separates actual Git/lifecycle checks from full source, physical and signed acceptance.

The connected patch command batch adds source Format Patch, archive Export and mailbox Import entry, revision presets, preserved command drafts and owning preferences. External mailbox inputs retain separate grants, and an owned chooser handles repository selection without late/cancelled handoffs. Existing source icons, native controls and Git workflows remain the consumers. Batch evidence separates focused validation from full source, signed and App Store acceptance.

The connected Merge/Stash entry batch adds the source Merge/Abort and four Stash commands, preserved native command drafts, owning preferences, scoped pending-operation guards and request-specific untracked warning replies. Existing native dialogs, source icons, Git progress and result/post-action workflows remain the consumers. Batch evidence records actual Git effects, grouped checks and remaining source/platform limits.

The connected Compare editing-history batch addresses the hosted combined-row Undo failure with document-owned history and native pane-role rebinding. A production view-reuse fixture reproduced the owner failure locally after the ordinary typing case passed. Snapshots retain exact text, row metadata and caret across native pane replacement; stale role callbacks refuse mutation. Batch evidence separates local validation from hosted, physical and full-port acceptance.

The repository maintenance entry family adds source Create Repository, Cleanup and Ignore commands with captured native folder authorization, parent permissions for new destinations, preserved Cleanup drafts and linked-worktree exclude grants. Exact ignore/removal identities survive rule deduplication. Existing dialogs and actual Git operations remain the workflow. Batch evidence records validation and remaining platform/source limits: 35 focused Core passes, eight native case/engine passes on their first runtime attempts, and all eight receivers reaped. The complete port is still in progress. Previous-commit hosted CI now reports a typing/system “Combined cycle Undo failed” assertion; that editor repair remains open.

The source-file launch family adds Blame revision/line viewers, Previous Diff file/directory/unified routes, source-style file Add progress and folder checklist, Rename and Remove/keep confirmation. Delayed Add preparation owns cancellation/permissions and preserves existing drafts and another repository's output. The native dialogs, colored source icons and existing Git operations are reused. See batch evidence for actual validation and remaining entry/platform limits: 54 distinct focused Core passes, ten native case/engine passes after unified-range and busy-transfer repairs, and all twelve owned receivers reaped. No all-dialog completion is inferred.

The connected Clone/Init workspace handoff family replaces busy polling with captured completion ownership, unifies permission and rollback behavior with ordinary Open, preserves compound grants and stops superseded transport batches. Explicit Open/Close, workspace closure and termination retire queued results. The original reproduced stall and grouped validation are recorded in batch evidence: eight distinct native case/engine passes after the actual closed-dialog grant release repair, with all thirteen owned runtime attempts reaped. Signed Finder/App Store and all-dialog acceptance remain open.

The network/reference launch family connects eleven further command handlers to native options and browser windows, including Clone exact-path handling, reference names/base revisions, RefLog and Force Rebase presets, plus per-repository Fetch/Pull/Push preparation. Dialogs retain their own grants and no operation starts on launch. Validation and remaining source/platform differences are recorded in batch evidence: 38 focused Core passes, eight distinct native case/engine passes, the deferred-Force and directory-URL repairs, and all ten owned receivers reaped.

The command input/output family connects path-list permissions, bounded reads and explicit list deletion to native dialogs, adds source Log hash/Cancel output, and opens unified Diff or a requested source line through existing viewers. Owned workers hold grants through drain; remaining CLI and distribution gaps stay explicit. Batch evidence records 37 focused Core passes, six distinct native case/engine passes, the source-line startup repair, cancellation fences and all eight owned receivers reaped.

The connected Compare/Merge pane presentation work separates native split/viewport ownership from source styling and inline ticks. Exact peer/source changes invalidate shared presentation caches; unchanged hosted updates preserve editor owners, folds, wrapping and selection. See batch evidence for one passing Debug build, thirteen distinct grouped native passes, the fixture setup repair and all fourteen owned receivers reaped. Hosted Intel timeout resolution remains unproven.

The primary command-line entry family now connects startup readiness, repository/file authorization and editable Commit/Log presets to six existing native workflows. Diff reuses historical, standalone pair and directory routes. Remaining CLI switches and commands are listed explicitly in that guide. Validation records 27 distinct scoped Core passes and two complete native family/engine passes, including the actual Log eager-load repair, two final focused bare-repository guard passes and all seven owned receivers reaped. The older hosted wrapped-editor timeout still persists; this batch does not claim to repair it.

The connected Resolve/Rebase conflict path family now carries exact UTF-8 stage, checked and highlighted identities through both native lists, source binary checkboxes, refresh, captured menus and checked Rebase recovery. Private commit-index preparation retains new canonical peer identities before Git discovers current content. The initial failure, affected repair, 148 distinct Core passes, two Debug builds and fourteen native case/engine passes are recorded in batch evidence. All fifteen owned receivers are absent. The retained Revert table warning and full hosted/physical/signed acceptance remain open.

The connected whole-source Merge recovery now keeps Mine/Theirs whole-file choices available after custom editing invalidates result row mappings. Selected endings, excluded source records, complete result alignment and native Undo/Redo share one captured command; format changes fence stale menu targets. The first-attempt Debug build, 57 scoped Core passes and eight grouped native case/engine passes, with all owned receivers absent, are recorded in batch evidence. Full hosted, physical and signed acceptance remains open.

The connected Compare/Merge presentation family now preserves settled fold and wrap geometry on unchanged hosting updates and keeps Find/marked-word paint until an actual input or source-style change. Both editor families share an atomic presentation checkpoint, and palette colors retain identity across redraws. The single Debug build, 26 focused Core passes with one expected skip and 13 distinct grouped native passes are recorded in batch evidence, including fixture repairs and cleanup of all 18 receivers. The captured macOS 15 Intel timeout still requires a passing current hosted run; local acceptance does not close it.

A macOS fork of TortoiseGit

The connected Add/Revert file-command flow now uses source checked-path ordering, once-only acceptance and owned native file choosers through copy/launch drain, including forced closure and late replies. A hosted equality-overload compilation failure was diagnosed and repaired without changing Blame selection behavior. The checkpoint passed 53 distinct relevant Core cases and twelve native case/engine combinations across retained and affected runs; three affected fixture callers compile, and all owned helpers are absent. Batch evidence records the native cache/ refresh fixture repairs, hosted failures and remaining physical/signed/CI limits.

The connected Add/Revert selection family now retains exact Git path keys through checked/highlighted native rows, marked menus, refresh and private-index Add/mode/Revert/Retry operations. Revert checkbox clicks follow the highlighted-row rule; Add context actions retain command/payload/epoch receipts. The checkpoint passed 43 relevant Core cases and twelve distinct final native case/engine combinations with system/bundled Git. Four raw light/dark captures were individually reviewed and all owned receivers/helpers are absent. See batch evidence for the initial compile/fixture repairs, existing AppKit diagnostic and remaining acceptance.

The connected Commit/Working Tree selection family now preserves exact Git path membership through native row IDs, checked/highlighted sets, marked menus, groups, refresh and selected-index preparation, including the shared Sync conflict table. Native programmatic replacement handles a SwiftUI multi-to-subset failure independently reproduced with an ASCII control. The checkpoint passed 67 distinct relevant Core cases and ten final native case/engine combinations; four updated fixture callers also compile. All owned receivers are absent. Original failures, four reviewed light/dark captures and remaining identity/physical/signed limits are in batch evidence.

The Send Mail source family now connects exact native recipient/history controls, synchronous Combine/Subject transitions and captured list/form callbacks with owned target discovery and retained preparation lifetime. Options/progress have explicit host bounds and native minimum constraints. Four final-build case/engine checks pass with system/bundled Git, including independent loopback MIME verification; all eleven receivers and five servers are absent. See the batch record for the layout diagnosis, actual light/dark captures and physical/signed acceptance limits.

The serial-import source family now uses a native headerless checked list with right-side source commands, colored row outcomes, four options, saved divider and in-pane Patch/Log tabs. Captured input/menu callbacks, owned picker/questions and retained worker/provider cancellation connect the form to real serial imports and recovery. Both source and full retained workflows pass with system/bundled Git on the final build; twelve receivers and their fixture helper paths are absent. See batch evidence for the capture/fixture repairs, actual screenshots and open acceptance gates.

The connected reference browser and remote-tag dialog now add source filter cues, synchronous filter/scope handling, captured OK range choices and full-width native tag scrolling. Source layouts and retired callbacks have ten distinct grouped native case/engine passes after a layout repair and initial-load fixture correction. All thirteen receivers are absent; actual light/dark captures, remaining gates and the validation boundary are in the batch record.

The connected Submodule Add and Update forms now retain source option layout with captured native fields, synchronous scope/title changes, cancellable metadata reads, diagnostic Retry and retired list callbacks. Eight grouped native case/engine checks pass after fixture repairs; all owned receivers are absent. Light/dark captures and remaining Unicode/physical/signed limits are recorded in the batch evidence.

The native Merge command-menu family now connects File/Edit/Navigate/View/Help commands, active-pane Save As, F6 pane focus, named regex and checked comparison/view choices to the existing owners. Source icons, focus epochs and busy/field/sheet/Open/replacement fences retain native clipboard/ Undo and unrelated app menu items. Nine grouped native runs and the affected transition recheck pass; all owned processes are closed. Toolbar fading persists with enabled/active diagnostics; full menu-root/physical/signed acceptance remains open. Batch evidence.

The Merge view-controls family now adds guarded left/right input exchange with reversed Save/Save As/reload routing, saved native Toolbar/Status Bar visibility and an owned two-pane divider fraction preserved through combined view. The Debug build, icon checks and all eight native case/engine runs pass after fixture/resource repairs; every owned receiver is closed. Faded toolbar icons in optional captures, full input-route/physical and signed acceptance remain open; batch record.

The moved-block family now adds the source detector, saved View toggle, original colored margin icons/tooltips, bidirectional whole-block navigation and combined-view routing. Surviving view-record links move with edits and return with Undo/Redo; accepted toggle reloads share owned Save/Cancel handling. The Swift detector matches 1,265 cases from the compiled pinned implementation; 45 focused Core cases and eight native editor cases pass within the recorded repair scope. Actual light/dark captures and ownership evidence are included in the batch record. Full row-pairing, edit boundaries/tooltips, physical and signed acceptance remain open.

The wrapped editor navigation family now enters actual first/last wrapped fragments, retains context-click sublines and restores shared reading positions through width/font/wrap changes. Explicit input and completed Find/Go to Line own reading intent; transient locator/selection publication and redundant scroll feedback are suppressed. All seven grouped native cases pass after repairs, with reviewed light/dark captures and all owned receivers closed. Physical gestures, full TextKit/Windows equivalence and signed acceptance remain open; batch evidence.

The checkbox Commit index family now resets unchecked ordinary rows to the comparison base and optionally restores unchecked additions, deletions and renames after the Git attempt. Native Commit captures the source preference and path set; staging mode retains exact index contents. The grouped batch evidence records validation and remaining action-mask, external-writer, physical and signed acceptance.

The independent helper now has the optional cache menu: source counts, a bounded activity window, shared cache-mode controls and awaited Exit. CacheTrayIcon has an effective consumer; accepted shared overlay settings remain authoritative when the app next opens. Signed service/Finder and physical menu-bar acceptance remain open; batch evidence.

The image conflict family now uses source extension routing, keeps undecodable sides selectable by their captured bytes, and supports empty Base selection in add/add conflicts. Rebase-state checks, workspace-owned Merge Tool settings, one-response resolution sheets and actual worker/Quit lifetime are connected. See the batch record for validation, capture review and remaining physical/signed acceptance.

The connected image/tool routing family now separates source Merge, IDiff and configured-program selection. Captured Shift and Settings determine dispatch before image decoding. Reload preserves that choice; explicit Load Images and Merge Open/source views retain their own viewer. Unsupported image sides keep IDiff diagnostics, and retired launches cannot publish late viewers. Validation scope is recorded in the batch evidence; complete image format, physical and signed acceptance remain open.

The Excel comparison family now connects full/fast workbook comparison, source-style value highlighting and worksheet handling, protected-sheet warnings, private copies, Settings associations and serialized Automation ownership. Thirty-one Core cases and six grouped native case/engine pairs pass after a fixture return repair and a native warning-window sizing repair. Light/dark warning captures are published. Live Excel rendering/security/locales, synchronized scrolling and signed acceptance remain open; see the batch record.

The Word merge family now connects three-way stage preparation, owned instructions, Word handoff and explicit reviewed-result resolution. Merge Settings/defaults and both Word handlers share automatic-macro suppression with security restoration attempts. Twenty-seven Core checks and five grouped native case/engine pairs pass; actual Word output/security and signed acceptance remain open.

The Word comparison family now connects six document-format associations, exact private snapshots, a fixed native Apple-event handler and retired-worker/permission ownership. Twenty-three focused Core cases, the Debug build/package audit and all three grouped native comparison cases pass. The handler compiles against installed Word terminology; actual Word execution and signed AppStore acceptance remain open.

The bundled comparison family now adds native binary byte/version reports (PE and Mach-O), source Mathematica notebook preparation/ handoff, shared default associations and retained/failed launch ownership. Nineteen focused Core cases and both native family cases pass; light/dark binary window captures are published. Actual Mathematica execution and signed acceptance remain open.

The bundled ZIP comparison now connects default associations, Advanced Restore Defaults, bounded ZIP64/Unicode metadata reading and a read-only native inventory viewer. Raw Shift comparison and saved custom associations are preserved. Fourteen focused Core checks and the real-archive native workflow pass. Other Windows document scripts and full physical/signed acceptance remain open.

The remote-management family now owns tag confirmation, worker drain, ordered error acknowledgement and fresh reload independently of its window. Remote-reference selection accepts once; Add Remote captures submission and shows saving/cancelling state. Four native case/engine pairs pass; physical and signed acceptance remain open.

The shared path-entry family now connects source filesystem completion to Clone, New Worktree, Rename and Export with native full-field completion, owned directory reads, access scoping and retired-result guards. Literal input, owner-icon Complete Path menus, caret ownership and native completion Undo/Redo binding now pass across all four dialogs. Physical keyboard/IME/popup and signed acceptance remain open.

The application identity/file-open family now packages original app/document icons, full macOS icon slots, native patch/diff file-URL routing and scoped document Save/Undo ownership. The website uses the same artwork. Physical Finder/Launch Services and signed acceptance remain open.

The native Dock progress family now connects transport, Commit, replay and shared local command progress, including unknown/paused/error states, simultaneous operations, reduced motion and closed-window retirement. Physical Dock and signed acceptance remain open.

Rebase/Cherry Pick Add and merge-parent preparation now share cancellable ownership, atomic plan/draft publication, private multi-selection Log preferences and retired question/picker callbacks. See Add and mainline preparation. Physical, full source and signed acceptance remain open.

Log range commands now follow source raw/displayed-row continuity through search, graph projection and streamed rollback. Single/two-row exceptions remain; Compare, Format Patch and Combine no longer treat hidden rows as adjacent selection. Captured popup/Combine replies expire on projection replacement. See range selection. Physical, full consumer masks and signed acceptance remain open.

Changed Files and Rebase Revision Files now prepare Revert per file so copied/ missing historical files can use source Ignore/Abort and completed-count results. Root comparisons expose empty-tree Revert, and historical export reads only the chosen destination. See connected recovery. Physical, full copy/gitlink/Trash variants and signed acceptance remain open.

Create Branch/Tag now owns creation, cancellation questions, Switch acknowledgement and description-only retry independently of the options window. Cancel drains metadata/creation workers; forced closure closes its Switch sheet and refuses late handoffs. Tracking-name suffix behavior and source tooltips are restored. See Branch/Tag completion. Physical signing/transport, full visual and signed acceptance remain open.

Commit staging activation now closes the old preview, refreshes in the new mode and presents the owned three-state explanation with the source's remembered hint choice. Serialized mode/preview preference writes own cancellation, error/retry, input and Quit lifetimes while preserving the draft, checks and index. See staging activation. The incremental staging follow-up now retains source rows/groups/status while refreshing independent index state and partial previews. Whole-file rename and unborn mixed-file unstage targets are corrected. See incremental staging. Full physical, amend and signed acceptance remain open.

Blame's annotation menus now capture line/text/parent/rename targets, honor owner icon preferences and support Shift-F10/accessibility menu requests in both source and gutter. Source and embedded Log invocations dispatch once and reject stale document targets. See annotation menus. Full physical, visual, command-artwork and signed acceptance remain open.

RefLog now distinguishes full Refresh's missing-reference fallback to HEAD from post-deletion row reload, and owns cancellable refresh/parent/unified reads through actual worker drain. Delete/Clear confirmations, per-error sheets and exclusive mutations retain their source defaults and closed-window/ Quit lifetimes. See RefLog lifecycle. Full physical, visual, menu/caller and signed acceptance remain open.

Repository Browser's revision picker now inherits its owner preferences/theme, connects the shared selectable-Log actions and owns one modal selection lifetime. The header shows source-style friendly reference labels while preserving pinned objects; folder summaries include names and captured tree/file menu actions run once. See Browser revision selection. Full physical, visual, Finder and signed acceptance remain open.

Log Revert now preserves the original selected rows through its native workflow. Mixed working-tree/root selections can undo the root; merge/stash batches keep source Skip/Abort policy without guessing a mainline. Empty working-tree hashes are skipped before Git, and earlier inverses/messages survive Abort. See Revert selection context. Physical, complete caller, visual and signed acceptance remain open.

Log revision popups now follow source single/root/merge/multi-selection and bare/working-tree command groups. The common Find/clipboard tail, captured Find selection mark, synthetic working-tree clipboard and contiguous working-tree comparison endpoints are connected. See popup variants. Full consumer-mask, physical and signed acceptance remain open.

Rebase's action row now has the source-ordered sticky bulk split button, corrected oldest-commit Squash rules, canonical reference metadata tooltips and footer Edit/Split placement. Completion also remembers its chosen command through the shared native control. See action controls. Full physical, visual and signed acceptance remain open.

Rebase's Revision Files pane now connects the Changed Files inspection family: comparison/unified, Revert, history, Blame, historical Open/Save/export, clipboard and independently saved native column layouts. Original status colors and icons, root/parent snapshots and owner-bound cancellation accompany the shared controls. See Revision Files and native captures. Full source-menu, physical and signed acceptance remain open.

Log-to-Rebase now carries the selected canonical branch/tag identity into native options, including configured child Logs. Same-named tags cannot replace a preferred local branch. Core commit-ID reads separate successful stdout from warning diagnostics, retaining Git's typed-revision resolution. See Log parity and Rebase reference preparation. Full dialog, physical Finder and signed distribution acceptance remain open.

The shared status-text family now preserves raw source colors and conversion while adapting low-contrast dark text against composited native table backgrounds. Working Tree and Commit count columns use their owning stores. The final Debug build, pinned 29-input C++/settings oracle and both native engine cases passed; nine real captures include live custom-color Apply pixels. See status text. Full physical, selected-row, all-dialog and signed acceptance remain open.

The connected Log scope/information family now adds source revision endpoints, file-selection and line/status totals, old/current-name word queries, hidden-file selection cleanup and persisted Whole Project history/title/reopening with Follow, busy and retired guards. Debug, five Core cases and both native engine cases passed; current footer captures are reviewed. See scope/information. Physical/signed and complete visual acceptance, including dark rename contrast, remain open.

The Log filter/layout family now combines source-ordered native filter menus, one-second typing, immediate clear/Return/Escape, actual ECMAScript validation, owner preferences and cancellation/retirement/Quit accounting. Header and footer commands follow the source layout; current light/dark compositor captures were reviewed. Debug, eight Core tests and both native Git-engine cases passed. See Log filters; full physical/signed and complete Log parity remain open.

The connected Finder overlay path-policy family now compiles source precedence rules per refresh, follows per-directory volume/case metadata across mount boundaries, resolves Finder badge aliases, refreshes on volume events and reports precise include/exclude editor errors. Existing icon sets and handler choices retain their shared Apply/Cancel workflow. See overlay parity. Real mount, physical Finder and signed acceptance remain open.

The connected transport selection family now uses the shared source/destination reference browser in Push, private owned Log/RefLog selectors and repository-bound commands, plus captured-draft and post-sheet handling across Push/Pull/Fetch/Sync. Remote and branch names containing slashes retain their configured namespaces. See Push parity. Physical, authenticated-server and signed/App Store acceptance remain open.

The connected file-history comparison family now reconstructs renamed endpoint paths for Follow renames, shares direct native comparison preparation across primary/picker Logs, preserves numbered-parent and live working content, and uses recovered names for selected/parent/working unified diffs. Cancellation, selection replacement and requested/forced Close share the owned reader lifetime. See Log parity. Filtered/ambiguous merge walks, physical and signed acceptance remain open.

The connected Changed Files action family now adds both-version Revert, Blame, Export and child-submodule Log with source rename/deletion rules, pinned data, owned folder/error/result sheets and protected checkout cancellation/Close lifetimes. See Changed Files parity. Revision entry now has delayed validation and native completion, shared owned reference/Log/RefLog pickers, source query filtering and saved file-table layout. Physical and signed acceptance remain open.

The connected Revision Graph command family now adds source menu groups and one-use popup ownership, configured external unified viewers with captured Shift choice and owned errors, selected-node Shift-F10 menus and native accessibility nodes/selection actions. See Graph parity. Physical, third-party viewer and signed acceptance remain open.

The connected Log working-tree action family now includes Clean up and Abort Merge, shared repository-bound primary/picker dialog routing, path-scoped Commit, fresh merge/stash/submodule gates and cancellable metadata preparation through Close/Quit. Revision Reset/Branch/Tag/Export availability follows the active bare and stash source rules. See Log parity. Full consumer masks and physical/signed acceptance remain open.

The connected Log inspection family now includes forward/reverse/symmetric range Logs with path-aware child reuse, first-parent change-set comparison, continuous multi-row endpoint comparison and merge-parent/combined unified choices. These use the existing native Log and comparison dialogs, original menu artwork and owned preparation lifetimes. See Log parity. Full source masks, rename-following parent paths and physical/signed acceptance remain open.

The Log revision-menu family now binds 46 existing selectors to a one-use popup snapshot, preserving native item artwork and typed payloads while rejecting selection/reference changes, reload and retired/blocked owners. Fresh callbacks, working-tree commands, byte-distinct refs and existing real Revert/Combine workflows passed both grouped Git-engine cases. See menu ownership evidence. Source menu variants, physical/accessibility and signed acceptance remain open.

The Blame pane interaction family now adds saved native tab groups, group auto-hide/pinning, caption drag sessions and outside-workspace floating with captured-document guards. Native pane/File Open checks passed on both engines; the final pane-only recheck passed after the documented layout/selector repairs. Four current light/dark tab captures were reviewed. See pane evidence. Physical drag, full MFC docking and signed acceptance remain open.

The workspace permission family now includes a native access manager under File → Open Recent. It connects repository/extra-folder lists, independent stale renewal, captured Add/Replace pickers and confirmed Remove/Forget, with workspace and Quit guards and live-grant retention. Debug, 18 Core checks and both grouped native engine cases passed; light/dark captures were reviewed after a sizing repair. See access guide and evidence. Signed acceptance remains open.

Workspace opening now prepares external Git metadata permissions for linked worktrees, submodules and shared object stores, with owned folder sheets, per-repository saved grants, cancellation/rollback and child-window scope lifetime. The final Debug build, 35 affected Core tests and both grouped native engine cases passed. See folder access and batch evidence. Signed sandbox and Finder acceptance remain open.

The connected Clone/Create Repository family implements owned browse/permission sheets, captured submission choices, cancellable metadata discovery and guarded warning/result lifetimes. Debug, six initialization tests and four unique native cases passed after the recorded repairs. See batch evidence; physical/signed acceptance remains open.

The connected remote-manager family adds source Sync history cleanup on Rename/ Remove, timed native origin help, owned collision reads and draft-preserving Push catalog refresh on manager return, with Pull/Fetch/Sync consumers. Its grouped validation passed: Debug plus six native cases across system/bundled Git, with all owned receivers reaped. See batch evidence; full physical/signed acceptance remains open.

The connected Commit/patch/comparison preview batch implements movable sticky previews, screen-aware placement, mode reuse, unwrapped patch extent/reset and comparison navigation after viewport layout. Debug and six unique native cases passed; two current light/dark preview captures are in the gallery. See batch evidence. Full physical/signed acceptance remains open.

The connected Push/Pull/Fetch preparation batch implements cancellable metadata, source/remote replacement, Retry loading, close settlement and complete Push preflight/post-hook ownership. Debug, 15 Push Core checks and six grouped native cases passed after a real Core cancellation repair. See batch evidence; full physical/signed acceptance remains open.

The connected Statistics/Revision Graph continuation implements calculation close/ retry, source summary-control visibility, owned exports and destination scopes. Debug and four grouped native cases passed; see batch evidence. Full visual/signed acceptance remains open.

The connected bundled SVN authentication batch implements five native callbacks with combined credentials, explicit certificate details/trust, secure certificate passwords and command-owned client-certificate copies. The pinned runtime retains its dependency caches and records the native adapter/Keychain/plaintext policy. See authentication parity. The certificate inspection follow-up adds DER SHA-1/SHA-256, original artwork and an owned read-only Open certificate sheet. Live server, other callers and signed/physical acceptance remain open.

The native SMTP caller now connects its actual TLS handshake to certificate review, including same-connection STARTTLS, default Cancel, exact temporary acceptance and an owned read-only inspector with DER/PEM export. Authentication and upload wait for the decision; cancellation and Quit retain actual worker and sheet ownership. See SMTP certificate parity for the grouped validation record and separate Git HTTPS/signed/physical gaps.

Native Issue Tracker Integration now connects its formerly missing association page/editor and embedded provider to Commit, with project fallback, owned selection, message/ID results, pre-commit checks and completion interfaces. The two settings dialog families and Commit button have explicit partial native mappings. See native issue-provider parity; Windows COM provider execution, vendor native ports and physical/signed acceptance remain open.

The connected working-file Revert recovery batch adds owned cancellable preparation, streamed private-index Git output, captured progress closing policy, retained Trash locations/action logs and fresh-status Retry. Forced retirement keeps protected-step lifetime accounting while suppressing late results. See Revert parity and the user guide; physical/signed and complete source acceptance remain open.

Workspace and Working Tree URL drops now connect the active upstream Move, Move/Rename and Copy/Add choices to the existing operation windows, with captured repository/destination context and owned preparation/picker retirement. See dropped-file transfer parity. Installed Finder right-drag and signed/physical acceptance remain open.

The connected Rename/reference-management batch covers guarded file/folder Rename, inline branch Rename, tracked-branch Set/Drop and ordered local/remote deletion. Owned questions, cancellable streamed results, retained action logs and final catalog/parent refresh now share operation lifetimes. Description retains its source Input layout with captured-tip validation. See Rename parity and reference browser parity; these remain partial family audits, with physical/signed and full upstream parity gates open.

The comparison configuration batch adds custom comment profiles in Application Support and a native editor with draft/Apply/Cancel, validation and stale-edit protection. Both viewers capture profiles on reload; the three-pane editor retains its dirty Save/discard/Cancel workflow. See comment comparison parity.

The merge locator batch adds colored Left/Bottom/Right stripes, viewport tracking, nonselecting navigation, an optional fish-eye lens and saved native View/Settings controls in both viewers. See locator parity.

The merge Save batch adds Backup original file and the source empty-result Delete/Keep workflow to both viewers, including absent-file recreation and deleted conflict staging retry. See save workflow parity.

The whitespace display batch adds source space/tab/EOL overlays and original CR/LF/CRLF icons to both viewers, with saved View/Settings controls and original ending metadata preserved. See display parity.

The General settings batch adds native fixed-pitch font/size choices, live pane/ ruler metrics, an inline-diff length bound and source load-navigation flags. See General settings parity.

The Merge Colors page adds native light/dark foreground/background controls, selective defaults and shared palette updates across text panes, locator and whitespace rendering. See Colors parity.

The Encoding/Go To batch adds the source nine/ten-choice native format sheet in both viewers, atomic draft validation and source navigation bounds. See format dialog parity.

The native Merge Open dialog routes one/two standalone files, three-file merges and unified patches/clipboard bytes through retained file permissions. See Open parity.

The Merge Find/Replace family now uses native pane-local windows with the source search options, Count, Replace/Replace All and grouped Undo/Redo in both viewers. See Find parity.

The About family now has native app/tool windows with original attribution, selectable packaged runtime reports, source links and bundled license access. See About parity.

The target is complete behavioral parity, with native macOS windows and Finder integration. This first implementation establishes the architecture and common workflows. It does not represent the complete port or reproduce all upstream windows. No item is complete merely because its underlying Git command runs.

Format Patch's three export modes and no-prefix command are implemented in the repository layer with seven tests, including binary mail patch application. Its native dialog, live source-style progress and captured mail handoff have hidden native verification with system and packaged Git; physical UI, full Send Mail options and signed sandbox acceptance remain pending. See FORMAT-PATCH-PARITY.md for the audited controls and scope.

Configured Send Mail's View Patch action now opens the highlighted file in a read-only native unified-diff viewer, preserving its original bytes independently of the Send checkbox. Shift uses the alternate viewer setting; owned reads, missing-file recovery and close fencing have hidden native verification. Review and Apply now open independent native patch-review/serial-import tools with inherited file grants; real working-tree application and two-commit import have hidden native checks. Mail-client delivery, physical UI and signed grants remain pending. See Send Patch parity.

Direct mail now groups To/CC recipients by domain, resolves system MX exchanges, and submits domain-specific envelopes while preserving full MIME headers. Retries skip domains that already accepted the message; definite failures still permit later domains to receive mail, while ambiguous uploads stop failover. Cancelling a retry wait retains partial-domain acceptance. Format and Import use the native Send Mail options/progress route for direct as well as configured SMTP. Request Pull now uses that route with full ordinary document text and a custom subject independent of Combine One Mail. Focused core tests, hidden native route checks and the built SDK framework's private loopback queue passed. Public mail delivery, mail-client parity and signed/physical acceptance remain unverified. See Send Patch parity.

Mail-client mode now shares native Send Mail options for Format/Import/Request Pull and has a captured Apple Mail visible-draft adapter with separate To/CC and immutable attachments. The client now retains recipient display names and applies MAPI path-map attachment deduplication/UTF-16 ordering. Progress distinguishes draft preparation from actual mail delivery. Actual Apple Mail, signed automation and full mail-client lifecycle acceptance remain unverified. See Send Patch parity.

The Log’s Show branches this commit is on action now opens a native modeless reference dialog with containment filtering, original branch/tag artwork, one/two/ many selection menus, comparisons and owned Browse References/Log/Reflog pickers. Targeted Core and hidden native checks pass; light/dark content captures are on the website. Abort Merge progress now also has reviewed native control mappings. Synchronization has native outgoing/incoming graph and file tabs, reference changes, bounded transport output, separate checkout/fast-forward progress and Fetch & Rebase source choices. Shift+Pull/Fetch opens owned full options and refreshes results after dismissal. The backend covers nine source CLI actions; the native Compare Tags tab adds sorting, icon menus, confirmed tag actions and owned loading/command progress. Native Push variants and owned Shift Push options are implemented; project hooks, remaining controls, full visual matching and signed acceptance are still pending. See Synchronization parity. Across the 130 inventoried dialogs: 120 dialogs have recorded partial family audits and 10 await a family review. No dialog is certified complete. Of 1,659 static controls, 1,566 have recorded native mappings and 93 still await control review. These are audit-coverage counts, not a feature-completion percentage. See all dialog coverage. See the reference dialog audit.

Log commit ordering now has the source’s four-choice native sheet, deferred header entry, draft OK/Cancel, Return/Escape and saved Git walk preference. Core three-engine and native two-engine checks pass, including retained selection and owned sibling/modal close behavior. See the ordering audit.

Abort Merge now owns its Changed Files sheet and opens a separate Reset progress window, with mode-specific retry and cancellation through all owned reads. Hidden controller and key-equivalent checks pass with system and packaged Git; inspected light/dark content captures are on the website. Physical input, full progress options and signed acceptance remain pending. Reset output now streams through the shared bounded parser; the native selectable output adds original-icon Copy/Copy All, error and link styling, current-work/percentage presentation and a source-style completion footer with optional elapsed time. See the Merge follow-up.

Git configuration now has a native Settings page with scoped source views, identity inheritance, line-ending choices, three-state QuotePath/Prune and a separate save destination. Implementation is still in progress and has not been compiled or tested. Config editors and remembered sandbox directory grants are implemented; their displayed and signed execution checks remain in scope. See the Git configuration continuation and the unverified native Settings tree.

Audited baseline

Worktree creation, listing, locking, unlocking, removal and pruning now have a repository-layer port with disposable-repository tests. New Worktree has a native dialog and create routing with actual model verification. Worktree List and management menus now have native implementation and actual model verification; full native/signed acceptance remains pending. See WORKTREE-PARITY.md.

Upstream: https://github.com/TortoiseGit/TortoiseGit

Commit: 7338078f8ddd924b8cddee35f512f2286072136d.

The checked-in inventory covers 3,277 tracked entries and 130 dialog resources. upstream-files.csv maps paths, blob hashes, review status, replacement and notes. upstream-dialogs.csv lists dialog resources and captions, including the settings pages and helper applications. Gitlinks must be recursively audited before using those dependencies. Resources such as menus, icons, accelerators and strings also require review; a dialog count is not a count of all upstream UI.

Current integration verification

The historical 1cfadcc3 hosted run completed its Core stage with 2,489 tests, two skipped and two failures. The legacy failed-Pick receipt incompatibility has a focused two-method local repair pass, retaining all recovery guards. MaskBlt matrix rendering was under diagnosis at that checkpoint; later graphics family records above supersede that status. No complete current hosted pass follows from those historical scoped checks. Evidence records both failures.

A historical complete local SwiftPM suite passed 980 tests, zero failures, with one optional MX probe skipped, on October 11, 2026. The system Git 2.50.1 / Swift 6.3.3 process exited normally after 874.897 seconds. It covers the recorded Core checkpoint, including generated change-set comparison, but not native app UI. The later Sync Find icon/resource addition passed the three focused MenuIcon tests; the complete suite has not been rerun for that addition. See the complete Core checkpoint. Recent Sync native checks, unsigned builds and bundle audits have separate workflow records; these do not expand the Core result's scope. These checks do not prove full dialog parity, activated Finder behavior, signed sandbox execution, passing hosted CI on the latest source or App Store readiness.

Current component and workflow state — October 25, 2026

This consolidated table supersedes the old first-pass feature backlog. It uses implemented consumer paths and the dated family checkpoints linked below; “implemented” does not certify every upstream control, visual state, physical interaction or signed deployment. Full-port completion is not claimed, and the resource ledger is not a feature percentage. The newer family records at the top of this document retain failed attempts and the exact scope of later passes.

Architecture replacements

Connected workflows

Open work versus platform mappings

The connected Inaccessible repository workflow now has a native implementation: source-style Finder/command-line entry before adoption, unconditional typed libgit2 diagnosis, separate configuration-folder authorization and explicit exact-root trust, retained workspace/drafts, and owned Retry/Close/cancellation. The source anchors are TortoiseShell/MenuInfo.cpp:29–30, TortoiseShell/ContextMenu.cpp:964,1006–1011,1300–1301, and TortoiseProc/Commands/{InaccessibleCommand.cpp:25–77,Command.cpp:465–488}. Existing global/XDG entries are preserved; Retry reopens only the diagnosed root as an explicit native adaptation. The grouped checkpoint records 83 distinct focused Core passes, eight native case/engine pairs, and affected Finder/Settings source checks. Physical installed Finder/sandbox grants and complete source acceptance remain separate; this does not imply it was the only remaining workflow.

Confirmed implementation differences remain in the linked families; the table above is not an exhaustive missing-control inventory. Examples that must not be hidden behind acceptance language include raw-byte filesystem/history delivery beyond Browser's implemented identity-preserving inspection, provider-specific integrations outside the embedded adapters, recorded graphics/ encoding compatibility limits, and UDiff's explicit native entry behavior (no-input marker opens empty; stdin needs a switch; unmarked filenames are not a standalone mode in the combined app). The dated records distinguish deliberate native adaptation from unsupported behavior; none amounts to complete parity.

Acceptance is a separate workload: every source dialog/control and exceptional Git state, physical keyboard/VoiceOver/drag/focus, full visual comparison, current complete hosted CI, signed external grants/authentication, Intel/minimum OS and distribution/App Store archive/export/submission. Selected local/native/ installed passes do not close these global gates. No new test/build is required merely to update this state summary.

The older de753 hosted run reached 2,836 Core methods with two skips and two unexpected History Inspection failures. Their protocol fixtures were stale; the repair retains existing assertions and adds a strict malformed-revision case, with three focused methods passing in session 12430. See the hosted fixture repair. This is focused local evidence, not a complete latest hosted green run.

The pending resource ledger likewise is not a queue of ten missing user dialogs. Its ten currently pending resources are five Windows CrashServer dialogs, a Windows 11 context-registration dialog, testCache, a contributed example wait label, the Windows Plink login resource (native OpenSSH/askpass replaces it), and the dormant URL dialog with no active caller. Other unmapped controls include Explorer process/elevation/registry slots, drive-letter exclusions, hidden Cygwin/MSYS/animation and language-pack installer controls. The source's statistics file-changes-per-unit controls have inactive presentation updates; the shared patch-view editor already has native continuations. These bounded source findings need their mapping rationale, not invented active workflows. They do not excuse skipping genuine user-facing differences in partial families.

Porting method

1. Review a file and its related call sites, resource IDs, tests and documentation.
2. Record whether it is portable, requires a framework replacement, is an external dependency, or is Windows infrastructure with a documented macOS equivalent.
3. Implement its behavior in the named macOS module. Shared upstream logic can be retained as C/C++ where that reduces divergence; Windows UI is rewritten.
4. Compare native dialogs against upstream controls, options, defaults, shortcuts, error behavior and selection semantics. Preserve familiar workflow ordering and status colors while using macOS layout, menus and accessibility.
5. Exercise real Git fixtures for expected results and failure/conflict cases.
6. Mark a feature parity-complete only after all relevant source/resource mappings, behavior tests and UI acceptance checks pass. Platform exclusions need explicit rationale and a replacement or an acknowledged gap.

Every unreviewed file remains pending. The initial mapped command and dialog rows are marked partial, not complete. A broad Swift rewrite still needs this source-by-source audit; copying C++ files alone would not establish parity.

Verification records

Recent Add receiver checks and unsigned build/package results are recorded in Add history and Add missing-file comparison and Add current-column clipboard and Add unified diff and Add restoration copies and Add Revert and Revert progress table and Add index flags and Log search fields and Log subject and case search and Log filter selection and Log reference search and Log notes search and Log annotated-tag search and Log changed-path search and Log history cancellation. These checks do not establish full application parity, displayed-window acceptance, signed Finder activation or distribution readiness. Workflow-specific parity files record the remaining requirements.

Earlier validation milestones

The following records describe earlier milestones. Test and icon counts belong to those milestones; use the recent QA records for current validation scope.

swift test covers raw path parsing, renames/conflicts, stage/unstage including an unborn branch, multiline commits and log parsing, working-tree diffs, literal wildcard filenames, ignored files, linked worktrees, large output without deadlock, failure propagation, blank message rejection, directory badge aggregation and branch/tag/switch/merge/rebase argument compatibility with Git.

Manual UI checks on a disposable repository verified the branding, status list, selected-file diff and history. They also caught and fixed an absent shared-cache directory failure and a commit-layout issue that squeezed the file list.

The application, shared framework and embedded Finder extension compile using xcodebuild with signing disabled. These checks do not establish Finder activation, signed App Group access, accessibility, full UI correctness, credential prompts, Intel compatibility or upstream parity.

App Store preparation

Saved security-scoped repository permissions and a separate sandboxed AppStore configuration have been added. The runtime selector requires a bundled Git engine for that configuration. The pinned runtime build includes HTTPS helpers and source material. See DISTRIBUTION.md for runtime acceptance, signing, worktree permissions and license gates. These changes do not narrow the full-port objective or establish App Store readiness.

The following paragraph records early bring-up at 1b66080; its test/icon counts and local toolchain problem are historical, not current release evidence. Current feature-specific QA records live under docs/qa, and signed/hosted acceptance remains separate from local unsigned builds.

The early Swift package built and 78 tests passed, including topological graph continuity, root/merge/rename file statistics, annotated tag resolution, commit search, and decoding all 37 original upstream icons. Finder source type-checks with application-extension restrictions. The early local Xcode bundle build was blocked by a missing CoreSimulator.framework in the Xcode installation. Subsequent local Debug and AppStore bundle builds pass; that toolchain block is resolved. GitHub's macOS CI successfully compiled the app and embedded Finder extension in both Debug and sandboxed AppStore configurations at 1b66080. Bundle validation confirmed all 32 original icons, their hashes and license, the shared framework, and the embedded Finder extension in both configurations. The CI run also passed the 24 Swift tests. Signed Finder appearance remains unverified.

Finder requests now carry all selected paths as repeated URL fields, preserving literal filename characters. One security grant must contain every item; each item's containing repository is checked before replacing the current session or running a command. Mixed and nested repository selections are rejected. Selected folders expand to changed rows using path component boundaries. Finder Diff uses the requested paths even when no status rows exist, and Log accepts multiple path filters with a Show Whole Project checkbox. The commit dialog now keeps checked files separate from highlighted rows. Checkbox mode commits selected working-tree files; staging mode commits the index. Other upstream shell commands remain pending. New tests cover URL parsing, legacy requests, malformed input, directory selection, literal multi-path history, and clean-file diff isolation.

The Commit window now follows the upstream message-above-file-list arrangement, with category check links, original status icons, line counts, amend, author and sign-off controls. Its optional staging support uses native three-state checkboxes in the same file list. Git integration tests cover unchecked index preservation, unborn commits, staged rename/deletion, amend with no checked files, custom author, sign-off, partial index contents, and rejection by a pre-commit hook. A native UI commit on disposable sample data committed only README.md and left the unchecked Sources/Repository.swift change staged. Native staging checkboxes, mixed-state rendering, stage/unstage of an unversioned file and an index commit preserving later working-tree edits were also exercised on disposable sample data. The right-hand patch window now stages/unstages selected lines and hunks in tracked UTF-8 text files, with native UI and real Git integration verification. See COMMIT-PARITY.md for remaining parity.

Submodule conflict chooser now has native Base/destination groups and choice actions, with 167 passing tests and actual light/dark captures. See SUBMODULE-CONFLICT-PARITY.md for the remaining full-port requirements.

Resolve now matches upstream file-to-gitlink checkout and failed submodule removal Delete/Abort choices, with native Abort/Delete and recoverable Trash verification. Remaining type transitions, registered/multi-item removal and full progress still require audit.

Text merge source panes now align base removals, additions, conflicts and gaps with upstream light/dark colors and original source line numbers. The latest full suite passes 180 tests; alignment tests reconstruct exact source contents over exhaustive and seeded Unicode/CRLF cases. Actual native captures verify the palette and layout. Full libsvn segmentation parity, source scrolling QA and broader keyboard acceptance remain incomplete; see TEXT-MERGE-PARITY.md.

The text editor's source context menus now expose Use this whole file with undoable original-stage replacement. Native Mine/Theirs, keyboard Undo/Redo and unsaved-close Cancel are verified. Reload now exposes existing stage reload with original artwork and history reset; its native dirty prompt/Cancel are verified, while confirmed reload remains pending. Full source-block selection and upstream EOL handling are still partial.

The merge Reload prompt now includes Save before Reload. A real-Git regression test verifies Unicode/CRLF/EOF draft saving followed by conflict regeneration without changing unresolved stages or unrelated data. Native Save and Reload saved exact Mine contents; final view/history acceptance remains pending.

EOF conflict choices now retain original missing-final-newline metadata across saves, with five real-Git ending combinations and native combined-choice Save verification. Upstream EOL normalization and native CRLF/Undo/resolve coverage remain partial.

The text merge result now offers the upstream nine-style line-ending submenu with reversible conversion. A shared UTF-16 scanner fixes CRLF marker detection and caret line numbers. Native CRLF → LF, Undo/Redo and unresolved Save warning were verified; complete EOL/encoding metadata and exotic native combinations remain partial. See TEXT-MERGE-PARITY.md.

The text merge context menu now includes upstream leading tabs/spaces conversion and Trim right, with single-step Undo and conditional availability. Native conversion, Undo and exact Unicode/CRLF Save bytes were verified. Global tab-width preferences, EditorConfig and locale-specific Unicode trim remain pending. See TEXT-MERGE-PARITY.md.

The merge editor now has independent 1/2/4/8 tab-width menus in each pane. Native width changes preserved clean state and Undo history; merged-result conversion and Save bytes at width eight were verified. Global persistence, global insertion-mode preferences and EditorConfig remain pending.

Merge pane menus now include Tab/Space and Smart tab char. Native Space insertion, nearby-tab Smart choice, multiline Tab/Shift-Tab, Undo and exact Save bytes were verified. Global preferences, EditorConfig, precise partial-column selection restoration and broader key/view behavior remain pending.

Advanced Settings now has a native Name/Value editor for all 52 registered source settings, with source defaults, deferred Apply and blank-value reset. Most setting consumers, the complete settings host and native/signed acceptance remain pending. See ADVANCED-SETTINGS-PARITY.md.

The October 10 Abort Merge control audit maps its nine already-implemented native roles from pending review to partial. This is an inventory correction, not a new completed dialog: modal comparison, Quit/forced-close cancellation and separate options/progress windows still need work. See the owner audit.

Hosted Git runtime dependency order (October 11, 2026)

The macOS workflow now builds pinned universal Git before the Debug application and all tests that explicitly select the bundled executable. Previously the Synchronization and Log checks appeared before that build, which left their Git path absent on a clean checkout. The move preserves all other steps. Local ordering checks pass; hosted execution remains pending. The observed prior macOS job was queued with no assigned runner, whose cause is not yet established. See ordering verification and hosted limits.

Git/LFS deployment validation (October 11)

Hosted run 38160034341 passed the repaired universal graph build and then failed on the Git LFS deployment-target count. The old validator counted minos lines from default otool -l output across a universal file. The log does not include raw load commands, so the exact host-output cause remains unproven.

The replacement reads each architecture's Mach-O deployment command directly, accepting modern macOS LC_BUILD_VERSION and legacy LC_VERSION_MIN_MACOSX. It requires one target per slice, validates command bounds/platform, and enforces the pinned maximum macOS version independently. Publisher LFS provenance and dependency gates remain intact. Three regression tests and explicit per-slice otool comparisons for real Git/LFS pass, as does the full local Git runtime audit. Hosted Intel execution is still required; this is not a green CI claim. See the deployment record.

Implementation and validation cadence

The requested cadence is to implement a complete major port section before building and testing it. Small command groups and individual dialog edits are not separate validation milestones. Accumulate the related UI, menu, icon, backend, ownership and documentation work, then run a combined verification pass for that section. During implementation, read the pinned upstream source and review diffs; defer builds, native receivers, bundle audits and broad suites until the section is ready. Correct a concrete failure from that pass and rerun only the affected checks. Reuse completed evidence within its proven scope. Always close the owned test receiver and child processes when a check ends.

Shared Settings section, 2026-10-11

Implemented native host OK/Cancel/Apply with page-ordered draft participants for currently available pages, asynchronous Git/Remote saves, failure-page selection, input shielding during save and a termination guard. Dialogs/Commit no longer persist every click in this host. Color, font, viewer, history-limit and saved-data preferences participate; Unified Diff retains both subpage drafts. Standalone settings retain their local controls. Remote immediate actions remain immediate.

Validation was grouped after the implementation batch: Debug build passed and three focused Git configuration tests passed. No app/native receiver was launched and no full suite was rerun. Native workflow/visual/sandbox acceptance remains open; see qa/settings-history-batch-2026-10-11.json. This does not certify any additional inventory dialogs or the full port.

Dialogs 1/2 source continuation, 2026-10-11

Added working source Describe strategy/format/first-parent controls, optional asterisk message sections and abbreviated rename presentation. Split implemented Misc/Commit preferences into Dialogs 2 and isolated Message Editor extras; aligned Commit with the source shared history-limit key. This is the next major section in progress, with source/diff review only. Builds, tests and app launches remain deferred until the rest of this section is implemented. Remaining behavior and acceptance is listed in SETTINGS-NAVIGATION-PARITY.md; no inventory certification has changed.

Dialogs 2 behavior continuation, 2026-10-11

Connected remaining source Misc preferences to .mailmap display/clipboard, validated FETCH_HEAD picker entries and detached/new-branch checkout semantics, source Sync position sequencing, reversed native tag choices and shared operation sounds. Explicit raw amend-author reads prevent display mailmaps from changing author identity. Added source timeout/history Apply validation. Native sounds are enabled only by actual application startup, not headless logging installation.

This extends the same major Dialogs section without a new build, test or app launch. The next section work is persistent Log cache and Dialogs 3; combined validation follows implementation. Details and acceptance limits are in SETTINGS-NAVIGATION-PARITY.md. Inventory remains unchanged.

Log cache and Dialogs 3 backend continuation, 2026-10-11

Added persistent opt-in Log changed-file caching and its source checkbox, with configuration/tree/index/attribute invalidation, cancellation fencing, bounded atomic records and Git fallback on cache failure. Added all five Dialogs 3 project settings with source scopes/inheritance, .tgitconfig hierarchy, bare HEAD reads and source-ordered writes. Native page/editor integration remains in progress.

No build, tests or app launches were run for this continuation; validation stays with the whole Dialogs section. See LOG-CACHE-PARITY.md and SETTINGS-NAVIGATION-PARITY.md for implementation scope and open acceptance.

Development cadence and General/setup batch, 2026-10-11

Implement substantial feature sections before grouped validation. Repeat checks only for failures, meaningful subsequent changes or unresolved concerns. Close every app instance launched for testing. Avoid full-suite or UI relaunch loops between small edits.

The General engine preferences, update checking and five-stage First Start Wizard were validated together: Debug native build exited 0 and 13 focused Core tests passed. Compile failures were repaired within that checkpoint. No app was launched. Native, network and sandbox acceptance remains open; see qa/general-setup-batch-2026-10-11.json. Full-port certification is unchanged.

Credential settings implementation batch, 2026-10-11

Implemented scoped/origin-aware credential configuration, exact-file advanced writes/removal, simple helper choices with confirmed simplification, native source-layout controls, original credential icon, shared Settings Apply/Cancel and the First Start Wizard's owned Advanced credential sheet. Keychain Access replaces Windows Credential Manager. No build/test/app launch was run for this continuation; validation is deferred to the authentication-section boundary. See CREDENTIAL-SETTINGS-PARITY.md for current behavior and acceptance limits.

Authentication section checkpoint, 2026-10-11

Added the native SSH Key Generator using bundled OpenSSH and owned wizard/menu entry points, secure passphrase helper channels, exclusive key-pair publication and cancellable process cleanup. Validated together with the preceding credential settings batch: Debug native build exited 0; 17 focused Core tests passed. No app or full suite was launched. Remaining native/sandbox/source utility parity is recorded in SSH-KEY-GENERATION-PARITY.md and qa/authentication-settings-batch-2026-10-11.json.

Network settings implementation batch, 2026-10-11

Added source-layout Network controls, global proxy configuration and retained disabled drafts with Keychain password storage, custom OpenSSH bookmarks and validation, shared Apply/Cancel, actual Git process environment integration and the original source icon. No build, tests or app launch were run for this continuation; validation remains grouped with the next Finder-settings section. See NETWORK-SETTINGS-PARITY.md for behavior and remaining acceptance.

Finder overlay settings and Network checkpoint, 2026-10-11

Added source-grouped Icon Overlays/Overlay Handlers pages, original artwork, volume/path filters, handler suppression and unversioned/subrepository folder propagation. Direct overlay entries are cached independently of raw menu status; App Group preferences and notification reloads drive the extension. Validated with the preceding Network batch: native Debug build exited 0 and 22 focused Core tests passed. No app or full suite was launched. Remaining source/native/ signed acceptance is in FINDER-OVERLAY-SETTINGS-PARITY.md and qa/network-finder-settings-batch-2026-10-11.json.

Finder icon/index/menu continuation, 2026-10-11

Ported all 16 source overlay icon sets (144 original ICO files and per-set notices) with native List/Symbols previews and shared Apply/Cancel selection. Finder reloads all nine badge images on set changes. Main/submodule snapshots now retain Git skip-worktree and assume-unchanged flags, with source normal-state precedence and handler toggles. Subtree refresh clears stale flags and preserves independent repositories. Known roots retain versioned menus despite aggregated untracked or ignored status; untracked files keep Add eligibility. One grouped native build exited 0 and 34 focused tests passed, zero failures, with no app launch. Native Finder/UI/signed acceptance and complete source certification remain open; see qa/finder-icons-batch-2026-10-11.json and FINDER-OVERLAY-SETTINGS-PARITY.md.

Context Menu settings continuation, 2026-10-11

Added the two upstream Context Menu pages with all 55 source list entries, original command icons/labels/64-bit IDs, page-specific defaults and one shared Apply/Cancel draft. Implemented commands can move to Finder's main menu, stay in the TurtleGit submenu or require Shift. Hide-unversioned and source-specific path exclusions now apply before command capture, including mixed selections. Grouped Ignore/Bisect/Merge commands share source preference IDs; empty submenus are omitted. The toolbar remains flat. Advanced icon preferences preserve saved menu policy and stale page drafts re-read the current icon choice on Apply. Unavailable Finder commands and drag-menu integration remain explicit. See CONTEXT-MENU-SETTINGS-PARITY.md for the source comparison, validation and remaining native/signed acceptance. The full port remains incomplete.

Finder command and native Settings ownership continuation, 2026-10-12

Added eight source menu entries and their original clauses/order/icons: Sync, previous-version Diff, parent gitlink Log, Blame, conflict editor and application Settings/Help/About. Previous Diff uses source path-history semantics and immutable directory comparison/patch scope. Submodule-folder Log revalidates registration and authorizes the parent. App/Finder Settings now share a native property-sheet owner; global requests suppress local config sources and known-repository requests retain normal authorization. Dirty/busy context switches retain existing drafts. The source catalog now exposes 47 groups; eight commands remain unavailable. See FINDER-COMMAND-HANDOFF-PARITY.md for grouped evidence and remaining physical/ signed acceptance. The full port remains incomplete.

Finder LFS and mail continuation, 2026-10-12

Added source LFS group and its three inner actions using cached marker metadata, original icons, shared placement/Shift policy and fresh literal versioned-file preflight. Existing LFS results/Force/cancellation/Pull/Quit flows now support a standalone progress owner. Send Mail launches the native composer outside Git with file/root grants and an exclusive owned global-sender context; opening it does not submit mail or change the active checkout. Outside-repository Review/ Apply chooses a target working repository with owned-sheet/late-reply fencing. The catalog exposes 49 groups; six remain unavailable. Native LFS/mail receivers now compile once and run together. See FINDER-LFS-MAIL-PARITY.md for exact source, validation and remaining signed/physical/patch-review acceptance.

Git daemon batch — 2026-10-12

Daemon now uses the upstream warning/remember-choice and serving defaults, with a native progress window, URLs, bounded output, cancellation and process-tree cleanup. App and Finder commands share one window per root, including bare repositories, source icon/conditions/order and menu preference mapping. The catalog now exposes 50 of 55 groups; four SVN groups and Review Patch remain unavailable. Incoming-network entitlement is configured, with signed sandbox, physical layout, firewall and LAN/IPv6 acceptance still open. See DAEMON-PARITY.md. Validation is grouped after the complete implementation batch, using loopback-only real Git serving and native receiver fixtures; no installed app or Finder extension is activated.

Single-patch review and directory-target batch — 2026-10-12

The missing Review/apply single patch Finder group now routes to native owned patch/target choosers and the existing before/after editor without adopting a repository or applying on launch. Source artwork, single-file/Extended clauses, placement before Send Mail and shared menu preferences are retained. Directory mode supports plain targets and nested Git folders, anchors patch paths via disposable administration, preserves the real index during application and avoids initializing Git in ordinary folders. Edited new files auto-add only when the target is a Git working tree. Outside-repository Send Mail Review uses the same workflow; serial import still chooses a working Git repository. The Finder catalog now exposes 51 of 55 groups; the four SVN groups remain unavailable. Full clipboard/path-guessing/TortoiseGitMerge behavior, physical layout and signed acceptance remain open; see REVIEW-PATCH-PARITY.md.

SVN workflow/runtime batch — 2026-10-12

All four remaining Finder groups now have native routes: source DCommit radio/ remember/stash flow, Fetch with captured Diff/Log, source fetch/fast-forward/ Rebase handoff and both Ignore destinations. The common svn/.metadata marker is cached with backward-compatible decoding, exact source clauses/order/icons and original preference masks. The catalog now has implementation routes for all 55 groups; this does not certify full application/dialog/Finder parity.

The previously disabled git-svn stub is replaced by a relocatable universal dispatcher and private per-CPU Perl/Subversion/Serf/OpenSSL runtime, with pinned sources, notices, reconstruction, hashes, contained dependencies and macOS 13 deployment. Real private file:// clone/fetch/dcommit/ignore validation passed with build-prefix fallbacks hidden. CI builds the interpreter component on Apple Silicon, transfers a permission-preserving tar payload, and retains the Intel main test job. Remote CI, signed inheritance/trust/credentials, physical dialog matching and release review remain open; see SVN-PARITY.md and GIT-SVN-RUNTIME.md.

Clipboard patch and target-matching batch — 2026-10-12

The diff viewer copies original patch bytes into native/legacy custom formats, and File → Review Clipboard Patch captures that snapshot before its owned target chooser. Single-patch preparation now follows the upstream current/ancestor/ immediate-child/directory matching order and strict one-third threshold, with Suggested/Selected/Cancel confirmation and permission-bounded searches. Git headers use p1 and plain unified paths p0. Preflight cancellation/late-reply fences retain the existing target grants and Quit ownership. Remaining Open accessory/Finder clipboard/format/physical/signed gates are recorded in PATCH-CLIPBOARD-TARGET-PARITY.md; the complete port remains active.

Development cadence requested by the user: implement substantial connected feature batches before validation. Run one relevant grouped validation pass at the batch boundary; repair actual failures with focused checks. Do not repeat broad suites after successful checks without new changes or unresolved evidence. Reuse native receiver compilation where possible and retire all test-owned windows/processes when verification ends.

Merge regex filters batch — 2026-10-12

The native filter-list and Name/Regex/Replace editor dialogs now connect to two-pane comparisons, window-local filter selection, the bundled ECMAScript replacement engine and original light/dark green filtered-row colors. Comparison keys are separate from original source bytes and writable drafts. The complete batch includes persistence/cancel, validation errors, cancellation, stale-reply fencing, annotation remapping and owned-dialog cleanup before grouped checks. Three-pane filtering and complete source/signed acceptance remain open; see MERGE-REGEX-FILTERS-PARITY.md.

Subversion merge engine foundation — 2026-10-12

The pinned Subversion diff2/diff3 APIs now have a universal native adapter, typed Swift source ranges, optional ECMAScript keys, original line retention, bounded cancellation/output validation, source/license reconstruction and app/CI build integration. It shares existing GitSVN libraries. Twelve focused Core tests and actual embedded arm64/x86_64 loading passed after implementation. Current editor alignment and Git-generated result text are not switched yet; that integration and resolved conflict children remain necessary work for source parity. See SUBVERSION-MERGE-ENGINE.md.

Three-pane engine and regex integration — 2026-10-12

Native conflict preparation now consumes Subversion ranges for source rows and result generation, preserving original Mine/Theirs text, removed Base rows, one-side gaps and filtered green rows. Window-local regex choices regenerate only through the dirty Save/discard/Cancel workflow. Native Undo, successful reload history reset, Save-before-Reload, explicit resolution and preparation Close cancellation passed after a complete implementation batch. Core snapshots retain engine source rows across saves; staged/working/HEAD checks pass. The older Swift compiler's Remote Settings nested-defer actor error from CI was repaired. Resolved children, two-pane conversion and physical/signed acceptance remain open. Offscreen capture omitted SwiftUI toolbar text; those images were rejected.

Two-pane engine and editing integration — 2026-10-12

Two-pane ordinary/filtered comparisons now request Subversion ranges while retaining immediate native editing coordinates. Debounced requests cancel stale work, preserve source selections and remap annotations before publishing the authoritative result. Transfers/navigation/inline diff wait for completion; engine errors clear alignment instead of silently using the projection. The batch includes native typing, Unicode selection, Undo/Redo, marked Save and encoding/EOL preservation checks. Source-engine resolved children, full options, complete captures and physical/signed acceptance remain open.

Resolved-child metadata and source padding — 2026-10-12

Protocol 2 exports Subversion's resolved children with their parent IDs and validates side partitions, containment and repeated parent Base ranges. The source rendering follows DiffData.cpp's first-child padding rule; parent result blocks remain unresolved, including shared child lines. This corrects the earlier assumption that the source split those parents into smaller resolved results. Original numbered lines and block choices are preserved. Full source option, segmentation, physical/signed and visual-capture acceptance remain open.

Comparison options and settings batch — 2026-10-12

Both comparison workflows now expose source whitespace choices, Ignore line endings and Ignore case, with saved defaults in Merge Editor settings. Defaults retain source IgnoreEOL=true, case-sensitive and compare-whitespace behavior. Original text/encodings stay separate from normalized keys. Three-pane changes use the dirty reload transaction and persist only on success; two-pane changes preserve drafts and recompute with existing cancellation/selection gates. Comment profiles, Unicode locale equivalence and physical/signed acceptance remain open; see MERGE-COMPARISON-OPTIONS-PARITY.md.

Comment profiles and comparison batch — 2026-10-12

Pinned original profiles, extension precedence and the source UTF-16 comment heuristic now feed comparison keys before regex/whitespace/case conversion. Both viewers expose Ignore Comments only for supported extensions. Original text/bytes and existing dirty reload/save/Undo flows remain separate. Core and combined native checks pass after the connected implementation; original profile packaging is verified. Source quote limitations are documented, with bounded cancellation added. Overrides and physical/signed acceptance remain open; see MERGE-COMMENTS-PARITY.md.

The two-pane Merge viewer now has a source-style Line Diff Bar: saved visibility, Base/Mine pointer preview, forced inline/whitespace colors, original EOL markers and horizontal-scroll alignment. See Line Diff Bar parity. Physical whole-window layout and docking acceptance remain open.

Merge General's source Misc/Diffing grouping and signed patch-context setting are now wired to the two-file Create patch file workflow, native File command and owned Save panel. Git no-index output retains saved bytes/modes and quoted comparison names, independently of unsaved drafts and display filters. See Create patch parity; General and Colors remain partial.

Merge Colors now has all 17 source color channels with native wells, Automatic/More colors menus, selected-channel/palette restore, independent Light/Dark drafts and shared Settings Apply/Cancel. Owned color panels release on page/window closure and fence late actions. See Colors parity; physical/full-page acceptance remains open.

The combined Merge view now projects source removal/addition ordering into one native editor with Mine edits, removed-row payload retention, Save/Undo/Redo, mode-switch dirty prompts, a saved General default and combined locator/navigation. See one-pane parity for state/menu/physical acceptance that remains open.

The one-pane context menu now follows the source left-view role. Hidden-opposite transfer operations are gated, right-view mark actions are omitted, and clipboard commands retain their own pasteboard/editor context. Source-ordered encoding menus dispatch by format identity. See context parity; physical popup/full-menu acceptance remains open.

Merge General's Default to UTF-8 control now shares the source detector with completion scanning and feeds two-pane, Git conflict and standalone three-way loads. Legacy Windows-1252 input can load/save losslessly; generic Core callers retain their original detection defaults. See default encoding parity for locale/malformed and remaining load-caller acceptance.

Merge viewers now provide saved long-line wrapping, native width/font/tab reflow, horizontal-scroll gates and shared wrapped heights across aligned source rows. Combined/result panes retain logical editing offsets. See wrapping parity; full result-row alignment, unchanged-section collapse and physical/large-file acceptance remain open.

Network settings now have grouped native verification of private real Git writes, credential-cache boundaries, source-ordered partial failures and Settings validation/Cancel. Forced deactivation no longer reactivates after Apply, and late reads cannot touch the password cache. The Network resource is reviewed as a partial native replacement; production Keychain/physical/signed acceptance remains open. See Network parity.

Credential settings now retain destination-only draft edits and restore the scope on Cancel. Captured saves and read/selection responses are fenced on retirement; Settings Apply does not reactivate a closed page. Private native receivers passed with system and bundled Git, covering helper resets/chains, scoped copy, confirmation choices, Remove, None and lifecycle. The Credential resource is classified as partial; physical layout, production Keychain and signed acceptance remain open. See Credential audit.

Advanced external tool associations now use a native AppKit table with sorted Extension/Program columns, visible argument templates, double-click Edit routing and source-style next/previous selection after Remove. Diff/Merge parent settings share an explicit draft/validation/persistence model. Private native checks cover association editing and shared Settings Apply/Cancel; actual receiving-app launch, Windows-script replacement, exit-code trust and signed grants remain open. The Advanced, association editor and Merge Tool resources are partial replacements, not certified complete. See Tool settings audit.

Blocking external Merge launches now own their wait/confirmation lifecycle. Caller close and cancellation release TurtleGit's wait, preserve the external application, and fence late Mark Resolved responses. Private native checks with both Git engines verify exact working-byte staging and stale-stage refusal. Actual external app/KVO/signed acceptance remains open; see the Tool audit.

Overlay settings now scroll within small native hosts; handler rows use the selected source icon set. Shared draft validation, publication and unsigned notices have private native acceptance across all three pages. Publication failure retains the draft without saving local preferences or notifying Finder. Icon Overlays, Overlay Handlers and Icon Set are partial native replacements; signed extension refresh, mount handling and full physical layout remain open. See Overlay settings audit.

Email Settings now has explicit model ownership in the shared Settings host; credential work blocks page switches/dismissal and app Quit. Forced host retirement invalidates its model, fencing late credential responses. The existing private Email receiver now joins the object-linked group and additionally checks shared Apply/Cancel/busy validation and Quit gating. Email is a partial native replacement; real Keychain, physical credential sheets and mail/signed acceptance remain open. See Email audit.

Commit progress now includes the source's conditional SVN DCommit action before Push/Pull/ReCommit/Create Tag for git-svn metadata. Its callback preserves the Commit repository/access context through the native SVN workflow. Both-engine private commit checks passed, including once-only selection and the existing cancellation/cleanup cases. Actual SVN submission, receiving-window/scoped grant acceptance and physical menus remain open; see the Commit audit.

Hosted run 38267892128 failed in the grouped comparison receiver after reference folders passed. The Comparison/Fetch/Create Branch fixture audit corrected incomplete PID publication and added bounded failure cleanup while retaining the original assertions. All three focused families passed with both Git engines; newer CI remains unverified. See the Reference Browser audit and scoped QA record.

SVN workflows now freeze retired presentation and own their prompt/cancellation lifetimes. Scoped window checks retain the Commit repository/executable/lease under a different busy workspace and cover options reuse/conflicting operations. Final private native checks passed with both Git engines after correcting an initial fixture URL-equality assertion. Actual SVN authentication, physical UI and signed App Store acceptance remain open; see the SVN audit.

SVN progress now shares the native styled output/control family with Commit and Merge: links, colored prefixes, completion metadata and original-icon copy menus. Actual native log checks with both Git engines cover private clipboard behavior, light/dark warning colors and error/Retry state, alongside the existing SVN workflow checks. Physical/signed/public SVN acceptance remains open.

The Bugtraq Regex Tester now has a native editable sample, source-order Message part/Bug-ID fields, C++ ECMAScript highlighting and OK/Cancel expression return. File → Bugtraq Regex Tester opens the utility with current repository expressions when available; it does not write configuration. Invalid edits retain the last valid expressions for styling current text. Owned debounce/helper work is fenced against editing/closure and counted for Quit. The dialog is a partial replacement; the full Issue Tracker configuration page/parent Apply integration and plugin providers remain open. See the issue audit.

Settings → Issue Tracker Config now ports the source scope selector, BugTraq fields/inheritance/booleans, provider metadata and Save-to control. It owns the Regex Tester; tester OK edits the page draft, shared Apply writes the selected configuration and Cancel restores unsaved values. The original Bugtraq icon is bundled with provenance. Focused Core and native checks passed; provider execution, physical/signed acceptance and Windows association adaptation remain open. See Issue tracker audit.

Reviewed compositor captures now document Issue Tracker Config and Regex Tester in both themes on GitHub Pages and README. The page uses a dedicated native host with shared footer, not the complete Settings navigation window. Source field/ group order was compared with the pinned screenshot/resource; full physical and signed parity remain open. Visual review corrected repeated placeholders in empty fields and refreshed the captures after a passing Debug build. Core/behavior suites were not rerun.

Autotext Tester

The native content/regex/Scan/results/timing/Exit workflow and owned Settings entry point are implemented. It uses the original C++ capture engine. Physical and signed acceptance remain open. See Autotext audit.

Client Hook Scripts

The native Hook Scripts list and configuration dialog retain source controls, with the original hook icon, global/project persistence, shared Apply/Cancel and per-user repository-script approval. Owned execution is connected to the six Commit/Push/Rebase boundaries and non-wait scripts remain cancellable through File. Focused Core/native checks pass; alternate routes, precise source edge cases and visual/signed acceptance remain open. See Client Hooks audit.

Clean now owns manual folder authorization and fresh Retry, refuses duplicate options submissions and cancels retired progress workers while retaining their Quit/grant lifetime. Debug and six grouped native cases passed. Automatic access discovery, durable additional grants and physical/signed acceptance remain open. See Clean audit.

Both comparison editors now expose saved Collapsed view, source-context folding, marker expansion and reveal-before-navigation without rewriting editor text. Three-pane result expansion uses exact engine anchors retained in edit/Undo presentation. Debug, 39 focused Core checks and a grouped native folding/wrapping/ editor receiver passed. Physical, VoiceOver, large-document and signed acceptance remain open. See folding audit.

Native File/Open now checks Save/discard/Cancel and replaces two/three-pane content in the same window, retaining its geometry and ownership. Scoped Open/ Reload menus, duplicate/Close/Quit guards, independent pending Save lifetime and identity-safe cached callers accompany the replacement. Debug and grouped native Open/editor regressions passed after a frame repair and fixture window-lifetime repair. Patch mode still opens the separate native Review/Apply workflow; physical/visual/signed acceptance remains open. See Open audit.

File/Open patch mode now prepares and checks Review/Apply before replacing the same native editor window; invalid patches/cancellation retain the original. Review/Apply can Open back into comparison with existing dirty Save handling. Scoped menus, shared keyboard ownership and preparation Close/Quit guards cover the round trip. First Debug and grouped native patch/Open checks passed; Core was unchanged. Physical/signed/full-source acceptance remains open. See the Open patch follow-up.

Three-pane Save As now offers left/right/result, with source row inclusion, encoding and owned export handling. Compare either source with Base opens a separate native comparison of private read-only stage snapshots. Debug, 16 Core checks and grouped native source/editor checks passed; source path rebinding, physical/visual/signed acceptance remain open. See source tools.

Create Patch Serial now uses source no-tag Browse References and entered-revision single-selection Log pickers, captured folder/range ownership, cancellable initial and unified reads, source count limits and private viewer preferences. The connected options/progress/streaming family passed grouped system/bundled native checks and 30 affected Core cases (plus the changed no-tag case recheck). Physical and signed acceptance remain open; see Format Patch.

Request Pull now owns its Start Log/options and closes cancellable branch, validation and generation processes before ordinary retirement. Forced closure fences generated documents and retires mail options while preserving operation accounting. Its source End/URL presets also flow through authorized macOS action links into editable native inputs. See Request Pull for grouped evidence, command-link syntax and physical/signed acceptance limits.

SSH key file permissions now have a user-facing Saved Data manager alongside saved passphrases: inspect paths without reading keys, authorize, copy and confirmed selected/all forgetting with stale snapshots and owned native panels. See SSH identities. Core CI also skips the duplicate SwiftPM UI-executable build through an opt-in manifest mode; full Xcode app/native checks remain in the workflow. The package graphs retain identical Core tests, resources, SMTP and revision utility targets. Hosted execution is still pending.

The hosted Merge Find timeout in 583a6534 was reproduced and repaired in its fixture: unresolved aligned placeholder rows are now checked before selecting both sides and exercising the original three-match Find/Replace/Undo assertions. The isolated native phase passed; this is not a full hosted CI pass. See the repair record.

The older hosted run at 78bcdd06 failed its small Settings footer containment check after passing the build/Core and earlier native steps. The native page/footers now reserve explicit control-frame space; the original assertion plus a stricter margin check passes locally, with six refreshed light/dark captures. Hosted verification remains pending. See the scoped repair.

LibreOffice document workflow — October 16, 2026

The bundled LibreOffice family now provides source UNO tracked-change comparison and mine/theirs merge, literal private inputs, isolated profile/runtime ownership, Settings associations and native Save As/ resolution flow. Live LibreOffice and signed sandbox acceptance remain open. See grouped evidence for exact checks, repairs and limits.

Merge menu lifecycle and source accelerators — October 16, 2026

The connected native menu batch restores detached application/submenu contributions, defers structural changes while menus track, and adds source block/navigation and selected-text search shortcuts through existing checked commands and Undo. See menu parity and grouped evidence. Toolbar fading remains a visual defect; enabled/full-opacity image diagnostics and public redraw/reset attempts did not resolve it. Full physical menu, accessibility and signed acceptance remain open.

Merge typing family — October 16, 2026

Insert/Overwrite and current-row endings connect native typing, caret/mode feedback, source keys and Edit commands, exact row/Unicode transformations, combined-view materialization and existing Save/Undo ownership. Ctrl-M exposes existing comparison marks. Grouped evidence and remaining physical input, appearance and signed limitations are recorded with that family.

Native patch file panel — October 16, 2026

The connected panel batch ports source selection, explicit preview, native context/keyboard actions, captured-menu lifetimes, file state presentation and hiding/restoration. It uses the existing owned per-file application and comparison flows and shares the Merge main-menu owner. Initial failed-hunk/conflict counts and complete patch-engine/source acceptance remain open.

Recorded-base patch recovery — October 16, 2026

The connected recovery family ports versioned-base preparation, initial per-file classification, embedded Subversion merge/native toolbar, guarded resolved Save and clean batch continuation. Missing-version and special-file recovery, complete physical/signed acceptance and full port certification remain open; the dated record distinguishes checks and repairs.

Special-file patch recovery — October 16, 2026

Recorded-base recovery now prepares binary bytes, symbolic links and absent endpoints. The existing native review window presents exact Current/Patched choices, side previews, original action icons and scoped shortcuts, with owned deletion confirmation and operation/retirement fences. The shared guarded save validates all captured endpoints; batch application leaves these conflicts for explicit choice. See special-file recovery.

Merge save ownership and read-only targets — October 16, 2026

Normal Compare and three-pane Save now redirect read-only outputs into an owned Save As flow, retain the dirty draft on Cancel/failure and bind later saves and backups to the selected target. Repository conflict copies preserve the original index and disable resolution of a different target. Marked/empty/unresolved save questions and output panels share cancellation and forced-retirement fences; late choices cannot write or publish stale errors. PatchSave keeps its distinct no-backup/zero-line deletion semantics. See save workflows.

Editor save folder scopes — October 16, 2026

Compare and Merge normal saves, read-only and explicit Save As, source/result exports and unified patch output now share owned containing-folder authorization in Store builds. Existing and related scopes are reused; file-only/sibling grants do not authorize temporary/backup siblings. Cancellation and retirement retain operation ownership while refusing late grants and writes. The unsigned injected scope checks cannot certify signed sandbox acceptance. See save workflows.

Commit native command family — October 16, 2026

Commit now exposes owner-scoped native commands with source action icons and live checked/enabled states, current-action Control/Command-Return and dedicated macOS ReCommit/Commit & Push shortcuts. Source Shift-check category direction applies to checked files and staging; issue-field Return requests message focus. Sign-off identity reads share owned cancellation/Close/Quit and late-retirement gates. Menu repair and installation epochs reject detached/background targets. See Commit parity.

Private SSH lifecycle and replacement — October 16, 2026

The connected agent/transport batch replaces stopped sessions and reloads cached identities, validates the real socket, drains concurrent closure and terminates owned helper descendants on normal exit. The observed hosted credential-loading marker race is repaired through atomic readiness publication with all original cleanup assertions retained. See agent lifecycle and transport ownership. Full hosted and signed acceptance remain open.

Blame commands and native Go To — October 16, 2026

The connected Blame navigation batch supplies source F3 and Control aliases, native Command conventions, F6 source/Log focus across docked/tabbed/floating panes, shared menu availability and an owned native Go To Line sheet. Validation, Cancel, accepted focus and forced closure use the actual document lifetime. See Blame parity for source references and remaining physical/signed acceptance.

Resolve interaction family — October 16, 2026

Resolve now accepts same-worktree file/folder drops, coalesces scoped status reads, rechecks dropped conflicts and preserves manual unrelated checks. Owned provider reads, Close/Cancel/Quit and source F5/Control-Return share existing lifetime guards. Conflict-resolution parent list refreshes now consume the source Advanced preference. See Resolve parity for source behavior, native adaptations and remaining acceptance.

Resolve captured file actions — October 16, 2026

Resolve now connects history/Blame, ordinary/submodule handoffs, Open/editor/Finder, two-file and unified comparison, and shared clipboard formatting through a one-use conflict-stage snapshot. Open With owns its native panel and validates after the choice; parent closure retires associated unified viewers. The source conflict group remains first. See Resolve parity for exact scope and still-missing mutation/physical/signed acceptance.

Resolve mutation continuation — October 16, 2026

The source Revert/missing-mark Delete family now connects native confirmation, shared progress/retry, exact conflict and HEAD validation, Trash/permanent index updates, actual post-operation list reads and the submodule comparison handoff. Captured selection marks are observed within the owning table and retired on Close. See Resolve mutations for remaining action-mask, physical and signed acceptance.

Merge line-change margin family — October 16, 2026

Original added/removed/conflict/ignored/edited/equal/whitespace artwork now connects to two/combined/three-pane view records and live history. Source bounded whitespace-block classification, marked-before-moved priority, hover labels and icon-only margins are retained. See Merge margins for source limits and remaining physical/signed acceptance.

Merge gutter interaction family — October 16, 2026

Native margin click/Shift/drag now keeps active text selection and peer row boundaries distinct across comparison and aligned conflict panes. Wrapped entry, fold/move double-click, autoscroll capture, stale/sheet rejection and owner cleanup share the existing navigation/editing lifetimes. See Merge margins.

Comparison final-record family — October 16, 2026

Two-pane comparison now restores the source NoEnding final record for empty/ended files, including Added/Removed and first-trailing-gap placement. Combined view excludes the source’s two-pane-only record. Original line coordinates, encoded output, input/history and block-transfer ending repair share the existing owners. See EOF records for source rules and remaining acceptance.

Reference browser presentation family — October 16, 2026

Source column controls now retain order/width/visibility, owned reset confirmation, sizing and sort state; native splitter/filter alignment persists across browsers. Window-scoped filter/list/F5/F2 behavior uses the existing captured-reference and inline-rename paths. See browser presentation.

Image pointer navigation family — October 16, 2026

Ported source Ctrl-wheel scale with pointer anchoring, linked origin handling, Shift-drag isolation, unlinked border snapping and independent overlay-image panning in alpha/XOR. Native input now shares the owning comparison/conflict operation/sheet/retirement gates; replaced frame/scale/layout retires a drag. See image comparison parity and batch evidence. Physical and signed acceptance and full application parity remain open.

Image drop and information family — October 16, 2026

Per-pane native file-URL drops now follow the source first-file preview rule, including unsupported image content. Owned asynchronous reads retain scoped grants and Quit accounting, fence late replies and disable competing actions. Conflict drops preserve the source's original Select bytes and explain the preview distinction. Shared metadata/tooltips now include zoom and both overlay inputs. See image comparison parity and batch evidence. Physical Finder drops and signed sandbox/App Store acceptance remain open.

Log selection-history navigation family — October 16, 2026

Connected source Back/Forward/select-versus-highlight, side-button, Jump and clipboard-hash routes to the native window. Navigation preserves the history cursor/future; manual selection branches it. Native text-editor and active-window ownership gates retain normal editing, and hidden targets preserve selection. See Log parity and batch evidence. Physical input and signed acceptance remain open.

Repository Browser presentation family — October 16, 2026

Moved divider persistence into the owning browser preference domain with native restore/clamps and retired-observer fences. Header choices/default Reset now follow ColumnManager; single-use popup/layout/generation captures reject stale actions. Native Ctrl/Cmd list aliases, active-window F5/Enter and folder-copy ownership complete this connected presentation batch. See Browser parity and batch evidence. Physical and signed acceptance remain open.

Revert planning family — October 16, 2026

The Revert file-selection window now connects shared original-icon file menus, comparison/export/application handoffs, native sortable/persisted columns and source default checks. Atomic owned reads, coalesced same-repository drops, confirmed context Revert/recovery children and related-dialog refresh replace its older standalone handling. Planning, retained progress and shared file-menu checks pass on both Git engines within the recorded repair scope; all owned receivers are closed. Full source masks, visual/physical and signed acceptance remain open. Batch evidence. See Revert planning parity.

Revert saved-file command family — October 16, 2026

Revert now adds the source-enabled Save As/Mark/Compare commands, Finder mark/grant import, owned save-panel/copy cancellation and captured column clipboard targets. Original list-background artwork follows the current native viewport and source preference. Working Tree/Commit/Resolve keep their source-disabled menu masks. The Debug build, three icon checks and six native case/engine runs pass after the recorded fixture correction. Light/dark captures are reviewed and published; all owned receivers are closed. Full gitlink, physical and signed acceptance remain open. Batch evidence. See Revert saved-file commands.

Prepared and renamed submodule comparison family — October 16, 2026

Revert's marked gitlinks now use the native Submodule Diff route with the source index-to-checkout baseline, file-only Save As and mixed-target rejection. Old tree paths survive Changed Files/Rebase/shared historical handoffs and staged direct rename discovery. Native From (Index), rename headers, owner-scoped F5 and common preferences connect the existing Log/Compare/Update lifecycle. Seventeen Core cases and six native case/engine runs pass; two affected prepared and two Browser presentation runs pass after display/compiler repairs. All owned receivers are closed. Light/dark captures are published; exhaustive gitlink/copy cases, physical and signed acceptance remain open. Batch evidence. See Submodule Diff parity.

Native file-list refresh and input family — October 16, 2026

Commit full/incremental staging, Working Tree and Revert now connect successful reads to actual native viewport/selection/focus settlement. Source position preference, scope reset, filters, file-only Select All and newer reading intent share owned cancellation. Working Tree includes LFS in atomic table publication; full Commit reloads retain post-retirement Quit/access lifetime. Eight grouped native case/engine runs pass; all eleven owned receivers were reaped and absent. Physical, complete metadata-pipeline and signed acceptance remain open. See the evidence. See file-list refresh parity.

Comparison common-record and interval family — October 16, 2026

Engine-captured options now drive two-pane common-row visibility. Combined common records retain Mine payload/Base EOL, distinct from each side's input bytes and encoding; editing/export uses that captured layout. Moved-block display joins contiguous modified intervals before pairing and preserves original move plans. See source rules and acceptance limits.

Seventy focused Core checks and all four grouped native workflows pass. The four owned receivers were reaped and independently absent. See batch evidence for scope and limits.

RefLog native command and header family — October 16, 2026

Scoped source/native shortcuts and keyboard/accessibility row popups now share the owning RefLog command gates. Popup sessions consume once, expire across model refresh/replacement and capture tool modifiers. Header Reset owns its Yes/No question and lifetime, keeps Hash visible, restores defaults and preserves native selection/reading position. See source mapping and limits.

Twelve native case/engine combinations pass after the recorded fixture repairs. All sixteen owned receivers, including failed attempts, were reaped and absent. Core sources were unchanged and its suite was not repeated. See batch evidence.

Clone completed-command and history family — October 17, 2026

Clone now separates transport success from later SSH-setting warnings and opening failures. Successful warning results retain Log/Finder actions for review; opening retries cannot reclone a populated destination. Native histories support exact saved deletion and source submission timing after read-only validation. See source rules and acceptance limits.

Twenty distinct focused Core cases and eight grouped native case/engine runs pass. The Core fixture repair and private cleanup are recorded; all eight owned receivers were reaped and absent. See batch evidence.

Connected Clone/Submodule Add inputs — October 17, 2026

Source clipboard defaults and first-history fallback now enter new dialogs from captured application input. Submodule Add shares bounded native deletion across its source/path/key histories, exact source filename derivation and captured-draft picker acceptance. Closed/replaced pickers refuse late folder/key replies and controls inherit private preferences. See source comparison and limits.

Six distinct native case/engine combinations and sixteen focused Core cases pass. The affected capture recheck, compile/runner repairs and owned cleanup are recorded in batch evidence. New reviewed light/dark Submodule Add frames are published in the gallery.

Clean metadata preparation family — October 17, 2026

Clean now prepares external Git/common/object access before parent and recursive checkout reads, reuses compound workspace grants, and carries the same preparation through full pre-removal revalidation. Required native pickers share cancellation, retirement/late-response fencing and operation-scoped grant/Quit ownership. See CLEAN-PARITY. Thirty-eight distinct focused Core cases and eight grouped native case/engine combinations pass after two fixture/runner repairs. All ten owned receivers were reaped and independently absent. Signed/physical and complete upstream acceptance remain open; see the batch evidence.

Complete Commit refresh publication — October 17, 2026

Full Commit refresh now collects required file/configuration/message metadata before changing its accepted native display. Failed/cancelled reads retain the old scope/checks/locks; Retry re-reads initial preferences and templates when the first load never completed. Optional LFS failures, current draft precedence, start-hook completion and dependent previews share the publication boundary. See file-list refresh parity. Twelve grouped native case/engine combinations pass after a template-newline fixture correction. All thirteen owned receivers were reaped and independently absent. Core Git algorithms are unchanged and its suite was not repeated. See batch evidence.

Email Settings and native credential family — October 17, 2026

Email now detects the Apple Mail choice and uses an explicitly owned native Password sheet with source focus/length/default-button behavior. Duplicate, changed-context and retired replies cannot store credentials; modal Settings/Quit ownership and immediate Store/Clear remain connected to the existing Keychain work lifetime. See Email Settings parity. Both native families pass after a readiness-fixture repair. Four individually reviewed passive light/dark captures are published; all three owned receivers were reaped and absent. Sixteen source controls now have explicit native mappings. Physical/signed acceptance remains open. See batch evidence.

Hosted combined-pane selection repair — October 17, 2026

The observed wrapped-editor CI failure retained a left-pane restore after switching to combined view. Native registration/capture now refuses the absent pane and checks actual owner attachment. A deterministic late-registration regression, wrapped navigation and view switching pass locally; all owned receivers are closed. Hosted verification remains pending. See the repair record.

Network source layout and SSH owners — October 17, 2026

Network now retains source proxy labels/group order and uses native SSH path completion. Captured Browse requests reject changed/retired replies, while independent read/chooser counts guard Quit and retain cancellation until drain. Check now includes Cancel check and associates results with its captured client. Source-ordered proxy/SSH Apply behavior remains. See Network parity. Four distinct native case/engine combinations pass; affected source rechecks cover the recorded layout and cached-page repairs. Two reviewed passive page captures are published, and all eight owned receivers are closed. Core was unchanged and not repeated. See batch evidence.

Credential source inputs and refresh — October 17, 2026

Credential now retains field labels and the source editable Helper combo, keeps chains until explicit edits, and fences callbacks by accepted editor identity. Refresh accepts origins/list/helper metadata together, preserves failed reads and clears externally removed selections. Independent selection requests guard Settings/Quit, while the password-manager action remains available in simple modes. See Credential parity. Four grouped native case/engine combinations pass with system and bundled Git. Both raw light/dark page captures were individually reviewed: labels, editable Helper, list, actions and footers fit without clipping. All four owned receivers were reaped and independently absent. Core algorithms were unchanged and their suite was not repeated. Physical keyboard, signed Keychain/Finder and complete upstream acceptance remain open. See batch evidence.

Source tool forms and Browse ownership — October 17, 2026

Diff/Merge/Unified Diff/association forms now share persistent labels, native path completion and captured, validated, owned Browse choices. Advanced uses the source group/footer structure and returns focus to its sorted native table after editing or removal. Merge draft acceptance rejects Diff-only adapters. See tool parity. All three distinct native families pass after the recorded fixture/runner repairs, including actual Settings navigation; the two affected tool families pass again after the presentation-identity repair. Four raw light/dark captures were individually reviewed: the source group/footer and populated Extension/Program/Arguments captions fit without clipping. All eleven owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for the build diagnostics, fixture failures and physical/signed limits.

General source inputs and engine validation — October 17, 2026

General now uses native Git path completion and a persistent Extra PATH label, captured executable Browse/update-disable questions, cancellable version checks with independent worker drain, and changed-draft validation before Apply. Cached page reactivation and actual owner closure share the lifecycle. See General parity. Four distinct native case/engine combinations pass with system and bundled Git, with two affected source rechecks after the checkbox layout repair. Both raw light/dark captures were individually reviewed: compact groups, persistent labels and footers fit without clipping. All seven owned receivers were reaped and independently absent; source receivers also assert real child-process cleanup. Core was unchanged and not repeated. See batch evidence for the build/capture failures, repairs and remaining acceptance. Localization and Windows Library adaptation remain open.

Browser historical file actions and source Path — October 17, 2026

Browser now has a relative selectable/read-only native Path field and owned historical Save/Open/Open With operations. Atomic writes and preview creation run off the UI thread; captured panels reject stale replies, while in-flight writes and receiving-app callbacks retain independent Quit, scope and input lifetimes after caller closure. See Browser parity. Four grouped native case/engine combinations pass with system and bundled Git after the recorded fixture URL repair. Both raw light/dark captures were individually reviewed: the native relative Path, tree/list and information/footer fit. All five owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for build diagnostics, failed-fixture details, intercepted launch scope and remaining acceptance.

Git configuration source forms and owning editors — October 17, 2026

Git settings now publish level/origins/draft/destination coherently, reject changed pre-write confirmation contexts, fence retired form/editor callbacks, retain the source hierarchy row and use bounded native mixed-state inputs. Editor delivery uses the owning preferences, and the recovery folder chooser owns Quit/Settings. See Git configuration parity. Four distinct native case/engine combinations pass with system and bundled Git; the two affected source cases pass again after visual layout repairs and the recorded fixture correction. Both raw light/dark page captures were individually reviewed, including full-width CrLf and three editor columns. All eight owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for build diagnostics, fixture failures, intercepted editor scope and open physical/signed acceptance.

Working Tree detailed footer and captured Stash — October 17, 2026

Working Tree now offers source-format action/line statistics in a selectable read-only native field, plus source-ordered Stash choices with original icons and single-use captured popup dispatch. Scope/filter acquisition, dormant source controls and source normal-counter behavior are explicit. See Working Tree parity. Four distinct native case/engine combinations pass with system and bundled Git. Both raw light/dark captures were individually reviewed: the selectable statistics wrap without clipping and the native Stash footer fits. All eight owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for the fixture repairs and remaining acceptance. Physical/signed and all combined-action acceptance remain separate.

Merge Open source form and chooser family — October 17, 2026

Merge Open now aligns source groups and five native path/Browse rows, validates file/directory choices before grants, captures the form/slot/window for each one-response choice, retains independent Quit ownership after forced closure and refuses reentrant Open delivery while allowing failed preparation to retry. All 24 static controls receive explicit partial mappings. See Open parity. The Debug build and all four grouped native families pass: source form/chooser ownership, standalone Open, text replacement and patch replacement. The affected source case passes again after the footer-spacing repair. Both raw light/dark captures were individually reviewed; all five receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for the fixture compile repair, captures, diagnostic warnings and acceptance limits.

Merge search forms and pane ownership — October 17, 2026

Find now has fresh-controller close/reopen semantics, preserved live drafts, source selection/empty seeding, separate relative pane positions, empty Count option persistence and complete pending/retired control gates. Go to Line uses a native source-shaped range/input/OK/Cancel sheet, one-response cancellation and independent request drain for Quit. All 18 static controls have partial mappings. See search parity. All three native families have passing runs, including the actual Find/Replace/Undo Git-conflict workflow with system and bundled Git. The source-form and initial-navigation cases exercise native UI without Git commands; their repeated engine environments do not prove additional Git backend coverage. Affected source rechecks pass after capture/footer repairs. One initial-navigation block/caret assertion failed before the two passing diagnostic attempts; its intermittent cause remains open. Four final raw light/dark captures were individually reviewed, and all eleven receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for exact failures, repairs, capture provenance and acceptance limits.

Merge startup and viewport ownership — October 17, 2026

Compare now separates one-time appearance loading from explicit Reload, waits for attached current panes before initial block/inline selection, fences deferred viewport/history writes by visible owner/slot and retires native pane callbacks without removing a newer replacement. Dirty drafts survive repeated appearance. See navigation parity. The Debug build and six grouped native families have passing runs: deterministic ownership, initial navigation, wrapping, margin, folding and Find. The first margin run timed out at editability; the unchanged assertion passed after adding diagnostics, without an app change. That intermittent timeout remains open. All seven owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for the exact attempts and limits. The earlier intermittent initial-navigation observation is not treated as proven fixed merely from these changes.

Merge Colors source contexts and footer — October 17, 2026

Merge Colors now captures palette/edit ownership across swatches, reset and visibility changes, preserves authorized hidden-page Apply, and shares captured single-use Automatic/More colors menus with other Settings pages. Source groups and 17 channels remain; palette/reset choices now share the source footer row. All 35 static resource controls receive explicit partial mappings. See Colors parity. The Debug build and all three grouped native families pass on their first attempt: source contexts, retained Merge Colors and the six shared Settings color pages. Both raw light/dark page captures were individually reviewed; all 17 swatches, source columns/groups and palette/reset footer fit. All three owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for build diagnostics, capture provenance and acceptance limits.

Merge Editor source form and profile owner — October 17, 2026

Merge Editor now has a coherent captured settings draft, source Misc/Diffing layout, enabled/retired native font/context/UTF-8 controls, and an owned validated Comment Profiles session with Settings/Quit guards. Inline profile failures and profile-only recovery preserve unrelated drafts; a failed file save cannot save other preferences. All 24 source controls receive partial mappings. See General parity. The Debug build and four grouped native families have passing checks: source form/profile ownership, live fonts/preferences, default encoding and patch settings/export. The build catch-shadowing error and three fixture issues are recorded with their focused repairs; no app rebuild followed those fixture changes. Both raw light/dark captures were individually reviewed: source groups, paired controls, fonts and additional options fit. All seven owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for exact attempts, capture scope and acceptance limits.

Native source Encoding sheet and editor lifetime — October 17, 2026

Encoding/EOL now uses a native pane/Encoding/EOL/OK/Cancel sheet with source choices and one-response cancellation. Compare retains and retires its prompt; three-pane requests keep independent Quit accounting until an actual response drains after forced closure. All seven source controls receive partial mappings. See format parity. The Debug build and all three grouped native families passed on their first attempt: source prompt/retirement, retained two-pane format transactions and three-pane formatting/Undo/Save. Both raw light/dark captures were individually reviewed; pane, labels, choices and lower-right buttons fit. All three owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for build diagnostics, capture provenance and acceptance limits.

Merge Regex source list/editor session — October 17, 2026

The connected regex list/editor family now retains captured child sessions, source action layout with original icons, draft-only Cancel and once-only OK. External saves preserve older drafts with an inline conflict; stale controls, validation replies and retired owners cannot mutate or persist them. Existing ECMAScript validation retains independent worker accounting until drain after forced closure. All fourteen source controls have partial mappings. See regex parity. The Debug build and both grouped native families pass: source list/editor ownership and retained actual comparison filtering. Raw light/dark captures of both windows were individually reviewed; source labels, complete fields, action icons and footer buttons fit. The first capture exposed collapsed editor width, now fixed with an explicit native content size. A retained fixture expected content at the final EOF row; diagnostics showed source line 3 plus the deliberate blank line 4, and assertions now check both and the complete draft. All five owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for exact attempts and acceptance limits.

Source Context Menu settings pair — October 17, 2026

Both pages now retain headerless native checkbox/icon lists, selected-row keyboard toggling, source groups and shared draft publication. Captured page/owner contexts fence cached native callbacks; Apply validates first, preserves current Advanced icons, rejects reentrant/changed drafts and orders notification after local save. Errors and unsigned notices are separate. Source drag-menu limits remain explicit; clipboard actions are a separate macOS group. All fourteen source controls have partial mappings. See context parity. The Debug build and both grouped native families pass: source pages/native actions and retained settings/publication/Advanced/transaction behavior. The initial source check found disabled native rows; diagnostics isolated the missing observation of model changes, repaired with direct observation and rendered-state readiness. All four raw light/dark captures were individually reviewed: source groups, original icons, native checkboxes, exclusions and page controls fit. All four owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for exact attempts, provenance and acceptance limits.

Release downloads and App Store isolation — October 17, 2026

Check for Updates now retains the source result/changelog/download hierarchy, checked published files, size/digest validation, progress/Abort and native Finder reveal. Folder scopes, private staging, non-overwriting publication, retained partial results and actual request drain connect the whole workflow. App Store builds stay on their own update path. All thirteen source controls have partial mappings. See release parity. The Debug build, nine focused Core checks and both grouped native families pass. Core covers metadata/eligibility, old feeds and duplicate assets, real URLSession transport through a private URLProtocol, cancellation, digest/size rejection and non-overwriting file publication. Native checks cover captured feed/defaults, native/injected folder cancellation, two verified file installs, existing-file and digest failure, held request drain, late replies and App Store isolation. Initial captures exposed unbounded hosting growth; disabling automatic host sizing repaired it, and the affected source case passed again. All four final raw light/dark captures were individually reviewed, and all three owned receivers were reaped and independently absent. See batch evidence for exact scope and limits.

Issue Tracker source configuration and Regex Tester — October 17, 2026

The connected configuration/tester family now retains source radio precedence, field/inherit/Save to order, complete draft confirmation and tester-return guards, and owner-aware cached forms. Exact UTF-8 changes drive settings dirtiness and fresh UTF-16 issue styling; retired clipboard/editor bindings cannot publish. All fifty source controls receive partial mappings. See issue parity. The Debug build, 12 focused Core checks and five native case/engine runs pass. The initial source assertion and diagnostic recheck exposed Git’s argv precomposition; a private reproduction confirmed the cause, and the scoped writer now preserves exact values with a command-only override. Core verifies all writable scopes and the unchanged persistent preference; native source/configuration checks pass with system and bundled Git, plus the retained actual C++ Regex Tester. All four raw light/dark captures were individually reviewed, and all seven owned receivers were reaped and independently absent. See batch evidence for exact attempts, provenance and remaining acceptance.

Branch/Tag source forms and exact follow-ups — October 17, 2026

The connected creation family now captures fields, base selectors and picker intent, preserves edited Unicode suggestions, and retires shared native radio/ Track targets. Tracking respects disabled parent forms and rapid source cycling. Git creation, description, Switch and Push commands retain exact names/messages without changing persistent path preferences. All 22 source controls have partial mappings. See Branch/Tag parity. The Debug build and eight grouped native case/engine checks pass. Core initially passed 32 of 35 cases; repairs to exact catalog reads and semantic error arguments then passed all 13 affected cases without rerunning unaffected checks. Native validation exposed a fixture entry-point error and delayed Track updates; both were repaired before the grouped pass. All four raw light/dark captures were individually reviewed, and all nine owned receivers from the attempts were reaped and independently absent. See batch evidence for failures, scope and remaining acceptance.

Switch source form and accepted choices — October 17, 2026

The connected Switch options/validation/picker/progress family now uses captured native form bindings, synchronous source suggestions and exact remote suffix tracking, source eight-character commit suggestions and owned native radios. Remembered tag/commit choices publish after validation/warning acceptance; checkout rejects malformed object output and propagates failed existence probes. All 17 previously pending static controls receive partial mappings. See Switch parity. The Debug build, 14 focused Core checks and six native case/engine checks pass. Two retained fixtures needed repairs: explicit owned/foreign key-window injection for F5 and command-option parsing for the held Switch cancellation helper. Production ownership and cancellation assertions remain intact; unaffected Core/source checks were not repeated. Both raw light/dark captures were individually reviewed, and all eight owned receivers from the attempts were reaped and independently absent. See batch evidence for exact scope and remaining acceptance.

Push/Fetch/Pull source forms — October 17, 2026

This connected three-form family now owns synchronous source/remote mutations, captured option/mode/history/chooser actions, exact Unicode native ref/remote choices and unique captured Push confirmations. Native targets retire with their owners, disabled dependencies reject callbacks and explicit hosting bounds retain source order. All 52 previously pending static controls have partial mappings. See transport form parity. The Debug build and ten native case/engine checks pass across system and bundled Git. Build repair added explicit main-actor coordinator isolation; a retained history fixture now waits for source preparation before submission. Raw review repaired Rebase left alignment. Six final captures were individually reviewed and all thirteen owned receivers from the attempts were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for exact attempts and acceptance limits.

Rebase/Cherry Pick source form and reviewed intent — October 17, 2026

The connected source form/reference/action/replay family now captures field and phase callbacks, updates Force/Preserve/attribution synchronously, protects full picker intent and retires native split segments. Typed one-use confirmations retain reviewed plans/messages/conflict choices across presentation dismissal; Close/Quit honor their lifetime. Fast-forward/idle footer labels match source. All 23 previously pending static controls receive partial mappings. See Rebase parity. Both Debug builds pass, with ten distinct native case/engine passes across system and bundled Git. Repairs corrected the source fixture’s internal Cherry Pick Force assumption, the retained reference helper’s global-option parsing and incoming refresh/Fetch ownership during confirmation. Only affected source cases were repeated after that final app repair. Six final raw captures were individually reviewed; all fourteen owned receivers were reaped and independently absent. Core was unchanged and not repeated. See batch evidence for cumulative scope and remaining acceptance.

First Start five-page source forms — October 17, 2026

The native wizard now retains a persistent footer around its scrollable page body, links Git runtime/OpenSSH help, owns executable selection and cancellable version checks, rejects retained page/dependency actions and completes Finish once. Fourteen previously pending static controls receive partial mappings. Native localization and Windows language-pack/workaround adaptations remain explicit gaps. The Debug build and two complete native case/engine flows pass with system and bundled Git. All ten raw light/dark captures were individually reviewed and both owned receivers were reaped and independently absent. Core was unchanged and not repeated. See FIRST-START-WIZARD-PARITY and batch evidence for scope and limitations.

SVN source forms and accepted operations — October 17, 2026

DCommit and Import Ignore now capture all accepted choices before runtime checks or stash questions, preserve that submission on Retry, and revalidate failed initial eligibility before presenting options. Native option/result actions retire across operations and owned questions; source-order compact forms grow into explicit progress bounds with effective native minimum constraints. All twelve source controls receive partial mappings. Four distinct source/workflow case-engine combinations pass across system and bundled Git, with only affected source checks repeated after the path-layout repair. All eight final raw captures were reviewed and all four owned receivers were reaped and independently absent. Core was unchanged and not repeated. See SVN parity and batch evidence for scope and remaining public transport, physical and signed acceptance.

Shared patch Find source matcher and forms — October 17, 2026

Standalone and attached patch Find now use pinned Scintilla Unicode folding and literal, complete-scalar matching with native UTF-16 ranges. Native fields, actions, queued focus and editor registrations reject old document/form/attachment callbacks. Six previously pending TortoiseProc Find-bar controls receive partial mappings. The original C++ converter agrees for every valid Unicode scalar, eight focused Core tests pass and six distinct native case/engine combinations pass across both Git engines. Only two affected source checks were repeated after a visible label/row layout repair. Four final raw captures were reviewed and all eight owned receivers were reaped and independently absent. See Unified Diff parity and batch evidence for actual source/backend scope and remaining physical, codepage and signed acceptance.

About source family — October 17, 2026

All five native About variants now retain original tool artwork and source-style header/version/attribution grouping. App and Merge include the pinned water effect, with Reduce Motion and owned timer retirement. Captured selected-Git reads cancel on closure and hold Quit accounting until settlement; registered links and reused windows reject stale/foreign actions. The grouped checkpoint and ten raw light/dark captures are recorded in About parity and its QA record. Twenty-seven source controls receive partial mappings; no dialog is certified complete. Source/component version details, Retina/physical acceptance and signed distribution remain open.

The previous Pages run failed because generated Mac Help lagged DIALOG-GUIDE.md. The Help book has been regenerated and its freshness check passes locally. A new hosted run is still required; local success is not a hosted integration result.

Project-dialog source settings — October 17, 2026

Dialogs 3 now uses captured source/dependency contexts throughout its native fields, source/destination pickers and icon Browse flow. Current-icon folder and path display, once-only chooser results, exact UTF-8 modified-state, owner-close retirement, invalid-value refusal and readable scrolling are implemented together. Bare HEAD project configuration stays readable while worktree-only destinations stay unavailable. The grouped native family passed with both Git engines, including real five-key writes/removals, exact Unicode property-sheet Apply, private picker cancellation and held reads/writes across closure. Core serialization was unchanged. Two raw appearance captures were reviewed; all four owned receivers are absent. Four source separator controls map partially to the native hierarchy hint. Full physical/geometry/signed sandbox acceptance remains open. See scope and evidence.

Finder overlay and watch controls — October 17, 2026

The three overlay settings pages now capture page/owner/dependency generations, preserve exact UTF-8 path-rule edits, retain shared Apply/Cancel and retire after owner closure. Watched-repository root/grant choosers and confirmations own their native Settings window, reject stale/duplicate responses and support captured multi-selection Refresh/Remove. Accepted operations stay under the existing watch manager. Debug builds, 12 overlay Core checks and the combined two-engine native family pass. All three receivers are absent and eight raw appearance captures were reviewed. Windows cache engines/registry/overlay-slot controls, physical Finder activation and signed/App Store acceptance remain open. Coverage counts remain partial, with no newly certified dialog. See Finder control scope.

Exact submodule paths — October 17, 2026

Submodule index/.gitmodules catalogs, Update scope/selection/focus/persistence and Sync containment retain exact UTF-8 identities. Add/Update/Sync commands disable argv precomposition per invocation; Add's contained absolute path suffix is also exact. Ambiguous rows expose byte-distinguishing tooltips/accessibility labels. Add/Update minimum constraints are effective on native hosting views. The grouped checkpoint passed 58 Core tests and ten distinct native case/engine pairs cumulatively; one bounded-progress error regression was repaired and only affected native cases repeated. Four raw captures were reviewed; all 13 receivers are absent. Fifteen Add source controls gain explicit partial mappings. Existing working-file String-set models, filesystem-specific aliases, physical/signed Finder and App Store acceptance remain open. See scope and evidence.

Native problem-report review and export — October 17, 2026

Help → Report a Problem now supplies captured bundle versions, reproduction steps, owned Apple IPS/legacy crash import, explicit inclusion, home-path replacement, a selectable exact preview and local Copy/Save. A separate action opens the blank fork issue form without report data in its URL. Reads, accepted snapshot exports, pickers, cancellation/closure, scopes and application Quit counts are connected. The SwiftUI root retains its controller weakly so closed windows can release.

Six Core cases and one grouped native workflow pass. Core covers supported Apple formats, original Unicode text, invalid/binary/oversized input, file type/symlink/ cancellation boundaries and explicit inclusion/redaction limits. Native checks cover private Copy/Save snapshots, native chooser cancellation, late/duplicate replies, failed writes, retained work after owner close and release-after-close. Both raw appearance captures were reviewed; the receiver is absent. Generated Mac Help passes its freshness check. Direct Windows DrDump transport, minidumps/ assert collection, server solutions, unsaved-session recovery and physical/signed acceptance remain open; original crash resource controls remain unmapped. See scope and evidence.

Fresh universal distribution candidates — October 17, 2026

Release and AppStore archive builds now measure repository input bytes and modes before and after compilation and retain the actual build revision and dirty-input flag. Reusing an audit requires its original complete source/bundle inventory; changed resources, aliases, modes and stale source inputs are refused. Local preview packaging verifies the unsigned copy before signing and compares the signed app against its independently extracted ZIP. CI uses the measuring build entry point directly. These guards establish recorded source/bundle provenance; they do not claim hermetic or bit-reproducible builds.

Seven provenance contract checks pass. One fresh universal Release build and one fresh unsigned AppStore archive pass their package/cache audits; eight archived app components have matching universal dSYMs. One ad-hoc preview packaging run passes app and extracted-ZIP seals and inventory matching. The 349,429,725-byte local ZIP is retained under build/previews/TurtleGit-2026-10-17, with checksums, license notices and a manifest. Existing unrelated work was measured and preserved. No app was installed, launched, registered, uploaded or submitted by packaging.

Hosted integration remains open: one run timed out in the native folding case. A focused local reproduction with temporary phase diagnostics passed, and its owned receiver was reaped and independently absent; this is not a production fix. Another run exposed a hosted compiler type-check limit in the About water oracle test. The pixel expression now uses explicit typed RGB components with the same reference assertions. All three affected Core checks pass locally, including 96 reference RGB frames; full hosted confirmation remains open. See batch evidence for exact artifacts, validation and outstanding physical/signed/full-parity gates.

Statistics source form and accepted graph saves — October 17, 2026

This connected Statistics batch adds the source author-slider activity cutoff, contribution/commit ranking shared with graphs, bounded native input, stale form callback protection and captured File menu ownership. Its summary uses source label/value rows and right-aligned Average/Min/Max columns, retaining blank/zero activity for empty history. Native styles use original icons with selected-state feedback; the minimum content size preserves controls and footer.

Save Graph retains the graph, metric, style, viewport and appearance captured before its owned picker. Old/duplicate/closed/replaced-form replies are rejected. Accepted atomic saves run outside the main actor and keep Quit protection after forced owner closure; ordinary close waits, errors belong to the original window, and closed owners suppress late UI. Existing export encodings and calculation semantics remain intact.

Sixteen Core checks and the grouped native family pass with system and bundled Git. Build repair added explicit self captures; a stale menu object was rebuilt before receivers ran. Raw review repaired activity-column alignment, followed only by its narrow capture recheck. Four final raw light/dark captures were individually reviewed, and all three owned native receivers were independently absent. Help and source parity documentation are updated. Full physical, visual, VoiceOver, large history and signed acceptance remain open. See batch evidence.

Exact changelist storage and Commit/Working Tree groups — October 17, 2026

This connected changelist batch replaces normalized Swift dictionary/set identity with exact UTF-8 path/name keys. Native group equality, stable row IDs, Move menu items, ambiguous-name help/accessibility and Commit menu invalidation now retain canonically equivalent spellings separately. Source ordering uses UTF-16. Version 2 metadata writes array records; legacy version 1 JSON and upstream UTF-8/BOM UTF-16 import remain supported, with atomic locked mutation, cross-actor reload, exact scoped pruning and cancellation. Commit retains unchecked/restored keys before set insertion for cleanup. Product consumers use exact lookups; the old String dictionary projection remains a limited compatibility API.

One Debug build, sixteen focused Core checks and one native group across system and bundled Git pass, with no repair/repetition. A real selected-file commit prunes its own assignment and retains the two exact unchecked names. Four raw light/dark Commit/Working Tree captures were individually reviewed; both owned native receivers were reaped and independently absent. The later working-file identity continuation advances status parsing and metadata joins. File-table selection, checked-path and restore-copy identity migration remains open, along with physical and signed acceptance. This is a changelist family improvement, not full filename or application certification. See batch evidence.

Atomic folding and aligned-result expansion — October 17, 2026

The shared comparison folding family now reveals selected folded runs in one mutation/projection/expansion batch. Attributed fold application/restoration uses TextKit editing transactions; result anchors use an exact UTF-16 offset index. Aligned result expansion uses source display coordinates rather than serialized conflict-marker row positions. Source/result synchronization runs once per batch, while gates, original text, attributes, anchors and Undo state remain intact.

One Debug build, 23 focused Core checks, seven receiver ownership contracts and all eight grouped native cases pass. A fixture-only repair normalizes AppKit's emoji fallback font before capturing the restoration baseline; its strict full attribute assertion remains. No Core/build repeat followed. A stronger short-section/two-conflict coordinate fixture also passed its focused folding recheck without repeating other cases. All eleven owned native receivers from the attempts were reaped and independently absent. Persistent native phase diagnostics and bounded timeout output tails retain evidence if the hosted folding timeout returns; no timeout/assertion is weakened. The earlier hosted implementation has now passed Git integration and reached native checks, but full current hosted and physical/signed acceptance remain open. See batch evidence.

Native language resources and selection — October 17, 2026

The connected General/First Start language family now bundles English and 37 pinned TortoiseGit PO catalogs as native String Catalog resources. There are 1,242 safe matching literal keys; this is resource coverage, not complete UI translation. Fuzzy, ambiguous, formatted and plural entries retain English fallback. Translator headers, source blob pins and notices travel with the app.

General Language participates in Apply/Cancel with captured lifecycle/revision bindings. First Start saves Language on Next and retains that save after later Cancel. System removes the app-specific override; no global preference is changed. The app asks for a restart. Shared source-icon command captions and AppKit checkboxes localize while user-derived names remain verbatim. A bundled Languages guide is available offline.

Five PO contracts and three Core preference cases passed; after correcting Xcode's Serbian locale canonicalization only the affected choice case was repeated. The Debug app, full bundle audit, German/French/English native checks and 48-topic Help receiver passed. Four actual German light/dark captures were reviewed; partial English remains visible. All owned receivers were reaped and independently absent. See batch evidence for failures and repairs. Full dynamic/AppKit/formatted/plural/RTL translation, physical input and signed acceptance remain open. No source dialog is newly certified complete.

Synchronization child progress family — October 17, 2026

Separate Checkout, fast-forward Merge and tag progress now consume live work and percentage, native completion/timing details, Copy/Copy All source-icon menus, one Action log entry and the shared Dock adapter. Compact tag waits retain parent error handoff and explicit source auto-close behavior. Abort is once-only and keeps natural success while its question remains pending.

Forced closure retires late publications while retaining the repository lease, independent Quit guard and parent continuation through actual worker drain. The parent receives one result after drain, avoiding overlapping mutation/recovery. Natural completion does not cancel the shared parent token. A grouped regression found that token-cancellation defect; it was repaired and the affected families rechecked on both system and bundled Git. The native activity indicator was constrained after visual review exposed unwanted expansion.

The Debug build, two progress engine cases and two Compare Tags engine cases pass; four final raw light/dark captures were reviewed. Every owned receiver was reaped and independently absent. Core was unchanged and not repeated. The source Merge failure conflict/Commit post-action, full generic progress controls and physical/ signed acceptance remain open. See batch evidence.

Separately, hosted d7133b3b passed Git integration but failed the Merge menus step with Conflict menu choice lost Undo; the receiver was reaped. That outstanding Undo defect is distinct from the earlier folding timeout. No full hosted green result is claimed from this local batch.

Native Merge editing and history readiness — October 17, 2026

Native conflict commands now require an attached result editor carrying the current source-layout and presentation revisions. Toolbar, menu, footer and actual model dispatch share the gate, preventing an early/detached choice from using the model-only fallback without Undo. Headless model computations retain their path. Result edit/Undo/Redo synchronously installs aligned text, row colors, folding, whitespace and ruler data; queued rendering uses coherent current source/result projections. Whole-source context commands now capture their source/layout/result identity and reject retained actions after edits or identical-text Undo.

Seven grouped native cases pass: menus, typing, three-pane engine, result formats, folding, wrapping and initial navigation. The menu case checks immediate Undo/Redo and light/dark colors, detach/reattach, stale/fresh whole-file actions and unchanged inputs. Ten owned receivers including the initial diagnostic and interrupted render-loop attempt were reaped and independently absent. Core was unchanged and not repeated. The batch needed a missing-declaration build repair and removal of an unconditional view-update history publication; a process sample confirmed that render loop. History flags now publish only changed values.

The older hosted Conflict menu choice lost Undo timing was not reproduced by the local diagnostic, and a current hosted pass remains necessary. Complete physical input, source behavior and signed acceptance remain open. See batch evidence.

Synchronization failure recovery and Commit handoff — October 17, 2026

The source separate fast-forward failure callback now reads actual unmerged entries and offers Resolve with its original artwork. The native action closes the acknowledged progress result, drains the worker and calls the existing whole-project Commit route. Failure inspection has its own cancellable token; its errors or cancellation cannot rewrite the original Git result, exit-code footer or completion timestamp. No action is offered without confirmed conflicts.

Captured recovery receipts reject nested-sheet, duplicate and retired clicks. Cancellation questions capture their current worker, so an old Git answer cannot cancel a replacement read. Forced closure cancels that read and retains lease, Quit guard and parent continuation until actual drain; late actions/footer stay retired. Windows' separate-process Commit launch is adapted to the app's existing acknowledged-result post-action route.

One Debug build and the expanded connected native family pass on system and bundled Git. Actual Sync-to-Commit presentation retains conflicted index stage entries, HEAD and file bytes. Four raw light/dark captures were reviewed. Two fixture repairs selected the synchronous sheet overload and supplied an NSError with the intended localized diagnostic. No app/Core rebuild followed those fixture-only fixes. All three owned receivers were reaped and independently absent. Core was unchanged and not repeated. Physical/signed behavior, full Commit/Sync parity and current hosted CI remain open. See batch evidence.

Synchronization conflict status-list family — October 17, 2026

The generic conflict List has been replaced by a native multi-select five-column status table matching SyncDlg's column mask. It shares Working Tree actual status/ statistics, colors, file operation ownership, list font/artwork, focus mark and clipboard/header adapter. Its ConflictSyncDlg column profile and reset defaults are independent of Working Tree.

The captured source action mask now provides direct conflict editing, current/ Mine/Theirs resolution with rebase labels, Log, alternative editor, Open/Open With, Finder reveal and clipboard formats. It excludes unrelated destructive/flag/ changelist commands. Real conflict changes use the existing optional refresh policy; F5 explicitly reloads. The active empty conflict tab remains valid. An owned application chooser gates Close/Quit and is cancelled/retired on forced closure, retaining the actual worker/security-scope lifetime and rejecting late launches.

Four grouped case/engine combinations pass: new Sync conflict files and existing Working Tree menus with system and bundled Git. Actual Mine/Theirs resolution, stale/retired routes, isolated settings, native chooser cleanup, unchanged HEAD and restored unresolved stage entries are covered. Both actual light/dark captures were reviewed; all four receivers were reaped and independently absent. Core was unchanged and not repeated. The first build needed a missing row parameter; the final pre-native review aligned Status colors and retained the empty active tab. See batch evidence. Full source, physical, path-identity and signed acceptance remain open.

The latest inspected terminal hosted 33391321 run failed the moved-block family with Discard/reload did not restore move mapping, with receiver 24007 reaped. The newer a4811601 run was in progress and a0138ef3 pending at observation. Pages deployed a0138ef3 successfully. A full current macOS pass is still required.

Compare Reload, view changes and history — October 17, 2026

Explicit Reload and two-pane/combined switching now share the owned comparison Save/Don't Save/Cancel transaction, including separate Save left/right/both choices when both panes are dirty. Cancel retains drafts and mode; accepting reload invalidates document-owned Undo even between native view replacements. Sheet dismissal retains the pending operation until AppKit releases the sheet, and combined reload selects Mine. See reload parity and batch evidence.

The Debug build and six grouped native cases pass: savepoints/reload decisions, chronological history, combined view, moved blocks, viewport ownership and folding. An existing insertion fixture omitted the source-compatible EOF record; precise diagnostics showed the correct payload and two added rows, and its assertion now compares the exact two-row delta and restored baseline. Only fixture compilation was repeated for that repair. All seven receivers from diagnostics/attempts/final checks were reaped and independently absent. Core was unchanged and not repeated. Localization generation/check and the 267-page site build pass. Full hosted and physical/signed acceptance remain open.

Local post-crash report recovery — October 17, 2026

App launch now discovers recent matching Apple reports and offers native Review/Dismiss. Exact process/bundle matching, bounded background reads, regular-file/no-follow checks, age limits, private handled-content hashes and an opt-out preference connect discovery to the existing support editor. Review keeps crash inclusion off; busy editors allow retry. Closure cancels scans and rejects late presentation while retaining drain/Quit ownership. No report is uploaded, removed or silently included. See crash parity and batch evidence.

Ten focused Core checks and the expanded grouped native support workflow pass. The Debug app build passes, followed by an incremental build to copy regenerated Help. All four raw light/dark recovery/editor captures were individually reviewed with visible labels and footers. Receiver 90665 was reaped and independently absent. Help freshness, localization and the site build are checked separately. Actual system-crash delivery, installed signed/App Store access, physical input and complete Windows collector/transport/solution parity remain open.

Exact working-file reads, metadata and index flags — October 17, 2026

Status coalescing, row equality/hashing, rename/statistics/gitlink joins, Working Tree and amend status aggregation now retain canonically equivalent valid UTF-8 spellings separately. GitPathMap carries metadata through Commit staging, Working Tree, Revert, Rebase and Finder flags. The index-flag writer selects each exact stage-zero path and supplies NUL-delimited stdin. Finder absolute flag keys avoid Foundation suffix normalization; snapshot records retain exact keys alongside a legacy compatibility object. See scope and remaining migration and batch evidence.

There are 48 distinct relevant Core passes across the initial retained checks and affected repairs, plus four native case/engine passes for Commit staging and Working Tree. The initial clipboard fixture type, invalid numstat fixture and actual Foundation-normalized absolute flag keys were repaired. Only affected identity/amend checks were repeated after those changes. Both Debug builds pass; all four owned receivers were reaped and independently absent. Core metadata and native sorting/clipboard checks do not certify String-based row selection, filesystem aliases, arbitrary invalid UTF-8 paths or signed Finder/App Store acceptance. No dialog is newly certified complete.

Persistent Log cache, Saved Data ownership and consistent branding, 2026-10-17

Repaired cache reuse (Git echoed a parsing marker), exact newline metadata and global attribute paths, byte-stable attribute fingerprints, bounded cancellable reads, descriptor-pinned atomic records, and namespace-safe eviction/clear. Saved Data owns background cleanup through completion and application Quit; new Log windows capture the source cache preference. The complete application turtle with Git on its shell now replaces the older small branding artwork in About, setup, menus, Finder and authentication prompts, including small AppIcon slots. Original command/status artwork and attribution remain.

Focused Core checks and affected repairs, three bundled-engine cache cases, three icon checks, four grouped native cases and packaged branding audit passed. Failed attempts, limitations and all seven receiver cleanup checks are retained in dated evidence. No full Core/hosted CI, signed deployment, physical Finder or complete dialog parity claim follows from this checkpoint. Inventory counts are unchanged.

Connected Log external document opening, 2026-10-17

Log Open, Open With and alternative editor now retain the originating file epoch through Git reads, application choice, preview creation and Launch Services. Historical/working reads have cancellation/Quit ownership; application and repository grants survive handoff. Historical previews retain exact read-only bytes, undispatched copies are discarded, and possibly accepted inputs survive uncertain launch receipts. Editor settings are captured before deferred work. Normal Close can retire preview/launch sessions; late callbacks cannot overwrite a retired/new selection's errors. Native source menus/icons are unchanged.

Both Debug builds, twelve focused Core cases and four distinct grouped native workflow/engine combinations passed. Final Close review required only the two affected handoff cases to be repeated. All six receivers were reaped and independently absent. Scope and limits and dated evidence retain the actual checks. Physical receiving-app/AX and signed App Store acceptance remain open; this does not certify the whole Log or application port.

Native certificate inspector and public export, 2026-10-17

Open certificate now supplies native expandable macOS certificate fields plus the read-only Text report. Copy uses the exact named fingerprints; Export captures DER/PEM encoding before its owned Save panel. Cancelled, repeated and retired callbacks cannot write, and an accepted write retains the destination scope until completion before a closing authentication helper returns its response. Native trust editing is disabled and this view does not accept the SVN connection.

Seven focused Core cases and the grouped native authentication/inspector receiver passed. Initial Debug packaging failed because an added Core import accidentally linked the standalone helper against the app framework; the helper now keeps shared source models, packaged artwork paths and native URL scope handling. The Debug repair passed with the runtime audit intact. No Core repeat followed the helper-only repair. Raw light/dark captures were individually reviewed; receiver 35542 was reaped and independently absent. Guide and evidence retain scope/limits. Live TLS, physical/AX, signed helper/save grants and full application parity remain open. Dialog inventory counts are unchanged.

Clipboard patch Finder/chooser entry family, 2026-10-17

The existing source-eligible Finder Review action now captures registered patch clipboard bytes for a non-patch selection, while a selected patch file retains priority. A one-use App Group cache receipt carries exact bytes without putting the patch in a URL or treating it as repository permission. The app loads that snapshot through its owned review preparation, rejects recent repeated receipts, and retains folder authorization/target matching and explicit Apply.

The native patch source chooser offers Use Clipboard Patch with original artwork. It validates only on explicit activation, retains the chosen bytes through the later target chooser, and keeps invalid text in the file chooser for retry. Source/target responses wait for sheet release and reject cancelled, repeated, old or closed-owner callbacks. The existing Merge Open checkbox remains.

Twenty focused Core cases and two grouped native cases passed. Initial Debug caught a catch-variable naming error; the repair passed. The default shared cache path moved under Library/Caches; injected-root Core checks were not repeated. Both receiver PIDs 36893/37008 were reaped and independently absent. Scope and evidence retain physical, privacy, signed/cross-process and format/performance limits. No full hosted CI, App Store or complete dialog/application parity is certified.

Exact Finder repository-root family, 2026-10-18

Repository metadata now shares the existing lossless file path map. Root/child ownership, mixed-selection eligibility, request-relative paths, folder/submodule badges, collection failures, service directory counts, queued removals and subtree publication preserve exact UTF-8 identities. Current readers prefer lossless metadata records while a stable reduced legacy field remains for older extensions. Writer state migrates to version 2, fences old lossy writers and preserves known counters/tickets; canonical peers cannot supersede or remove one another's work. Unique filesystem aliases remain supported and ambiguous aliases fail closed.

The scoped checkpoint has passing evidence for 71 distinct Core cases, both Debug builds and both native engine cases. Compile/legacy-fixture failures and the final submodule-alias parent-owner repair are retained in dated evidence. Only affected transfer/creation and native checks were repeated for that repair. All owned receivers/helpers exited. The native wire fixture does not assert that the host volume has two physical canonical-peer folders. Installed signed-version migration, other grant boundaries, physical Finder and full port/App Store/hosted acceptance remain open. No dialog is newly certified by this cache batch.

Finder snapshot query and directory-menu family, 2026-10-18

Finder snapshots now reuse immutable exact namespaces, watched-root sets and owner-grouped descendant states. Menu eligibility no longer rebuilds all path prefixes for every predicate or scans every cache entry for each folder action. Badge projection finds an exact owner by ancestor lookup. Copies share query data until a relevant field changes, then detach without altering a retained snapshot. The existing wire format and exact/unique-alias/nested-root rules remain intact.

All 48 scoped Core cases, the Debug build and both grouped native engine cases passed on the first checkpoint. Dense-cache timing, concurrent reads and all copy/field/encoding assertions are retained in dated evidence. Native original-icon menus, changed generations, fresh badges and retained exact-root/foreground/event/cross-process workflows pass. All owned processes exited. Full Core/unrelated families were not repeated. Synchronous snapshot reading/reload, huge/remote-volume performance, physical Finder and signed/App Store acceptance remain open. No whole dialog or port certification is implied.

Current universal preview and AppStore archive, 2026-10-18

Refreshed the actual local app/ZIP and unsigned archive at ae48b26a. Each build ran once using its existing derived-data cache; both generic-macOS builds and package/cache audits passed. Eight app components have both architectures, and the archive's eight matching dSYMs and 6,303 members are inventoried. The separate preview's app and extracted ZIP pass ad-hoc code seal/full-inventory checks. It contains exact LICENSE/NOTICE copies, checksum and measured build provenance. Preview notes now state that an ad-hoc process cannot access Finder's App Group. No GUI installation/launch, registration, distribution export/upload or submission was performed. No full Core or native workflow suite was repeated.

Artifact evidence preserves both builds' shared input hash and dirty script state, including unrelated pre-existing development work that remains unstaged. Hosted bdf35802 separately failed after five wrapped cases passed; the wrapped receiver timed out and was reaped. Its uploaded stack was downloaded and verified against the upload digest; stack evidence records active UI layout/draw frames without claiming a cause or repair. That blocker, physical/current signed acceptance and complete port/App Store clearance remain open.

Direct LFS commands and cancellation ownership, 2026-10-18

Ported all three pinned LFSCommands.cpp primary entries together: server-wide Locks, direct Lock and Unlock, with Force accepted only for Unlock. Typed options survive authorized path-file resolution; literal paths, missing/unversioned files and whole-batch validation retain the source command semantics. Finder keeps its stricter versioned selection policy. Existing list choices/result review are preserved, and list/progress inherit workspace presentation settings. Delayed preparation retains its original repository/access/window, cancels on owner close or retirement and remains accounted for until it drains. Parent closure now retires/cancels an attached progress controller and rejects late data.

Diagnosed the older hosted LFS/mail failure with one local reproduction: a cancelled Working Tree reload retained its complete prior ownership snapshot, while the assertion expected empty ownership. The corrected check verifies the unchanged owners/locks/known flag/file IDs, rejects the late reply and requires the next successful empty query to publish known-empty ownership. Product data retention was preserved.

All 47 focused Core cases and the single Debug build passed. The new command receiver passed with both engines after a fixture idle-wait repair. The affected LFS/mail subset of the hosted runner and bundled LFS regression passed once, including private loopback SMTP MIME checks; all owned processes were reaped. Exact batch evidence records attempts, failures, log hashes and scope. Full hosted CI, public-provider authentication, physical visual/input acceptance and current signed/App Store distribution remain open. No complete dialog/port certification or replacement distribution is implied.

Parallel Commit, Log and historical comparison batch, 2026-10-18

Three implementation agents completed connected workflow families before the parent checkpoint. Commit now has the source empty/read-state captions, owned hidden-unversioned Yes/No/suppression behavior, staging-compatible submodule selection policy, and independently merged date/time controls with source bounds. Log now routes its source Find/focus/select-filter/Refresh/Escape/Copy commands, protects Return in the revision table, and offers captured one-shot message Copy, Copy all and Edit Notes actions. Quit confirmation gates those commands and message callbacks through the application shutdown drain.

Diff now accepts the actual source submodule switch and historical path2 pairs, retains directory/unified precedence, normalizes working/index sentinels, supports missing historical files and explicit historical bare comparisons, and preserves its originating owner/preferences through authorization and child handoffs. A native check exposed directory-bit-sensitive URL identity selecting a child repository instead of its indexed parent. Discovery now compares exact normalized path bytes while retaining containment, indexed gitlink and registration checks.

The parent owns grouped validation and records initial failures, focused repairs, actual checks and process cleanup in batch evidence. Commit's source review and light/dark captures, Log command review and Submodule/Diff review retain remaining behavior and platform gaps. The README/privacy guide now reflects the recorded older installed Finder check and actual app/cache/service storage behavior. Current hosted CI, complete physical input/visual/accessibility review and signed distribution remain open. These batches do not certify a complete dialog or the whole port.

Read-only planning identified standalone Merge-tool command-line entry and Git mergetool/difftool integration as a substantial next workflow family; existing Merge Open editors can be reused. Reference-badge branch-description hover remains a smaller Log gap. Older partial notes must be reconciled with later implemented sections before scheduling replacement work.

Checkpoint outcome: 103 distinct focused Core cases and 16 distinct native case/engine combinations pass. The initial build access error, Commit fixture compile annotation, nondeterministic Log fixture query, actual submodule root selection defect and fixture snapshot-owner mismatch are retained in the evidence. Only affected checks repeated; the complete Core suite was not rerun. All 22 recorded receiver/metadata child processes are absent. Four owned inactive-window Commit captures were reviewed in light/dark. Hosted integration remains separate.

Standalone Merge-tool and Git editor entry, 2026-10-18

Ported the connected source/native command family across parser, independent merged-output snapshots, missing-input empty panes, source descriptive/reflected labels, readonly/Blame mutation policy, initial line and mandatory-save behavior. The waiting wrapper now launches native two-/three-file editors, Open fallback, reverse/readonly patch review or byte-preserving unified output. Authorization retains original preferences and file/folder grants. Startup and approved Quit return actual saved/unresolved/unsaved status after owned work drains; discarded requested Git results remain failed through File/Open replacement.

Integration review completed the same-window current-controller handoff, pre-load readonly patch policy, cancelled retired model/patch/export work, ownerless output Save As and empty Open chooser retirement. Explicit temporary input cleanup preserves changed objects and merged output. The source command options and remaining frame/Blame/reflected-header/platform states are retained in entry review, comparison review and the user-facing Git tool setup guide.

All 24 distinct focused Core cases and ten distinct native/workflow receipts pass; all 21 recorded owned processes are absent. Only checks affected by actual repairs repeated. Evidence preserves the Core Unicode failure, native fixture repairs, integration changes and exact build scope. Fixed the prior hosted Pages stale-help failure by regenerating the offline book; local resources now check 39 documents/48 topics, without claiming complete help or localization coverage. Current hosted CI, dedicated standalone scene/menu acceptance, complete visual/input/accessibility review and signed distribution remain open. The whole port is not certified complete.

Merge frame, Blame and reflected patch family, 2026-10-18

Three parallel implementation owners completed the connected standalone frame family. Command startup chooses between concrete repository and tool App types; the tool creates only its requested native editor/chooser and explicitly activates the process. Its native commands reuse macOS's localized menu roots, retain the existing lifecycle/epoch checks, and include focused Save All and Close through the controller's ordinary save/cancellation policy.

Pinned source review corrected two earlier notes: Merge Blame does not add columns, and reflected patch rewriting belongs to MainFrm.cpp::OnEditCreateunifieddifffile, not a TryGitUnifiedDiff symbol. Blame now matches the source's converted-file gates and fixed 66 UTF-16-unit prefix rule while preserving displayed source rows. Three-way readers supply actual input encodings on fresh reads and rebound-source comparison. Editor unified exports rewrite applicable reflected paths relative to a common working tree, preserve hunk bytes, and quote literal path bytes; CLI raw export keeps its source header behavior. File/Open retains current reflected frame metadata and Blame policy, including after Switch Sides, while clearing old document output, descriptive labels, initial line and required-save intent.

All 27 distinct focused Core cases and 17 distinct native/wrapper receipts pass, including both Git engines and retained toolbar behavior. The first SceneBuilder compile failure, real-process activation/localized-menu defects, source review correction and affected-only rechecks are retained in batch evidence. The final real app shows one localized menu-root set and no repository window; physical menu-action checking was interrupted by UI state changes and remains unproven. Every recorded owned process is absent, and all private QA app bundles were closed.

The earlier Pages help repair is confirmed by a successful hosted Pages run for a291a1b1; no full hosted macOS pass or current signed/universal distribution is claimed. See the frame review, Blame review, reflected export review and presentation review. Reflected-path EditorConfig semantics, shared installed-app identity/interleaved external requests, complete physical visual/input/VoiceOver, minimum-OS/Intel and signed App Store terminal-grant acceptance remain open. This is a partial port record, not whole-dialog or whole-application certification.

Editor metadata, Log references and external request family, 2026-10-18

Three parallel implementation owners completed related EditorConfig, Log and Commit work, integrated with independent workspace handoff from standalone Merge. Comparison panes resolve reflected EditorConfig filenames before temporary files, retain pane identity across Switch Sides, source rebinding and result Save As, and serialize owned permission/parser work with cancellation and actual drain. The source indentation-only behavior preserves existing saved bytes.

Log branch badges read local descriptions with source fallback and UTF-16 limits. Painted hit geometry and native accessibility share canonical reference identity; stale document/geometry generations refuse actions. Commit author/date callbacks check live ownership and model gates, retire replaced native targets, and keep cancelled metadata work counted until its actual return.

External Finder/patch events have one application receiver. Ordinary startup queues them in order; standalone Merge requests a separate workspace instance, retains launch/error acknowledgment ownership and returns its original Git result after accepted handoffs drain. The injected native checks do not prove physical signed Launch Services delivery or transfer of sandbox authority.

The batch evidence records grouped validation, actual failures and affected-only repairs. See the EditorConfig review, Log reference review, Commit ownership review and workspace handoff review. The earlier hosted Commit receiver's SIGSEGV is confirmed, but its precise cause is unproven without a crash stack. No full hosted pass, current signed/universal package, complete physical accessibility or whole-application parity is claimed.

History/reference action and replay identity family, 2026-10-18

Three parallel owners completed source Log command-mask policy, Reference Browser context dispatch and Rebase identity/hook boundaries; the integrated Blame consumer uses that shared policy in its actual embedded history list. Original command icons, canonical captured targets and native child/Git operation ownership remain. Log filters commands before binding their original action receipts, preserves the source Show log and range exceptions, and emphasizes the default comparison. Blame adopts source parent/repository command order, WC/HEAD gates, clipboard submenu and the actual double-click comparison preference.

Reference Browser now supports selected-row keyboard/accessibility context menus, retains an empty leaf selection for namespace menus, refuses replay of captured commands, preserves comparison preferences and reads local first-entry branch descriptions. Rebase checks all four source author/committer values after autostash, loops through its owned Git Settings repair, and only then invokes PreRebase. Cherry Pick shares the identity check without acquiring an invented client hook; automatic Merge commits retain source behavior. Sync/Fetch continue to inherit the existing Rebase path.

The grouped batch evidence records actual checks and repairs. See Log policy, Blame policy, Reference Browser and client hooks for precise source scope and remaining behavior. Physical input/VoiceOver/menu tracking, minimum-OS/Intel, current hosted CI and signed App Store/Finder acceptance remain separate gates. This partial connected batch does not certify an entire dialog or the whole application.

The user-reported replay Settings sheet Close/OK/Cancel refusal was reproduced with an enabled transaction and disabled sheet title button. The owned close path now retains its delegate policy and waits for actual sheet release. The same batch replaces the Remotes selector's unbounded appearance with a bordered native list, stable selection/scrolling during edits and explicit keyboard/draft ownership. See Remote Settings and the batch evidence for actual checks and acceptance limits. Automated receiver windows stay invisible/offscreen.

All 33 selected Core cases and 22 distinct native case/engine receipts pass. Actual failures included an optional-title fixture compile, the user's Settings sheet close refusal, an invalid Remote constraint activation and lost keyboard focus across the Remote read. Only affected checks repeated after repairs. All 27 recorded receiver processes are absent. Four Remote content-cache renders were inspected but have incomplete backdrops/button layers; they are not publication screenshots or complete visual parity evidence. No full hosted or current signed distribution pass is inferred from this local checkpoint.

Rebase connected history tools, 2026-10-18

The history tools batch connects occurrence-based Find, Export, containing references and forward/reverse/symmetric range logs to the replay table. Existing native consumers retain repository/access/preferences, source artwork and captured single-use menu receipts. Parent action/close ownership and actual cancelled-read lifetime extend through helper retirement. The remaining shared Log/reference menu family, complete visual parity, physical acceptance, current hosted CI and signed App Store deployment remain open.

Connected history/reference consumers, 2026-10-18

The connected workflow batch implements Rebase reference-pointed commands, Blame parent/file actions and Reference Browser comparison/child release. Canonical targets, captured alternative-tool choices, source artwork, actual cancelled-read ownership and inherited preferences remain part of the end-user workflow. Its evidence records the grouped checkpoint and remaining Windows matrix, physical/visual, signed and whole-port gaps.

Commit, replay message and transport workflow batch, 2026-10-18

Three parallel owners extended Commit option transitions, Rebase message editing and Fetch/Pull handoffs. Message-only list actions, checked-file Edit amendment, stopped-message drafts, actual native sheet release, failed owned-Rebase recovery and delayed Quit belong to these connected operation workflows. Follow-up windows inherit their originating presentation preferences. The grouped checkpoint is recorded in operation workflow evidence.

This remains a partial source-family audit. Existing source controls are not a completion percentage; full visual comparison, physical macOS/Finder acceptance, current hosted integration and signed/App Store distribution remain separate, unfinished gates. Bundled Mac Help is regenerated with included guide changes; the Pages source check must pass before website rendering and deployment.

Credential editing and Merge operation family, 2026-10-18

The next connected batch ports Credential advanced editing and Merge preparation/messages/completion. Credential Apply retains untouched origin values while explicit Save keeps its separate replacement behavior; Merge owns identity repair, replay checks, encoded/cleaned messages and Git-SVN completion. The Credential guide is also available from that Settings page's dedicated offline Help topic.

Scoped grouped outcomes, repairs, hosted evidence and remaining gaps are recorded in batch evidence. This is another partial source-family checkpoint, not a whole-port, signed Finder or App Store acceptance claim. The previous operation batch's Pages run 39150619295 built and deployed successfully, including bundled Mac Help source validation.

Stash and Submodule recovery family, 2026-10-18

Three parallel owners extended Stash preparation/completion, Submodule Add recovery and Submodule Update/Sync partial results. Stash owns identity Settings repair and closes results before post-actions. Submodule Add distinguishes a completed Add from failed child SSH key configuration and retries only that configuration against its captured checkout. Update batches large explicit selections without widening scope; Update and Sync retain attempted results for repository refresh after partial failure or cancellation. Successful completion callbacks remain separate. Follow-up Bisect and Working Tree windows inherit their originating preferences, and Quit waits for actual workers and native sheet release.

The grouped checkpoint is recorded in Stash/Submodule evidence. The preceding Credential/Merge Pages run 39152335835 built and deployed successfully. Its macOS workflow was still pending when this batch began. No full dialog, physical Finder, signed or App Store acceptance is inferred from this scoped checkpoint.

Switch, Reset and Bisect operations, 2026-10-18

Three parallel owners extended Switch execution and completion, Reset preparation and recovery, and Bisect review and progress. This connected batch keeps captured targets/options, source completion actions, owned confirmation/cancellation and actual sheet release through next-operation handoffs. Reset treats stdout as its object/reference protocol so successful Git warnings cannot contaminate its accepted target. Bisect retains attempted-mutation receipts for refreshed views, source split actions and completed progress. Root descendants retain their actual originating preferences, including Log, express Switch and Reset Cleanup routes.

The grouped checkpoint is recorded in operation evidence. The previous Stash/Submodule Pages run 39154284210 built and deployed successfully; its macOS workflow was still pending at this batch's start. Dialog/control audit coverage, physical Finder integration, current signed/Intel/older-SDK behavior and App Store distribution remain separate acceptance work.

The Debug build, 23 selected Core cases and 30 distinct native case/engine combinations pass. The checkpoint found and repaired early Switch progress-sheet acknowledgement. Retained fixtures were also corrected for actual reference refresh readiness, Git global-option parsing, captured menu-action targets, range-log dispatch and final model invalidation. Their behavioral assertions remain. All 40 recorded receiver PIDs are independently absent. Local passing cases do not establish a complete current hosted or signed deployment pass.

Remaining feature audit at this checkpoint

The 93 pending control reviews are not 93 missing features. The ledger includes external Windows examples, DrDump, Plink and test resources, as well as hidden or platform-specific controls. Several earlier chronological paragraphs describe features implemented in later batches; they are historical findings rather than a current missing-feature checklist. This review does not certify the remaining controls or all dialog behavior.

Two confirmed functional gaps need explicit treatment: upstream TortoiseIDiff advertises WMF/EMF and uses Windows GDI+; the native ImageIO/SVG decoder cannot render those metafiles. Native comparison routing also needs the corresponding format coverage. Finder drag-destination menus are absent; clipboard Copy/Move workflows already exist, while the Explorer drop-menu integration needs a macOS design. Neither adding Worktree Move/Repair (absent from the pinned upstream UI) nor repeating implemented Settings/Remote work would close those gaps.

Other open work includes source-layout/input/accessibility acceptance across the implemented dialogs, remaining workflow completion/recovery behavior, the custom TurtleGit artwork, current full hosted integration and current installed signed Finder/app acceptance. The signed preview and unsigned App Store archive remain evidence for their recorded older source revision. Distribution signing/export and App Store acceptance have not been completed. These requirements remain part of the full port; this scoped batch does not replace them.

Windows metafile comparison family, October 18, 2026

The previous checkpoint identified WMF/EMF decoding as a genuine feature gap. This batch adds a pinned MIT renderer in a universal JavaScriptCore helper, native drawing/encoding adapters, EMF+ transforms/state/clipping and dual-mode playback, original font names, embedded bitmap conversion and physical sizing. The renderer source comparison records the exact record support and remaining Windows graphics compatibility.

Native consumers decode comparisons, preview drops and conflict sides off the main actor, retain the accepted grants and operation lifetime through decoder drain, and discard retired results. WMF/EMF file types appear in the native Load Images filter; accepted Open waits for actual sheet release. Explicit IDiff/unsupported-side and explicit Merge routing remain. Runtime reconstruction retains the exact source archive, license, adaptations and compiler/package provenance without a Node or browser dependency. Source files and conflict selections retain their original bytes.

This is a connected implementation batch with grouped evidence in metafile workflow checks. A successful scoped checkpoint does not certify every Windows drawing operation, every native layout or current signed Finder/App Store deployment.

Direct Finder source transfers, October 18, 2026

Finder's selected-item Transfer action captures source URLs independently of the clipboard, then adopts the selected destination working tree through normal root and metadata permission checks. A native transfer chooser retains source-style Move/Move+Rename/Copy+Add eligibility, a validated destination and bounded recent destinations per repository. Accepted operations inherit captured preferences and wait for actual chooser/panel detachment; owner close, cancellation and deferred Quit fence late work while tokens/grants remain alive through drain.

The source comparison and batch evidence retain concrete checks and remaining gaps. Exact Finder right-drag menu replacement has no public FinderSync callback; this batch implements the native selected-source adaptation. Physical gestures, current installed signed Finder/grant delivery, every original control layout and full App Store distribution remain separate acceptance.

Settings teardown and reattachment, October 18, 2026

The older hosted ea108cf9 history workflow exposed a SwiftUI exclusive-access abort when closing Git Settings: its native probe synchronously published from graph destruction. The connected repair covers Git, Credential, Network, General, Context Menu, Merge main/colors, Remote, Hook Scripts and Email pages and the shared Settings transaction. Retirement revokes controls and captured requests immediately, defers observable cleanup and terminal replies until actual captured sheet release, and protects newer attachments from obsolete cleanup. Quit/navigation retain actual worker and modal lifetimes.

The source comparison describes the native ownership contract. The grouped checkpoint retains the exact failed Replay workflow and affected consumers. Recorded local evidence covers 24 distinct case/engine pairs, actual failed attempts and independent receiver cleanup. Hosted Intel/SDK execution, current installed signed workflows, physical layout/input acceptance and complete Settings parity remain separate requirements.

Metafile painting interoperability, October 18, 2026

The user-provided layout2vector EMF/EMF+ writers supplied an independent source comparison for reusable ImageAttributes, transformed bitmap placement and gradient brush records. TurtleGit now handles the documented subset of linear presets and blend factors, centered elliptical radial gradients, tile/axis flips, clamp colors, float/Int16/relative image destinations and separate ARGB opacity. Original source bytes remain authoritative for comparisons and conflict results.

Native SVG limitations require bounded gradient raster paints with vector clips and explicit visible bitmap copies. Serialized tile budgets and radial precision guards reject inputs that cannot be rendered within the documented limits. The source comparison and batch evidence record implementation, actual failures/repairs and final focused checks. This extends the accepted format subset; the remaining record/font/painting gaps, full hosted integration and current signed distribution acceptance remain open.

Merge activation reload and retained edits, October 18, 2026

Two- and three-pane native editors now defer external-source checks on activation, matching the source Load/Ignore/Cancel workflow. Kept versions remain visible; observation acknowledgement grants no overwrite authority. Source copy Save As, independent result copies and rebound panes retain their own guarded save receipts. The batch also covers Single/combined input roles, identical-byte atomic writes, File/Open window adoption and actual probe/sheet/grant drain across close and Quit.

The source comparison and dated batch evidence record actual repairs and focused results: 59 distinct Core methods, the Debug app, and eight native case/engine pairs with every owned receiver reaped. Physical activation, all supported filesystems, current full hosted integration and installed signed App Store acceptance remain open; these checks do not establish the whole port.

Blame zoom and revision hover, October 18, 2026

Blame now provides per-document source zoom through native View menus, existing zoom artwork, keyboard shortcuts, modified wheels and pinch. Source/attribution fonts, row geometry and gutter widths update together while retaining wrapped logical/pixel anchors, horizontal position and UTF-16 selection. Configured font preferences remain separate; the initial viewer now reads its owning defaults. Rich row tooltips use loaded full revision metadata, with cancellable missing origin lookup for complete path-filtered history and bounded Unicode previews.

The source comparison and batch evidence retain actual compile/fixture failures and final results: 38 focused Core cases, the Debug app and six native case/engine pairs, with owned receivers reaped. Physical gestures, tooltip timing, accessibility, full hosted integration and current signed App Store acceptance remain open. This is scoped Blame progress, not whole-port completion.

Finder Worktree destination and post-create continuation, October 19, 2026

Finder now offers New Worktree for one watched working-tree root or bare repository, using the existing Worktrees menu settings and source icon. The app captures the source before choosing a destination parent, revalidates both, retains metadata grants and opens the existing creation form with the upstream basename preset. No repository mutation occurs until OK. Public FinderSync lacks Explorer's right-drag interception, so source selection plus a destination chooser is the documented native adaptation; the command-line drop backend already existed.

Creation retains its completed percentage, status and timing. Submodule Update captures the created path, related source/destination scopes, appearance and preferences, waits for actual creation-window/sheet/worker release, then opens its child once. Cancellation, owner closure, late replies, retirement and deferred Quit retain ownership until their operations drain.

The source comparison and batch evidence record actual failures and passing scoped results: 30 Core methods, Debug app build and eight native case/engine pairs. Every receiver was reaped; unrelated user WIP was preserved. Physical installed Finder delivery, real signed grants, complete dialog/input and VoiceOver acceptance, full hosted integration and App Store distribution remain open. This does not certify the whole port.

EMF+ region and pattern painting, October 19, 2026

Image Compare and conflict panes now render bounded EMF+ Boolean regions, FillRegion/SetClipRegion, all 53 canonical hatch cells and bitmap texture brushes. Device clips and rendering origins survive indexed state and containers; brush matrices, wrap/reflection, Clamp and DoNotTransform retain independent semantics. Unequal-alpha hatch coverage uses premultiplied interpolation. Converted metafiles use bilinear final sampling to preserve device cells instead of wide-filter halos.

Wine's hatch table is isolated with pinned LGPL provenance, complete license, notices and corresponding patch source in the packaged runtime. Forty-four new original fixtures include geometry/color/alpha/transform and malformed/budget cases. The source comparison and dated evidence preserve actual failures and focused repairs: 26 distinct Core methods, Debug app, six cache checks and four native case/engine pairs pass, with every receiver reaped. Existing user WIP was preserved. Relative/RLE region paths, negative region rectangles, singular region fills, nested-metafile textures, older format gaps, full Windows rendering acceptance, current hosted integration and signed App Store acceptance remain open. This is real format coverage, not complete GDI/GDI+ or whole-port parity.

Main Synchronization and Add/Resolve progress, October 19, 2026

The connected progress family now distinguishes upstream Sync's inline command surface from GitProgressList's Action/Path notifications. Sync replaces the input band while running, preserves phase and percentage, and records actual Git completion before reference/conflict metadata. Its colored timed footer and Dock state retain the command outcome independently of workflow completion.

Add and Resolve have native Action/Path tables, original background artwork, source file menus, distinct keyboard/menu clipboard text, finished timing and action logging. Add captures kill-confirmation and automatic-close settings; Resolve drains file notifications before completion. Commit captures repository access, preferences and appearance and waits for actual result-window, sheet and worker release. Root and Rebase continuations share those ownership gates. Quit counts owned work even after forced window closure.

The source comparison separates these changes from full upstream dialog, physical input/Dock/VoiceOver, installed signed Finder and App Store acceptance. Dated grouped evidence records four focused Core methods, Debug build and ten native case/engine pairs passing, with actual failures and focused repairs retained. All receivers were reaped; unusable optional content captures were not published. No screen or fixture count certifies the whole port.

Hook Scripts editor and owned decisions, October 19, 2026

Hook Add now begins disabled with no type or path, Copy clears its new scope, and local/global toggling retains the typed global draft. Existing-folder checks, the five-column native checked list and whole-row editing follow the pinned settings family. Choosers capture their owner and draft and publish only after actual detachment; equivalent binding writes do not discard accepted responses.

Scope/command identities and approvals compare original bytes while preserving existing configuration fields. Script grants use exact path records, retain legacy ordinary entries and renew only the same resolved stale grant. Partial acquisition and process failures release acquired access. Approval/failure questions and actual script/read work retain their ownership through cancellation, retirement and drain; pending launches block Quit too.

Source comparison and dated evidence record nine Core methods, Debug build and six distinct native case/engine pairs passing. Failed attempts and focused repairs are retained. A hidden Return event was not delivered; the actual No default cell and button action were verified instead. Physical input, the existing-local editor value presentation, signed sandbox grants and whole-port acceptance remain open. No new screenshots or full hosted pass are claimed.

Repository Browser working actions and child handoffs, October 19, 2026

Browser contents menus refresh the shared working-file mark before capturing their actions. New marks replace the current choice; repeated publication of the same mark preserves a subsequently chosen local historical mark. Clearing the shared mark removes the matching imported working choice while retaining a local historical choice. A changed or cleared mark rejects an old captured comparison. The live removal is an explicit native extension of the pinned source's nonempty DiffLater import. Initial contents focus waits for the first owned table/load settlement and is applied once; refresh, user folder/field focus and owned children do not repeatedly lose focus.

Working and marked comparisons, child submodule Log/Browser and Update routes capture their originating browser preferences, appearance and repository access. The unavailable-submodule question retains its request through actual sheet detachment before routing Update. Duplicate, stale, cancelled, retired and Quit replies cannot open a child; actual pending work remains counted through drain.

Working comparison, submodule resolution and historical Revert validate every path prefix against raw tracked paths and actual directory entries. Device/inode lookup identity detects Unicode/case aliases on the current volume, including untracked and ignored items, without rejecting distinct entries on sensitive volumes. The exact indexed scope may authorize macOS's equivalent Unicode disk spelling; an untracked or differently cased alias cannot substitute for it. Historical blob reads retain their pinned exact paths. Raw invalid-UTF8 filenames remain outside the supported boundary. Filesystem changes between validation and use remain an unavoidable race in this path-based Git workflow.

Browser source comparison and the forthcoming grouped batch record describe this scope; no passing build or check is claimed here before results are recorded. Physical menus/focus, Finder delivery, VoiceOver, exhaustive submodule/Revert combinations, signed grants and complete Browser/application parity remain open.

Primary Merge progress and recovery handoffs, October 19, 2026

Primary Merge now uses the shared native selectable progress output, including source diagnostic/URL styling, icon-aware Copy/Copy All, terminal status and the timing/date suffix. Timing is captured at Git completion before recovery reads or questions; disabling timings retains the status. The current-work label changes to the result and the completed progress bar retains 100 percent. Original Git output remains separate for repository refresh and error classification. Cancelled Git results keep their real exit code. Cancellation before a process result uses the explicit native User cancelled fallback; failures without an exit code use Operation failed. Failed conflict-status reads remain visible diagnostics.

The source result/recovery choices retain their order and conditions. No Commit and Squash offer Commit without adding committed-branch Push/removal/SVN actions. Conflict reminders, process-cancellation questions and branch-deletion questions settle after actual sheet detachment; duplicate/late/retired/Quit replies cannot start stale work. Post-actions wait for result-window, child and actual worker/read drain, carrying their originating repository permission, preferences and appearance. Per-instance pending-work accounting and workDidDrain keep forced closure owned until actual producers and one-shot questions settle. A forced close cannot run a queued handoff. Commit, Resolve, Abort, Stash Save/Pop, Push and SVN receive an appearance/opacity value snapshot from the closing progress window, avoiding retention of that window merely to present the next child. Unrelated-history retry keeps its own attempt/completion boundary. Close keeps the merge result; Cancel/title-bar dismissal checks conflicts before Abort Merge.

Source comparison and the forthcoming grouped evidence describe the scope; no passing validation is claimed before results are recorded. Physical output/ question/menu/default/Escape/VoiceOver acceptance, complete source geometry, all recovery/post-action combinations, signed sandbox/Finder and whole-port acceptance remain open. Windows taskbar and native Dock rendering differ.

Switch/Reset command progress and recovery, October 19, 2026

Switch and Reset now capture the real Core command invocation immediately before launch and prepend its quoted executable/argument display to progress output. There is no second UI argv builder, and display quoting does not change Git's argument-array execution. Existing styled native output now includes distinct completion ranges, execution timing/date, result current-work text and retained 100 percent completion. Post-command metadata retains its own diagnostic boundary; a failed Reset bisect-state read does not relabel a successful command. Cancelled Git results use their real exit code, with explicit native labels when no process result exists.

Queued start/retry work reserves per-instance and Quit ownership before scheduling. Actual command/metadata work retains its token and grant through invalidation and drain. One-shot kill questions wait for actual sheet release; result closure and child handoffs wait for work and native children. Forced closure cannot dispatch a queued child. Captured appearance/opacity values and the original preferences/ access reach Switch's Submodule/Merge/Pull/Commit/Stash and Reset's Submodule/Clean/ Bisect factories. Switch's source Resolve-labelled failure action still opens Commit. Existing source post-action ordering and Reset's original-plan/changed-HEAD guard remain authoritative.

Switch comparison, Reset comparison and the forthcoming grouped record define this scope; no passing validation is claimed before results are recorded. Physical menus/questions/keyboard/VoiceOver, all recovery combinations, complete source geometry/rendering, signed grants, Windows libgit2-progress equivalence and whole-application acceptance remain open.

Stash Save/Export results and follow-up ownership, October 19, 2026

Stash Save and Export now prepend the actual Core command invocation and retain styled completion ranges, timing/date and 100 percent after command settlement. Save's final stash-reference read and Export's atomic destination replacement remain distinct owned phases. Later metadata/finalization diagnostics preserve the actual Git receipt, and completion actions require full workflow success. Both native output views receive captured preferences and private clipboard ownership. Save's source Pull/Merge/Pop/Apply order and Export's success-only Explore action remain; Apply/Pop retain their source system-progress/result-question workflow.

Queued start reserves work before scheduling; invalidation/forced closure retains actual worker/read/finalization drain. One-shot kill questions and result/options callbacks wait for real sheet detachment. Intended child/reveal handoffs follow actual closure; forced closure and Quit cannot dispatch stale work. Stash child factories and Restore→Working Tree carry appearance/opacity snapshots, preference identity and repository grants. Different Working Tree preference owners retain independent drafts/cache entries, and repository refresh/rename fan out to all owners of that root. Export options and results participate in Quit fencing.

Stash comparison, Export comparison and grouped evidence distinguish source behavior, native adaptations and actual validation. This scoped work does not establish exhaustive visual/physical/Finder/signed/App Store acceptance, complete hosted CI or completion of the entire port.

Repository creation result family, October 19, 2026

Clone now shares the styled native command log, captured Copy/preferences, actual invocation and completion receipt/footer/timing100. Command success, post-clone configuration warnings and repository inspection retain separate outcomes. Retry/open-only retry, source actions and independent workspace adoption remain. Options/panels/result/questions retain actual worker/native release ownership; stale form, forced-close and Quit callbacks cannot launch late children. Show Log/Explore dispatch only after intentional result/options closure, carrying captured repository access, preferences and appearance values.

Init retains source Bare/text/buttons and simple warning/error/success workflow. It captures the accepted bare form, owns one-shot actual-detached questions and retains init/discovery/grants through forced closure. Errors remain reviewable for retry; success closes only after acknowledgment. Root retains the originating workspace and prevents reopening an already retiring cached Init controller.

Clone comparison, Init comparison and the grouped record define the implementation and actual verification scope. Physical/all-source UI parity, Finder folder artwork, live authentication/git-svn, signed sandbox/App Store and whole-port acceptance remain open.

Branch/Tag acceptance and captured creation family, October 19, 2026

Creation now follows the source form-acceptance boundary before remembering its Switch/Push checkbox. Invalid name/cross-name Abort preserve saved defaults; accepted forms remember their choice before later base/Git errors. Immutable Core form/plan phases preserve existing exact names, prepared local/tag hashes and Git remote tracking semantics, without pretending to provide an atomic transaction.

Native source-default cross-name, error and cancellation questions settle after actual sheet detach. Actual queued create/load/description/chooser/Switch and native child release retain owner/Quit lifetime after forced closure. Description recovery does not recreate or re-checkout a branch. Tag Push opens only after an intended drained creation close with captured full ref, preferences, access and appearance; forced or stale/Quit replies cannot dispatch it. Source controls, icons, option order and direct-Git result behavior remain.

Source comparison and grouped record distinguish actual checks from physical/full visual/signing/transport/sandbox/App Store acceptance.

EMF+ indexed and 16-bit bitmap family, October 19, 2026

The shared renderer now decodes indexed1/4/8 palettes and RGB555/RGB565/ARGB1555 raw bitmaps in image objects and texture brushes. Shared parsing accounts for palettes before scan lines, retains packed ordering, alpha, signed row layout and padding, and refuses malformed palette/index/stride/storage combinations. The existing 24/32-bit conversion and original comparison/conflict bytes remain in use. Native Compare, preview and conflict consumers receive the formats through their existing background decoder, rather than introducing another UI.

Format contracts and remaining graphics behavior and batch evidence distinguish this implementation from complete GDI+/physical/signed/App Store acceptance.

Custom TurtleGit application identity, October 19, 2026

New generated turtle/Git artwork replaces the earlier upstream-derived app branding across the ten native application icon slots, patch-document ICNS, shared menu/Finder/cache/authentication image, launch introduction and all five About variants. The unmodified high-resolution RGBA source and exact generation prompt/hash remain tracked. Deterministic packaging derives the native sizes and website artwork; pinned upstream originals remain separately attributed. Ordinary command glyphs and Finder status overlays retain their source artwork.

Application identity records the actual source, consumer and bundle checks, previews and remaining physical/signed/App Store acceptance. Historical screenshots are not retouched to imply newer captures.

Current signed metafile runtime, October 19, 2026

The universal development-signed AppStore candidate now includes the packaged metafile helper and custom TurtleGit artwork. Actual disposable sandbox parents pass Git/Lexilla/App Group sharing and denial, and native loading of eight WMF/EMF/EMF+ images spanning vector/text/bitmap/gradient/region/hatch and selected indexed4/RGB565 texture behavior. Malformed refusal, a post-launch helper deadline, source preservation and private/process cleanup pass. The complete shipping candidate inventory stays unchanged. Dated evidence retains measured dirty inputs and exact scope. Installed shipping GUI/Finder, all-format fidelity, physical Intel/minimum macOS and distribution/App Store acceptance remain open; the older preview/archive were not regenerated.

Format Patch progress review and mail continuation, October 19, 2026

The connected export→progress→Send Mail family now uses an actual Git command receipt for review/copy, captured output preferences/private clipboard and owned native progress/question retirement. Mail begins after the progress sheet really detaches, carrying captured output permissions. Cancellation, forced closure, Quit epochs and late callbacks retain/drain their work without launching stale continuations. Existing export modes, full-stdout patch discovery, policies, retry and shared Send Patch composition remain in use.

Source comparison and batch evidence separate selected checks from physical/visual, live mail, signed external grants, Finder and App Store acceptance. Full source parity remains unproven.

Request Pull waiting, configured editor and authentication, October 19, 2026

The connected Request Pull family preserves source branch ordering through originating preferences, accepts its form before owned indeterminate generation progress and waits for actual Git/private-write/native-sheet drainage before editor, mail, error or cancellation continuation. Generated documents use the configured Alternative Editor and retain Open request recovery; shared Send Mail options retain captured files/permissions/appearance. Source histories and End validation timing remain. Git/SSH askpass inheritance now includes the actual request-pull transport command. Picker reads, submission/field contexts, Quit epochs and forced closure fence stale continuations.

Source comparison and batch evidence distinguish the selected checks from public transports, real editor/Apple Mail/TCC/credentials, physical visual/input parity and signed/App Store acceptance.

Connected exact-text settings family, October 19, 2026

Git identity, credential grouping/selection/field masks, proxy credentials and SSH preferences now distinguish exact entered Unicode spellings. Invocation-local Git config argument handling preserves those values even when the repository's stored precompose preference is enabled. Shared save confirmation, captured drafts, stale snapshot refusal, source write order, included origins and unknown credential fields remain connected to their existing native settings consumers.

Source behavior and remaining gaps and batch evidence separate the grouped private-state checks from production Keychain, live transports, signed grants, physical controls and complete source/App Store acceptance.

Explicit metafile native raster family, October 19, 2026

A terminal hosted follow-up passed app/extension compilation but failed three metafile pixel methods (86 assertions within 2,089 Core methods). The native SVG fallback previously assumed an unspecified intermediate image was always 2× and then reconstructed it again, blurring hatch cells and wrapped gradients on the hosted platform. The continuation controls intrinsic raster dimensions, sRGB color and embedded-paint interpolation, removes the helper's backing-scale guess, and retains pixel, alpha, phase, geometry and resource-limit assertions.

Compatibility evidence records the terminal hosted failure, local grouped scope and remaining hosted/Intel, physical and current signed distribution acceptance. Earlier local checks alone do not establish cross-platform rendering parity.

Optional libgit2 Clone/Fetch/Sync transport — October 19, 2026

The previously stored UseLibgit2 master switch now has connected Clone/Fetch consumers with the source operation mask and unchanged command-line defaults. The actual pinned engine, native combined credentials, same-connection HTTPS certificate review, source-shaped fields, temporary authority/certificate exceptions, progress and cancellation/export ownership are connected through Clone, Fetch, Fetch & Rebase and Sync tag fetch. The universal private runtime carries source, patch, licensing and reconstruction metadata. See scope and QA. Other libgit2 command consumers, complete HTTP/provider compatibility and public/signed/physical/App Store acceptance remain open; this is not complete backend or whole-app parity.

Symbolic-link Blame family — October 19, 2026

Committed symbolic links now participate in the same Blame blob/attribution, history/rename and previous-revision workflow as regular files. File Open/MRU, Log and Browser handoffs retain the link's own path. Finder/command-line entry and native grant reuse use parent/root containment without reading the link's target. Captured callbacks, actual cancellation and old-document retention stay within their existing owners. Source scope and QA separate this implementation from physical Finder/powerbox, signed grants, accessibility and complete Blame/App Store acceptance.

Remote-reference engine family — October 19, 2026

Remote reference/tag catalogs and remote tag/branch deletion now honor the source libgit2 mask through native remote pickers, Browser deletion and Sync tag work. The actual engine retains per-reference rejection/partial success, native prompt and cancellation ownership, captured preferences and source HEAD-list differences. Source comparison and batch evidence keep the shared authentication continuation, other backend consumers and public/signed/physical App Store acceptance explicit rather than declaring the engine or port complete.

Historical materialization continuation — October 19, 2026

The historical file family connects the source default GetOneFile backend to historical opening/editors, Save As and selected/recursive output. Accepted operations retain their engine choice through panels and delayed file delivery. Raw comparison and Blame readers remain distinct; source filter semantics and actual grouped evidence are recorded in that family.

Clone checkout-filter continuation — October 19, 2026

The Clone checkout family connects configured custom smudge filters to selected libgit2 Clone and its recursive checkout option. It distinguishes initial destination cleanup from later recursive partial work, retains bare/no-checkout suppression and owns actual filter cancellation/progress. Configured LFS one-shot smudge, source boundaries and grouped evidence are tracked in that family; it does not claim persistent filter-process or complete providers.

Shared Git transport authentication — October 19, 2026

The shared authentication family covers the native credential form layout, username-dependent focus, missing-value feedback, readable certificate identity/validation diagnostics and temporary certificate acceptance across separate helper calls. Actual authority/port/DER scoping, operation-private exchanges and prompt/export retirement preserve cancellation ownership. Password persistence and permanent trust are outside the selected source callback. Grouped evidence records the verified scope; physical/signed, public-provider and full hosted acceptance remain open.

Source-selected Add/index family — October 19, 2026

The Add/index continuation connects source-default Add10 selection, configured clean filters, private-index publication and mode post-actions to the native Add/status family. Commit's explicit Add now owns the shared progress sheet; Rebase and workspace entry retain accepted backend and preference snapshots. Per-path receipts, actual worker cancellation and final publication remain owned. General Commit staging and its separate backend bit retain their independent contracts. Grouped evidence and remaining acceptance are recorded with that family.

The Commit index engine and Blame author/details panes complete two further implementation families in a shared grouped checkpoint. Commit owns its separate source engine choice/cleaned tree and Blame gains native selected-value and author controls. Evidence separates actual checks from the remaining full hosted, physical/signed and source-layout gates.

Revert completed-result workflow — October 19, 2026

The Revert result family now connects the shared native file-progress surface: source-ordered file menus, double-click open/reveal, independent selected-path and action/path copying, post-completion sorting and status colors. Captured result attempts, chooser/launch lifetime, sheet detachment and Quit ownership cover standalone and workspace, Resolve and Rebase callers. The existing Trash, Retry and submodule post-actions retain their operation boundary. Source scope and grouped verification are tracked in the Revert result parity guide; this implementation does not establish full physical, signed or source-layout parity.

Optional Clone/Fetch result notifications — October 19, 2026

The captured libgit2 Clone/Fetch branch now carries typed full-OID reference updates and literal checkout-file receipts from the private helper into native Action/Path result lists. Captured old/new Log ranges, recursive repository identity, file actions, separate copy formats, sorting, saved action logs and owned chooser/launch cancellation accompany the source backend gate. Metadata loss produces an explicit warning while preserving the actual Git result. The source scope and grouped evidence keep default command-line/SVN behavior and remaining physical/signed/full-layout acceptance separate from this implementation family.

Compare/Merge pane input — October 19, 2026

The connected input family covers caret and Shift-selection traversal around collapsed source sections, source smart Home with native aliases, and deletion through Empty alignment records while preserving actual blank lines. Both comparison panes and the merged result use the existing edit/Undo transactions; source panes keep navigation with their read-only protection. Explicit Find, Go To Line and history reveal remain separate from ordinary movement. The source contract and checkpoint record the actual validation and remaining physical/signed/editor parity limits.

Selected Reset and Log commit-revert backend — October 20, 2026

The connected selected-engine family adds Reset5 and Revert6 dispatch, captured preferences, Hard Reset pre-overwrite recycling, typed checkout/progress records and owned native result actions. Parent-side macOS Trash acknowledgments retain literal targets and partial outcomes through refusal/cancellation. Log preserves its commit-level Skip/Abort loop, message aggregation and Commit review, including the pinned library's zero-result conflict state. The source contract and dated checkpoint distinguish actual validation from physical, signed and remaining source acceptance.

Selected-file macOS Services — October 20, 2026

The six Log/Commit/status/Diff/Clone/Create Services capture literal selected URLs outside Finder Sync's watched roots and route through owned repository permission and discovery. Cold-start, standalone-tool forwarding, busy/Quit rejection and chooser cancellation retain the request's original owner and paths. The implementation scope and remaining acceptance distinguish macOS Services placement from Explorer menus. The Debug app, 23 distinct focused Core methods across the checkpoint and repair, provider check and both Git-engine native routing cases passed. Evidence records the encoded-NUL and fixture URL repairs and owned cleanup. Physical registration, signed sandbox and App Store delivery remain open.

Apply Patch Serial identity and recovery ownership — October 20, 2026

The connected mail-import family checks all four effective identity fields before Apply and completed OK, uses the full owned Git Settings loop, and retains failed recovery sessions for retry with captured-session validation. Forced close holds workers, grants and child replies through actual drain. The source contract separates git am from recorded-base patch review and records the deliberate failed-abort close adaptation. The Debug app, twelve distinct focused Core methods with system and bundled Git, and six native case/engine checks passed. Evidence records the one derived object timestamp repair, corrupt-state keep-close correction with only the two affected native cases repeated, actual scope and owned cleanup. Physical, signed and complete upstream dialog acceptance remain open.

Classic WMF/EMF Boolean raster family — October 20, 2026

The connected implementation batch adds full ROP2/ROP3 truth-table evaluation, white destination playback, independent coverage and the related WMF DIB/PATBLT and EMF bitmap-transfer records. Saved DCs, source crop, brush selection, transforms and clipping belong to the same operation contract. The bounded native raster bridge retains private helper cancellation and original source bytes. The source scope and limits distinguish evaluator coverage from unsupported masks, transfer geometry, device-dependent formats and EMF+ compositing. The grouped evidence records 13 distinct focused Core methods, the initial failures and three-method repair pass, and four passing native case/engine combinations with owned receivers reaped. Local scoped passes do not establish full hosted, Windows visual, Intel execution or signed distribution acceptance.

Log Statistics author identity — October 20, 2026

The connected author family carries exact decoded-name identity through summary counts, interval measurements, activity/authorship ranking, slider omission and graph projection. Native chart grouping and color scales use graph positions so canonically equivalent display strings and a real author named like synthetic Others retain independent groups. The summary, tooltips, legend and captured export preserve original display names. Source scope and remaining acceptance record this behavior and its decoded-input/locale limits. The grouped evidence records 19 passing focused Core methods plus the new actual-Git bundled check, and passing native groups with both Git engines. Two pixel-fixture assumptions were corrected from retained output; no extra app/Core rebuild was needed. Physical, full hosted, signed and complete dialog acceptance remain open.

First-use Finder repository workflow Services — October 20, 2026

Thirteen additional selected-item Services connect transport, branch/tag, Switch, Merge/Rebase and the four stash actions to existing native workflows. The typed request retains source cardinality and literal selection; discovery checks live source eligibility before dispatch, with owned repository access and independent child lifetimes. Multi-root Pull/Fetch/Push keeps selected-root order, waits for each actual dialog and worker drain, skips invalid roots and continues after per-dialog cancellation. Owner closure cancels the remaining queue while retaining live operation/grant accounting. Explicit Stash Apply/Pop retain source execution semantics. The scope and remaining acceptance and batch evidence distinguish local checks from physical registration, signed grants and complete Finder parity.

The focused checkpoint passed eleven Core methods, the existing provider check, and expanded provider/routing checks with both Git engines. The multi-root Fetch case passed with both engines after a PID-publication fixture race was repaired. A trapped receiver exposed a private held-helper cleanup gap; the owned wrapper was stopped and a dedicated Python cleanup probe passed. The final app build passed after an explicit main-actor annotation repair; Core was not rerun for native-only changes. Evidence records exact scope and separate CLI, physical/signed and unverified Pull/Push multi-root acceptance limits.

First-use Finder selected-file workflow Services — October 20, 2026

Thirteen additional Services complete the selected-file Add/Revert, Resolve, Blame/previous-version/conflict-editor and four Ignore routes, for thirty-two Service declarations. Live source predicates retain cardinality, literal paths and repository ownership; asynchronous preparation carries its originating Services context into actual child windows. Add selected files and quick Resolve retain their real Git effects; folder Add, Revert, Ignore and other review dialogs retain their native controls and questions. Multiple Edit Conflict paths consume the first captured path, matching upstream. Ignore mask menus and rules retain upstream dotfile/trailing-dot suffixes and multi-selection behavior; directory leaves are skipped and symlinks remain Git leaves.

Source scope and remaining acceptance and the batch evidence distinguish focused local checks from physical menu registration, signed sandbox access, full hosted integration and complete TortoiseGit dialog parity. The separate CLI transport batch gap remains open.

The focused checkpoint passed twenty-three Core methods, the app build, the actual Finder menu builder and five distinct Services provider/path/conflict case/engine combinations. Initial compilation exposed a Core reference to an app-only helper; the equivalent enum gate repaired the layer boundary. Native fixtures needed Git check-ignore flag, Open-readiness and source-menu adaptation projection corrections. Only affected scopes repeated; Core/app were not rebuilt for fixture repairs. All nine recorded receiver PIDs, including failed attempts, are absent. These scoped passes do not certify current hosted CI or signed Finder/App Store deployment.

Ordered command transport and connected result workflows — October 20, 2026

The Fetch/Pull/Push command family now retains original path-list count, order and duplicate roots through direct arguments and authorized pathfile decoding. Each original multi-root entry uses strict working-tree/bare-root preparation; invalid entries are skipped, and individual dialog Cancel or operation failure continues to later roots. Fetch remote and Push branch presets remain editable captured input in each actual form.

Native transport ownership spans options, actual Git operations and result windows plus source-modal Reset, Switch, Rebase, Stash, Request Pull and mail follow-ups. Independent source-process commands remain separate windows. Saved primary grants can cover roots independently; missing batch authority uses an owned asynchronous folder chooser. Workspace retirement/adoption and Quit cancel the current owned chain and remaining queue, while exact workers and detached sheets retain their access and accounting until drainage. The same lifetime mechanism covers Finder Services without replacing its distinct source-menu eligibility rules.

Command-line behavior, transport presentation and batch evidence distinguish this connected source scope from current full hosted integration, physical interaction, signed sandbox grants and App Store distribution acceptance.

The checkpoint passed four focused Core parser methods, the final app build and ten distinct native case/engine combinations: six CLI dialog/effect/lifetime combinations with both Git engines, plus related Services, retained network, Request Pull and Format Patch groups with system Git. The recorded failures exposed an explicit-self compile error, directory-hint URL enrollment mismatch and an overbroad CLI bare-Pull guard; affected app/native checks passed after repair. The older network fixture also needed its optional reader-hook fallback. All fourteen recorded receiver PIDs are independently absent. No complete Core rerun followed native-only repairs, and no complete hosted, installed signed or whole-port claim follows from this scoped checkpoint.

Classic EMF masked and transparent transfer family — October 20, 2026

The image comparison decoder now implements MASKBLT foreground/background ROP4 truth tables, PLGBLT parallelograms and repeating monochrome masks, TRANSPARENTBLT exact RGB color keys, and ALPHABLEND constant and premultiplied per-pixel alpha. Mask selection follows bitmap bits independently of palette colors. Destination clipping, saved state, source crops and original repository bytes remain part of the contract. Unsupported or malformed required operands refuse the whole conversion rather than expose a partially painted image.

The same native compositor and bounded helper serve comparison panes and binary conflict review; accepted conflict choices must write the original metafile bytes. The connected painting review also identified a hosted regression: raster background-state interception bypassed positioned text state, while opaque text rectangles used the selected brush instead of the background color. That shared state repair belongs to this painting batch.

Source semantics and limits distinguish these classic EMF records from device-dependent WMF payloads, separate EMF+ compositing, remaining Windows font/edge compatibility and signed distribution acceptance. The checkpoint passed twelve distinct focused Core methods cumulatively, the universal helper and app builds, and four native comparison/conflict case/engine combinations with system and bundled Git. Initial checks found duplicate antialias coverage on skewed image operands and an invalid transparent-canvas fixture expectation. Bounded inverse-mapped operand planes, half-open crop clamping and exact white-DC assertions repaired those cases; only the six affected transfer methods repeated. The previously failing hosted positioned-text method passed locally. Native fixture entry discovery and Swift expression complexity needed preparation repairs before launching; their assertions remain intact. All four native receivers are independently absent. Batch evidence records failures and scope; this is not a complete hosted, visual or signed distribution pass.

Native issue-provider callbacks and credential workflows — October 20, 2026

The provider registry now supports the retained offline catalog and an embedded HTTP/JSON tracker adapter. Settings association selection, validated options, credential drafts, Apply/Cancel, picker loading/Refresh/filtering, message/issue selection, pre-staging validation and post-success completion form one connected workflow. Bearer tokens stay in the exact endpoint's app-private Keychain entry; failed or retired Settings publication rolls back credential changes.

An enabled exact-root local association authorizes remote requests. A shared project fallback alone cannot send drafts or paths to a server. Requests are bounded, ephemeral, redirect-free and cancellable, retaining ownership through URLSession invalidation. Native picker close fences late results and waits for network/sheet drainage; Commit and application Quit preserve pending ownership. Successful Git operations capture their revision within the repository actor before provider completion can suspend. Completion warnings/failures retain Git success and cannot retry the commit or substitute a later HEAD.

The user/protocol guide, source comparison and privacy disclosure distinguish this data adapter from Windows COM binary execution, vendor-specific options/discovery and installed signed/App Store acceptance. The checkpoint passed nine distinct focused Core methods cumulatively, the app build and six native case/engine combinations with system and bundled Git. Compilation needed a provider initializer repair. Core fixtures needed bounded process reaping and startup receipt handling; the sampled hung test process was terminated only after its helper had exited. Native fixture isolation/readiness repairs retained the actual sheet, Git and ownership assertions. Only affected or previously unrun checks repeated. All seven native receivers, including the failed attempt, and the terminated owned Core process are independently absent. Batch evidence records the actual scope and failures. No complete hosted, installed physical or signed distribution claim follows from these local checks.

First-use Finder filesystem Services — October 20, 2026

Rename, Delete, Delete (keep local) and Cleanup now join the registered macOS Services family. These entries connect existing native forms and Git operations after repository discovery, access authorization and the pinned shell's live eligibility rules. Rename retains singleton selection; both Delete modes retain ordered paths and distinct index/disk effects; Cleanup keeps folder scopes through its options-to-progress handoff. Ordinary repository-root exclusions and the registered-submodule exceptions remain command-specific. Selected symlink leaves retain their literal identity.

Forms keep the repository captured at dispatch while the workspace can open another repository. Forced close retires panels/questions, cancels work and fences late replies; final callbacks and access release wait for actual workers and child-sheet detachment. Application Quit observes open children and detached retirement. Retired Rename/Delete forms cannot be reused before drainage.

The Services guide records registration, source rules and remaining physical Finder/signed sandbox acceptance. The grouped checkpoint and actual failures are recorded in batch evidence. The checkpoint passed sixteen distinct focused Core methods cumulatively, the app build and five native case/engine combinations: provider registration once, plus effects and ownership with system and bundled Git. New fixture assertions needed corrections for the committed registration order and URL directory hints; only failed or previously unrun scopes repeated. All seven native receiver PIDs, including failed attempts, are independently absent. Generated localization/Help checks passed and the final Help wording received a bundle resource refresh. This expansion does not establish all Finder commands, installed extension acceptance, complete upstream dialog parity or App Store readiness.

First-use Finder Worktree and Submodule Services — October 20, 2026

Six linked-repository Services connect native Worktree List/Create, Submodule Add/Update/Sync and parent-folder history. Source predicates and literal ordered scope survive repository discovery and native successor windows. Worktree List uses an explicit singleton macOS boundary; New Worktree adapts the upstream right-drag source root into a native destination chooser. Update/Sync selected gitlink roots and parent Log retain the containing superproject. Parent-history eligibility is evaluated against the selected child's live registration metadata. Actual parent primary grants remain distinct from retained metadata grants.

Submodule forms and progress now retain workers, grants, SSH prompts and native children through forced close and late responses. Worktree List owns its Create child until its worker/picker retirement completes; creation destination replies settle exactly once and cannot approve a retired owner. Application Quit observes open native children and detached retirement. Services registration preserves the previous thirty-six entries in order and appends six folder entries, forty-two total. Existing source artwork, control layouts, histories and operation options remain shared with the application commands.

The Services guide documents adaptations and remaining gaps; batch evidence records actual validation. Twenty focused Core methods passed, followed by the app build and seven distinct native case/engine combinations cumulatively. The first native submodule case found parent Log missing its Services presentation enrollment; the affected app build and submodule case, plus previously unrun Worktree and ownership cases, passed after that connection was repaired. Passed provider and Core checks were not repeated. All eight native receivers, including the failed attempt, are independently absent. Generated localization/Help checks passed and the built Help bytes match the generated guide. Installed Finder Services activation, signed sandbox operation, minimum-OS/keyboard/VoiceOver/visual acceptance, complete upstream parity and App Store distribution remain unproven.

Paused older/external Rebase action recovery — October 20, 2026

Recognized older and externally created paused sessions now feed the durable Pick/Edit/Squash/Skip workflow. A read-only projection retains full occurrence history and the current draft identity. The first explicit future-action change publishes the adopted command skeleton and requested action with captured identity/message metadata. Completed Git commands and current HEAD/index/worktree remain untouched. Structural labels, reset/merge and reference-update commands retain their original meaning rather than being regenerated under new names.

The existing native window, action menus/icons, keys, saved drafts and cancellation ownership remain connected through save, reopen and actual Continue. Unsupported custom commands are refused without discarding their todo. Checked journal publication retains rollback/roll-forward at the todo commit point and the older journal compatibility boundary. Source comparison and batch evidence distinguish this accepted family from arbitrary custom conversion, physical/visual/minimum-OS acceptance, complete upstream parity and signed/App Store distribution.

The checkpoint passed twenty distinct focused Core methods cumulatively and six native case/engine combinations with system and bundled Git. Initial static review repaired repeated-hash identity in the remaining reader before Core validation. Native preparation needed an entry annotation correction; structural QA then needed a valid earlier Skip target rather than the source-refused merge first parent. The passed groups stayed intact. A confirmed Current Skip display bookkeeping gap received its affected app refresh and one additional actual Skip/reopen/future-edit/Continue regression, without rerunning passed suites. All seven native receivers, including the failed runtime attempt, are independently absent. Generated localization/Help checks passed. These local results do not certify complete hosted, physical, signed or whole-port parity.

Shared native graph scenes and enhanced-metafile output — October 21, 2026

Statistics and Revision Graph now export genuine enhanced EMF using the source .wmf suffix or explicit .emf alias. Native drawing and graphical exports share ordered geometry, source palettes and captured fonts. Statistics restores its source Pictures default and retains five native chart styles with hover and accessibility geometry; Revision Graph retains arrows, selection markers and Base captions. SVG/EMF shape native text into glyph paths, with bounded label-local color-font images; SVG editable text remains an explicit source difference. PDF keeps native text. Interactive Revision Save now captures immutable scenes before its panel and retains a cancellable staged writer until actual completion.

The contract and limits and dated evidence record 31 distinct Core methods and 24 native case/engine combinations passing across focused repairs. The initial test compile literals, app actor/accessibility calls, thin-stroke pixel oracle, dynamic edge alpha and older fixture compile ambiguities are recorded. Only affected failed/unrun groups repeated. Two new complete Statistics chart captures were reviewed and updated; all 25 receiver attempts are absent. Complete Windows geometry/font identity, physical/signed and minimum-version acceptance, current full hosted CI, whole-port parity and App Store distribution remain open.

First-use Finder history and reference Services — October 21, 2026

Five Services connect RefLog, Browse References, Repo-browser, Revision Graph and Daemon to previously unmonitored selections. The original forty-two declarations remain unchanged and the five append in order, forty-seven total. Fresh source folder/bare/tracked/added predicates apply after actual access and discovery. A confirmed folder aggregation defect now follows GitStatus::AdjustFolderStatus: added/deleted children mark containing folders modified while literal leaf and exact overlay states remain separate. Added-file exclusion is retained.

Accepted preferences are captured before permission/discovery and travel with the repository and primary access through native windows and later history actions. Closing controllers cannot be reused, late callbacks cannot clear replacements, and actual reads, mutations, Save writers and owned child sheets remain accounted for until completion. Graph Filter/Find, reference pickers/remote settings, historical browser Save and Daemon questions/worker retirement share those fences. The native dialogs, icons, histories and operation choices remain the existing source-backed workflows; Services keeps macOS's system placement and icon limits.

Source contract and limits and dated evidence record 67 distinct Core methods and eight native scenarios passing across focused repairs. The initial app accessor, confirmed folder classification and fixture compile/helper repairs are recorded. Passed unrelated groups were not repeated. All ten receiver attempts are independently absent. No new capture or installed activation was performed. Physical Services, signed grants, minimum-OS/Intel, keyboard/VoiceOver, complete source/layout parity, hosted CI and App Store distribution remain open.

Main dialog controls continuation

The connected Commit, Log and Settings continuation addresses source form commands and metadata ownership, revision-list column fitting and owned header questions, and direct Colors appearance transactions with compact native groups. Scope and remaining work distinguish these changes from complete dialog parity. The grouped checkpoint record reports actual validation scope and failures after implementation freezes.

Compare/Merge panes and patch application continuation

The pane presentation family connects compact source-colored headers, literal identities, dirty/active state and focused caret and marked-word status across Compare and Merge. The patch policy family connects captured AutoAdd, per-file progress/results, readonly automatic actions and explicit Backup/Keep/Delete decisions. Automatic PatchSave retains its separate source empty-result policy. The dated checkpoint records actual checks and failures. The source text-patch adapter gap remains explicit; this continuation does not claim complete patch or editor parity.

Decoded source text-patch workflow

The Unicode/source patch family connects decoded UTF-16/UTF-32 and GNU/SVN headers to existing target discovery, Review, original byte Copy/Save, per-file comparison and checked application. Parsing and pure simulation retain source hunk, keyword, BOM and automatic-EOL semantics. The Git engine remains authoritative for successful ordinary patches and opaque binary or special-file records. Accepted encoding policy crosses native preparation and preview; mode, rename/copy and input state remain part of the Core receipt. The family guide and its dated evidence distinguish implemented behavior from actual grouped verification and remaining acceptance.

The October 23 Statistics interaction continuation unifies native/export hit geometry with source tooltip priority, virtual averages, first-series group selection, sparse line rectangles, integer bar borders and tiny-pie endpoints. Chart callbacks now capture form and projection receipts and respect actual save/error sheets, held exports, Quit and retirement. Six native case/engine pairs pass after one fixture-only average-band collision repair; no Core production changed or Core suite was repeated. See the parity scope and dated checkpoint.

The October 23 viewport navigation family connects Graph zoom-origin preservation, focused source key distances, Escape/cursors and current-press gesture ownership with explicit all-pane Compare/Merge scroll commands. The editor submenu is a documented native discovery adaptation; text/caret shortcuts and editing history retain their contracts. Its dated checkpoint records grouped native validation and remaining physical/signed/full-port work.

The October 23 Synchronization transfer-result family connects actual selected libgit2 Fetch notifications to the inline Action/Path Log and workspace child-Log routing. Command presentation follows post-checkout execution, typed buffers drain before completion, and original endpoint/copy semantics survive partial results, warnings and retirement. The dated checkpoint records actual grouped validation and captures; this does not certify the whole Synchronization dialog or application.

The October 23 source-selected Fetch lifecycle continuation implements load-remote → append requested spec → fetch-same-object ordering in the optional helper, connected to Sync and standalone Fetch/Rebase. It replaces the prior concrete per-operation-spec configuration gap. The current invocation uses loaded specs; later loads see appended duplicates. CLI behavior is unchanged. The new checkpoint separates its validation from the preceding notification-log pass. All Remotes remains a Mac named-remote iteration adaptation; pinned libgit2 can swallow config-write errors while returning zero. Those boundaries, public/signed/physical and complete source-resource acceptance remain explicit; this does not complete Sync or the application.

Commit report-row continuation — October 25, 2026

The Commit report-row family implements compact single-line file and group captions, regular/bold configured-font sizing, full value help and exact native geometry ownership/restoration. The original AppKit row-span recursion is captured separately from the source layout defect; its affected-workload checkpoint is recorded without attributing an unproven cause to the shared selection decorator.

Configured expression failure family — October 25, 2026

Configured issue-regex semantics separates HasBugID from extracted ranges, preserves a valid first expression when the second is invalid, and routes Commit/history/shared consumers through caught configuration syntax behavior. The explicit tester stays strict. The family also separates syntax fallback from actual helper/protocol/cancellation failures and documents the fresh-property snapshot boundary. Its grouped checkpoint is recorded separately from full dialog, signed and hosted acceptance.