test(cli): indoor-kit-migrate v1-to-v2 CLI regression coverage

[cursor]

Description

Adds focused cli_main tests for the indoor-kit-migrate-v1-to-v2 command: successful v1→v2 migration (including nested doorhooks), and failure paths (missing input, invalid JSON, already v2, empty kit id). This closes the gap between library migration tests (migrate_kit_json_v1_to_v2 in test_tilekit_v2.py) and the CLI entrypoint in dispatch.py / commands/indoor_kit_migrate.py.

Type of Change

• ✅ Test addition or update

Package(s) Affected

• PyKotor (core library)

Changes Made

• New file: Libraries/PyKotor/tests/cli/test_indoor_kit_migrate_cli.py — five deterministic tests using tmp_path only.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Test Results

QT_QPA_PLATFORM=offscreen uv run pytest --import-mode=importlib -m "not gui and not slow" tests/cli/test_indoor_kit_migrate_cli.py -v --rootdir=/workspace/Libraries/PyKotor -c /dev/null
# 5 passed

Risky behavior now covered

• Dispatch + CLI: cli_main([...]) for indoor-kit-migrate-v1-to-v2 ensures the subcommand stays wired in dispatch.py.
• I/O and validation: Missing file, malformed JSON, double-migrate (format_version 2), and invalid v1 metadata (empty id) all return exit code 1 without writing partial output.
• Migration fidelity (smoke): Output JSON has format_version: 2, preserved id, and floor templates with hooks copied from v1 components.

Why this reduces regression risk

The migrate command is the supported path for authors moving legacy kit JSON to tile templates; silent wiring breaks or swallowed errors would break modding workflows. These tests fail fast on regressions in argument parsing, dispatch routing, or error handling without requiring a game installation or slow integration fixtures.

Related Issues

Related to coverage automation / missing CLI tests for recently merged indoor tooling.

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• New and existing unit tests pass locally with my changes