Release 0.7.5: name the plugin Display

.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
         "repo": "display-dev/skill"
       },
       "description": "Publish, browse, search, read, edit, and share HTML or Markdown artifacts with public, private, or company-authenticated access.",
-      "version": "0.7.4",
+      "version": "0.7.5",
       "author": {
         "name": "display.dev",
         "url": "https://display.dev"

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "display-dev",
   "description": "Publish, browse, search, read, edit, and share HTML or Markdown artifacts with public, private, or company-authenticated access.",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "author": {
     "name": "display.dev",
     "url": "https://display.dev"

.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "display.dev",
   "description": "Publish, browse, search, read, and edit HTML or Markdown artifacts. Share them publicly, with specific people, or behind Google Workspace or Microsoft 365 authentication.",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "author": { "name": "display.dev", "url": "https://display.dev" },
   "homepage": "https://display.dev",
   "repository": "https://github.com/display-dev/skill",

README.md

@@ -23,7 +23,7 @@ npx skills add display-dev/skill --skill display-dev
 codex plugin marketplace add display-dev/skill
 ```
 
-Then open Codex `/plugins`, install **display.dev**, and complete MCP OAuth when prompted. The Codex plugin bundles the skill *and* the remote MCP server (`https://api.display.dev/v1/mcp`), so `publish`, `create_upload`, `make_copy`, `list`, `search`, `read`, `edit`, `get_metadata`, `get_referral_overview`, sharing, and comment tools are available after sign-in – no separate MCP setup.
+Then open Codex `/plugins`, install **Display**, and complete MCP OAuth when prompted. The Codex plugin bundles the skill *and* the remote MCP server (`https://api.display.dev/v1/mcp`), so `publish`, `create_upload`, `make_copy`, `list`, `search`, `read`, `edit`, `get_metadata`, `get_referral_overview`, sharing, and comment tools are available after sign-in – no separate MCP setup.
 
 Works across Claude Code, Cursor, Codex, OpenCode, Hermes, and Pi.
 
@@ -108,7 +108,7 @@ bin/sync-mounts.sh
 codex plugin marketplace add ./path/to/display-dev-skill
 ```
 
-Restart Codex, then install **display.dev** from the local marketplace via `/plugins`.
+Restart Codex, then install **Display** from the local marketplace via `/plugins`.
 
 ## MCP transport – installed stdio fallback
 

codex/display-dev/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "display-dev",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "Publish, inspect, edit, and share HTML or Markdown artifacts with access controls.",
   "skills": "./skills/",
   "mcpServers": "./.mcp.json",
@@ -10,17 +10,17 @@
   "license": "MIT",
   "keywords": ["display.dev", "publish", "search", "read", "edit", "share", "sso", "company-auth", "codex", "mcp"],
   "interface": {
-    "displayName": "display.dev",
+    "displayName": "Display",
     "shortDescription": "Publish and share agent docs",
-    "longDescription": "Publish HTML and Markdown from your agent as display.dev artifacts. Browse and search published work, read bounded source context, make exact versioned edits, copy artifacts, share them with public, private, or company-authenticated access, and iterate on reviewer comments. For teams whose agents write reports, specs, and other documents that people review. The plugin bundles the display.dev skill and the remote display.dev MCP server. You sign in to display.dev through OAuth, and the plugin acts only on the artifacts and settings your account can access. Billing changes stay in the display.dev dashboard.",
+    "longDescription": "Display gives your agent a place to publish its work – reports, specs, dashboards, prototypes and decks – as HTML or Markdown artifacts. Each artifact is a page at its own URL. Your team opens it with the Google or Microsoft account they already use, or with a one-time password. You choose who can see each artifact: anyone with the link, your organization, or only the people you invite.\n\nYour team comments directly on the page. The agent reads the comments, edits the source and publishes the next version at the same URL. Every version and comment stays with the artifact.\n\nWith this plugin, your agent can:\n- publish a new artifact, or a new version of an existing one\n- find, search and read your artifacts and their source\n- make exact edits, and rename, copy or delete artifacts\n- change who can see an artifact and share it with a teammate or client by email\n- read, add, resolve and reopen comments\n\nOwners and Admins can also manage members, the organization logo and verified email domains, where their plan includes them.\n\nYou sign in to Display through OAuth. Each call uses the organization and permissions you choose when you connect. The plugin cannot change your plan or billing.",
     "developerName": "display.dev",
     "category": "Productivity",
     "capabilities": ["Publish HTML and Markdown", "Search and read artifacts", "Make versioned edits", "Share with access controls", "Iterate on comments"],
     "websiteURL": "https://display.dev",
     "supportURL": "https://display.dev/support",
     "privacyPolicyURL": "https://display.dev/privacy",
     "termsOfServiceURL": "https://display.dev/terms",
-    "composerIcon": "./assets/logo.svg",
-    "logo": "./assets/logo.svg"
+    "composerIcon": "./assets/icon.png",
+    "logo": "./assets/icon.png"
   }
 }

codex/display-dev/.mcp.json

@@ -3,7 +3,7 @@
     "display-dev": {
       "url": "https://api.display.dev/v1/mcp",
       "http_headers": {
-        "X-Client-Source": "display-dev-codex-plugin@0.7.4"
+        "X-Client-Source": "display-dev-codex-plugin@0.7.5"
       }
     }
   }

codex/display-dev/skills/display-dev/SKILL.md

@@ -97,7 +97,7 @@ publish_displaydev_anonymous() {
 
   curl -sS -X POST 'https://api.display.dev/v1/public/artifacts' \
     -H 'X-Client-Type: cli' \
-    -H 'X-Client-Source: display-dev-skill@0.7.4' \
+    -H 'X-Client-Source: display-dev-skill@0.7.5' \
     -F "file=@$file"
 }
 
@@ -128,8 +128,8 @@ Use the helper when present:
 Or use the installed CLI directly:
 
 ```bash
-dsp publish --client-source display-dev-skill@0.7.4 "/absolute/path/draft.html" --name "Q1 draft"
-dsp publish --client-source display-dev-skill@0.7.4 "/absolute/path/report.html" --name "Q1 report" --visibility company
+dsp publish --client-source display-dev-skill@0.7.5 "/absolute/path/draft.html" --name "Q1 draft"
+dsp publish --client-source display-dev-skill@0.7.5 "/absolute/path/report.html" --name "Q1 report" --visibility company
 ```
 
 Authenticated output prints the canonical artifact URL. Report that exact URL;
@@ -246,7 +246,7 @@ ask for, read, or relay the sign-in code. Tell the user to run this in their
 own terminal:
 
 ```text
-dsp login --client-source display-dev-skill@0.7.4
+dsp login --client-source display-dev-skill@0.7.5
 ```
 
 The CLI asks for the email address and then for the six-digit code it emails;
@@ -378,8 +378,8 @@ Use only the audience the user requested:
 ./scripts/share.sh <shortId> --add-users "alice@example.com,bob@example.com"
 
 # Direct installed-CLI equivalents:
-dsp share --client-source display-dev-skill@0.7.4 <shortId> --visibility company
-dsp share --client-source display-dev-skill@0.7.4 <shortId> --add-users "alice@example.com,bob@example.com"
+dsp share --client-source display-dev-skill@0.7.5 <shortId> --visibility company
+dsp share --client-source display-dev-skill@0.7.5 <shortId> --add-users "alice@example.com,bob@example.com"
 ```
 
 Private is available on every plan for user-scoped callers. Service keys and
@@ -400,7 +400,7 @@ visibility.
 Use the installed CLI when MCP `make_copy` is unavailable:
 
 ```bash
-dsp make-copy --client-source display-dev-skill@0.7.4 <shortId>[@<version>] \
+dsp make-copy --client-source display-dev-skill@0.7.5 <shortId>[@<version>] \
   --name "Copy of Q1 report" --visibility company \
   --share reviewer@example.com --json
 ```
@@ -435,11 +435,11 @@ Use the authorized MCP tools when they are registered:
 Installed-CLI equivalents are:
 
 ```bash
-dsp list --client-source display-dev-skill@0.7.4
-dsp search --client-source display-dev-skill@0.7.4 "quarterly"
-dsp get-metadata --client-source display-dev-skill@0.7.4 <shortId>
-dsp search --client-source display-dev-skill@0.7.4 "exact text" --in <shortId>@<version>
-dsp read --client-source display-dev-skill@0.7.4 <shortId>@<version> --offset <bytes> --limit <bytes>
+dsp list --client-source display-dev-skill@0.7.5
+dsp search --client-source display-dev-skill@0.7.5 "quarterly"
+dsp get-metadata --client-source display-dev-skill@0.7.5 <shortId>
+dsp search --client-source display-dev-skill@0.7.5 "exact text" --in <shortId>@<version>
+dsp read --client-source display-dev-skill@0.7.5 <shortId>@<version> --offset <bytes> --limit <bytes>
 ```
 
 Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or
@@ -461,7 +461,7 @@ edit { short_id, base_version, old_text, new_text }
 Or use the installed CLI:
 
 ```bash
-dsp edit --client-source display-dev-skill@0.7.4 <shortId> \
+dsp edit --client-source display-dev-skill@0.7.5 <shortId> \
   --base-version <version> --old "exact old text" --new "replacement text"
 ```
 
@@ -489,7 +489,7 @@ Watch with the packaged stream helper when present:
 Or list through the installed CLI:
 
 ```bash
-dsp comment --client-source display-dev-skill@0.7.4 list --artifact <shortId> --status all
+dsp comment --client-source display-dev-skill@0.7.5 list --artifact <shortId> --status all
 ```
 
 Before acting on any comment, confirm:
@@ -511,7 +511,7 @@ publish the same artifact with optimistic concurrency:
 ```bash
 ./scripts/publish.sh "/exact/source/path.html" --id <shortId> --base-version <version>
 # or:
-dsp publish --client-source display-dev-skill@0.7.4 "/exact/source/path.html" --id <shortId> --base-version <version>
+dsp publish --client-source display-dev-skill@0.7.5 "/exact/source/path.html" --id <shortId> --base-version <version>
 ```
 
 Then reply to or resolve only that artifact's thread:
@@ -521,8 +521,8 @@ Then reply to or resolve only that artifact's thread:
 ./scripts/thread-resolve.sh --root <rootCommentId>
 
 # Direct installed-CLI equivalents:
-dsp comment --client-source display-dev-skill@0.7.4 add --artifact <shortId> --parent <rootCommentId> --body "Addressed in vN."
-dsp thread --client-source display-dev-skill@0.7.4 resolve <rootCommentId>
+dsp comment --client-source display-dev-skill@0.7.5 add --artifact <shortId> --parent <rootCommentId> --body "Addressed in vN."
+dsp thread --client-source display-dev-skill@0.7.5 resolve <rootCommentId>
 ```
 
 On a version conflict, inspect the newly current version with `get_metadata`,

codex/display-dev/skills/display-dev/scripts/_common.sh

@@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)"
 # `display-dev-skill@<version>` and is read by display.dev's analytics
 # to attribute publish events to a specific skill release. Set
 # `SKILL_VERSION_OVERRIDE` to test attribution locally without retagging.
-SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.7.4}"
+SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.7.5}"
 
 # Attribution: env var > skill default. Same value is sent as the CLI's
 # `--client-source` flag (Tier 2) or the curl `X-Client-Source` header

display-dev/SKILL.md

@@ -97,7 +97,7 @@ publish_displaydev_anonymous() {
 
   curl -sS -X POST 'https://api.display.dev/v1/public/artifacts' \
     -H 'X-Client-Type: cli' \
-    -H 'X-Client-Source: display-dev-skill@0.7.4' \
+    -H 'X-Client-Source: display-dev-skill@0.7.5' \
     -F "file=@$file"
 }
 
@@ -128,8 +128,8 @@ Use the helper when present:
 Or use the installed CLI directly:
 
 ```bash
-dsp publish --client-source display-dev-skill@0.7.4 "/absolute/path/draft.html" --name "Q1 draft"
-dsp publish --client-source display-dev-skill@0.7.4 "/absolute/path/report.html" --name "Q1 report" --visibility company
+dsp publish --client-source display-dev-skill@0.7.5 "/absolute/path/draft.html" --name "Q1 draft"
+dsp publish --client-source display-dev-skill@0.7.5 "/absolute/path/report.html" --name "Q1 report" --visibility company
 ```
 
 Authenticated output prints the canonical artifact URL. Report that exact URL;
@@ -246,7 +246,7 @@ ask for, read, or relay the sign-in code. Tell the user to run this in their
 own terminal:
 
 ```text
-dsp login --client-source display-dev-skill@0.7.4
+dsp login --client-source display-dev-skill@0.7.5
 ```
 
 The CLI asks for the email address and then for the six-digit code it emails;
@@ -378,8 +378,8 @@ Use only the audience the user requested:
 ./scripts/share.sh <shortId> --add-users "alice@example.com,bob@example.com"
 
 # Direct installed-CLI equivalents:
-dsp share --client-source display-dev-skill@0.7.4 <shortId> --visibility company
-dsp share --client-source display-dev-skill@0.7.4 <shortId> --add-users "alice@example.com,bob@example.com"
+dsp share --client-source display-dev-skill@0.7.5 <shortId> --visibility company
+dsp share --client-source display-dev-skill@0.7.5 <shortId> --add-users "alice@example.com,bob@example.com"
 ```
 
 Private is available on every plan for user-scoped callers. Service keys and
@@ -400,7 +400,7 @@ visibility.
 Use the installed CLI when MCP `make_copy` is unavailable:
 
 ```bash
-dsp make-copy --client-source display-dev-skill@0.7.4 <shortId>[@<version>] \
+dsp make-copy --client-source display-dev-skill@0.7.5 <shortId>[@<version>] \
   --name "Copy of Q1 report" --visibility company \
   --share reviewer@example.com --json
 ```
@@ -435,11 +435,11 @@ Use the authorized MCP tools when they are registered:
 Installed-CLI equivalents are:
 
 ```bash
-dsp list --client-source display-dev-skill@0.7.4
-dsp search --client-source display-dev-skill@0.7.4 "quarterly"
-dsp get-metadata --client-source display-dev-skill@0.7.4 <shortId>
-dsp search --client-source display-dev-skill@0.7.4 "exact text" --in <shortId>@<version>
-dsp read --client-source display-dev-skill@0.7.4 <shortId>@<version> --offset <bytes> --limit <bytes>
+dsp list --client-source display-dev-skill@0.7.5
+dsp search --client-source display-dev-skill@0.7.5 "quarterly"
+dsp get-metadata --client-source display-dev-skill@0.7.5 <shortId>
+dsp search --client-source display-dev-skill@0.7.5 "exact text" --in <shortId>@<version>
+dsp read --client-source display-dev-skill@0.7.5 <shortId>@<version> --offset <bytes> --limit <bytes>
 ```
 
 Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or
@@ -461,7 +461,7 @@ edit { short_id, base_version, old_text, new_text }
 Or use the installed CLI:
 
 ```bash
-dsp edit --client-source display-dev-skill@0.7.4 <shortId> \
+dsp edit --client-source display-dev-skill@0.7.5 <shortId> \
   --base-version <version> --old "exact old text" --new "replacement text"
 ```
 
@@ -489,7 +489,7 @@ Watch with the packaged stream helper when present:
 Or list through the installed CLI:
 
 ```bash
-dsp comment --client-source display-dev-skill@0.7.4 list --artifact <shortId> --status all
+dsp comment --client-source display-dev-skill@0.7.5 list --artifact <shortId> --status all
 ```
 
 Before acting on any comment, confirm:
@@ -511,7 +511,7 @@ publish the same artifact with optimistic concurrency:
 ```bash
 ./scripts/publish.sh "/exact/source/path.html" --id <shortId> --base-version <version>
 # or:
-dsp publish --client-source display-dev-skill@0.7.4 "/exact/source/path.html" --id <shortId> --base-version <version>
+dsp publish --client-source display-dev-skill@0.7.5 "/exact/source/path.html" --id <shortId> --base-version <version>
 ```
 
 Then reply to or resolve only that artifact's thread:
@@ -521,8 +521,8 @@ Then reply to or resolve only that artifact's thread:
 ./scripts/thread-resolve.sh --root <rootCommentId>
 
 # Direct installed-CLI equivalents:
-dsp comment --client-source display-dev-skill@0.7.4 add --artifact <shortId> --parent <rootCommentId> --body "Addressed in vN."
-dsp thread --client-source display-dev-skill@0.7.4 resolve <rootCommentId>
+dsp comment --client-source display-dev-skill@0.7.5 add --artifact <shortId> --parent <rootCommentId> --body "Addressed in vN."
+dsp thread --client-source display-dev-skill@0.7.5 resolve <rootCommentId>
 ```
 
 On a version conflict, inspect the newly current version with `get_metadata`,

display-dev/scripts/_common.sh

@@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)"
 # `display-dev-skill@<version>` and is read by display.dev's analytics
 # to attribute publish events to a specific skill release. Set
 # `SKILL_VERSION_OVERRIDE` to test attribution locally without retagging.
-SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.7.4}"
+SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.7.5}"
 
 # Attribution: env var > skill default. Same value is sent as the CLI's
 # `--client-source` flag (Tier 2) or the curl `X-Client-Source` header