@andwhy/e2e-pipeline 0.15.0 → 0.15.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andwhy/e2e-pipeline",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "Scaffolds the full e2e testing pipeline: agent-assisted Playwright tests, CI runs against Vercel previews, and Checkly monitors that follow production deploys",
   "type": "module",
   "license": "MIT",

package/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "e2e-pipeline",
   "displayName": "&why e2e pipeline",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "Agent-assisted Playwright e2e tests: planner, generator and healer agents plus the playwright-test-pipeline skill that drives Plan → Generate → Heal, Checkly preview validation and deployment.",
   "author": {
     "name": "&why",

package/plugin/skills/playwright-test-pipeline/SKILL.md

@@ -7,7 +7,7 @@ description: Guides the full workflow for creating and maintaining Playwright
   tests, asks to "test" a page/feature/flow, or asks how the test pipeline
   works.
 metadata:
-  version: "0.15.0"
+  version: "0.15.1"
 ---
 
 # Playwright Test Pipeline
@@ -506,9 +506,10 @@ Set up once per project:
    the e2e channel tagged `[e2e:<repo-name>]`; the rule matches the **full
    bracketed tag** — never a short name like `shop`, which collides with
    other text — and sends the message to the project channel. The sent
-   message's template is just the message-text variable (plus the
-   link-to-original variable when available, so threads happen on the
-   original) — no static prefix text. Have the user add a **second
+   message's template is an arrow plus the link-to-original variable only
+   (`→ {link}`): Slack's preview under the link shows the message, and
+   threads happen on the original. No text variable, no static prefix.
+   Have the user add a **second
    manager** to the rule and record it in the rule registry in the e2e
    channel's canvas.
 7. Dry run: GitHub → Actions → "Checkly auto-heal" → Run workflow, with the