Bläddra i källkod

fix(community,llm): remove duplicate README assets

lsdsjy 1 månad sedan
förälder
incheckning
49b48369db

+ 2 - 2
.agents/notes/implemented/process/2026-08-17-readme-assets-on-cdn.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write .agents/notes/implemented/process/2026-08-17-readme-assets-on-cdn.md
-2026-08-17-readme-assets-on-cdn.md: 2cc4736224315c38be933a1b29f669b8ad29749d
-2026-08-17-readme-assets-on-cdn.zh.md: 04fe1650c11ee723b8915e88484960bd13e2205e
+2026-08-17-readme-assets-on-cdn.md: 8918e2118123382553e1ea295351482030e0e640
+2026-08-17-readme-assets-on-cdn.zh.md: a1314068ff0bbebfef5bb0053f04aebe650f6101

+ 2 - 2
.agents/notes/implemented/process/2026-08-17-readme-assets-on-cdn.md

@@ -16,7 +16,7 @@ The README references fixed URLs under `https://cdn.deepseek.com/harness/readme/
 
 The uploader accepts only the three README filenames, verifies each source is a PNG file, and uploads it to `dp-cdn-deepseek/harness/readme/` with `Content-Type: image/png` and `Cache-Control: no-store`. It checks the OBS response status, reports the resulting public URL, and closes the client on both success and failure. Repository Actions Secrets supply `OBS_DSH_README_ACCESS_KEY_ID` and `OBS_DSH_README_SECRET_ACCESS_KEY`; the OBS identity needs write access only to that object prefix.
 
-The assets repository history is the update ledger and rollback source. The public README keeps the same URLs across image replacements, so ordinary image updates do not require a product-repository change or a public-repository synchronization.
+The assets repository provides the update history and rollback source. The public README keeps the same URLs across image replacements, so ordinary image updates do not require a product-repository change or a public-repository synchronization.
 
 ## Alternatives considered
 
@@ -30,6 +30,6 @@ The assets repository history is the update ledger and rollback source. The publ
 
 ## Consequences
 
-Community QR codes can change through one assets-repository push while the public README remains unchanged. The product repository carries no OBS dependency or credential, uploads retain an auditable git source, and both the object metadata and CDN route prevent stale cached QR codes.
+Community QR codes can change through one assets-repository push while the public README remains unchanged. The product repository carries no OBS dependency or credential, uploads retain an auditable git source, and CDN responses carry `Cache-Control: no-store`.
 
 The README depends on the public CDN and GitHub's image proxy, while publication depends on a second private repository and its two Actions Secrets. `no-store` gives up edge and browser caching for these small files.

+ 2 - 2
.agents/notes/implemented/process/2026-08-17-readme-assets-on-cdn.zh.md

@@ -16,7 +16,7 @@ README 引用 `https://cdn.deepseek.com/harness/readme/` 下的固定 URL。私
 
 上传脚本只接受 3 个 README 图片文件名,验证每个源文件均为 PNG,并以 `Content-Type: image/png` 和 `Cache-Control: no-store` 上传到 `dp-cdn-deepseek/harness/readme/`。脚本检查 OBS 响应状态、报告对应公开 URL,并在成功或失败后关闭客户端。仓库级 GitHub Actions Secret 提供 `OBS_DSH_README_ACCESS_KEY_ID` 和 `OBS_DSH_README_SECRET_ACCESS_KEY`;OBS 身份只需拥有该对象前缀的写权限。
 
-资产仓库历史充当更新记录和回滚真源。图片替换后,公开 README 继续使用相同 URL,因此常规图片更新无需修改产品仓库或同步公开仓库。
+资产仓库提供更新记录和回滚真源。图片替换后,公开 README 继续使用相同 URL,因此常规图片更新无需修改产品仓库或同步公开仓库。
 
 ## 曾考虑的替代方案
 
@@ -30,6 +30,6 @@ README 引用 `https://cdn.deepseek.com/harness/readme/` 下的固定 URL。私
 
 ## 后果
 
-社区二维码可以通过一次资产仓库 push 更新,公开 README 无需改变。产品仓库不携带 OBS 依赖或凭证;上传内容保留可审计的 git 真源;对象元数据和 CDN 路由均会阻止二维码使用陈旧缓存。
+社区二维码可以通过一次资产仓库 push 更新,公开 README 无需改变。产品仓库不携带 OBS 依赖或凭证;上传内容保留可审计的 git 真源;CDN 响应携带 `Cache-Control: no-store`。
 
 README 依赖公开 CDN 和 GitHub 图片代理,发布流程则依赖另一个私有仓库及其 2 个 GitHub Actions Secret。`no-store` 为这些小文件放弃边缘节点和浏览器缓存。

BIN
assets/community-wechat-official-account.png


BIN
assets/community-wecom-assistant.png


+ 0 - 0
assets/community-wecom-survey.png → packages/llm/llm-pi-ai/tests/fixtures/qr-code.png


+ 1 - 1
packages/llm/llm-pi-ai/tests/provider-apis.e2e.ts

@@ -210,7 +210,7 @@ for (const profile of providerCases) {
       if (profile.provider === 'anthropic') {
         it('sends a real image through the authenticated Anthropic visual path', async () => {
           const data = new Uint8Array(await readFile(
-            new URL('../../../../assets/community-wecom-survey.png', import.meta.url),
+            new URL('./fixtures/qr-code.png', import.meta.url),
           ))
           const ref: ImageAttachmentRef = {
             attachmentId: AttachmentId(`sha256:${'a'.repeat(64)}`),