Tree: 87b56a4d3f

TEST-s

TEST-x

codex/popi-tv-header-logo

feature-img

feature/071

feature/0710

feature/0722ui

feature/0724

feature/0724-patch

feature/260608

feature/627

feature/add_agent_md

feature/add_provider_popi

feature/canvas-chatbot-copilot

feature/composer

feature/create-task

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

production-5d63e3e

songxh-popiart-node-canvas

test-0523

video_node

xuzhijie-popiart-node-canvas

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '87b56a4d3f'

${ noResults }

Commit Graph

3 Commits (87b56a4d3f1ccc2695494fd65934ef9c8d219335)

Author	SHA1	Message	Date
jiajia	87b56a4d3f	Keep new Popi users on tested gateway defaults New users now land on Popi gateway defaults that match the tested production-style path: APIYI Nano Banana 2 for images, Doubao Seedance for video, and Doubao Seed 2.0 Lite for LLM chat/tool use. Settings and FTUX screens render these effective defaults instead of empty placeholders, while existing local node defaults keep taking precedence. The same pass keeps provider-overload errors user-facing by formatting the model name that the node currently displays, so fallback and switched-model failures are easier to understand across media nodes. Constraint: Popi mode should hide internal NewApiWG naming and default to models available through the Popi gateway. Rejected: Persist default values into localStorage for every new user | would make future system default changes harder and could overwrite explicit user preferences. Confidence: high Scope-risk: moderate Directive: Do not change these defaults without checking the Popi gateway model ids and www.popi.art login/model-routing assumptions. Tested: npm run test:run -- src/lib/__tests__/llmModels.test.ts src/store/utils/__tests__/nodeDefaults.test.ts src/store/execution/__tests__/generateVideoExecutor.test.ts src/components/__tests__/ProjectSetupModal.test.tsx src/components/__tests__/GenerationComposer.test.tsx src/app/api/chat/__tests__/route.test.ts src/components/__tests__/LLMGenerateNode.test.tsx src/utils/__tests__/userFacingErrors.test.ts Tested: PROVIDER_MODE=popi NEXT_PUBLIC_PROVIDER_MODE=popi npm run build Tested: git diff --check Not-tested: npm run lint currently fails because next lint is no longer a valid project command in this Next.js setup	2 months ago
jiajia	ca0b039a88	Restore reliable high-priority generation paths P0/P1 reports clustered around unavailable LLM defaults, video media connections, and missing controls on the generation surface. This routes the default NewApiWG LLM away from the unavailable Doubao channel, makes video a first-class schema and canvas connection type, carries request ids into node errors, and fills the composer, trim, audio, and 3D gaps without changing the canvas workflow model. Constraint: NewApiWG Doubao channels are not reliably routed in the default gateway Constraint: Video model schemas expose video fields that must not flow through image handles Rejected: Continue accepting video through image handles | hides incorrect graph types and loses schema-specific dynamic inputs Confidence: high Scope-risk: moderate Directive: Keep media handle types explicit; add schema mapping when adding a new connectable media type Tested: npm run test:run -- src/store/execution/__tests__/generateVideoExecutor.test.ts src/store/utils/__tests__/connectedInputs.test.ts src/store/execution/__tests__/generateAudioExecutor.test.ts src/store/execution/__tests__/llmGenerateExecutor.test.ts src/store/__tests__/workflowStore.integration.test.ts src/lib/__tests__/llmModels.test.ts src/store/utils/__tests__/nodeDefaults.test.ts src/components/__tests__/GenerationComposer.test.tsx src/app/api/chat/__tests__/route.test.ts src/app/api/llm/__tests__/route.test.ts src/app/api/models/[modelId]/__tests__/route.test.ts src/app/api/generate/providers/__tests__/newapiwg.test.ts Tested: npm run build Tested: git diff --check Not-tested: npm run lint | package script calls removed Next 16 next lint command Not-tested: npx tsc --noEmit | existing test type errors remain; changed runtime files filtered clean	3 months ago
jiajia	f5cf6017a0	Route generation defaults through NewApiWG This aligns image, video, and text defaults with the PopiArt NewApi gateway while keeping provider-specific escape hatches available. Chat now uses the OpenAI-compatible NewApiWG route so workflow editing and LLM generation share the same Doubao-first text default. The canvas composer and quick-add controls are tightened so visible actions map to real clickable behavior, while temporarily unused header actions stay hidden. Constraint: Text/chat requests must prefer Doubao-Seed-2.0-lite through NewApiWG. Constraint: Image and video defaults should prefer PopiArt NewApi gateway models when configured. Rejected: Keep /api/chat on Gemini 3 Flash | conflicts with the requested NewApiWG text/chat default. Rejected: Hand-roll AI SDK chat streaming | would risk tool-call and UI stream compatibility. Confidence: high Scope-risk: moderate Directive: Do not add new text/chat defaults without updating src/lib/llmModels.ts and the chat route together. Tested: npm test -- --run src/app/api/chat/__tests__/route.test.ts src/components/__tests__/LLMGenerateNode.test.tsx src/lib/__tests__/llmModels.test.ts src/store/utils/__tests__/nodeDefaults.test.ts src/components/__tests__/GenerationComposer.test.tsx src/lib/chat/tools.test.ts Tested: npm test -- --run src/lib/__tests__/llmModels.test.ts src/store/utils/__tests__/nodeDefaults.test.ts src/components/__tests__/GenerationComposer.test.tsx src/lib/quickstart/__tests__/templates.test.ts src/lib/quickstart/__tests__/validation.test.ts src/lib/quickstart/__tests__/prompts.test.ts src/components/__tests__/ProjectSetupModal.test.tsx Tested: npm test -- --run src/components/__tests__/WorkflowCanvas.test.tsx Not-tested: Full suite; repository has pre-existing unrelated type/test warnings outside this change.	3 months ago