toga-ai 1.0.468 → 1.0.470

package/knowledge/2.0/apps/api2/features/request-logging.md

@@ -6,7 +6,7 @@ project: API
 client: shared
 type: feature
 status: active
-updated: 2026-07-28
+updated: 2026-07-29
 owners: ["mhammontree"]
 files:
   - api2/Component/Api/V2/V2.php
@@ -66,8 +66,39 @@ fact AIG **does** post live entitlements — the writes were **failing (HTTP 500
 core `Logs`**, not `Logs_Aig`. See
 [AIG entitlement intake → Intake is a live API feed](../../../../clients/aig/features/entitlement-intake.md).
 
+## Recovering an intake backlog from logged payloads
+
+Because the core/writer `Logs.Api` stores **every** inbound request — including failed writes —
+each row retains the **complete original `requestPayload`** (full contact / device / pricing /
+coverage). That makes the log a **replayable source of truth** for a client's dropped-intake
+backlog and a diagnostic for *which* upstream programs actually attempted intake:
+
+- **Rebuild the backlog** by replaying the stored `requestPayload`s, **deduped to one row per
+  contract** via a MySQL 8 window function keyed on
+  `JSON_UNQUOTE(JSON_EXTRACT(requestPayload,'$.number'))` (many failed attempts exist per contract
+  when a feed re-sends — see below).
+- **Determine which programs/vendors reached the API** with a split on
+  `JSON_UNQUOTE(JSON_EXTRACT(requestPayload,'$.vendor.number'))` — a vendor present in the failed
+  writes attempted intake; a vendor entirely absent never routed to api2 at all.
+
+This is both a **fallback recovery path** and a **scope diagnostic**. In the TRUE-80179 AIG
+incident it answered the scope question — the failed writes contained only vendor `STS_001` and
+**zero `SA_001`**, proving `SA_001` never reached api2 — while the *replay* itself was ultimately
+**not needed**, because AIG's scheduled feed re-sent the outstanding contracts and self-healed the
+backlog once intake succeeded. Keep the replay technique as the fallback for feeds that do **not**
+re-send.
+
+> **Never copy a logged row's values into a doc or a replay artifact you commit** — these rows
+> carry live Bearer tokens (in `requestHeaders`) and customer PII. Reference the row by location;
+> replay operationally, not by pasting payloads into the KB.
+
 ## Change history
 
+- 2026-07-29 — Documented (TRUE-80179) that the core/writer `Logs.Api` retains the **full original
+  `requestPayload`** on failed writes, making it a **replayable backlog source** and a scope
+  diagnostic: dedupe to one-per-contract with a window function on
+  `JSON_EXTRACT(requestPayload,'$.number')`, and split on `$.vendor.number` to see which programs
+  actually attempted intake. (mhammontree)
 - 2026-07-28 — Refined (TRUE-80179): a **failed write (non-2xx `POST`/`PUT`) lands in the core/writer
   `Logs`** on `api-writer.togahub.com` **even when the request is fully client-scoped** — not just
   pre-scope auth failures. `Logs_<Client>.Api` therefore shows reads + successful writes; failed

package/knowledge/2.0/apps/toga2-view/INDEX.md

@@ -3,6 +3,7 @@
 | Doc | Summary | Files |
 |-----|---------|-------|
 | [TOGa View Frontend (toga2-view) Architecture](architecture.md) | `toga2-view` is the **React/TypeScript single-page frontend** for the TOGa 2.0 platform — the customer-facing web app (home warranty / tech-support portals). | toga2-view/src/main.tsx, toga2-view/src/App.tsx, toga2-view/src/routes.tsx, toga2-view/src/api/axiosInstance.ts, toga2-view/src/api/apiFunctions.ts, toga2-view/src/utils/queryHelpers.ts, toga2-view/src/contexts/AuthContext.tsx, toga2-view/src/contexts/useUserStore.ts, toga2-view/src/hooks/useAuthenticationFlow.ts, toga2-view/vite.config.ts, toga2-view/package.json |
+| [Get Support — Subscription Details & Cancel Subscription Gating](features/get-support-cancel-subscription.md) | The Get Support page (`/get-support?itemUuid=…`) shows a **subscription details card** (plan · price · renewal date) for the service the user clicked, and — **o | toga2-view/src/pages/GetSupport/viewModels/getSupportPageViewModel.ts, toga2-view/src/pages/GetSupport/view/GetSupportPage.tsx, toga2-view/src/pages/GetSupport/viewModels/DUMMYFIELDS/SUPPORTDUMMYFIELDS.json, toga2-view/src/constants/featureFlags.ts, toga2-view/src/hooks/useBundleServices.ts |
 | [Mobile Nav Header](features/mobile-nav-header.md) | The `MobileNavToggle` component renders the fixed 72 px header (hamburger + Rate logo) and the slide-in drawer nav. | toga2-view/src/components/MobileNav/MobileNav.tsx, toga2-view/public/assets/Rate_Logo.svg |
 | [/v2 Query-String Builder (assembleOptions / where coercion)](features/query-string-builder.md) | `src/utils/queryHelpers.ts` converts a structured JS options object (`fields`, `where`, `join`/`ojoin`, `sort`, …) into the `api2` `/v2` query string. | toga2-view/src/utils/queryHelpers.ts, toga2-view/src/utils/queryHelpers.test.ts |
 | [Service Card Component](features/service-card.md) | The `ServiceCard` component renders a single service subscription (tech support or home warranty) on both the Home and Services pages. | toga2-view/src/components/ServiceCard/ServiceCard.tsx, toga2-view/src/pages/Services/view/ServicesPage.tsx, toga2-view/src/pages/Home/view/HomePage.tsx, toga2-view/src/constants/bundleConstants.ts, toga2-view/src/pages/Services/viewModels/DUMMYFIELDS/SERVICESDUMMYFIELDS.json |

package/knowledge/2.0/apps/toga2-view/features/get-support-cancel-subscription.md

@@ -0,0 +1,145 @@
+---
+title: "Get Support — Subscription Details & Cancel Subscription Gating"
+framework: "2.0"
+repo: toga2-view
+project: TOGa View Frontend
+client: shared
+type: feature
+status: active
+updated: 2026-07-28
+owners: ["tcox"]
+files:
+  - toga2-view/src/pages/GetSupport/viewModels/getSupportPageViewModel.ts
+  - toga2-view/src/pages/GetSupport/view/GetSupportPage.tsx
+  - toga2-view/src/pages/GetSupport/viewModels/DUMMYFIELDS/SUPPORTDUMMYFIELDS.json
+  - toga2-view/src/constants/featureFlags.ts
+  - toga2-view/src/hooks/useBundleServices.ts
+related:
+  - ../architecture.md
+  - ../../../../clients/rate/features/service-card-entitlements.md
+  - ../../../../clients/rate/profile.md
+---
+
+## Summary
+
+The Get Support page (`/get-support?itemUuid=…`) shows a **subscription details card**
+(plan · price · renewal date) for the service the user clicked, and — **only for tech-support
+services** — a **Cancel Subscription** button plus a confirmation modal. Whole Home (WH) warranty
+services and unclassified services get the subscription details card **without** any cancel path.
+
+Two things about this flow are easy to get wrong and are the reason it is documented:
+
+- The cancel affordance exists **only on this page** — `ServiceCard` has none.
+- **There is no backend cancellation endpoint yet.** The viewModel's `cancelSubscription()` is a
+  stub that always rejects, so confirming surfaces an error instead of faking success.
+
+## Key files / entry points
+
+- `pages/GetSupport/viewModels/getSupportPageViewModel.ts` — resolves `activeService`, builds the
+  `subscription` object, exposes `canCancelSubscription` and the `cancelSubscription()` stub
+- `pages/GetSupport/view/GetSupportPage.tsx` — the **only** place a cancel affordance is rendered;
+  computes `showCancelUi` and owns the confirm-modal state (`showCancelModal`, `cancelError`)
+- `constants/featureFlags.ts` — `CANCEL_SUBSCRIPTION_ENABLED` (currently `true`); flipping it to
+  `false` hides the whole cancel path in one place
+- `viewModels/DUMMYFIELDS/SUPPORTDUMMYFIELDS.json` — copy: `renewsPrefix`, `cancelNote`
+  ("You can cancel anytime. Coverage continues until the end of your current period."),
+  `confirm.*` (including `confirm.errorMessage`)
+- `hooks/useBundleServices.ts` — `detectServiceType()`, the classification the gate reuses
+
+## How it works
+
+1. **`activeService` resolution.** The viewModel picks the bundle service whose `uuid` matches the
+   URL's `itemUuid`, falls back to the first service with `isActive`, else `null`:
+   ```ts
+   const activeService =
+       bundleServices?.find((service) => service.uuid === itemUuid) ??
+       bundleServices?.find((service) => service.isActive) ??
+       null;
+   ```
+   The subscription card **and** the cancel gate both read this same `activeService`, so older links
+   without a resolvable `itemUuid` behave consistently across both.
+
+2. **Subscription details.** `subscription` = `{ plan, price, renewalDate, entitlementUuid }` from
+   `activeService`, else `null`. The card renders whenever `subscription` exists — **including for
+   warranty services**. Gating cancel does not hide the plan/price/renewal information.
+
+3. **The gate (positive, not negative).**
+   ```ts
+   const canCancelSubscription = activeService?.serviceType === "tech";
+   ```
+   `'warranty'` **and** `'other'` therefore both hide it — an unclassified service fails closed.
+   `serviceType` comes from `detectServiceType(bundleName || itemTitle)` in `useBundleServices`
+   (title-substring classification: contains "warranty"/"whole home" and not "tech" → `'warranty'`;
+   contains "tech"/"support" → `'tech'`; else `'other'`). This is the same signal that switches
+   `ServiceCard`'s second data row between **Price** (tech) and **Address** (warranty), so the cancel
+   gate and the service cards agree by construction.
+
+4. **The view gates three things with one boolean.**
+   ```ts
+   const showCancelUi = CANCEL_SUBSCRIPTION_ENABLED && canCancelSubscription;
+   ```
+   - the Cancel Subscription button
+   - the confirm modal (`showCancelUi && showCancelModal`)
+   - the `cancelNote` sentence appended to the `subscriptionDetails` string
+
+   The note is gated deliberately: leaving *"You can cancel anytime…"* on a card with no cancel
+   button is self-contradictory copy.
+
+5. **Confirm flow.** `handleConfirmCancel()` awaits `cancelSubscription()`; it closes the modal
+   **only** on a genuine resolve, and on rejection keeps the modal open and renders
+   `subscriptionFields.confirm.errorMessage`. Since the stub always throws, today's real-world
+   outcome is always the error state — intentional, so nothing reports a cancellation that did not
+   happen.
+
+## Decision — gate on `serviceType`, not on `isRateWarranty`
+
+The page already carries a separate warranty signal: `isRateWarranty = bundleUuid ===
+HOME_WARRANTY_BUNDLE_UUID`, used to route the **TICKETS** support method to the claims-style
+create-ticket link. It was deliberately **not** reused for the cancel gate:
+
+- `serviceType` is a *product classification*, so any service classified `'tech'` gets cancel —
+  it does not need a bundle uuid allowlist maintained per product.
+- It keeps this page consistent with the service cards, which already branch on `serviceType`.
+- A bundle-uuid check would silently fail open for any new warranty bundle uuid.
+
+**Why WH is excluded at all:** Whole Home warranty contracts (the AIG-backed warranty product) are
+not self-service cancellable from the portal; only tech-support subscriptions are.
+
+## Gotchas / known issues
+
+- **The cancel UI lives only on `GetSupportPage.tsx`.** `ServiceCard` has no cancel affordance —
+  do not go looking for one in `components/`, and do not add a second entry point without
+  reproducing the same `showCancelUi` gate.
+- **No backend endpoint exists.** `cancelSubscription()` throws
+  `"Subscription cancellation is not available yet."` by design (reject, never resolve). Swap the
+  body for the real API call when the endpoint ships; do not "fix" it by resolving.
+- **`detectServiceType` now has a second consumer with a policy consequence.** Widening its
+  `'tech'` keywords does not just change a card row any more — it **exposes the cancel button** for
+  whatever newly matches. Check both call sites before touching the classifier.
+- **The gate fails closed on `'other'`.** If a legitimately cancellable service stops matching
+  "tech"/"support" in its bundle/item title, its cancel button silently disappears. The title is the
+  only input.
+- **`cancelNote` is not standalone copy** — it is concatenated into `subscriptionDetails` and gated
+  by `showCancelUi`. Any new surface rendering that string must gate it the same way.
+- **`CANCEL_SUBSCRIPTION_ENABLED = false` hides button + modal + note but keeps the subscription
+  details card** — that is the intended kill-switch behavior.
+- **Never close the confirm modal on failure.** Closing it reads to the user as a successful
+  cancellation.
+
+## Client variations
+
+Rate is the consumer of this page today. Its product mix — Whole Home Warranty (AIG-backed) plus
+tech support — is what makes the gate load-bearing: both products appear as active services for the
+same user, so the page must distinguish them per service rather than per account. See
+[Rate profile](../../../../clients/rate/profile.md) and
+[Service Card Entitlement Display](../../../../clients/rate/features/service-card-entitlements.md).
+
+## Change history
+
+- 2026-07-28 — Cancel Subscription UI gated by service type: viewModel exposes
+  `canCancelSubscription` (`activeService?.serviceType === "tech"`), and the view's `showCancelUi`
+  now gates the button, the confirm modal, and the `cancelNote` sentence. WH warranty and
+  unclassified services keep the subscription details card with no cancel path. Also first capture of
+  the pre-existing flow: cancel exists only on `GetSupportPage`, is flagged by
+  `CANCEL_SUBSCRIPTION_ENABLED`, and `cancelSubscription()` is a stub that always rejects until the
+  backend endpoint ships. (tcox)

package/knowledge/INDEX.md

@@ -23,7 +23,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **dbchanges2** (Database Changes) _(framework core)_ — 3 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)
 - **toga2-supply** (TOGa Supply) — 3 doc(s) → [2.0/apps/toga2-supply/INDEX.md](2.0/apps/toga2-supply/INDEX.md)
 - **saml** (SAML SSO Gateway) — 3 doc(s) → [2.0/apps/saml/INDEX.md](2.0/apps/saml/INDEX.md)
