Treat an export notification as the start of verification. Inspect every configured destination, the complete diff, generated imports, assets, and the consumer's own build result.
That is current behavior. Export Code To Local Folder and MCP export-code-to-folder generate the whole project to every configured local-folder target. Use export-code when you only need read-only generated text for one Page or Component.
Assume partial external writes. Read all configured targets, inspect each directory, and compare against the pre-export snapshot. Fix the invalid target before rerunning; do not assume the operation rolled back earlier destinations.
Generated files are replaceable output. Restore from version control if needed, then move owned changes into an adapter, wrapper, or separate application module outside the generated boundary.
The exporter does not guarantee pruning of stale destination files. Compare the generated manifest/current project tree with the destination and remove stale artifacts deliberately through version control.
Inspect the generated file rather than guessing. Confirm the consumer supports TypeScript/TSX, SCSS/CSS Modules, referenced asset paths, misaki-studio-internal, React/React DOM, and any feature-driven data or runtime imports. Then run a clean installation and production build.
Misaki diagnostics are intentionally not a full consumer compiler. Use the consumer's TypeScript check, tests, bundler/build, and rendered smoke test as the authority for that destination.
Treat current branch selection as unfinished. A branch value is stored in target settings but is not passed through the current clone/push implementation. Protect the remote with a disposable repository/branch and review the actual remote commit; project Undo cannot remove it.
Check Current limitations and the selected boilerplate status. The public backend action engine and npm-package starter currently have explicit unfinished boundaries.