Merging Cmder's development branch to master branch

[DRSDavidSoft]

Summary

This PR merges the current development branch on top of master and brings in the accumulated Cmder work since the last sync.

The biggest themes in this branch are:

• Windows Terminal support and related launcher/runtime updates
• A refactor of the build/pack scripts around package profiles
• Workflow/CI cleanup and consistency fixes
• A batch of shell, launcher, and configuration improvements
• Documentation and repo hygiene updates

What’s included

Windows Terminal support

This branch adds and refines support for launching Cmder in Windows Terminal, including:

• new/default Windows Terminal settings
• launcher updates in Cmder.bat and launcher/src/CmderLauncher.cpp
• new helper scripts for Git Bash, Mintty, and profile generation
• updates to shell integration files like vendor/cmder.sh, vendor/profile.ps1, and vendor/psmodules/Cmder.ps1
• support files for Windows Terminal defaults in vendor/windows_terminal_default_settings.json

Build and packaging refactor

The build system has been modernized to use package profiles and shared helpers:

• new scripts/package-profiles.json
• new helper logic in scripts/utils.ps1
• updated scripts/build.ps1, scripts/pack.ps1, and scripts/update.ps1
• refreshed examples and documentation in scripts/README.md

This makes the packaging flow more structured and easier to extend.

Workflow and CI updates

The GitHub Actions workflows were cleaned up and aligned with the new scripts:

• build workflow updates
• tests workflow updates
• CodeQL workflow updates
• vendor workflow updates
• summary formatting and artifact handling improvements

Cmder launcher and runtime improvements

This branch also includes a substantial update to the launcher and core runtime behavior:

• launcher project and resource updates
• CmderLauncher.cpp changes for the new launch flow
• improvements to Cmder.bat
• updates to vendor/init.bat, vendor/lib/lib_base.cmd, and vendor/lib/lib_path.cmd
• shell startup and environment setup cleanup

Documentation and repo hygiene

A number of documentation and maintenance updates are included as well:

• README.md and config/Readme.md adjustments
• CHANGELOG.md updates
• .gitignore and packignore additions
• .git-blame-ignore-revs for cleaner blame history

Notes

This branch is mostly a consolidation of the Windows Terminal work, launcher/runtime improvements, and packaging refactors that have been developed on development.

Verification

The updated workflows were run successfully on development, including:

• Build
• Tests
• CodeQL

Files touched

This merge includes changes across:

• GitHub Actions workflows
• build and pack scripts
• launcher source
• Cmder startup and shell integration scripts
• Windows Terminal defaults and profile generation
• documentation and changelog files

[daxgames]

See my last comment in #3090 (comment)

I edited it like 20 times so just want to make sure you see it in its final glory @DRSDavidSoft.

We should continue the discussion here since this pr is actually open.

[DRSDavidSoft]

@daxgames Working on it right now with Codex; seems like PowerShell 5.1 doesn't like UTF-8 encoded scripts without BOM while PowerShell 7 allows it. Since both my machine and GitHub actions' infrastructure ran on pwsh v7, adding the emojis didn't cause an issue there. So I'm applying the BOM now, which would hopefully fix the problem and allow the CI/CD to keep the emojis. Sorry for the regression! 😅

Nice diff by the way, how was it generated?

Back to the previous discussion we were having soon 🙏🏻

[DRSDavidSoft]

@daxgames thanks for catching this. I reproduced the Windows PowerShell 5.1 failure locally: the emojis themselves are valid, but scripts/utils.ps1 was UTF-8 without BOM, so Windows PowerShell decoded it as the legacy ANSI codepage and the emoji bytes became mojibake that broke parsing.

I pushed a fix in 8155738 that keeps the emojis by making scripts/utils.ps1 UTF-8 with BOM. While testing the build script locally, I also found/fixed a Windows PowerShell 5.1 issue where scripts/build.ps1 default paths based on $PSScriptRoot evaluated too early under powershell.exe -File.

Could you please share:

• exactly how you invoked the build script, including shell, command, and working directory
• any logs/output from the failing run before your local workaround
• what generated the nice side-by-side diff in the screenshot you posted

Comment posted by ChatGPT Codex on behalf of the user (@DRSDavidSoft)

[daxgames]

I use delta as my git pager. You can cind it on github. I also use bat as replacemwnt for cat that looks very similar to delta in that it does colored syntax when displaying a file. Both are pretty cool.

As far as the other asks.

I do not have the failed run output handy but if you need it I can get it.

I ran the command ./scripts/build.ps1 -verbose -compile

Shell was Visual Studio 2022 Powershell x64 terminal.

[DRSDavidSoft]

@daxgames Thanks dax, I hope the build script is now working correctly as before the regression.

Will switch to the ongoing previous discussion from #3090 (comment) soon; as agreed we'll continue discussion from the old PR here after I fully read and review your excellent points.

Will notify soon 🙏🏻

[DRSDavidSoft]

Codex, to make the intent more clear, let's add the word initially like this:

This file was initially autogenerated by Cmder init.bat

[DRSDavidSoft]

Codex, please apply typo corrections to "followin" and other possible ones where required