toga-ai 1.0.246 → 1.0.247

package/knowledge/2.0/apps/toga2-commerce/features/expedited-shipping-gating.md

@@ -70,20 +70,20 @@ This mirrors the toga2.5 / toga25-supply "named rule" / config-driven cart patte
 behavior is expressed in config, not in code branches.
 
 ## Gotchas
-- **Compass MacBook catalog categorization is INCONSISTENT, and it breaks the computer-kit
-  assumption.** Verified in prod `Client_Compass.Items`: MacBooks are spread across at least
-  **four** categories — `"APPLE LAPTOP"` (e.g. 14" MacBook Pro M5, partNumber `MDE54LL/A-S`),
-  `"COMPUTERS"` (14"/16" MacBook Pro M4, `MW2W3LLA-S` / `MX2X3LLA-S`), `"MAC & ACCESSORIES"`
-  (~18 older M1/M2 MacBook Air/Pro models), and `"PDC NEW HIRE - APPLE"`. The gate matches
-  `itemCategory.name === "COMPUTERS"` **only**, so MacBooks tagged `APPLE LAPTOP` /
-  `MAC & ACCESSORIES` do **not** qualify for expedited shipping (and would not trigger the
-  one-per-order limit either). Confirmed live on beta and prod: the "Compass 14\" Macbook"
-  kit's primary item resolves to `APPLE LAPTOP`. The backend assumption (Alex) was that all
-  MacBooks were already `COMPUTERS`; the data shows otherwise. **Team decision this session:**
-  keep the rule keyed to `COMPUTERS` only (intended). The fix is **catalog data
-  normalization** (or extending the config `value` list to
-  `["COMPUTERS","APPLE LAPTOP"]`) — it is *not* a code gap. Hand the categorization to the
-  catalog/data team.
+- **Computer-kit eligibility depends on consistent `COMPUTERS` categorization (was a data gap,
+  now resolved).** The gate matches the primary item's `itemCategory.name === "COMPUTERS"`
+  **only**. MacBook kits were initially mis-categorized: during this session
+  `Client_Compass.Items` showed MacBooks spread across **four** categories — `"COMPUTERS"`
+  (14"/16" MacBook Pro M4, `MW2W3LLA-S` / `MX2X3LLA-S`), `"APPLE LAPTOP"` (14" MacBook Pro M5,
+  `MDE54LL/A-S`), `"MAC & ACCESSORIES"` (~18 older M1/M2 models), and `"PDC NEW HIRE - APPLE"`.
+  A MacBook tagged anything other than `COMPUTERS` did **not** qualify for expedited (nor
+  trigger the one-per-order limit). **Resolved 2026-06-30:** the catalog/data team
+  re-categorized the computer/laptop kits (incl. MacBooks) to `COMPUTERS`; the tested
+  "Compass 14\" Macbook" was confirmed updated and now shows expedited. **Lesson:** the rule is
+  only as correct as the catalog — new computer/laptop kits must be filed under `COMPUTERS`
+  (the same category the bundle-page one-per-order limit keys off). If a future kit
+  legitimately needs a different category, extend the config `value` to a list (e.g.
+  `["COMPUTERS","APPLE LAPTOP"]`) rather than adding code.
 - **The gate is UI-only, not server-enforced.** Shipping methods come from `/shipping-methods`
   (UPS carrier, fetched in `useCartViewModel`) and are filtered client-side. The gate is a
   selection restriction, not order validation. Follow-up recommended: enforce
@@ -104,5 +104,8 @@ behavior is expressed in config, not in code branches.
   base-name compare via `getBaseShippingOptionName`; edit-order silent-downgrade/load race →
   reset guarded on dirty + loaded options. Documented the Compass MacBook category
   inconsistency as a known gotcha (data-normalization item, not a code gap). (tcox)
-</content>
-</invoke>
+- 2026-06-30 — Catalog data normalized: the computer/laptop kits (incl. MacBooks) were
+  re-categorized to `COMPUTERS`, so MacBook kits now qualify for expedited; the tested
+  "Compass 14\" Macbook" was confirmed updated. Updated the MacBook-categorization gotcha to
+  reflect the resolution, and removed stray closing tags accidentally written into the doc.
+  (tcox)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.246",
+  "version": "1.0.247",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",