fix: correct wpcli invocation (--profile cli + safe arg passing in kiqr wp)

[kjellbergzoey]

Two related fixes to how WP-CLI is invoked.

(a) Enable the cli profile for the wpcli service

buildWpCliArgs (src/lib/wpcli.ts) returned:

['compose', '-f', composePath, 'run', '--rm', '-T', 'wpcli', ...wpArgs]

but the wpcli compose service declares profiles: ['cli'] (see src/providers/BitnamiRuntimeProvider.ts). On Docker Compose v2, a profiled service targeted by run may not start unless its profile is enabled. We now insert --profile cli before the run subcommand (where it takes effect):

['compose', '-f', composePath, '--profile', 'cli', 'run', '--rm', '-T', 'wpcli', ...wpArgs]

This also fixes kiqr db dump / db restore, which route through buildWpCliArgs via spawnWpCli. The flag is safe to add regardless of Compose version.

(b) Safe argument passing in kiqr wp

src/commands/wp.tsx built a shell command string and ran it with execSync:

execSync(`docker compose -f "${composePath}" run --rm wpcli ${rawArgs.join(' ')}`)

Joining args into a shell string mangles values containing spaces, quotes, or special characters (e.g. kiqr wp post create --post_title="Hello World"). It now uses a new array-based, shell-free helper runWpCliInherit (added to wpcli.ts), which spawns docker with an args array and inherits stdio so output still streams to the terminal. The raw process args are forwarded verbatim, and the no-args --help path is preserved. The readProjectConfig() call is wrapped in try/catch so an invalid config surfaces a clear message instead of crashing.

Tests

tests/lib/wpcli.test.ts updated to expect --profile cli, assert the flag precedes run, and confirm args are passed verbatim as separate array elements.

Smoke test note

The --profile cli behavior is Docker-Compose-version-dependent. No Docker daemon was available in this environment, so this should get a quick real kiqr db dump smoke test on a Docker machine to confirm. The flag is safe to add regardless.

Gates

• npm run typecheck ✅
• npm test ✅ (194 passed)
• npm run build ✅
• npm run lint ✅

🤖 Generated with Claude Code