Validate the migration

After your AI agent completes prompt 10, a full validation sweep runs automatically when the prompt recorder succeeds. Follow the steps below to perform additional validation and cleanup tasks.
  • Migrate your Android app to use the BlackBerry Dynamics SDK.
  • Confirm that prompt 10 (10-generate-migration-report.md) recorded completion and that the validation was successful. If the recorder exited with an error, validation failed and the executedPrompts entry for prompt 10 was not written. You can review violations in output/.last-check.json or the recorder stderr, then ask your agent to run the relevant migration prompts again.
  • For troubleshooting guidance, see Troubleshooting the migration.
  1. To run a manual validation check from the project root:
    ./dynamics-migration-tool/tooling/validate.sh

    Note that validation checks are automated and may not identify all issues. You should plan to manually review and verify the results. If you want to run a validation check for a specific prompt, add --check-prompt <id>, where <id> is the prompt number.

  2. Audit the code changes that the AI agent made during the migration process. All code changes are tagged with an inline comment, for example:
    rg "\[BB_DYNAMICS-MIGRATION\]" -g "*.java" -g "*.kt" \
 -g "*.xml" -g "*.gradle" -g "*.gradle.kts" -n
  3. Review the migration report (migration-report.json), migration retrospective (migration-retrospective.md, produced by the optional prompt 12), and visual HTML report (migration-report-viewer.html) that the agent generated in the output repository.
  4. Keep or remove migration output artifacts as needed for audits.
    Migration changes in your app source code remain after you remove the migration toolkit.
Perform Runtime verification and analysis.