epicmerch-mcp 1.3.12 → 1.3.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "epicmerch-mcp",
-  "version": "1.3.12",
+  "version": "1.3.13",
   "description": "MCP server for EpicMerch — integrates e-commerce into Claude and ChatGPT",
   "type": "module",
   "main": "src/index.js",

package/skills/epicmerch.md

@@ -1,6 +1,6 @@
 ---
 name: epicmerch
-description: EpicMerch umbrella — guided 6-step onboarding wizard for new merchants (ends with a full smoke test against the live API), plus an intent router for merchants who already know what they want (scaffold a storefront, set up payments, add a Buy Now button, manage a store, migrate from Shopify, verify the store).
+description: EpicMerch umbrella — guided 6-step onboarding wizard for new merchants that ALWAYS ends by auto-running a live end-to-end order test (/epicmerch-e2e), plus an intent router for merchants who already know what they want (scaffold a storefront, set up payments, add a Buy Now button, manage a store, migrate from Shopify, verify the store). Verification is the non-negotiable definition of done for any build.
 ---
 
 # EpicMerch — the umbrella
@@ -21,6 +21,18 @@ If ambiguous, ask ONE disambiguating question: *"Want me to walk you through a f
 
 ---
 
+## DEFINITION OF DONE — read this before you finish (applies to BOTH modes)
+
+**`/epicmerch` is not complete until a live end-to-end test has run and passed.**
+
+This holds no matter how the build happened — the wizard's scaffold step, an intent-mode `/epicmerch-storefront`, OR a fully custom build you designed through brainstorming (e.g. a themed multi-page store). However you got here, the LAST thing you do before telling the merchant "your store is set up" is run **`/epicmerch-e2e`** (full pipeline) — falling back to `/epicmerch-verify` only if the server's test-login isn't configured.
+
+Common trap: a design-heavy request ("build me a saree store") pulls you into scope/theme/spec brainstorming and a custom build, and the flow ends at "looks good!" without ever testing against the live API. **Don't let that happen.** After the storefront files are written and the `.env` has a real API key, run the e2e/verify gate. A store that was never tested against the live API is not done — that's exactly how the cart-shape / productId / out-of-stock bugs reached real merchants.
+
+If you realize you're wrapping up `/epicmerch` and haven't run the test → run it now.
+
+---
+
 ## Step A — Wizard mode (guided onboarding)
 
 The merchant either said nothing or asked to "start". Walk them through the 5 steps below **in order**. After each step, briefly recap (`✓ done` or `✗ skipped — <reason>`) and move on. Don't dump all 5 questions at once; one step at a time.
@@ -130,35 +142,48 @@ Ask:
 - Yes → run `/epicmerch-magic-checkout`. (That skill verifies Razorpay is configured first; if step 2 set it up, this just works.)
 - No / skip → `✗ Skipped.` (They can always add it later by saying *"add a Buy Now button"*.)
 
