Branch: a1-labels → main
PR 7 of the review fixes plan (docs/review-fixes-plan.md), part of the 0.5.3 series; the version does not change in this PR.
"A1" labels everywhere (M6). The app showed pads and sequence slots as "A01", "B02"; the CLI and project.SlotName used "A1", "B2". As decided, it is "A1" everywhere now: bank letter, then pad number without a leading zero.
app.Label is removed, and the app's state uses project.SlotName, the one Go implementation. That covers the pad grid, pad panel, sequence grid and confirm dialogs, which all take their labels from the state.slotLabel in frontend/src/lib/slots.ts now gives "A1". The sequence panel uses it for the slot shown in its header.app.go, SlotGrid.svelte, slots.ts, and the regenerated models.ts.docs/checkpoint-b.md keeps "A01" in its steps and results: it records the device test as run with that UI. The earlier PR records are left alone too.On the server, every command with GOTOOLCHAIN=go1.27.4:
go test ./... passes.go vet ./... (also with GOOS=windows) and staticcheck ./... are clean.govulncheck ./...: "No vulnerabilities found."npm install, npm run check (0 errors, 0 warnings) and npm run build pass. The lockfile was not committed.wails3 build builds, and the app starts under Xvfb.go run ./cmd/mpckit-cli -load testdata/device/DemoFile.xpj -name LabelCheck -out <tmp> -mute B2=3 prints A1 … B2 in its summary.On the laptop (PowerShell, in the repo):
git fetch; git checkout a1-labelscd frontend; npm run check; cd ..: 0 errors, 0 warnings.wails3 dev: load testdata\device\DemoFile.xpj.
go run ./cmd/mpckit-cli -load testdata\device\DemoFile.xpj -name LabelCheck -out $env:TEMP: the summary lists A1 … B2. Then delete LabelCheck.xpj and LabelCheck_[ProjectData] from $env:TEMP.