Branch: mpckit-casing → main
The app's name is written MPCkit wherever people see it:
build/config.yml, Windows file properties (info.json), the macOS bundle name (CFBundleName), the NSIS installer's product name, and the MSIX display names and description. The Linux menu entry uses a new PRODUCT_NAME: "MPCkit" in Taskfile.yml.Kept lowercase: these are identifiers or file names, not the displayed name.
bajdev/mpckit).APP_NAME: "mpckit": bin/mpckit, mpckit.exe, mpckit.app, the Linux package name.com.monoexp.mpckit, mpckit-cli, mpckit-checkpoint-a.zip, and internal names (the drag data type, temp-folder prefixes, the frontend package name).pull-requests/.Version 0.5.1 (bajdev, 2026-11-12): v0.5.0 was tagged before this rename, so this is released as 0.5.1 rather than moving that tag. APP_VERSION and the version in every build file are now 0.5.1. The README's beta note now says "The 0.5 releases are betas", and a new "Releasing" paragraph lists the files that carry the version. After the merge, the merge commit is tagged v0.5.1.
File names stay lowercase (bajdev, 2026-11-12): mpckit.exe, mpckit.app, bin/mpckit.
Also fixed: the MSIX manifests still had the template's com.example.mpckit identifier; it is now com.monoexp.mpckit. Their install folder is C:\Program Files\MPCkit.
On the server: go vet (also for Windows) and go test ./... pass; the Taskfile parses. Frontend changes are text only.
On the laptop:
npm run check in frontend: 0 errors, 0 warnings.wails3 build, run bin\mpckit.exe: the window title and taskbar say MPCkit, and About says "About MPCkit" and "Version 0.5.1".mpckit.exe: product name MPCkit, version 0.5.1.