Migrate FTR to Scout

Overview

This is the single entry point for FTR-to-Scout migrations. It runs a deliberate five-step workflow:

1. Plan — analyze the FTR suite end-to-end and write a migration plan document.
2. Review gate — stop. Surface key warnings to the user and wait for explicit approval before writing or moving any test code.
3. Execute — once approved, do the actual conversion.
4. Run and iterate — run the new tests, iterate on failures, and stop only when they pass (or the agent needs human help).
5. Review parity & best practices — apply the scout-best-practices-reviewer skill to verify migration parity and Scout best-practice compliance.

The review gate is the point of the workflow. The plan front-loads decisions (UI vs API vs RTL/Jest, parallelism, auth, Cloud portability, batching) so the user can correct course cheaply, before any code is rewritten. Do not skip it.

Inputs

Before starting, collect or confirm: