@zenuml/core 3.46.8 → 3.46.10

package/.claude/skills/propagate-core-release/references/downstreams.md

@@ -1,6 +1,6 @@
 # Downstream Repos
 
-Canonical downstream targets for propagating a published `@zenuml/core` release.
+Canonical downstream targets for filing rollout issues after a published `@zenuml/core` release.
 
 ## Repo Table
 
@@ -14,29 +14,29 @@ Canonical downstream targets for propagating a published `@zenuml/core` release.
 | `ZenUml/codemirror-extensions` | `~/workspaces/zenuml/codemirror-extensions` | pnpm | `pnpm update @zenuml/core` | `pnpm build` | CodeMirror language extensions for ZenUML DSL. HTML-renderer consumer. |
 | `ZenUml/jetbrains-zenuml` | `~/workspaces/zenuml/jetbrains-zenuml` | — | See notes | — | **Not an npm consumer.** Vendors a built JS bundle. Update by copying the new `dist/` output from core's build. Skip if unsure and report. |
 
-## Lockfile Handling
+## Issue Authoring Guidance
 
-After every dependency update, regenerate the lockfile:
+When writing a downstream issue for an npm consumer, explicitly include the lockfile refresh step:
 
 - **pnpm**: `pnpm install` (updates `pnpm-lock.yaml`)
 - **yarn**: `yarn install` (updates `yarn.lock`)
 
-Always commit the lockfile alongside the `package.json` change. A PR without an updated lockfile will fail CI.
+Tell the downstream team to include the updated lockfile in the PR. A PR without an updated lockfile will usually fail CI.
 
-## Clone Strategy
+## Local Checkout Usage
 
-If a local path does not exist:
+Local checkouts are optional for this skill. Use them only if you need extra context to clarify the issue body safely. Do not clone repos just to file the issue.
+
+If you do need a checkout and the local path does not exist:
 
 ```bash
 gh repo clone <repo-slug> <local-path>
 ```
 
-Then proceed with fetch + branch creation as usual.
-
 ## General Rules
 
-- Each repo gets its own update branch and its own draft PR.
-- Reuse existing propagation branches or draft PRs when they already target the same core version.
+- Each repo gets its own rollout issue.
+- Reuse an existing open issue when it already targets the same core version.
 - `mermaid-js/mermaid` and `mermaid-js/mermaid-live-editor` are under the `mermaid-js` GitHub org (not `ZenUml`).
 - Only `mermaid-js/mermaid` and `mermaid-js/mermaid-live-editor` should receive SVG-renderer integration changes tied to core API/export changes.
 - Treat all other downstreams as HTML-renderer consumers unless the user explicitly asks for a renderer migration.

package/.mcp.json.example

@@ -0,0 +1,17 @@
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["@playwright/mcp@latest", "--extension"],
+      "env": {
+        "PLAYWRIGHT_MCP_EXTENSION_TOKEN": "<your-token-here>"
+      }
+    },
+    "chrome-devtools": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "chrome-devtools-mcp"],
+      "env": {}
+    }
+  }
+}