-- **toga2-view** (TOGa View Frontend) — 6 doc(s) → [2.0/apps/toga2-view/INDEX.md](2.0/apps/toga2-view/INDEX.md)
+- **toga2-view** (TOGa View Frontend) — 7 doc(s) → [2.0/apps/toga2-view/INDEX.md](2.0/apps/toga2-view/INDEX.md)
 - **toga2-hub** (TOGa Hub) — 2 doc(s) → [2.0/apps/toga2-hub/INDEX.md](2.0/apps/toga2-hub/INDEX.md)
 - **talos** (TOGa IQ) — 7 doc(s) → [2.0/apps/talos/INDEX.md](2.0/apps/talos/INDEX.md)
 - **voice-to-voice** (TOGa Voice) — 4 doc(s) → [2.0/apps/voice-to-voice/INDEX.md](2.0/apps/voice-to-voice/INDEX.md)

package/knowledge/clients/aig/INDEX.md

@@ -2,6 +2,6 @@
 
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
-| [AIG Contract Reconciliation & Dealer Programs (STS_001 / SA_001)](features/contract-reconciliation.md) | 2.0 | How to reconcile an **AIG contract sales sheet** against the `Client_Aig` tenant, and the durable finding that the **Staples Advantage.com (`SA_001`) program is | _underscore/Model/Client/Entitlement.php, _underscore/Model/Aig/Entitlement.php, _underscore/Model/Client/Contact.php, _underscore/Model/Aig/Contact.php |
+| [AIG Contract Reconciliation & Dealer Programs (STS_001 / SA_001)](features/contract-reconciliation.md) | 2.0 | How to reconcile an **AIG contract sales sheet** against the `Client_Aig` tenant, and the durable finding that the **Staples Advantage.com (`SA_001`) program do | _underscore/Model/Client/Entitlement.php, _underscore/Model/Aig/Entitlement.php, _underscore/Model/Client/Contact.php, _underscore/Model/Aig/Contact.php |
 | [AIG Entitlement Intake & SaleItem Code Resolution](features/entitlement-intake.md) | 2.0 | The `_Model_Aig_Entitlement::prePost` interceptor below is the code path for AIG protection-plan entitlements arriving as `api2` V2 JSON POSTs — and that path * | _underscore/Model/Aig/Entitlement.php, dbchanges2/Client_Aig/2026-06-18a - TRUE-79534 AIG SaleItem codes.sql |
 | [AIG (Staples Protection Plan)](profile.md) | 2.0 | AIG is the warranty underwriter behind the **Staples Protection Plan** retail program. |  |

