Summary

openclaw migrate and openclaw migrate apply register --no-backup, but the CLI action reads opts.backup === false instead of opts.noBackup, so the apply path still creates a pre-migration backup.

Steps to reproduce

1. Run openclaw migrate apply hermes --yes --force --no-backup.
2. Observe that the CLI still enters the pre-migration backup path.

Expected behavior

When --no-backup is supplied with --force, migration apply should skip createPreMigrationBackup.

Actual behavior

The CLI passes noBackup: opts.backup === false, but the registered Commander option is --no-backup, so the parsed option is exposed as opts.noBackup. params.opts.noBackup remains false and the backup path runs.

OpenClaw version

Current main after v2026.4.26; observed at commit 0f24a8d8e1.

Operating system

Static repo inspection only.

Install method

Source checkout.

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

src/cli/program/register.migrate.ts:32 registers --no-backup
src/cli/program/register.migrate.ts:62 passes noBackup: opts.backup === false
src/cli/program/register.migrate.ts:100 registers --no-backup for apply
src/cli/program/register.migrate.ts:111 passes noBackup: opts.backup === false
src/commands/migrate/apply.ts:64-66 skips backup only when params.opts.noBackup is true

Impact and severity

Affected: users running non-interactive migrations with explicit backup control.

Severity: Medium.

Frequency: Always when relying on --no-backup.

Consequence: scripted migrations may unexpectedly create backups or fail in environments where backup output is unavailable or intentionally disabled.

Additional information

Likely fix is to pass noBackup: Boolean(opts.noBackup) or equivalent in both migrate action handlers.