@andwhy/e2e-pipeline 0.14.3 → 0.14.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andwhy/e2e-pipeline",
-  "version": "0.14.3",
+  "version": "0.14.5",
   "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.14.3",
+  "version": "0.14.5",
   "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.14.3"
+  version: "0.14.5"
 ---
 
 # Playwright Test Pipeline
@@ -512,15 +512,15 @@ Set up once per project:
 7. Dry run: GitHub → Actions → "Checkly auto-heal" → Run workflow, with the
    suite's check name. Confirm the run completes and the message shows up in
    the e2e channel and, via the rule, in the project channel (a passing
-   check should end as "not reproducible" — summary only, no message — so a
-   real dry run is easiest right after any genuine failure).
+   check ends as "not reproducible", posted as a short info message).
 
 What the user should expect afterwards: a failing monitor produces either a
 `checkly-heal` PR plus a Slack note (stale or flaky test — **review
 required, the PR is never merged automatically**; PRs carrying app-side test
 hooks say so and point at their preview run for validation), or a Slack
 escalation (regression, fix needs a behavioral app change, agent failed). A
-transient blip that doesn't reproduce stays silent by design.
+failure that passes on re-run gets a short info message and nothing else;
+the same check showing up there repeatedly is the cue to look at it.
 
 ## Checkly auto-heal (CI, not this session)
 

package/templates/github/prompts/checkly-heal.md

@@ -87,6 +87,9 @@ BASE_URL=<production-url> pnpm playwright test <failing-spec> --project=Chrome -
   immediately — no repeat runs, no wider investigation. Checkly saw it fail
   and it passes now, so the blip was transient; a genuinely unstable test
   will alert again, and that repetition is the signal a human acts on.
+  The summary is all the Slack message shows: if you saw something that
+  makes such blips fail the check (retries off in the monitor, a fragile
+  wait), name it there in a second sentence.
 
 ### 3. Triage — before any edit