diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index c9a259d..9dfb264 100644 --- a/.claude-plugin/marketplace.json +++ b/.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. Includes Visualize, the display.dev MCP server, and /display-dev:feedback for reviewer comments.", - "version": "0.8.0", + "version": "0.9.0", "author": { "name": "display.dev", "url": "https://display.dev" diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index aed121b..07633f8 100644 --- a/.claude-plugin/plugin.json +++ b/.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. Includes the Visualize skill for on-brand HTML, the display.dev MCP server, /display-dev:feedback for reviewer comments, a secret scan before publishes, and a session-start note about new comments.", - "version": "0.8.0", + "version": "0.9.0", "author": { "name": "display.dev", "url": "https://display.dev" @@ -19,7 +19,7 @@ "type": "http", "url": "https://api.display.dev/v1/mcp", "headers": { - "X-Client-Source": "display-dev-claude-plugin@0.8.0" + "X-Client-Source": "display-dev-claude-plugin@0.9.0" } } } diff --git a/.cursor-plugin/plugin.json b/.cursor-plugin/plugin.json index a6207bd..c00ad63 100644 --- a/.cursor-plugin/plugin.json +++ b/.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.8.0", + "version": "0.9.0", "author": { "name": "display.dev", "url": "https://display.dev" }, "homepage": "https://display.dev", "repository": "https://github.com/display-dev/skill", diff --git a/README.md b/README.md index 6a5a48a..4cfb6be 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,7 @@ sets of display.dev tools and uses one of them. 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.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`, sharing, and comment tools are available after sign-in – no separate MCP setup. Works across Claude Code, Cursor, Codex, OpenCode, Hermes, and Pi. @@ -66,7 +66,6 @@ Once installed, your assistant picks up the skill on phrasings like: - "add a company email domain" - "transfer an email domain" - "change the email domains add-on" -- "show my referral link" / "show referral rewards" You can publish without a `display.dev` account or any setup – you get a 30-day preview URL and a browser claim URL. To create an account or sign in, connect the bundled remote MCP server through OAuth where the host supports it, or run `dsp login --email you@example.com` in your own terminal and enter the six-digit code there. The installed `dsp` CLI stores the resulting session. The skill never asks for, reads, or relays the code, and never instructs an agent to inspect your inbox. @@ -105,12 +104,6 @@ and the CLI never perform the irreversible confirmation. The paid email domains add-on is also managed by a current Owner in **Settings → Email Domains**. MCP and the direct CLI do not enable or disable it. -For the referral program, the skill uses the read-only -`get_referral_overview` MCP tool to return the link available to the current -member or organization connection and to explain earned, available, and used -organization rewards. It reports missing links without guessing why they are -unavailable. - For an existing artifact, the skill prefers MCP `make_copy` or `dsp make-copy` to create a new artifact from a retained version. Discussions and people invited to the source are not carried over. The user can choose recipients for the new artifact. diff --git a/claude/commands/feedback.md b/claude/commands/feedback.md index 19b5fb4..2c91b45 100644 --- a/claude/commands/feedback.md +++ b/claude/commands/feedback.md @@ -24,7 +24,7 @@ argument is optional: `$ARGUMENTS` Use one display.dev tool path for the whole task: 1. If a shell is available and `dsp` is on PATH, use the CLI. Add - `--client-source display-dev-claude-plugin@0.8.0` to every `dsp` command. + `--client-source display-dev-claude-plugin@0.9.0` to every `dsp` command. Prefix every command that changes state (`publish`, `edit`, `share`, `comment add`, `thread resolve`) with `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code`, so the @@ -39,7 +39,7 @@ Use one display.dev tool path for the whole task: List the user's artifacts that have open comments: ```bash -dsp list --client-source display-dev-claude-plugin@0.8.0 --author me --sort updated_at --dir desc --limit 100 --json +dsp list --client-source display-dev-claude-plugin@0.9.0 --author me --sort updated_at --dir desc --limit 100 --json ``` (MCP: `list` with `author: ["me"]`, `sort: "updated_at"`, `limit: 100`.) @@ -57,8 +57,8 @@ updated artifacts has open comments, and stop. before the first hyphen: `https://display.dsp.so/abc12345-q3-plan` → `abc12345`. 2. Read the metadata and the open threads: - `dsp get-metadata --client-source display-dev-claude-plugin@0.8.0 ` and - `dsp comment --client-source display-dev-claude-plugin@0.8.0 list --artifact --status open` + `dsp get-metadata --client-source display-dev-claude-plugin@0.9.0 ` and + `dsp comment --client-source display-dev-claude-plugin@0.9.0 list --artifact --status open` (MCP: `get_metadata`, `list_comments`). Note the current version. 3. Sort each open thread into one group: - **Change request**: a change to the artifact's content. @@ -77,19 +77,19 @@ updated artifacts has open comments, and stop. 5. Make the approved changes as one new version: - If the artifact was published from a file in this workspace and the user confirms that file, edit it and publish it: - `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp publish --client-source display-dev-claude-plugin@0.8.0 --id --base-version `. + `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp publish --client-source display-dev-claude-plugin@0.9.0 --id --base-version `. - Otherwise export the current version - (`dsp export --client-source display-dev-claude-plugin@0.8.0 @ > `), edit the copy, and + (`dsp export --client-source display-dev-claude-plugin@0.9.0 @ > `), edit the copy, and publish it the same way. With MCP, edit the content you read and call `publish` with `short_id` and `base_version`. - For one small change, - `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp edit --client-source display-dev-claude-plugin@0.8.0 --base-version --old --new ` + `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp edit --client-source display-dev-claude-plugin@0.9.0 --base-version --old --new ` (MCP: `edit`) is also fine. 6. Close the threads: - Applied change: reply with one line, for example "Changed in v7: the churn figure now uses Q3 data.", then resolve the thread - (`DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp comment --client-source display-dev-claude-plugin@0.8.0 add --artifact --parent --body `, - `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp thread --client-source display-dev-claude-plugin@0.8.0 resolve `; MCP: `add_comment`, + (`DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp comment --client-source display-dev-claude-plugin@0.9.0 add --artifact --parent --body `, + `DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp thread --client-source display-dev-claude-plugin@0.9.0 resolve `; MCP: `add_comment`, `resolve_thread`). - Question: reply with the answer and leave the thread open for the person who asked. @@ -103,10 +103,10 @@ Say so, then offer: - **Ask someone to review it**: ask for the reviewer's email address, then share the artifact with them - (`DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp share --client-source display-dev-claude-plugin@0.8.0 --add-users `; MCP: `share`). Do not change + (`DISPLAYDEV_ACTOR_TYPE=agent DISPLAYDEV_ACTOR_NAME=claude-code dsp share --client-source display-dev-claude-plugin@0.9.0 --add-users `; MCP: `share`). Do not change the artifact's visibility. - **Wait for comments**: available only with a shell. Poll - `dsp comment --client-source display-dev-claude-plugin@0.8.0 list --artifact --status open --since ` + `dsp comment --client-source display-dev-claude-plugin@0.9.0 list --artifact --status open --since ` every 60 seconds in the background. When a comment arrives, continue with B. Stop after the time the user gives, or after 60 minutes. - **Nothing for now**: stop. diff --git a/codex/display-dev/.codex-plugin/plugin.json b/codex/display-dev/.codex-plugin/plugin.json index d49e9b2..5f80a88 100644 --- a/codex/display-dev/.codex-plugin/plugin.json +++ b/codex/display-dev/.codex-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "display-dev", - "version": "0.8.0", + "version": "0.9.0", "description": "Publish, inspect, edit, and share HTML or Markdown artifacts with access controls.", "skills": "./skills/", "mcpServers": "./.mcp.json", diff --git a/codex/display-dev/.mcp.json b/codex/display-dev/.mcp.json index d0fd307..f1b4346 100644 --- a/codex/display-dev/.mcp.json +++ b/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.8.0" + "X-Client-Source": "display-dev-codex-plugin@0.9.0" } } } diff --git a/codex/display-dev/skills/display-dev/SKILL.md b/codex/display-dev/skills/display-dev/SKILL.md index b199339..6387220 100644 --- a/codex/display-dev/skills/display-dev/SKILL.md +++ b/codex/display-dev/skills/display-dev/SKILL.md @@ -11,8 +11,7 @@ description: > "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", - "show my referral link", "show referral - rewards", "watch comments on this artifact", + "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. @@ -99,7 +98,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.8.0' \ + -H 'X-Client-Source: display-dev-skill@0.9.0' \ -F "file=@$file" } @@ -130,8 +129,8 @@ Use the helper when present: Or use the installed CLI directly: ```bash -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/draft.html" --name "Q1 draft" -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/report.html" --name "Q1 report" --visibility company +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/draft.html" --name "Q1 draft" +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/report.html" --name "Q1 report" --visibility company ``` Authenticated output prints the canonical artifact URL. Report that exact URL; @@ -248,7 +247,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.8.0 +dsp login --client-source display-dev-skill@0.9.0 ``` The CLI asks for the email address and then for the six-digit code it emails; @@ -334,43 +333,6 @@ verify_email_domain. If the result is transfer_ready, the agent sends a target Owner to Settings → Email Domains for the final review and confirmation. ``` -## View the referral program - -Use the authorized MCP `get_referral_overview` tool when the user asks for a -referral link or the organization's referral rewards. It is read-only. - -Interpret the response exactly: - -- `referralUrl` is the current member's personal link for a human connection. - For an organization service-account connection, it is the generic - organization link. -- `organizationReferralUrl` is the generic organization link exposed to a - human Owner or Admin. It is `null` for ordinary Members and organization - service accounts. -- `referrerRewardsEarned` is the number of rewards the organization has earned - by referring new organizations, out of the 12-reward limit. -- `welcomeRewardEarned` says whether the organization earned the reward for - joining through a referral. -- `proRewardsAvailable` counts rewards waiting for an eligible Pro invoice. -- `proRewardsUsed` counts rewards already applied to Pro invoices. - -If either link is `null`, say that it is not available for the current -connection. Do not infer a role, plan, membership state, rollout state, or -specific reason. Do not construct a link from an ID or ask for a standalone -referral code. If the tool is not registered, direct the user to **Referral -program** in the display.dev dashboard rather than claiming the overview is -unavailable. - -Example: - -```text -User: Show me the referral link I can share and how many rewards are left. -Agent: Calls get_referral_overview. It returns the available personal or -organization link verbatim, reports earned rewards against the 12-reward limit, -and explains available versus used rewards without guessing why another link -is null. -``` - ## Share an artifact Use only the audience the user requested: @@ -380,8 +342,8 @@ Use only the audience the user requested: ./scripts/share.sh --add-users "alice@example.com,bob@example.com" # Direct installed-CLI equivalents: -dsp share --client-source display-dev-skill@0.8.0 --visibility company -dsp share --client-source display-dev-skill@0.8.0 --add-users "alice@example.com,bob@example.com" +dsp share --client-source display-dev-skill@0.9.0 --visibility company +dsp share --client-source display-dev-skill@0.9.0 --add-users "alice@example.com,bob@example.com" ``` Private is available on every plan for user-scoped callers. Service keys and @@ -402,7 +364,7 @@ visibility. Use the installed CLI when MCP `make_copy` is unavailable: ```bash -dsp make-copy --client-source display-dev-skill@0.8.0 [@] \ +dsp make-copy --client-source display-dev-skill@0.9.0 [@] \ --name "Copy of Q1 report" --visibility company \ --share reviewer@example.com --json ``` @@ -437,11 +399,11 @@ Use the authorized MCP tools when they are registered: Installed-CLI equivalents are: ```bash -dsp list --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "quarterly" -dsp get-metadata --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "exact text" --in @ -dsp read --client-source display-dev-skill@0.8.0 @ --offset --limit +dsp list --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "quarterly" +dsp get-metadata --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "exact text" --in @ +dsp read --client-source display-dev-skill@0.9.0 @ --offset --limit ``` Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or @@ -463,7 +425,7 @@ edit { short_id, base_version, old_text, new_text } Or use the installed CLI: ```bash -dsp edit --client-source display-dev-skill@0.8.0 \ +dsp edit --client-source display-dev-skill@0.9.0 \ --base-version --old "exact old text" --new "replacement text" ``` @@ -491,7 +453,7 @@ Watch with the packaged stream helper when present: Or list through the installed CLI: ```bash -dsp comment --client-source display-dev-skill@0.8.0 list --artifact --status all +dsp comment --client-source display-dev-skill@0.9.0 list --artifact --status all ``` Before acting on any comment, confirm: @@ -513,7 +475,7 @@ publish the same artifact with optimistic concurrency: ```bash ./scripts/publish.sh "/exact/source/path.html" --id --base-version # or: -dsp publish --client-source display-dev-skill@0.8.0 "/exact/source/path.html" --id --base-version +dsp publish --client-source display-dev-skill@0.9.0 "/exact/source/path.html" --id --base-version ``` Then reply to or resolve only that artifact's thread: @@ -523,8 +485,8 @@ Then reply to or resolve only that artifact's thread: ./scripts/thread-resolve.sh --root # Direct installed-CLI equivalents: -dsp comment --client-source display-dev-skill@0.8.0 add --artifact --parent --body "Addressed in vN." -dsp thread --client-source display-dev-skill@0.8.0 resolve +dsp comment --client-source display-dev-skill@0.9.0 add --artifact --parent --body "Addressed in vN." +dsp thread --client-source display-dev-skill@0.9.0 resolve ``` On a version conflict, inspect the newly current version with `get_metadata`, diff --git a/codex/display-dev/skills/display-dev/scripts/_common.sh b/codex/display-dev/skills/display-dev/scripts/_common.sh index ccc0f9d..537b691 100755 --- a/codex/display-dev/skills/display-dev/scripts/_common.sh +++ b/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@` 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.8.0}" +SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.9.0}" # 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 diff --git a/display-dev/SKILL.md b/display-dev/SKILL.md index b199339..6387220 100644 --- a/display-dev/SKILL.md +++ b/display-dev/SKILL.md @@ -11,8 +11,7 @@ description: > "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", - "show my referral link", "show referral - rewards", "watch comments on this artifact", + "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. @@ -99,7 +98,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.8.0' \ + -H 'X-Client-Source: display-dev-skill@0.9.0' \ -F "file=@$file" } @@ -130,8 +129,8 @@ Use the helper when present: Or use the installed CLI directly: ```bash -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/draft.html" --name "Q1 draft" -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/report.html" --name "Q1 report" --visibility company +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/draft.html" --name "Q1 draft" +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/report.html" --name "Q1 report" --visibility company ``` Authenticated output prints the canonical artifact URL. Report that exact URL; @@ -248,7 +247,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.8.0 +dsp login --client-source display-dev-skill@0.9.0 ``` The CLI asks for the email address and then for the six-digit code it emails; @@ -334,43 +333,6 @@ verify_email_domain. If the result is transfer_ready, the agent sends a target Owner to Settings → Email Domains for the final review and confirmation. ``` -## View the referral program - -Use the authorized MCP `get_referral_overview` tool when the user asks for a -referral link or the organization's referral rewards. It is read-only. - -Interpret the response exactly: - -- `referralUrl` is the current member's personal link for a human connection. - For an organization service-account connection, it is the generic - organization link. -- `organizationReferralUrl` is the generic organization link exposed to a - human Owner or Admin. It is `null` for ordinary Members and organization - service accounts. -- `referrerRewardsEarned` is the number of rewards the organization has earned - by referring new organizations, out of the 12-reward limit. -- `welcomeRewardEarned` says whether the organization earned the reward for - joining through a referral. -- `proRewardsAvailable` counts rewards waiting for an eligible Pro invoice. -- `proRewardsUsed` counts rewards already applied to Pro invoices. - -If either link is `null`, say that it is not available for the current -connection. Do not infer a role, plan, membership state, rollout state, or -specific reason. Do not construct a link from an ID or ask for a standalone -referral code. If the tool is not registered, direct the user to **Referral -program** in the display.dev dashboard rather than claiming the overview is -unavailable. - -Example: - -```text -User: Show me the referral link I can share and how many rewards are left. -Agent: Calls get_referral_overview. It returns the available personal or -organization link verbatim, reports earned rewards against the 12-reward limit, -and explains available versus used rewards without guessing why another link -is null. -``` - ## Share an artifact Use only the audience the user requested: @@ -380,8 +342,8 @@ Use only the audience the user requested: ./scripts/share.sh --add-users "alice@example.com,bob@example.com" # Direct installed-CLI equivalents: -dsp share --client-source display-dev-skill@0.8.0 --visibility company -dsp share --client-source display-dev-skill@0.8.0 --add-users "alice@example.com,bob@example.com" +dsp share --client-source display-dev-skill@0.9.0 --visibility company +dsp share --client-source display-dev-skill@0.9.0 --add-users "alice@example.com,bob@example.com" ``` Private is available on every plan for user-scoped callers. Service keys and @@ -402,7 +364,7 @@ visibility. Use the installed CLI when MCP `make_copy` is unavailable: ```bash -dsp make-copy --client-source display-dev-skill@0.8.0 [@] \ +dsp make-copy --client-source display-dev-skill@0.9.0 [@] \ --name "Copy of Q1 report" --visibility company \ --share reviewer@example.com --json ``` @@ -437,11 +399,11 @@ Use the authorized MCP tools when they are registered: Installed-CLI equivalents are: ```bash -dsp list --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "quarterly" -dsp get-metadata --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "exact text" --in @ -dsp read --client-source display-dev-skill@0.8.0 @ --offset --limit +dsp list --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "quarterly" +dsp get-metadata --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "exact text" --in @ +dsp read --client-source display-dev-skill@0.9.0 @ --offset --limit ``` Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or @@ -463,7 +425,7 @@ edit { short_id, base_version, old_text, new_text } Or use the installed CLI: ```bash -dsp edit --client-source display-dev-skill@0.8.0 \ +dsp edit --client-source display-dev-skill@0.9.0 \ --base-version --old "exact old text" --new "replacement text" ``` @@ -491,7 +453,7 @@ Watch with the packaged stream helper when present: Or list through the installed CLI: ```bash -dsp comment --client-source display-dev-skill@0.8.0 list --artifact --status all +dsp comment --client-source display-dev-skill@0.9.0 list --artifact --status all ``` Before acting on any comment, confirm: @@ -513,7 +475,7 @@ publish the same artifact with optimistic concurrency: ```bash ./scripts/publish.sh "/exact/source/path.html" --id --base-version # or: -dsp publish --client-source display-dev-skill@0.8.0 "/exact/source/path.html" --id --base-version +dsp publish --client-source display-dev-skill@0.9.0 "/exact/source/path.html" --id --base-version ``` Then reply to or resolve only that artifact's thread: @@ -523,8 +485,8 @@ Then reply to or resolve only that artifact's thread: ./scripts/thread-resolve.sh --root # Direct installed-CLI equivalents: -dsp comment --client-source display-dev-skill@0.8.0 add --artifact --parent --body "Addressed in vN." -dsp thread --client-source display-dev-skill@0.8.0 resolve +dsp comment --client-source display-dev-skill@0.9.0 add --artifact --parent --body "Addressed in vN." +dsp thread --client-source display-dev-skill@0.9.0 resolve ``` On a version conflict, inspect the newly current version with `get_metadata`, diff --git a/display-dev/scripts/_common.sh b/display-dev/scripts/_common.sh index ccc0f9d..537b691 100755 --- a/display-dev/scripts/_common.sh +++ b/display-dev/scripts/_common.sh @@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)" # `display-dev-skill@` 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.8.0}" +SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.9.0}" # 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 diff --git a/hermes/productivity/display.dev/SKILL.md b/hermes/productivity/display.dev/SKILL.md index b199339..6387220 100644 --- a/hermes/productivity/display.dev/SKILL.md +++ b/hermes/productivity/display.dev/SKILL.md @@ -11,8 +11,7 @@ description: > "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", - "show my referral link", "show referral - rewards", "watch comments on this artifact", + "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. @@ -99,7 +98,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.8.0' \ + -H 'X-Client-Source: display-dev-skill@0.9.0' \ -F "file=@$file" } @@ -130,8 +129,8 @@ Use the helper when present: Or use the installed CLI directly: ```bash -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/draft.html" --name "Q1 draft" -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/report.html" --name "Q1 report" --visibility company +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/draft.html" --name "Q1 draft" +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/report.html" --name "Q1 report" --visibility company ``` Authenticated output prints the canonical artifact URL. Report that exact URL; @@ -248,7 +247,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.8.0 +dsp login --client-source display-dev-skill@0.9.0 ``` The CLI asks for the email address and then for the six-digit code it emails; @@ -334,43 +333,6 @@ verify_email_domain. If the result is transfer_ready, the agent sends a target Owner to Settings → Email Domains for the final review and confirmation. ``` -## View the referral program - -Use the authorized MCP `get_referral_overview` tool when the user asks for a -referral link or the organization's referral rewards. It is read-only. - -Interpret the response exactly: - -- `referralUrl` is the current member's personal link for a human connection. - For an organization service-account connection, it is the generic - organization link. -- `organizationReferralUrl` is the generic organization link exposed to a - human Owner or Admin. It is `null` for ordinary Members and organization - service accounts. -- `referrerRewardsEarned` is the number of rewards the organization has earned - by referring new organizations, out of the 12-reward limit. -- `welcomeRewardEarned` says whether the organization earned the reward for - joining through a referral. -- `proRewardsAvailable` counts rewards waiting for an eligible Pro invoice. -- `proRewardsUsed` counts rewards already applied to Pro invoices. - -If either link is `null`, say that it is not available for the current -connection. Do not infer a role, plan, membership state, rollout state, or -specific reason. Do not construct a link from an ID or ask for a standalone -referral code. If the tool is not registered, direct the user to **Referral -program** in the display.dev dashboard rather than claiming the overview is -unavailable. - -Example: - -```text -User: Show me the referral link I can share and how many rewards are left. -Agent: Calls get_referral_overview. It returns the available personal or -organization link verbatim, reports earned rewards against the 12-reward limit, -and explains available versus used rewards without guessing why another link -is null. -``` - ## Share an artifact Use only the audience the user requested: @@ -380,8 +342,8 @@ Use only the audience the user requested: ./scripts/share.sh --add-users "alice@example.com,bob@example.com" # Direct installed-CLI equivalents: -dsp share --client-source display-dev-skill@0.8.0 --visibility company -dsp share --client-source display-dev-skill@0.8.0 --add-users "alice@example.com,bob@example.com" +dsp share --client-source display-dev-skill@0.9.0 --visibility company +dsp share --client-source display-dev-skill@0.9.0 --add-users "alice@example.com,bob@example.com" ``` Private is available on every plan for user-scoped callers. Service keys and @@ -402,7 +364,7 @@ visibility. Use the installed CLI when MCP `make_copy` is unavailable: ```bash -dsp make-copy --client-source display-dev-skill@0.8.0 [@] \ +dsp make-copy --client-source display-dev-skill@0.9.0 [@] \ --name "Copy of Q1 report" --visibility company \ --share reviewer@example.com --json ``` @@ -437,11 +399,11 @@ Use the authorized MCP tools when they are registered: Installed-CLI equivalents are: ```bash -dsp list --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "quarterly" -dsp get-metadata --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "exact text" --in @ -dsp read --client-source display-dev-skill@0.8.0 @ --offset --limit +dsp list --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "quarterly" +dsp get-metadata --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "exact text" --in @ +dsp read --client-source display-dev-skill@0.9.0 @ --offset --limit ``` Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or @@ -463,7 +425,7 @@ edit { short_id, base_version, old_text, new_text } Or use the installed CLI: ```bash -dsp edit --client-source display-dev-skill@0.8.0 \ +dsp edit --client-source display-dev-skill@0.9.0 \ --base-version --old "exact old text" --new "replacement text" ``` @@ -491,7 +453,7 @@ Watch with the packaged stream helper when present: Or list through the installed CLI: ```bash -dsp comment --client-source display-dev-skill@0.8.0 list --artifact --status all +dsp comment --client-source display-dev-skill@0.9.0 list --artifact --status all ``` Before acting on any comment, confirm: @@ -513,7 +475,7 @@ publish the same artifact with optimistic concurrency: ```bash ./scripts/publish.sh "/exact/source/path.html" --id --base-version # or: -dsp publish --client-source display-dev-skill@0.8.0 "/exact/source/path.html" --id --base-version +dsp publish --client-source display-dev-skill@0.9.0 "/exact/source/path.html" --id --base-version ``` Then reply to or resolve only that artifact's thread: @@ -523,8 +485,8 @@ Then reply to or resolve only that artifact's thread: ./scripts/thread-resolve.sh --root # Direct installed-CLI equivalents: -dsp comment --client-source display-dev-skill@0.8.0 add --artifact --parent --body "Addressed in vN." -dsp thread --client-source display-dev-skill@0.8.0 resolve +dsp comment --client-source display-dev-skill@0.9.0 add --artifact --parent --body "Addressed in vN." +dsp thread --client-source display-dev-skill@0.9.0 resolve ``` On a version conflict, inspect the newly current version with `get_metadata`, diff --git a/hermes/productivity/display.dev/scripts/_common.sh b/hermes/productivity/display.dev/scripts/_common.sh index ccc0f9d..537b691 100755 --- a/hermes/productivity/display.dev/scripts/_common.sh +++ b/hermes/productivity/display.dev/scripts/_common.sh @@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)" # `display-dev-skill@` 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.8.0}" +SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.9.0}" # 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 diff --git a/pi/agent/skills/display-dev/SKILL.md b/pi/agent/skills/display-dev/SKILL.md index b199339..6387220 100644 --- a/pi/agent/skills/display-dev/SKILL.md +++ b/pi/agent/skills/display-dev/SKILL.md @@ -11,8 +11,7 @@ description: > "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", - "show my referral link", "show referral - rewards", "watch comments on this artifact", + "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. @@ -99,7 +98,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.8.0' \ + -H 'X-Client-Source: display-dev-skill@0.9.0' \ -F "file=@$file" } @@ -130,8 +129,8 @@ Use the helper when present: Or use the installed CLI directly: ```bash -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/draft.html" --name "Q1 draft" -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/report.html" --name "Q1 report" --visibility company +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/draft.html" --name "Q1 draft" +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/report.html" --name "Q1 report" --visibility company ``` Authenticated output prints the canonical artifact URL. Report that exact URL; @@ -248,7 +247,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.8.0 +dsp login --client-source display-dev-skill@0.9.0 ``` The CLI asks for the email address and then for the six-digit code it emails; @@ -334,43 +333,6 @@ verify_email_domain. If the result is transfer_ready, the agent sends a target Owner to Settings → Email Domains for the final review and confirmation. ``` -## View the referral program - -Use the authorized MCP `get_referral_overview` tool when the user asks for a -referral link or the organization's referral rewards. It is read-only. - -Interpret the response exactly: - -- `referralUrl` is the current member's personal link for a human connection. - For an organization service-account connection, it is the generic - organization link. -- `organizationReferralUrl` is the generic organization link exposed to a - human Owner or Admin. It is `null` for ordinary Members and organization - service accounts. -- `referrerRewardsEarned` is the number of rewards the organization has earned - by referring new organizations, out of the 12-reward limit. -- `welcomeRewardEarned` says whether the organization earned the reward for - joining through a referral. -- `proRewardsAvailable` counts rewards waiting for an eligible Pro invoice. -- `proRewardsUsed` counts rewards already applied to Pro invoices. - -If either link is `null`, say that it is not available for the current -connection. Do not infer a role, plan, membership state, rollout state, or -specific reason. Do not construct a link from an ID or ask for a standalone -referral code. If the tool is not registered, direct the user to **Referral -program** in the display.dev dashboard rather than claiming the overview is -unavailable. - -Example: - -```text -User: Show me the referral link I can share and how many rewards are left. -Agent: Calls get_referral_overview. It returns the available personal or -organization link verbatim, reports earned rewards against the 12-reward limit, -and explains available versus used rewards without guessing why another link -is null. -``` - ## Share an artifact Use only the audience the user requested: @@ -380,8 +342,8 @@ Use only the audience the user requested: ./scripts/share.sh --add-users "alice@example.com,bob@example.com" # Direct installed-CLI equivalents: -dsp share --client-source display-dev-skill@0.8.0 --visibility company -dsp share --client-source display-dev-skill@0.8.0 --add-users "alice@example.com,bob@example.com" +dsp share --client-source display-dev-skill@0.9.0 --visibility company +dsp share --client-source display-dev-skill@0.9.0 --add-users "alice@example.com,bob@example.com" ``` Private is available on every plan for user-scoped callers. Service keys and @@ -402,7 +364,7 @@ visibility. Use the installed CLI when MCP `make_copy` is unavailable: ```bash -dsp make-copy --client-source display-dev-skill@0.8.0 [@] \ +dsp make-copy --client-source display-dev-skill@0.9.0 [@] \ --name "Copy of Q1 report" --visibility company \ --share reviewer@example.com --json ``` @@ -437,11 +399,11 @@ Use the authorized MCP tools when they are registered: Installed-CLI equivalents are: ```bash -dsp list --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "quarterly" -dsp get-metadata --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "exact text" --in @ -dsp read --client-source display-dev-skill@0.8.0 @ --offset --limit +dsp list --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "quarterly" +dsp get-metadata --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "exact text" --in @ +dsp read --client-source display-dev-skill@0.9.0 @ --offset --limit ``` Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or @@ -463,7 +425,7 @@ edit { short_id, base_version, old_text, new_text } Or use the installed CLI: ```bash -dsp edit --client-source display-dev-skill@0.8.0 \ +dsp edit --client-source display-dev-skill@0.9.0 \ --base-version --old "exact old text" --new "replacement text" ``` @@ -491,7 +453,7 @@ Watch with the packaged stream helper when present: Or list through the installed CLI: ```bash -dsp comment --client-source display-dev-skill@0.8.0 list --artifact --status all +dsp comment --client-source display-dev-skill@0.9.0 list --artifact --status all ``` Before acting on any comment, confirm: @@ -513,7 +475,7 @@ publish the same artifact with optimistic concurrency: ```bash ./scripts/publish.sh "/exact/source/path.html" --id --base-version # or: -dsp publish --client-source display-dev-skill@0.8.0 "/exact/source/path.html" --id --base-version +dsp publish --client-source display-dev-skill@0.9.0 "/exact/source/path.html" --id --base-version ``` Then reply to or resolve only that artifact's thread: @@ -523,8 +485,8 @@ Then reply to or resolve only that artifact's thread: ./scripts/thread-resolve.sh --root # Direct installed-CLI equivalents: -dsp comment --client-source display-dev-skill@0.8.0 add --artifact --parent --body "Addressed in vN." -dsp thread --client-source display-dev-skill@0.8.0 resolve +dsp comment --client-source display-dev-skill@0.9.0 add --artifact --parent --body "Addressed in vN." +dsp thread --client-source display-dev-skill@0.9.0 resolve ``` On a version conflict, inspect the newly current version with `get_metadata`, diff --git a/pi/agent/skills/display-dev/scripts/_common.sh b/pi/agent/skills/display-dev/scripts/_common.sh index ccc0f9d..537b691 100755 --- a/pi/agent/skills/display-dev/scripts/_common.sh +++ b/pi/agent/skills/display-dev/scripts/_common.sh @@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)" # `display-dev-skill@` 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.8.0}" +SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.9.0}" # 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 diff --git a/skills/display-dev/SKILL.md b/skills/display-dev/SKILL.md index b199339..6387220 100644 --- a/skills/display-dev/SKILL.md +++ b/skills/display-dev/SKILL.md @@ -11,8 +11,7 @@ description: > "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", - "show my referral link", "show referral - rewards", "watch comments on this artifact", + "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. @@ -99,7 +98,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.8.0' \ + -H 'X-Client-Source: display-dev-skill@0.9.0' \ -F "file=@$file" } @@ -130,8 +129,8 @@ Use the helper when present: Or use the installed CLI directly: ```bash -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/draft.html" --name "Q1 draft" -dsp publish --client-source display-dev-skill@0.8.0 "/absolute/path/report.html" --name "Q1 report" --visibility company +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/draft.html" --name "Q1 draft" +dsp publish --client-source display-dev-skill@0.9.0 "/absolute/path/report.html" --name "Q1 report" --visibility company ``` Authenticated output prints the canonical artifact URL. Report that exact URL; @@ -248,7 +247,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.8.0 +dsp login --client-source display-dev-skill@0.9.0 ``` The CLI asks for the email address and then for the six-digit code it emails; @@ -334,43 +333,6 @@ verify_email_domain. If the result is transfer_ready, the agent sends a target Owner to Settings → Email Domains for the final review and confirmation. ``` -## View the referral program - -Use the authorized MCP `get_referral_overview` tool when the user asks for a -referral link or the organization's referral rewards. It is read-only. - -Interpret the response exactly: - -- `referralUrl` is the current member's personal link for a human connection. - For an organization service-account connection, it is the generic - organization link. -- `organizationReferralUrl` is the generic organization link exposed to a - human Owner or Admin. It is `null` for ordinary Members and organization - service accounts. -- `referrerRewardsEarned` is the number of rewards the organization has earned - by referring new organizations, out of the 12-reward limit. -- `welcomeRewardEarned` says whether the organization earned the reward for - joining through a referral. -- `proRewardsAvailable` counts rewards waiting for an eligible Pro invoice. -- `proRewardsUsed` counts rewards already applied to Pro invoices. - -If either link is `null`, say that it is not available for the current -connection. Do not infer a role, plan, membership state, rollout state, or -specific reason. Do not construct a link from an ID or ask for a standalone -referral code. If the tool is not registered, direct the user to **Referral -program** in the display.dev dashboard rather than claiming the overview is -unavailable. - -Example: - -```text -User: Show me the referral link I can share and how many rewards are left. -Agent: Calls get_referral_overview. It returns the available personal or -organization link verbatim, reports earned rewards against the 12-reward limit, -and explains available versus used rewards without guessing why another link -is null. -``` - ## Share an artifact Use only the audience the user requested: @@ -380,8 +342,8 @@ Use only the audience the user requested: ./scripts/share.sh --add-users "alice@example.com,bob@example.com" # Direct installed-CLI equivalents: -dsp share --client-source display-dev-skill@0.8.0 --visibility company -dsp share --client-source display-dev-skill@0.8.0 --add-users "alice@example.com,bob@example.com" +dsp share --client-source display-dev-skill@0.9.0 --visibility company +dsp share --client-source display-dev-skill@0.9.0 --add-users "alice@example.com,bob@example.com" ``` Private is available on every plan for user-scoped callers. Service keys and @@ -402,7 +364,7 @@ visibility. Use the installed CLI when MCP `make_copy` is unavailable: ```bash -dsp make-copy --client-source display-dev-skill@0.8.0 [@] \ +dsp make-copy --client-source display-dev-skill@0.9.0 [@] \ --name "Copy of Q1 report" --visibility company \ --share reviewer@example.com --json ``` @@ -437,11 +399,11 @@ Use the authorized MCP tools when they are registered: Installed-CLI equivalents are: ```bash -dsp list --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "quarterly" -dsp get-metadata --client-source display-dev-skill@0.8.0 -dsp search --client-source display-dev-skill@0.8.0 "exact text" --in @ -dsp read --client-source display-dev-skill@0.8.0 @ --offset --limit +dsp list --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "quarterly" +dsp get-metadata --client-source display-dev-skill@0.9.0 +dsp search --client-source display-dev-skill@0.9.0 "exact text" --in @ +dsp read --client-source display-dev-skill@0.9.0 @ --offset --limit ``` Use `get_metadata` or `dsp get-metadata`, not the removed `get` interface or @@ -463,7 +425,7 @@ edit { short_id, base_version, old_text, new_text } Or use the installed CLI: ```bash -dsp edit --client-source display-dev-skill@0.8.0 \ +dsp edit --client-source display-dev-skill@0.9.0 \ --base-version --old "exact old text" --new "replacement text" ``` @@ -491,7 +453,7 @@ Watch with the packaged stream helper when present: Or list through the installed CLI: ```bash -dsp comment --client-source display-dev-skill@0.8.0 list --artifact --status all +dsp comment --client-source display-dev-skill@0.9.0 list --artifact --status all ``` Before acting on any comment, confirm: @@ -513,7 +475,7 @@ publish the same artifact with optimistic concurrency: ```bash ./scripts/publish.sh "/exact/source/path.html" --id --base-version # or: -dsp publish --client-source display-dev-skill@0.8.0 "/exact/source/path.html" --id --base-version +dsp publish --client-source display-dev-skill@0.9.0 "/exact/source/path.html" --id --base-version ``` Then reply to or resolve only that artifact's thread: @@ -523,8 +485,8 @@ Then reply to or resolve only that artifact's thread: ./scripts/thread-resolve.sh --root # Direct installed-CLI equivalents: -dsp comment --client-source display-dev-skill@0.8.0 add --artifact --parent --body "Addressed in vN." -dsp thread --client-source display-dev-skill@0.8.0 resolve +dsp comment --client-source display-dev-skill@0.9.0 add --artifact --parent --body "Addressed in vN." +dsp thread --client-source display-dev-skill@0.9.0 resolve ``` On a version conflict, inspect the newly current version with `get_metadata`, diff --git a/skills/display-dev/scripts/_common.sh b/skills/display-dev/scripts/_common.sh index ccc0f9d..537b691 100755 --- a/skills/display-dev/scripts/_common.sh +++ b/skills/display-dev/scripts/_common.sh @@ -43,7 +43,7 @@ DSP_BIN="$(type -P dsp 2>/dev/null || true)" # `display-dev-skill@` 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.8.0}" +SKILL_VERSION="${SKILL_VERSION_OVERRIDE:-0.9.0}" # 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