📦 deps(thirdparty): update snapshots

2026-06-18 16:04:36 +00:00
parent 71b421806e
commit dd4c084042
416 changed files with 35467 additions and 3065 deletions
@@ -1,6 +1,6 @@
 {
  "name": "antigravity-bundle-marketing-growth",
-  "version": "12.7.0",
+  "version": "12.8.0",
  "description": "Editorial \"Marketing & Growth\" bundle for Claude Code from Antigravity Awesome Skills.",
  "author": {
    "name": "sickn33 and contributors",
@@ -1,6 +1,6 @@
 {
  "name": "agyb-marketing-growth",
-  "version": "12.7.0",
+  "version": "12.8.0",
  "description": "Install the \"Marketing & Growth\" editorial skill bundle from Antigravity Awesome Skills.",
  "author": {
    "name": "sickn33 and contributors",
@@ -127,6 +127,20 @@ Estimate:

 ---

+### Tracking Verification (Required before Gate 8)
+
+Before entering the Execution Readiness Gate below, run through this checklist to make "Tracking is verified" mean something concrete:
+
+1. **Event firing:** Trigger each event the primary and secondary metrics depend on (sign-up, add-to-cart, custom event) on staging or a debug page, and confirm it lands in your analytics destination within 30 seconds.
+2. **Variant attribution:** Verify that the variant assignment ID is attached to every fired event — not just the entry event. Use your analytics' raw event view to compare a sample of 5+ events per variant.
+3. **De-duplication:** Confirm that a user reloading the page does not cause double-counted events. If your stack uses client-side de-duping, the variant ID must be part of the dedup key.
+4. **Sample randomization:** Pull the first 100 assignment records from your assignment table; the variant split should be within ±5% of the configured allocation.
+5. **Guardrail metric pipeline:** Each guardrail metric defined in §6️⃣ must have a working dashboard or alert by the time the test launches.
+
+If any of the above fails, stop and resolve it before Gate 8.
+
+---
+
 ## 8️⃣ Execution Readiness Gate (Hard Stop)

 You may proceed to implementation **only if all are true**:
@@ -113,6 +113,17 @@ A high score indicates _structural suitability_, not guaranteed rankings.

 ---

+### Scoring Guidance per Category
+
+For each of the six scoring categories, allot points within the category's weight band using these anchors:
+
+- **0–15% of band:** No alignment — the site/topic clearly does not meet the criterion (e.g. fewer than 10 candidate entities for a directory-style PSEO).
+- **16–40% of band:** Partial alignment — the criterion is partially met, OR met for a small subset of pages only.
+- **41–80% of band:** Strong alignment — the criterion holds for most of the planned page set.
+- **81–100% of band:** Exemplary — the criterion holds universally and is reinforced by a structural data source (DB, API, validated CSV).
+
+Sum the per-category scores to compute the Feasibility Index used in §"Feasibility Bands" below.
+
 ### Feasibility Bands (Required)

 | Score  | Verdict            | Interpretation                    |