feat: adapt image tuning by engine
This commit is contained in:
@@ -136,3 +136,8 @@
|
||||
- Uploaded and generated assets created through public API flows are tagged as `api-client:<clientId>` so integrations can query and download their own results later.
|
||||
- OpenAPI is generated dynamically from the current deployment origin at `/api/v1/openapi.json`.
|
||||
- Operations handoff docs live in `docs/DEPLOYMENT.md`; partner API docs live in `docs/API.md`.
|
||||
|
||||
## 2026-05-29 Image Tuning Findings
|
||||
- Jimeng image generation supports the current `scale` parameter, so UI presets should submit numeric text-influence values for that engine.
|
||||
- EvoLink image generation does not use Jimeng `scale`; the per-request engine-aware control should submit EvoLink `quality` instead.
|
||||
- Current local `/api/health` reports `image.generate` using EvoLink, so `/create` should show `生成质量` options rather than `文本影响`.
|
||||
|
||||
Reference in New Issue
Block a user