package/knowledge/clients/aig/features/contract-reconciliation.md

@@ -5,7 +5,7 @@ project: API
 client: aig
 type: client-feature
 status: active
-updated: 2026-07-28
+updated: 2026-07-29
 owners: ["mhammontree"]
 files:
   - _underscore/Model/Client/Entitlement.php
@@ -20,17 +20,18 @@ related:
 ## Summary
 
 How to reconcile an **AIG contract sales sheet** against the `Client_Aig` tenant, and the
-durable finding that the **Staples Advantage.com (`SA_001`) program is entirely absent from
-`Client_Aig`** (TRUE-80179). AIG runs **two dealer programs under the one `Client_Aig`
-tenant**, distinguished by `DealerId` in AIG's own data:
+durable finding that the **Staples Advantage.com (`SA_001`) program does not route into
+`Client_Aig` via api2 at all** (TRUE-80179). AIG runs **two dealer programs under the one
+`Client_Aig` tenant**, distinguished by `DealerId` in AIG's own data:
 
-| DealerId | Program |
-|---|---|
-| `STS_001` | **Staples Technology Solutions** |
-| `SA_001` | **Staples Advantage.com** |
+| DealerId | Program | Status |
+|---|---|---|
+| `STS_001` | **Staples Technology Solutions** | live api2 feed; intake gap **RESOLVED 2026-07-29** (self-healed) |
+| `SA_001` | **Staples Advantage.com** | **never reaches api2** — separate feed; scope decision is the one open item |
 
