mirror of https://git.openapi.site/https://github.com/desirecore/market.git synced 2026-06-06 05:50:41 +08:00

Files

xyx 0cb3758669 fix: 补全 dashscope-image-gen 和 xiaomi-tts 的 i18n CI 校验 (#4 )

## 变更说明

修复 dashscope-image-gen 和 xiaomi-tts 的 i18n CI 校验、补全英文翻译，并连带修复其他 stale
skill 的 source_hash 漂移问题。

### dashscope-image-gen / xiaomi-tts（PR 主线）
- `name` 字段从中文改为目录名（CI rule-1 要求 lowercase ASCII + hyphens）。
- 补全 `metadata.i18n` 块：`locales`、`zh-CN` (含 body 指向
SKILL.zh-CN.md)、`en-US`（含 description / body=./SKILL.md）。
- 新增 `SKILL.zh-CN.md`（zh-CN body 文件）。
- **root SKILL.md 改写为英文 body**（与 SKILL.zh-CN.md 内容对应），由本 PR
手工翻译；`default_locale=en-US`、`source_locale=zh-CN`，与 docs/I18N.md
约定一致：root SKILL.md = default_locale body (en-US)、SKILL.zh-CN.md =
source_locale body (zh-CN)。
- 两 locale 锁为 `translated_by: human` + 正确 `source_hash`。
- 内容质量修复：流程标题 "严格按此两步执行" 改为 "严格按此三步执行"；强制规则 2 措辞精确化（/tmp
仅作中转）；xiaomi-tts 用户意图映射表中 `response_format` 改为 `audio.format`
与请求体参数表一致；zh-CN.description 改为纯中文。
- locale header 由 shell 转义残留 `<\!--` 修正为标准 `<!-- locale: zh-CN -->`。

### 连带：6 个 main 上已 stale 的 skill（避免 translate workflow 失败）
- `manage-skills` / `minimax-music-gen` / `minimax-video-gen` /
`skill-creator` / `web-access`：`en-US.source_hash` 重新计算为当前 zh-CN source
实际 hash；`translated_by` 由 `ai:claude-opus-4-7` 改为 `human`
以锁定现有翻译不被自动重译覆盖。
- `markdown`：补正 `en-US.source_hash`（之前是占位 `sha256:0000000000000000`）。
- 这些 skill 的 `en-US` 翻译内容保持不变，仅修正元数据。

### scripts/i18n/translate.py 容错增强
- 413 Payload Too Large 时不再 retry（payload 不会变小，retry 浪费时间）。
- 主循环 catch RuntimeError，把单个 skill 的失败写入 `plan["errors"]` 后继续处理下一个
skill，避免一个大文件 fail 整个 workflow。
- `--check` 模式下 plans 含 errors 也 exit 1（之前仅看 needs_translation，broad
except 会把异常吃掉导致误报通过）。

## Test plan

- [x] `i18n-validate` 通过
- [x] `i18n-translate --check` 显示所有 skill `up-to-date` 或 `human-locked,
skipping`
- [x] CI 上 `validate` / `translate` / `wait-for-copilot-review` 全绿
- [ ] Copilot 评审 conversation 全部 resolve
- [ ] Squash merge

---------

Co-authored-by: yi-ge <a@wyr.me>

2026-05-13 12:57:25 +08:00

7.9 KiB

Raw Blame History

name, description, license, version, type, risk_level, status, disable-model-invocation, provider, tags, requires, metadata, market

name

description

license

version

type

risk_level

status

disable-model-invocation

provider

dashscope-image-gen Skill

Mandatory Rules (violations cause failure)

Must access agent-service over HTTPS — use https://127.0.0.1:${PORT} with -k to skip certificate verification
Must upload to media-store via /api/media/upload — /tmp is only a transient download/decode location, never use a local path as the final output
Must use the dc-media:// protocol to display images — the only form the frontend can render correctly
Use Bash curl throughout — do not use the HttpRequest tool or Python
Use compatible-mode (/chat/completions) — synchronous call; the response contains the image URL directly

Model Selection

Model	Characteristics	When to use
wan2.7-image-pro	Flagship, 4K resolution, thinking_mode	User asks for top quality, 4K, or rich detail
wan2.7-image	Standard high quality, thinking_mode	Default, for unspecified requests

Default rule: if the user does not specify a model, use wan2.7-image.

Full Execution Flow (strictly three steps)

Prerequisites

The user has configured an Alibaba Cloud DashScope provider in Resource Manager → Compute and filled in an API Key
agent-service is running

Step 1: Call the text-to-image API (synchronous)

Generate the image via media-proxy's compatible-mode endpoint; the response includes the image URL directly:

PORT=$(cat ~/.desirecore/agent-service.port)
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "dashscope",
    "serviceType": "image_gen",
    "endpoint": "/chat/completions",
    "body": {
      "model": "wan2.7-image",
      "messages": [
        {
          "role": "user",
          "content": [
            {"type": "text", "text": "Replace this with the image description (English usually gives better results)"}
          ]
        }
      ]
    },
    "responseType": "json"
  }'

