mpckit/pull-requests/mpckit-casing/name-the-app-mpckit.md

Name the app MPCkit

Branch: mpckit-casing → main

What changed

The app's name is written MPCkit wherever people see it:

• The app: the window title, the app name Wails uses, the page title, the (screen-reader) page heading, and "About MPCkit". The Load warnings now say "MPCkit is tested with …".
• Build metadata: product name in 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.
• Docs: README, build plan, format doc, the checkpoint A README, the mockup, and code comments.

Kept lowercase: these are identifiers or file names, not the displayed name.

• The repo and Go module path (bajdev/mpckit).
• The executable and bundle file names, which come from APP_NAME: "mpckit": bin/mpckit, mpckit.exe, mpckit.app, the Linux package name.
• The bundle identifier com.monoexp.mpckit, mpckit-cli, mpckit-checkpoint-a.zip, and internal names (the drag data type, temp-folder prefixes, the frontend package name).
• The historical PR records in pull-requests/.

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.

Testing

On the server: go vet (also for Windows) and go test ./... pass; the Taskfile parses. Frontend changes are text only.

On the laptop:

1. npm run check in frontend: 0 errors, 0 warnings.
2. wails3 build, run bin\mpckit.exe: the window title and taskbar say MPCkit, and About says "About MPCkit" and "Version 0.5.0".
3. Properties → Details of mpckit.exe: product name MPCkit.