-`STS_001` arrives as a **live API feed** (and had a large gap from a now-fixed intake bug — see
-below); `SA_001` was never ingested at all (open scope question).
+`STS_001` arrives as a **live API feed**; its 156-contract gap from the now-fixed intake bug
+**self-healed** (the feed re-sent and all 156 succeeded — see below). `SA_001` never reaches our
+API at all — a confirmed fact, not a missing-intake bug (see the `SA_001` section).
 
 ## Match keys (sales sheet → `Client_Aig`)
 
@@ -70,41 +71,62 @@ and dropping every contract that used an `ASI-*` code. Cause: the TRUE-79534 `AS
 query threw MySQL ERROR 1064 → 500. Full chain in
 [entitlement-intake → Root cause of the 500s](entitlement-intake.md#root-cause-of-the-intake-500s-true-79534-catalog-never-deployed).
 
-**Fix status (2026-07-28):** the catalog (~2,200 codes) is now loaded on prod, so **new** `STS_001`
-POSTs succeed. **Still open — do NOT mark resolved:**
-- **(a) Back-fill of already-dropped contracts.** Contracts that 500'd are **not** created
-  retroactively — back-fill needs **AIG to re-send** them, or a **manual/`dbchanges2` load**.
-  Quantify the exact set by re-running this reconciliation against a **fresh prod copy**.
-- **(b) Unguarded empty-`$itemId` in `prePost`** — a still-missing code will 500 again (ERROR 1064)
-  instead of returning a clean "Missing AIG item ID." Latent until guarded.
-- **(c) Deploy process gap** — investigate *why* the migration SQL step was skipped in the deploy,
-  so future `dbchanges2` changes aren't silently missed.
+**RESOLVED 2026-07-29 — the 156 self-healed.** After the catalog (~2,200 codes) loaded on prod, AIG's
+**next scheduled batch re-sent all 156 outstanding `STS_001` contracts and every one succeeded**
+(`POST /v2/entitlements` = 201 × 156, zero failures; `Client_Aig.Entitlements` gained exactly 156
+rows). **No manual back-fill was needed** — the feed re-sends OUTSTANDING contracts every run, so
+the backlog cleared itself once intake worked (see
+[entitlement-intake → scheduled re-send batch](entitlement-intake.md#feed-is-a-scheduled-re-send-batch-not-one-shot--self-healing)).
+The `STS_001` intake failure mode is **RESOLVED in prod.**
+
+**Still open (tickets, not doc work):**
+- **(a) Unguarded empty-`$itemId` in `prePost`** — a still-missing sale-item code will 500 again
+  (ERROR 1064) instead of returning a clean "Missing AIG item ID." Latent until guarded.
+- **(b) Deploy process gap** — investigate *why* the TRUE-79534 migration SQL step was skipped in
+  the deploy, so future `dbchanges2` changes aren't silently missed.
 
-### 545 `SA_001` missing — still an open scope question
+### 545 `SA_001` missing — confirmed out-of-pipeline (separate feed)
 
 The entire `SA_001` (Staples Advantage.com) feed is **absent from `Client_Aig`** — confirmed
 absent from **all** local tenant DBs, not just this one — and is a **separate** matter from the
 `STS_001` catalog bug above.
 
+**CONFIRMED (2026-07-29): `SA_001` never reaches our API at all.** The failed-POST logs and the
+vendor split (on `$.vendor.number`) show **only `STS_001`** (100 unique failed contracts) and
+**zero `SA_001`** across **all** response codes. So the 545 `SA_001` contracts (506 active) are a
+**genuinely separate feed that does not route into `Client_Aig` via api2** — this is **not** a
+missing-intake bug on our side. The long-open scope question is now a **decided fact**: `SA_001` is
+out-of-pipeline. Do **not** re-investigate whether it is a missing-intake defect.
+
 **Real support failure that surfaced it:** a customer (client contract `7679463206-2`, AIG
 contract `1000046237903`, an **active 2YR Printer** plan) called in and could not be found,
 because their `SA_001` contract was never ingested.
 
-**Open scope question (still unresolved):** is `SA_001` *supposed* to route into `Client_Aig` at
-all, or is it a separate program with its own destination? This needs an answer from AIG / the
-team before back-filling — do not assume the gap is simply a missed load.
+**The one remaining open item (a ticket/business decision, not a bug):** *should* `SA_001` flow
+into `Client_Aig`, and if so via what feed/integration? That is a scope/integration decision for
+AIG / the team — not a back-fill of a dropped load. Until decided, `SA_001` stays out-of-pipeline.
 
 ## How to load a missing program / sheet (back-fill)
 
-If `SA_001` (or a back-fill of dropped `STS_001` contracts) is confirmed in-scope for
-`Client_Aig` and AIG cannot re-send via the API, it can be loaded the same way the SaleItem
-catalog is — a `dbchanges2/Client_Aig/` migration with a session-scoped temp table + anti-join
+If `SA_001` is ever confirmed in-scope for `Client_Aig` and AIG cannot route it through api2, it
+can be loaded the same way the SaleItem catalog is — a `dbchanges2/Client_Aig/` migration with a
+session-scoped temp table + anti-join
 (see [entitlement-intake.md → Uploading new codes](entitlement-intake.md#uploading-new-codes-the-recurring-task);
-**pin the temp column's collation** to avoid the prod-only ERROR 1267). Preferred, though, is
-letting AIG **re-send** the contracts through the now-working live feed.
+**pin the temp column's collation** to avoid the prod-only ERROR 1267). Note the `STS_001` backlog
+did **not** need this — a scheduled re-send self-healed it once intake worked, so prefer letting a
+feed re-send over a manual load whenever the contracts do reach api2.
 
 ## Change history
 
+- 2026-07-29 — TRUE-80179 / TRUE-79534: **156 active `STS_001` RESOLVED (self-healed).** The next
+  scheduled batch re-sent all 156 outstanding contracts and every one succeeded (201 × 156, zero
+  failures; `Client_Aig.Entitlements` +156) — no manual back-fill needed, because the feed re-sends
+  outstanding contracts every run. Also **confirmed `SA_001` never reaches api2**: the failed-POST
+  logs / vendor split show only `STS_001` (100 unique failed) and zero `SA_001` across all codes, so
+  the 545 `SA_001` (506 active) are a genuinely separate out-of-pipeline feed — converting the old
+  scope question into a decided fact (not a missing-intake bug). Remaining open items are tickets:
+  the `SA_001` scope/integration decision, the unguarded `prePost` lookup, and the skipped-migration
+  deploy gap. (mhammontree)
 - 2026-07-28 — TRUE-80179 / TRUE-79534: root-caused the **156 missing active `STS_001`**. These are
   a **live API feed** whose writes were 500'ing (ERROR 1064) and being dropped because the
   TRUE-79534 `ASI-*`/`SM-*` catalog never deployed to prod `Client_Aig.Items` — corrects the earlier

package/knowledge/clients/aig/features/entitlement-intake.md

@@ -5,7 +5,7 @@ project: API
 client: aig
 type: client-feature
 status: active
-updated: 2026-07-28
+updated: 2026-07-29
 owners: ["mhammontree"]
 files:
   - _underscore/Model/Aig/Entitlement.php
@@ -25,13 +25,17 @@ The `_Model_Aig_Entitlement::prePost` interceptor below is the code path for AIG
 protection-plan entitlements arriving as `api2` V2 JSON POSTs — and that path **is a live
 production feed.** AIG posts real customer contracts to `POST /v2/entitlements` on
 `api-writer.togahub.com` (authenticated as client `Aig`, vendor `STS_001`) using the current
-`ASI-*` / `SM-*` sale-item codes. Until 2026-07-28 that feed was **silently failing with HTTP
-500** because `Client_Aig.Items` was missing the entire `ASI-*`/`SM-*` catalog (the TRUE-79534
-load never ran on prod), so every posted contract was dropped at intake (see
-[Intake is a live API feed](#intake-is-a-live-api-feed-and-was-silently-failing-true-80179--true-79534)
-and [Root cause of the 500s](#root-cause-of-the-intake-500s-true-79534-catalog-never-deployed),
-TRUE-80179 / TRUE-79534). The historical **430** `Client_Aig` entitlements were a one-time
-Sept-2025 bulk load — **that part stands** — but AIG has since switched to the live API feed.
+`ASI-*` / `SM-*` sale-item codes. From before 2026-07-28 until the catalog was loaded, that feed
+was **silently failing with HTTP 500** because `Client_Aig.Items` was missing the entire
+`ASI-*`/`SM-*` catalog (the TRUE-79534 load never ran on prod), so every posted contract was
+dropped at intake. **RESOLVED 2026-07-29** — once the catalog loaded, AIG's next scheduled batch
+delivered all **156** outstanding `STS_001` contracts and **every one succeeded** (`POST
+/v2/entitlements` = **201 × 156**, zero failures; `Client_Aig.Entitlements` gained exactly 156
+rows). **No manual back-fill was needed — the feed self-healed** (see
+[Intake is a live API feed](#intake-is-a-live-api-feed-resolved-2026-07-29-true-80179--true-79534)
+and [Feed is a scheduled re-send batch](#feed-is-a-scheduled-re-send-batch-not-one-shot--self-healing)).
+The historical **430** `Client_Aig` entitlements were a one-time Sept-2025 bulk load — **that part
+stands** — but AIG has since switched to the live API feed.
 
 On a V2 POST, before the entitlement is written, `prePost` resolves the **sold warranty SKU**
 (`saleItem.partNumber`) against `Client_Aig.Items` to set the `Entitlement.saleItemId` foreign
@@ -40,7 +44,7 @@ the lookup returns an **empty `$itemId`**, the downstream fulfillment query inte
 empty value, and it dies with MySQL **ERROR 1064** → **HTTP 500** (see the gotcha). Keeping
 `Client_Aig.Items` populated with AIG's current sale-item catalog is what keeps the feed working.
 
-## Intake is a live API feed (and was silently failing) (TRUE-80179 / TRUE-79534)
+## Intake is a live API feed (RESOLVED 2026-07-29) (TRUE-80179 / TRUE-79534)
 
 The API-intake path in *How it works* is the **real, live feed.** An earlier capture wrongly
 concluded "no live feed — periodic bulk load only." That conclusion came from auditing
@@ -65,10 +69,34 @@ What the corrected audit found (TRUE-80179):
   contracts in [reconciliation](contract-reconciliation.md), and it kept losing contracts **daily**
   until the catalog was loaded on 2026-07-28.
 
+**Resolution (2026-07-29):** once the catalog was loaded (TRUE-79534) and the temp-table collation
+fixed, AIG's **next scheduled batch cleared the entire backlog in one pass** — `Logs_Aig` shows
+`POST /v2/entitlements` = **201 × 156** on 2026-07-29 with **zero failures** in the core/writer
+`Logs`, and `Client_Aig.Entitlements` gained exactly the **156** previously-missing active
+`STS_001` rows. **No manual log-replay was needed.** The prior "intake 500s / Missing AIG item ID"
+failure mode is **RESOLVED in prod for the STS_001 side**, which is now healthy and self-maintaining
+(see next section for *why* it self-healed).
+
 **Practical takeaway:** AIG intake is a **live API feed whose health must be monitored** — not a
 manual bulk load, and not a phantom "no feed." When auditing it, check the **core/writer `Logs`**
 for non-2xx writes, not just `Logs_Aig`. For reconciling a sales sheet against the tenant (and the
-still-open `SA_001` program gap), see [AIG contract reconciliation](contract-reconciliation.md).
+one remaining `SA_001` scope decision), see [AIG contract reconciliation](contract-reconciliation.md).
+
+## Feed is a scheduled re-send batch (not one-shot) → self-healing
+
+**Correction of an interim read.** AIG's entitlement feed is a **scheduled batch that re-sends
+OUTSTANDING / unacknowledged contracts every run** — it is **not** one-shot-per-contract, and it
+does **not** "not retry." Supersedes any earlier note implying the feed does not retry.
+
+Evidence: the same ~156 contracts were **re-POSTed on every run** and 500'd on the missing catalog —
+that is what produced **~110,504 failed attempts for only ~100 distinct contract numbers** in the
+logs. The moment the catalog resolved, the **very next scheduled run cleared all 156 in a single
+pass** (156 × 201).
+
+**Operational consequence:** a persistent intake bug is **silently retried, not dropped**, until it
+is fixed — so a catalog/intake fix **auto-recovers the whole backlog on the next scheduled run**
+with no manual back-fill. This is the key operational fact for the next incident: fix the intake
+cause and let the feed re-send.
 
 ## Root cause of the intake 500s (TRUE-79534 catalog never deployed)
 
@@ -86,10 +114,12 @@ The full failure chain behind the HTTP 500s:
    ongoing daily, until the catalog was loaded (2026-07-28).
 
 The empty-`$itemId` is **unguarded** (see the gotcha): a missing code should fail cleanly with
-"Missing AIG item ID," not a raw SQL syntax error. This defect is now **confirmed firing in prod**,
-not theoretical. Loading the catalog fixes intake **going forward**; contracts already dropped are
-**not** retroactively created — back-fill is tracked in
-[contract reconciliation](contract-reconciliation.md).
+"Missing AIG item ID," not a raw SQL syntax error. This defect was **confirmed firing in prod**,
+not theoretical, and the **unguarded lookup remains open** (a future missing code will 500 again).
+Loading the catalog fixed intake, and because the feed re-sends outstanding contracts (see
+[scheduled re-send batch](#feed-is-a-scheduled-re-send-batch-not-one-shot--self-healing)), the
+**backlog of dropped contracts self-healed on the next scheduled run** — no manual back-fill was
+needed (see [contract reconciliation](contract-reconciliation.md)).
 
 ## Key files / entry points
 
@@ -245,6 +275,16 @@ this interceptor or use this dual-purpose Items pattern.
 
 ## Change history
 
+- 2026-07-29 — TRUE-80179 / TRUE-79534 (**RESOLVED + correction**): the `STS_001` intake gap is
+  **closed and it self-healed.** After the catalog load + collation fix shipped, AIG's next
+  scheduled batch delivered all **156** outstanding `STS_001` contracts and every one succeeded
+  (`POST /v2/entitlements` = 201 × 156 on 2026-07-29, zero failures; `Client_Aig.Entitlements`
+  +156 rows). **No manual replay needed.** Also corrected the feed model: it is a **scheduled batch
+  that re-sends OUTSTANDING/unacknowledged contracts every run** (the ~156 re-POSTs on the missing
+  catalog produced ~110,504 failed attempts for only ~100 distinct contracts), so a persistent
+  intake bug is silently retried until fixed and then **auto-recovers on the next run** — supersedes
+  any earlier "no retry" implication. The unguarded empty-`$itemId` lookup and the skipped-migration
+  deploy gap remain open. (mhammontree)
 - 2026-07-28 — TRUE-80179 / TRUE-79534 (**CORRECTION — supersedes the entry below**): AIG intake
   **is** a live production API feed, and it was **silently failing with HTTP 500.** The earlier
   same-day "no live feed / bulk load only" conclusion was **wrong** — it audited `Logs_Aig` alone,

package/knowledge/clients/rate/features/service-card-entitlements.md

@@ -6,7 +6,7 @@ project: TOGa View Frontend
 client: rate
 type: client-feature
 status: active
-updated: 2026-07-27
+updated: 2026-07-28
 owners: ["bala", "tcox", "mhammontree"]
 files:
   - src/components/ServiceCard/ServiceCard.tsx
@@ -24,6 +24,7 @@ files:
 related:
   - clients/rate/profile.md
   - whole-home-warranty-purchase-guard.md
+  - 2.0/apps/toga2-view/features/get-support-cancel-subscription.md
 ---
 
 ## Summary
@@ -101,6 +102,11 @@ This feature is Rate-specific. The warranty card showing Address instead of Pric
 by Rate's product mix (Whole Home Warranty + Tech Support). Other clients with different
 product types would need `detectServiceType` extended or overridden.
 
+**`detectServiceType` is no longer display-only.** As of 2026-07-28 it also gates the
+**Cancel Subscription** UI on the Get Support page (`serviceType === 'tech'` — WH warranty and
+unclassified services get no cancel path). See
+[Get Support — Subscription Details & Cancel Subscription Gating](../../../2.0/apps/toga2-view/features/get-support-cancel-subscription.md).
+
 ## Gotchas / known issues
 
 - **`ojoin` is required for address** — using INNER JOIN (`join`) drops every entitlement
@@ -115,6 +121,10 @@ product types would need `detectServiceType` extended or overridden.
   `AddSubscriptionSheet`) replaces the old "Get Started" inactive bundle cards.
 - **`useBundleServices` is shared** — both `useHomePageViewModel` and `useServicePageViewModel`
   call it. Changes to the hook affect both pages.
+- **Widening `detectServiceType`'s `'tech'` keywords now changes entitlement *permissions*, not just
+  a card row.** The Get Support page gates its Cancel Subscription button on
+  `serviceType === 'tech'`, so anything newly classified as tech becomes self-service cancellable.
+  Review both consumers (`ServiceCard` row 2 and the cancel gate) before editing the classifier.
 - **Show the entitlement's OWN pin only — never the contact's shared address.** The removed
   `contact.primaryContactAddress` fallback made every unpinned card display the same (latest)
   address because that field is one shared, purchase-overwritten value per contact. An unpinned
@@ -137,6 +147,9 @@ product types would need `detectServiceType` extended or overridden.
 
 ## Change history
 
+- 2026-07-28 — `detectServiceType` gained a second, non-display consumer: the Get Support page gates
+  its Cancel Subscription UI on `serviceType === 'tech'`, so the classifier now decides which
+  entitlements are self-service cancellable. (tcox)
 - 2026-07-27 — TRUE-79533: recorded that `fetchAddressesByIds`
   (`GET /v2/addresses?fields=id,line1,...`) returned **403 `EZ-2`** because the **`Addresses.id`
   field** had no read ACL grant in `Client_Rate` — the numeric `id` is ACL-gated like any field. Fixed

package/package.json

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