Verify the result and resume interrupted conversion

Beta. Compare behavior with the original before treating the converted app as ready. Preserve the source until this review is complete.

1. Open the converted project’s Preview.
2. Run the important workflows with synthetic records.
3. Compare fields, validation, navigation and results with the original application.
4. Test each role and an action that should be denied.
5. Configure external services separately and confirm their intended behavior.
6. Record missing behavior as focused user stories.
7. Review production configuration and data migration before publishing.

If conversion stops

1. Inspect conversion_status for the existing project.
2. Read outstanding questions or decisions and answer them.
3. If the status exposes a stopped run, inspect it with pipeline_status.
4. Use resume_pipeline for that recorded run when supported, then follow conversion status again.

Starting another intake is not the first recovery step. It creates separate work and can consume additional allowances or credits.

The original-source deletion action is separate from conversion. purge_origin is destructive and requires explicit confirmation. Keep the original until you no longer need it for comparison, licensing or recovery.

See MCP recovery and publishing.

Names and marks

Visual Studio Code, VS Code, TypeScript and related Microsoft marks belong to Microsoft Corporation. Usage policy.

React, Bun names and any associated marks remain with their respective owners or project maintainers. References identify products, standards or source examples. OwlMeans documentation does not imply sponsorship or endorsement by those owners.