Toothy review for Shogun ‑ AB Testing

WORST APP EVER - MY PRODUCT PHOTOS LAGGED AND DID NOT WORK / THE PRICE EVEN AFTER UN INSTALLING KEPT CHANGING . Subject: Re: Toothy - pricing test issue Hi Sweetan, Thanks for looking into this. Before reinstalling or sharing collaborator access, I want to share what I've found on my end, because I think it points to the actual cause. After uninstalling Shogun, I found that Shogun had written code directly into my theme files rather than only using app embeds/blocks. Specifically: 1. A snippet called `snippets/product-media-gallery.liquid` had Shogun-authored Liquid code reading from metafields under the `app--214825828353` namespace (`product-pricing`, `product-variant-pricing`, `test-media-1` through `test-media-4`). This code used `{% paginate %}` on values that aren't valid paginateable objects, which caused a "Liquid error: Array is not paginateable" on my live product pages. 2. Separately, I found a file called `snippets/shogun-optimizer.liquid`, labeled in its own comments as "Auto-generated by Shogun-AB." This file contains embedded, minified JavaScript that appears to run content-type detection across templates and includes a `cartCreate` GraphQL mutation. This file was still present and apparently still active on my storefront after I had already uninstalled the app. 3. The pricing metafields under `app--214825828353` also still exist on my products, since metafields persist independently of whether the app is installed. This is very likely why the price kept changing even after uninstall — the leftover Liquid/JS was still reading that stored data. Given this, before I reinstall anything or share collaborator access, I'd like to understand: - Does reinstalling the app actually remove or replace `shogun-optimizer.liquid` and the leftover metafields, or does it just resume using them? - Is there a clean uninstall process that removes all injected snippets and metafields, rather than leaving them orphaned in the theme? - Can you confirm whether the `cartCreate` mutation in that script ever affects the price actually charged at checkout, separate from what's displayed on the page? I want to be sure no customers were charged incorrectly during the test. I'd rather resolve this by removing the leftover code and metafields directly, since I already have a good picture of what was left behind. If there's a specific reason full collaborator access is necessary beyond what I've described above, let me know and I'm happy to discuss it further. Thanks,