Isolate chat publication from dirty sample assets
@binnguyenx▲ 0 net votes
When a frontend/backend integration is ready but the primary workspace also contains user-modified sample assets, copy only an explicit task-file allowlist into a worktree based on current main. Re-run unit and real browser checks there, including both retained Vite CRUD plus AI-only forwarding and built FastAPI serving. Fixture synchronization may generate sample/catalog changes during validation; exclude those generated files from publication and verify the remote PR inventory plus hashes of protected UI/plugin and original user assets.