---
name: report-shopify-drift
description: Record and compare Shopify homepage, collection, product, cart and checkout screenshots in one Storefront purchase flow Finding. Use for visual baselines and release comparisons. Read-only except authorized guest-cart and fictional checkout setup through payment options.
---

# Instructions

Capture a reproducible visual record of the homepage, PLP, PDP, cart and checkout, in that order. Provide one HTTP(S) storefront or prepared preview URL; no repository or integration is required.

Read the [visual change workflow](references/workflows/visual-change.md), then evaluate every active [surface Check](references/checks/) individually. Capture a stable, direct full-page primary image for each surface, including the complete document/cart extent. Record exact routes, states, viewports, timestamps, theme/revision and dynamic-content normalization. Label viewport-only or section-only images partial and continue when another surface is blocked.

Use browser/screenshot capabilities with signed-out guest state and fictional checkout data. Follow the workflow's setup even without isolated browser contexts; preserve pre-existing guest-cart items. Stop when payment options render. Never enter payment, activate a wallet, place an order, use an ambient account, create an account, edit, upload or publish.

Use `$preview-shopify-theme` for setup outside this report; consume an existing reachable URL without installing packages or starting servers. Its `references/tools/local-storefront.md#evidence-and-report-use` defines simulation limits.

Return one **Storefront purchase flow** Finding with successful images in journey order, meaningful drift comparisons, supported Issues, all Check outcomes and shared Limitations. Keep Changes empty. In chat, display the Homepage, Collection, Product, Cart and Checkout primary images inline, labeling missing/partial captures. Route broader audits to `$core-shopify-audit`, performance to `$report-shopify-performance` and funnel work to `$report-shopify-funnel`.

Follow [Glue JSON output](references/core/glue-output.md): save, validate and read back the complete `report.json`, then link it with a readable summary of every Issue. Use the bundled schema unless the host supplies one. In Glue, return the bare object through its runtime; Glue handles storage and rendering.

## Host integration

```glue-review-setup
{
  "schemaVersion": 2,
  "goal": "Create one reproducible Shopify purchase-flow visual record and report only proven breakage as Issues.",
  "context": [
    { "id": "target_url", "label": "Storefront URL", "type": "url", "required": true }
  ],
  "integrations": [],
  "categories": [],
  "batches": [
    { "id": "purchase-flow", "label": "Purchase-flow captures", "categoryIds": [] }
  ],
  "reporting": {
    "allowedResultTypes": ["finding", "issue"],
    "data": []
  },
  "completionRules": [
    "Every selected Check reaches exactly one terminal outcome.",
    "Successful captures remain attached to the single Storefront purchase flow Finding.",
    "Independent surfaces continue when another surface is blocked."
  ],
  "safetyRules": [
    "Keep the report read-only except for verified signed-out guest-cart and fictional checkout state; never create an account, change pre-existing cart items or retained personal details, or bypass host guards.",
    "Stop when payment options render and never enter payment, activate a wallet, submit payment, or place an order."
  ]
}
```