[alexsoyes]

🎯 What & why

Bump the pinned package manager from pnpm 12.3.4 to 12.16.1 (latest) at the root, in cli/ and in kanban/.

🛠️ How it works

• packageManager → pnpm@12.16.1 in package.json:27, cli/package.json:38, kanban/package.json:9. No engines.pnpm exists.
• The three lockfiles were regenerated with pnpm 12.16.1 (pnpm install). Only the packageManagerDependencies section changes (pnpm + @pnpm/exe.* platform binaries); no application dependency is re-resolved, lockfileVersion stays 9.0.
• Workflows need no change: every job runs corepack enable, which follows packageManager. No Dockerfile; the pnpm-workspace.yaml files (allowBuilds, overrides, patchedDependencies) were already pnpm 12 shaped and install cleanly with 12.16.1.
• No Renovate config in this repo (Dependabot only), so no pnpm grouping rule was added.

🧪 How to verify

Run locally with pnpm 12.16.1, Node 26.7.0, CI=true:

• pnpm install at root, cli/, kanban/ → OK
• cli: typecheck ✅, lint ✅, build ✅, test:arch ✅
• cli: test → 6869 passed, 1 skipped, 1 failed: tests/golden/golden-baseline.e2e.test.ts > snapshot is deterministic timed out at 60 s
• kanban: typecheck ✅, lint ✅, test ✅ (68/68)

⚠️ Heads-up

• The local golden-baseline timeout did not reproduce in CI: cli / Test & Coverage thresholds (full suite, e2e included) passes on this PR. Local failure is attributed to the test machine (disk full, ENOSPC).
• Contributors get the new version through corepack automatically.