Browse Source
Browser-local projects were deriving a null generations path, so carousel entries that only retained an image id could not resolve media during previous/next navigation. Generated images are now written into the browser-selected generations folder, project metadata keeps that browserfs generations path, and the image node can read browserfs generation files directly before falling back to the server load endpoint. Constraint: Browser-selected folders cannot be read through server API routes. Rejected: Keep relying on inline image history only | saved or migrated workflows can contain id-only history entries. Confidence: high Scope-risk: moderate Directive: Browser-local media paths must stay on the File System Access API path, not server /api/load-generation. Tested: npm test -- --run src/components/__tests__/GenerateImageNode.test.tsx src/store/execution/__tests__/nanoBananaExecutor.test.ts src/components/__tests__/GenerationComposer.test.tsx Tested: npx tsc --noEmit --pretty false filtered to touched files Not-tested: Full tsc remains blocked by existing test typing errors outside this change scopefeature/canvas-chatbot-copilot
6 changed files with 198 additions and 12 deletions
Loading…
Reference in new issue