Tree: 9b9331080e

TEST-s

TEST-x

codex/popi-tv-header-logo

feature-img

feature/071

feature/0710

feature/260608

feature/627

feature/add_agent_md

feature/add_provider_popi

feature/canvas-chatbot-copilot

feature/composer

feature/gateway

feature/group

feature/handle

feature/handleReconstruction

feature/interaction

feature/new_node

feature/remove

feature/video-erase

feature/workflow

feature_apikey

feature_gateway-migration

feature_login

handoff-20260429-1057

master

songxh-popiart-node-canvas

test-0523

video_node

xuzhijie-popiart-node-canvas

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '9b9331080e'

${ noResults }

Commit Graph

2 Commits (9b9331080e7153e2fb764a1a56c1e6b58ab07f5b)

Author	SHA1	Message	Date
jiajia	e009cb5046	Clarify processing-node controls in the composer The bottom composer now treats video stitch and ease curve as processing-node inspectors instead of unsupported prompt editors. The connection menu also keeps video streams and ease-curve settings on separate handle paths so downstream creation matches the node graph semantics. Constraint: Processing nodes should run existing local media operations and must not expose model or prompt controls Constraint: Ease curve Settings handles carry curve parameters, not video media Rejected: Let Settings handles reuse generic video/text drop options | creates misleading nodes and invalid graph intent Rejected: Make Video Input a downstream target from Video Out | Video Input is an import/source node, not a processing destination Confidence: high Scope-risk: moderate Directive: Keep media handles and settings handles separated in connection menus and validation Tested: npm run test:run -- src/components/__tests__/ConnectionDropMenu.test.tsx Tested: npm run test:run -- src/components/__tests__/GenerationComposer.test.tsx Tested: npm run test:run -- src/components/__tests__/WorkflowCanvas.test.tsx Tested: npm run build Tested: git diff --check Not-tested: npm run lint still uses the existing Next 16-incompatible next lint script	2 months ago
jiajia	95e152842b	Make the canvas composer the selected-node console The bottom composer now edits and reruns the current generation node while canvas-visible actions own downstream node creation. NewApiWG media normalization, video frame extraction, and node quick-add keep generated media flows explicit and connected rather than hidden behind the prompt box. Constraint: Composer must not call providers directly or create hidden downstream branches when a node is selected Constraint: NewApiWG video families use inconsistent media schemas, so common media aliases are normalized in the provider adapter Rejected: Let the bottom composer create next-step nodes from selected outputs | hides graph mutation and conflicts with the PRD source-of-truth rules Rejected: Put NewApiWG model-family payload rules in the composer | provider-specific schemas would leak into UI state Confidence: high Scope-risk: moderate Directive: Keep provider payload normalization in provider/executor layers; do not move it into GenerationComposer Tested: npm run test:run -- src/components/__tests__/GenerationComposer.test.tsx Tested: npm run test:run -- src/components/__tests__/WorkflowCanvas.test.tsx Tested: npm run test:run -- src/components/__tests__/GenerateVideoNode.test.tsx Tested: npm run test:run -- src/app/api/generate/providers/__tests__/newapiwg.test.ts src/app/api/generate/__tests__/route.test.ts Tested: npm run test:run -- src/store/execution/__tests__/videoProcessingExecutors.test.ts Tested: npm run build Not-tested: npm run lint fails because next lint is incompatible with the current Next 16 script configuration	2 months ago