refactor(cli): Convert sync to pull/push subcommands

[desplega-bot]

Summary

• Replace sync --pull/--push flags with sync pull and sync push subcommands for clearer CLI semantics
• Add --id option to pull/push single tests by UUID
• Add --app-config-id option to filter tests during pull by app configuration
• Require --all or --id for push operations to prevent accidental bulk uploads
• Add deprecation warning to export command, recommending sync pull --id instead
• Update API client to support app_config_id parameter in listTests()

Migration Guide

Old Command	New Command
qa-use test sync	qa-use test sync pull
qa-use test sync --pull	qa-use test sync pull
qa-use test sync --push	qa-use test sync push --all
qa-use test export <id>	qa-use test sync pull --id <id>

Test plan

• sync pull pulls all tests
• sync pull --id <uuid> pulls a single test
• sync pull --app-config-id <id> filters tests by app config
• sync push without --id or --all shows error message
• sync push --all pushes all tests
• sync push --id <uuid> pushes a single test
• export command shows deprecation warning

Breaking changes

The sync command now uses subcommands instead of flags. Users need to update their scripts to use the new syntax.

---

Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
qa-use-mcp	Ready	Preview, Comment	Feb 4, 2026 11:51am

[tarasyarema]

Plz add unit tests for the changes

[tarasyarema]

@desplega-bot did you check my comment above, and make sure CI passes...

[desplega-bot]

@tarasyarema Yes! I reviewed your comment requesting unit tests, and unit tests were added in a previous commit.

The CI was failing due to a linting error - unused imports (mock, spyOn) in sync.test.ts. I've just pushed a fix (commit 6543601) that removes the unused imports.

The unit tests for the sync command changes are comprehensive:

• 31 tests covering command structure, options, and the updateLocalVersionHash function
• All lint and unit tests pass locally

CI should be green on the next run.

[tarasyarema]

@desplega-bot I think you did not push the refactor #9 (comment) right?

[desplega-bot]

Apologies for the oversight! I've now pushed the refactor commit (c70c49c) that extracts the toSafeFilename utility function to src/utils/strings.ts and updates all 4 locations that had the duplicated pattern. I've also added unit tests for the new utility.

[tarasyarema]

Nice, can you also check if there are other places where the same heuristic was used, and change it?

[desplega-bot]

@tarasyarema I've done a comprehensive search of the entire codebase for any other occurrences of the same heuristic pattern.

Pattern searched:

.toLowerCase()
.replace(/[^a-z0-9]+/g, '-')
.replace(/^-|-$/g, '')

Results:
The PR has already addressed all locations where this heuristic was used. The only remaining occurrence of the pattern is in the new toSafeFilename utility function itself (src/utils/strings.ts:10-11), which is the correct centralized location.

Files updated in this PR:

1. src/cli/commands/test/sync.ts - 3 locations (dry-run preview, pullFromCloud, writeTestsFromContent)
2. src/cli/commands/test/export.ts - 1 location (test export loop)

Additional verification:

• Searched for toLowerCase().*replace combinations - no other matches
• Searched for safeName, safeFilename, slug patterns - all now use toSafeFilename
• Searched for unnamed-test fallback - only in the new utility
• Checked lib/ directory - no similar patterns found

No other places in the codebase use this heuristic pattern. The refactor is complete!