fix(workflow-editor): 接入真实生成任务

[xyh202131]

改动

• 在 entities/generation 提供浏览器生产适配器，统一处理 API 前缀、会话 Token、SSE 授权恢复与既有轮询兜底
• Workflow Editor 默认会话改用真实 GenerationApis，不再使用必然失败的占位实现
• 补充生产适配器和 Workflow Editor 默认控制器的回归测试

范围

• 仅修改 5 个前端文件，共 156 行新增、39 行删除
• 不修改 Quick Start，与 fix(quick-start): 打通自定义动作完整生成 #240 没有文件重叠
• 未包含真实服务地址、账号或密钥

验证

• npm run test:coverage：420 tests passed，Statements 88.71%，Branches 82.48%，Functions 90.75%，Lines 92.30%
• npm run typecheck
• npm run lint
• npm run build
• 变更文件 oxfmt --check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
windup	Ready	Preview	Aug 12, 2026 6:34pm

[codecov]

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
frontend/src/entities/generation/api.ts	90.00%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[fennoai]

Review summary

Found one authentication-recovery regression in the new production Generation adapter.

Verification note: the focused Vitest command could not start in this workspace because the local vitest executable returned Permission denied.

[fennoai]

High: Route these POST/GET requests through the shared unauthorized-recovery flow (or implement the same envelope-aware retry here). The backend returns expired-token failures as HTTP 200 with { code: 401 }, so this raw fetch never calls recoverApiUnauthorized; readData immediately throws instead. As a result, opening the editor with an expired access token causes generation creation/status polling to fail even when the refresh cookie can recover the session, while the SSE path below does recover correctly.