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.1 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-intercom",
"title": "Intercom",
"title_i18n": {
"zh-CN": "Intercom",
"zh-TW": "Intercom",
"ja": "Intercom",
"ko": "Intercom",
"de": "Intercom",
"fr": "Intercom",
"ru": "Intercom",
"es": "Intercom",
"pt-BR": "Intercom",
"it": "Intercom",
"vi": "Intercom",
"pl": "Intercom",
"id": "Intercom",
"nl": "Intercom",
"ar": "Intercom",
"tr": "Intercom",
"uk": "Intercom",
"en": "Intercom"
},
"version": "0.1.0",
"publishedAt": "2026-05-12T07:18:16Z",
"description": "Customer messaging. Friendly blue palette, conversational UI patterns.",
"description_i18n": {
"zh-CN": "客户消息传递。友好的蓝色调色板,对话式 UI 模式。",
"zh-TW": "客戶訊息傳遞。友善的藍色調色盤,對話式 UI 模式。",
"ja": "カスタマーメッセージング。フレンドリーなブルーパレット、会話型UIパターン。",
"ko": "고객 메시징. 친근한 블루 팔레트, 대화형 UI 패턴.",
"de": "Kundenkommunikation. Freundliche blaue Farbpalette, konversationelle UI-Muster.",
"fr": "Messagerie client. Palette bleue conviviale, motifs d'interface conversationnelle.",
"ru": "Обмен сообщениями с клиентами. Дружелюбная синяя палитра, разговорные UI-паттерны.",
"es": "Mensajería con clientes. Paleta azul amigable, patrones de UI conversacional.",
"pt-BR": "Mensagens com clientes. Paleta azul amigável, padrões de UI conversacional.",
"it": "Messaggistica clienti. Palette blu amichevole, pattern UI conversazionali.",
"vi": "Nhắn tin khách hàng. Bảng màu xanh thân thiện, mẫu UI đối thoại.",
"pl": "Wiadomości z klientami. Przyjazna niebieska paleta, konwersacyjne wzorce UI.",
"id": "Pesan pelanggan. Palet biru ramah, pola UI percakapan.",
"nl": "Klantcommunicatie. Vriendelijk blauw palet, conversationele UI-patronen.",
"ar": "رسائل العملاء. لوحة ألوان زرقاء ودية، أنماط UI حوارية.",
"tr": "Müşteri mesajlaşması. Arkadaş canlısı mavi palet, konuşma tarzı UI desenleri.",
"uk": "Обмін повідомленнями з клієнтами. Дружня синя палітра, розмовні UI-патерни.",
"en": "Customer messaging. Friendly blue palette, conversational UI patterns."
},
"license": "MIT",
"tags": [
"design-system",
"first-party",
"design",
"productivity-saas"
],
"od": {
"kind": "scenario",
"taskKind": "new-generation",
"mode": "design-system",
"scenario": "design",
"surface": "web",
"useCase": {
"query": {
"en": "Generate a {{artifactKind}} using the Intercom 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 Intercom 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": "intercom",
"primary": true
},
"assets": [
"./DESIGN.md"
]
},
"pipeline": {
"stages": [
{
"id": "generate",
"atoms": [
"file-write",
"live-artifact"
]
}
]
},
"capabilities": [
"prompt:inject",
"fs:write"
]
}
}