Files
nexu-io__open-design/plugins/_official/design-systems/github/open-design.json
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.5 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-github",
"title": "GitHub",
"title_i18n": {
"zh-CN": "GitHub",
"zh-TW": "GitHub",
"ja": "GitHub",
"ko": "GitHub",
"de": "GitHub",
"fr": "GitHub",
"ru": "GitHub",
"es": "GitHub",
"pt-BR": "GitHub",
"it": "GitHub",
"vi": "GitHub",
"pl": "GitHub",
"id": "GitHub",
"nl": "GitHub",
"ar": "GitHub",
"tr": "GitHub",
"uk": "GitHub",
"en": "GitHub"
},
"version": "0.1.0",
"publishedAt": "2026-05-12T07:18:16Z",
"description": "Code-forward platform. Functional density, blue-on-white precision, Primer foundations.",
"description_i18n": {
"zh-CN": "代码优先平台。功能密度高,蓝白配色精准,基于 Primer 设计体系。",
"zh-TW": "程式碼優先平台。功能密度高,藍白配色精準,基於 Primer 設計體系。",
"ja": "コード中心のプラットフォーム。機能密度が高く、青と白の精密なデザイン、Primerの基盤を採用。",
"ko": "코드 중심 플랫폼. 높은 기능 밀도, 청백 색상의 정밀함, Primer 기반 설계.",
"de": "Code-zentrierte Plattform. Hohe funktionale Dichte, Blau-Weiß-Präzision, Primer-Grundlagen.",
"fr": "Plateforme orientée code. Densité fonctionnelle, précision bleu sur blanc, fondations Primer.",
"ru": "Платформа, ориентированная на код. Высокая функциональная плотность, синяя на белом точность, основы Primer.",
"es": "Plataforma centrada en código. Alta densidad funcional, precisión azul sobre blanco, fundamentos Primer.",
"pt-BR": "Plataforma focada em código. Alta densidade funcional, precisão azul sobre branco, fundamentos Primer.",
"it": "Piattaforma incentrata sul codice. Alta densità funzionale, precisione blu su bianco, fondamenti Primer.",
"vi": "Nền tảng tập trung vào code. Mật độ chức năng cao, chính xác xanh trên trắng, nền tảng Primer.",
"pl": "Platforma skoncentrowana na kodzie. Wysoka gęstość funkcjonalna, precyzja niebieski na białym, fundamenty Primer.",
"id": "Platform berbasis kode. Kepadatan fungsional tinggi, presisi biru di atas putih, fondasi Primer.",
"nl": "Code-gerichte platform. Hoge functionele dichtheid, blauw-op-wit precisie, Primer-fundamenten.",
"ar": "منصة تركز على الأكواد. كثافة وظيفية عالية، دقة الأزرق على الأبيض، أساسيات Primer.",
"tr": "Kod odaklı platform. Yüksek fonksiyonel yoğunluk, beyaz üzerine mavi hassasiyet, Primer temelleri.",
"uk": "Платформа, орієнтована на код. Висока функціональна щільність, синьо-біла точність, основи Primer.",
"en": "Code-forward platform. Functional density, blue-on-white precision, Primer foundations."
},
"license": "MIT",
"tags": [
"design-system",
"first-party",
"design",
"developer-tools"
],
"od": {
"kind": "scenario",
"taskKind": "new-generation",
"mode": "design-system",
"scenario": "design",
"surface": "web",
"useCase": {
"query": {
"en": "Generate a {{artifactKind}} using the GitHub 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 GitHub 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": "github",
"primary": true
},
"assets": [
"./DESIGN.md"
]
},
"pipeline": {
"stages": [
{
"id": "generate",
"atoms": [
"file-write",
"live-artifact"
]
}
]
},
"capabilities": [
"prompt:inject",
"fs:write"
]
}
}