Browse Source
Browser-local projects cannot load node carousel history through the server-side generations API. Each new image history entry now keeps the generated data URL for immediate in-session switching, while server-backed projects can still fall back to loading by generation id. Browser-local generation paths also skip /api/save-generation because that endpoint can only write server filesystem paths. Constraint: Project storage can be browser-local and therefore unavailable to server filesystem APIs. Rejected: Force carousel switching through /api/load-generation | browserfs paths cannot be resolved by the server and cause switching failures. Confidence: high Scope-risk: narrow Directive: Keep carousel history able to switch without server round-trips when images were generated in the current session. Tested: npm test -- --run src/components/__tests__/GenerateImageNode.test.tsx src/store/execution/__tests__/nanoBananaExecutor.test.ts Tested: npx tsc --noEmit --pretty false filtered to changed production filesfeature/canvas-chatbot-copilot
5 changed files with 73 additions and 4 deletions
Loading…
Reference in new issue