-### Wizard step 6/6 — Verify the storefront
-
-Before declaring victory, run an end-to-end smoke test to make sure
-the site can actually talk to the API. Catches bugs like wrong field
-names, missing variants, stale orderItems shape — the kind of thing
-that would otherwise show up as a 422 only when a real customer hits
-checkout.
-
-> "Last step — let me run a smoke test to confirm everything works."
-
-Run `/epicmerch-verify` (or, if not in a slash-command client, fetch
-https://api.epicmerch.in/api/skills/epicmerch-verify.md and follow it).
-The verify skill does NOT send OTP and does NOT charge real money;
-it tests every read-only path and validates the checkout payload
-shape, then gives the merchant a 4-line manual recipe for the actual
-cart → checkout → Razorpay test-card flow.
-
-**If any check fails:** do NOT just print the failure and stop. Route
-to `/epicmerch-debug` automatically — it has a four-check playbook for
-the most common failure modes (OTP not persisting, products not
-loading, INSUFFICIENT_STOCK on checkout, cart returning 401) and will
-diagnose + fix without further merchant intervention. After debug runs,
-re-run `/epicmerch-verify` to confirm the fix held.
-
-Only proceed to wrap-up when verify is fully green.
+### Wizard step 6/6 — Verify the storefront (MANDATORY — always runs)
+
+**This step is NOT optional and is NOT skippable.** Whether the store was
+built by the wizard's scaffold step OR by a custom/brainstormed build,
+the final action of `/epicmerch` is ALWAYS to run a live test against the
+API. Do not print a "your store is set up" wrap-up until this has run and
+passed. If you find yourself about to end the `/epicmerch` flow without
+having run a verification, STOP and run it now.
+
+> "Last step — let me run a live end-to-end test to confirm everything actually works."
+
+**Run `/epicmerch-e2e` automatically.** It's the deepest check: it gets a
+customer session, creates a throwaway test product, adds it to a cart,
+creates a real order (exercising stock reservation + Razorpay order
+creation, no charge), verifies every response shape, then cleans up
+(cancels the order, deletes the product). This proves the WHOLE pipeline,
+not just read paths.
+
+`/epicmerch-e2e` gets its customer token via the server's env-gated test
+phone (`store_auth_send_otp` + `store_auth_verify_otp` against
+`E2E_TEST_PHONE`), so it needs no OTP/SMS and no manual login.
+
+**Graceful fallback** — if `/epicmerch-e2e`'s token step fails because the
+server doesn't have `E2E_TEST_PHONE`/`E2E_TEST_OTP` configured (you'll see
+a normal SMS channel instead of `e2e-test`, or a 401 on verify), fall back
+to `/epicmerch-verify` — it tests every read path + the checkout payload
+shape with no token needed, then gives a manual cart→checkout test recipe.
+Tell the merchant: *"Ran the read-path + payload checks; to enable the
+fully-automated order test, ask your EpicMerch operator to set
+E2E_TEST_PHONE/E2E_TEST_OTP on the server."*
+
+**If any check fails:** do NOT just print the failure and stop. Route to
+`/epicmerch-debug` automatically — its four-check playbook (OTP not
+persisting, products not loading, INSUFFICIENT_STOCK on checkout, cart
+401) diagnoses + fixes without further merchant intervention. Then re-run
+the test to confirm the fix held.
+
+Only proceed to wrap-up when the test is fully green.
 
 ### Wizard wrap-up
 
-Print a one-block recap after `/epicmerch-verify` finishes:
+Print a one-block recap after the step-6 test finishes:
 
 ```
 ━━━ Your store is set up ━━━
@@ -168,13 +193,13 @@ Print a one-block recap after `/epicmerch-verify` finishes:
   ✓ Catalog: <N> products
   ✓ Storefront: scaffolded into <project>   (or "skipped — no project")
   ✗ Buy Now button: skipped                  (or ✓ if they added it)
-  ✓ Smoke test: all read paths + checkout shape pass
+  ✓ End-to-end test: product → cart → order → cleanup all passed
+       (or "✓ Read-path + payload checks passed; order test skipped —
+        E2E_TEST_PHONE not configured on server")
 
-Next: restart your dev server (`npm run dev`) to pick up `.env`, then
-follow the manual recipe in Phase 4 of the verify report to test the
-final cart → checkout → Razorpay flow with the test card. Ask me
-about analytics, notifications, or abandoned-cart messages whenever
-you're ready.
+Next: restart your dev server (`npm run dev`) to pick up `.env`. Your
+store works end-to-end. Ask me about analytics, notifications, or
+abandoned-cart messages whenever you're ready.
 ```
 
 ---
@@ -223,11 +248,13 @@ If the fetch fails, fall back to the high-level intent using the MCP tools you h
 
 Briefly recap and ask if anything else is needed. One short sentence, not three follow-ups.
 
+**If the sub-flow built or changed the storefront** (`/epicmerch-storefront`, `/epicmerch-orders`, `/epicmerch-products`, `/epicmerch-magic-checkout`, or a custom build), run the **Definition of Done** gate above before recapping — `/epicmerch-e2e` (or `/epicmerch-verify` fallback). Don't say "done" on anything that touched checkout without testing it live. (Pure config sub-flows like Razorpay/Stripe setup don't need the storefront e2e, but a quick `merchant_diagnose` confirms they took.)
+
 Examples:
 
 > "Razorpay is now live on your store. Want a Buy Now button too?" *(routes to `/epicmerch-magic-checkout`)*
 
-> "Storefront scaffolded. Restart your dev server (`npm run dev`) to load `.env`. Need anything else — payments, Shopify migration, analytics?"
+> "Storefront scaffolded and end-to-end tested (product → cart → order all pass). Restart your dev server (`npm run dev`) to load `.env`. Need anything else — payments, Shopify migration, analytics?"
 
 ---