Example response:

{
  "success": true,
  "data": {
    "request_id": "...",
    "output": {
      "choices": [
        {
          "message": {
            "role": "assistant",
            "content": [
              {
                "type": "image",
                "image": "https://dashscope-result.oss.aliyuncs.com/..."
              }
            ]
          },
          "finish_reason": "stop"
        }
      ]
    }
  },
  "statusCode": 200
}

Locate the item with type: "image" inside data.output.choices[0].message.content and extract its image URL.

Step 2: Download and upload to media-store

The image URL is time-limited; download and persist it to the local media-store immediately:

PORT=$(cat ~/.desirecore/agent-service.port)
IMAGE_URL="image URL from step 1's response"
curl -sL "$IMAGE_URL" -o /tmp/dashscope-gen.png && \
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media/upload" \
  -F "file=@/tmp/dashscope-gen.png;type=image/png"

Pick the mediaId field from the JSON response (format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.png).

Step 3: Render the image via the dc-media protocol

In your reply text, write Markdown image syntax directly:

![Image description](dc-media://replace-with-mediaId)

For example: ![White fox in a forest](dc-media://a1b2c3d4-e5f6-47a8-b9c0-d1e2f3a4b5c6.png)

The frontend will translate dc-media:// into a reachable image URL and render it.

Parameter Mapping

Size selection

When calling Wan via compatible-mode, the size is passed as the top-level size parameter:

{
  "model": "wan2.7-image",
  "size": "1024x1024",
  "messages": [...]
}

User intent	size value
Square / avatar / default	"1024x1024"
Landscape / scenery / wallpaper	"1792x1024"
Portrait / mobile / poster	"1024x1792"

Optional parameters (top-level body fields)

Parameter	Description
`n`	Number of images, 1–4, default 1
`size`	Image size, e.g. "1024x1024"

Multiple Image Generation

When n > 1, the choices array contains multiple entries, each with an image inside message.content. Download and upload each image, then render them one by one:

![Image 1 description](dc-media://mediaId1)
![Image 2 description](dc-media://mediaId2)

Error Handling

success: false + error: "No matching provider": DashScope provider not configured or disabled
success: false + error: "API Key not configured": API Key missing
statusCode: 401: API Key invalid or expired
statusCode: 429: rate limited, retry later
statusCode: 400 + InvalidParameter: bad parameters (e.g. unsupported size)
statusCode: 403 + AccessDenied.Unpurchased: model not activated; enable it in the Alibaba Cloud console

Notes

compatible-mode calls are synchronous and typically return in 10–60 seconds (wan2.7-image-pro can take longer)
Image URLs expire; download promptly
English prompts usually produce the best results; Chinese is also supported
When the user does not specify a model or size, default to wan2.7-image + 1024x1024

7.9 KiB Raw Blame History Unescape Escape