Files
lefarcen da7c4ae051 fix(web): rank Community "Newest" by shipped publishedAt, not local install timestamps (#5597)
* fix(web): rank Community "Newest" by shipped publishedAt, not local install timestamps

The Community gallery Newest toggle sorted by the installed-record
updatedAt/installedAt. Those are stamped when a machine seeds its own
database, so a fresh install (or an upgrade that re-stamps the catalog)
writes the whole bundled catalog milliseconds apart in folder-walk
order — Newest showed reverse walk order (roughly reverse-alphabetical),
unrelated to publication recency.

Root-cause fix: bundled templates now ship a real publication date.

- packages/contracts: add optional manifest field publishedAt (ISO 8601).
- apps/web sortByNewest: freshness = publishedAt when parseable, else
  updatedAt (right signal for user-installed plugins); tie-breaks and
  stability unchanged.
- plugins/_official: backfill publishedAt into all 460 bundled manifests
  from each folder's first-appearance commit date in upstream git
  history.
- e2e: repository-resource guard requiring every bundled manifest to
  declare a parseable publishedAt, so the signal cannot silently erode.
- docs: field reference entries in plugins-spec (en + zh-CN).

Issue: https://plane.powerformer.net/open-design/projects/49832a02-3158-4faf-bf2f-d0e39c40c7e6/issues/ca0778af-97f5-4fc0-bc63-739280904979

Generated-By: looper 0.0.0-dev (runner=worker, agent=claude-code)

* worker: 模板用最新筛选,筛选出来的不是最新的

Generated-By: looper 0.0.0-dev (runner=worker, agent=claude-code)

* fix(web): keep shipped appeal order inside same-publishedAt batches

Review follow-up (#5597, nettee): after the freshness tie on an equal
publishedAt, the comparator still consulted local updatedAt/installedAt,
which a fresh install stamps in folder-walk order — so every
same-publication batch (largest: 322 manifests on one catalog date)
re-sorted per machine instead of keeping the shipped visual-appeal
ranking. Same-publishedAt records now preserve their incoming position;
local timestamps break ties only when at least one side has no usable
publishedAt. Adds the requested regression spec pinning
same-publishedAt / different-updatedAt records.

Generated-By: looper 0.0.0-dev (runner=worker, agent=claude-code)

* fix(web): gate publishedAt freshness to bundled records; untrack oversized looper attachment

Review follow-up (#5597, nettee round 2): publishedAt was overriding
updatedAt for every visible plugin, so a user-installed github/local/
marketplace plugin carrying an old manifest publishedAt would be buried
behind bundled templates despite a newer local install. publishedAtMs
now returns null for non-bundled records — "Newest" means install
recency for user installs, catalog publication for bundled ones. Adds
the requested regression (non-bundled, old publishedAt, newer
updatedAt) and clarifies the field docs (en + zh-CN).

CI repair: commit 578f7a9 tracked .looper-attachments/bug13_1.png
(3.8MB bug screenshot), tripping the Static gate 1MiB blob guard and
the Validate workspace aggregate. Untrack it and gitignore
.looper-attachments/ so harness attachments stay out of the repo.

Generated-By: looper 0.0.0-dev (runner=worker, agent=claude-code)
2026-07-14 08:43:57 +00:00

114 lines
4.0 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
"specVersion": "1.0.0",
"name": "design-system-replicate",
"title": "Replicate",
"title_i18n": {
"zh-CN": "Replicate",
"zh-TW": "Replicate",
"ja": "Replicate",
"ko": "Replicate",
"de": "Replicate",
"fr": "Replicate",
"ru": "Replicate",
"es": "Replicate",
"pt-BR": "Replicate",
"it": "Replicate",
"vi": "Replicate",
"pl": "Replicate",
"id": "Replicate",
"nl": "Replicate",
"ar": "Replicate",
"tr": "Replicate",
"uk": "Replicate",
"en": "Replicate"
},
"version": "0.1.0",
"publishedAt": "2026-05-12T07:18:16Z",
"description": "Run ML models via API. Clean white canvas, code-forward.",
"description_i18n": {
"zh-CN": "通过 API 运行机器学习模型。简洁白色画布,代码优先。",
"zh-TW": "透過 API 執行機器學習模型。簡潔白色畫布,程式碼優先。",
"ja": "APIで機械学習モデルを実行。シンプルな白いキャンバス、コード中心。",
"ko": "API를 통해 머신러닝 모델을 실행합니다. 깔끔한 흰색 캔버스, 코드 중심.",
"de": "ML-Modelle per API ausführen. Saubere weiße Leinwand, Code-fokussiert.",
"fr": "Exécutez des modèles ML via API. Canevas blanc épuré, axé sur le code.",
"ru": "Запуск ML-моделей через API. Чистый белый холст, ориентация на код.",
"es": "Ejecuta modelos de ML mediante API. Lienzo blanco limpio, enfocado en código.",
"pt-BR": "Execute modelos de ML via API. Tela branca limpa, focado em código.",
"it": "Esegui modelli ML tramite API. Canvas bianco pulito, orientato al codice.",
"vi": "Chạy các mô hình ML qua API. Giao diện trắng sạch sẽ, tập trung vào code.",
"pl": "Uruchamiaj modele ML przez API. Czyste białe płótno, skoncentrowane na kodzie.",
"id": "Jalankan model ML lewat API. Kanvas putih bersih, fokus pada kode.",
"nl": "Voer ML-modellen uit via API. Schoon wit canvas, code-gericht.",
"ar": "تشغيل نماذج ML عبر API. لوحة بيضاء نظيفة، تركز على الكود.",
"tr": "API ile ML modellerini çalıştırın. Temiz beyaz tuval, kod odaklı.",
"uk": "Запуск ML-моделей через API. Чисте біле полотно, орієнтація на код.",
"en": "Run ML models via API. Clean white canvas, code-forward."
},
"license": "MIT",
"tags": [
"design-system",
"first-party",
"design",
"ai-llm"
],
"od": {
"kind": "scenario",
"taskKind": "new-generation",
"mode": "design-system",
"scenario": "design",
"surface": "web",
"useCase": {
"query": {
"en": "Generate a {{artifactKind}} using the Replicate design system. Stay faithful to its colour palette, typography, spacing, iconography, and component vocabulary as documented in DESIGN.md.",
"zh-CN": "使用这个插件完成以下任务:Generate a {{artifactKind}} using the Replicate design system. Stay faithful to its colour palette, typography, spacing, iconography, and component vocabulary as documented in DESIGN.md."
}
},
"inputs": [
{
"name": "artifactKind",
"label": "Artifact kind",
"type": "select",
"options": [
"landing page",
"dashboard",
"marketing site",
"app screen"
],
"default": "landing page"
},
{
"name": "brief",
"label": "Brief",
"type": "text",
"placeholder": "What should the page communicate?"
}
],
"context": {
"designSystem": {
"ref": "replicate",
"primary": true
},
"assets": [
"./DESIGN.md"
]
},
"pipeline": {
"stages": [
{
"id": "generate",
"atoms": [
"file-write",
"live-artifact"
]
}
]
},
"capabilities": [
"prompt:inject",
"fs:write"
]
}
}