[MelaBuilt-AI]

Summary

• Bundle pinned Portable Git (including Git Bash) privately inside Windows packages; initialize it on first launch without changing system PATH or global Git identity.
• Preserve Portable Git's required empty archive directories and upstream setup behavior.
• Render the supplied icon at its intrinsic composition before downsampling; retain installer identity and state paths.
• Add a separate Workbench commit-author dialog for initial checkpoints and selected-file commits, saving explicit repository-local identity only.
• Identify the next unsigned Windows candidate as 0.15.0-rc.2-windows.2 (numeric 0.15.0.4).

Verification

• Formatting, lint, workspace typecheck, architecture gate passed.
• Full test suite: 291 files / 1,628 tests passed with an isolated XDG_DATA_HOME.
• Initial non-isolated run: 1 existing voice-default test failed because a managed voice provider is installed on the build host; 1,627 passed. No product/test assertion was weakened; rerunning with isolated app data passed the entire suite.
• Production build and startup/API smoke passed.
• Python packaging: 3 tests passed; Node launcher/bundled-Git helpers: 4 tests passed.
• Real-Git tests cover missing identity before staging, explicit selected-file commits, stale-head rejection, unchanged isolated global config and worktree inheritance.
• Component-only desktop/portrait checks cover the separate dialog, cancel/Escape/no write, save/resume and existing-identity bypass. No automated product-navigation journeys were run.
• Earlier native Windows Git/icon candidate passed pristine no-system-Git first/repeat-launch, project creation, disposable commit/worktree and runtime state-continuity checks. These are historical proof, not the new merged artifact's acceptance.

Delivery boundaries

Commit/push, exact-head green CI, merge, then merged-main green CI precede the next installer build. The manual packaging workflow is not dispatched. No binary upload, GitHub Release, npm publication, provider changes or retained operator-runtime mutation.

Linux shares the dialog and needs rebuilt DEB/tar payloads to receive it; Linux's Git prerequisite remains unchanged. The npm bootstrap must be repinned/retested against any new Linux archive. Native setup/upgrade and user visual acceptance remain separate from code checks.