toga-ai 1.0.131 → 1.0.133

package/knowledge/INDEX.md

@@ -5,7 +5,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 ## 1.0 framework
 
 - **library** (Library) _(framework core)_ — 4 doc(s) → [1.0/apps/library/INDEX.md](1.0/apps/library/INDEX.md)
-- **worker** (Worker) — 9 doc(s) → [1.0/apps/worker/INDEX.md](1.0/apps/worker/INDEX.md)
+- **worker** (Worker) — 10 doc(s) → [1.0/apps/worker/INDEX.md](1.0/apps/worker/INDEX.md)
 - **togadesk** (TOGa Desk) — 7 doc(s) → [1.0/apps/togadesk/INDEX.md](1.0/apps/togadesk/INDEX.md)
 - **togaview** (TOGa View) — 6 doc(s) → [1.0/apps/togaview/INDEX.md](1.0/apps/togaview/INDEX.md)
 - **webhook** (Webhook) — 1 doc(s) → [1.0/apps/webhook/INDEX.md](1.0/apps/webhook/INDEX.md)

package/knowledge/clients/compass-usa/INDEX.md

@@ -2,7 +2,7 @@
 
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
-| [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) | 2.0 | For Compass USA, posting an AdvanceShippingNotice (ASN) auto-creates the ItemFulfillment (IF) on the upstream SalesOrder. | _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Model/Compass/PurchaseOrder.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client_Compass/2026-06-11 - AsnItemTrackingNumberAcl.sql, dbchanges2/Client_Compass/2026-06-15b - BackfillSA132781ItemFulfillmentTracking.sql, dbchanges2/Client_Compass/2026-06-16 - CleanupSA132763CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql, dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql |
+| [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) | 2.0 | For Compass USA, posting an AdvanceShippingNotice (ASN) auto-creates the ItemFulfillment (IF) on the upstream SalesOrder. | _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Model/Compass/PurchaseOrder.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client_Compass/2026-06-11 - AsnItemTrackingNumberAcl.sql, dbchanges2/Client_Compass/2026-06-15b - BackfillSA132781ItemFulfillmentTracking.sql, dbchanges2/Client_Compass/2026-06-16 - CleanupSA132763CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql, dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql, dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql |
 | [Compass: Item-Fulfillment TableViews (for-sales-order-items & for-sales-orders, tracking via bridge)](features/item-fulfillment-tracking-tableview.md) | 2.0 | Two sibling Compass TableViews in `Client_Compass` display fulfilled items in toga2-supply, both driven by `TableViews` / `TableViewJoins` / `TableViewFields` c | dbchanges2/Client_Compass/2026-06-10 - ItemFulfillmentsForSalesOrderItemsTableView.sql, dbchanges2/Client_Compass/2026-06-11 - ItemFulfillmentsForSalesOrdersTableView.sql, dbchanges2/Client_Compass/2026-06-15a - FixItemFulfillmentTrackingNumberJoins.sql |
 | [Compass MITS PO → SO Item Linking](features/mits-po-to-so-item-linking.md) | 2.0 | MITS sends Compass inbound Purchase Orders (`POST /v2/purchase-orders`) against a Sales Order (`mitsSalesOrder`). | _underscore/Model/Compass/PurchaseOrder.php, worker/crons/toga2/compass/workflow/3a_import_office_depot_purchase_orders.php |
 | [Compass USA](profile.md) | 2.0 | Compass USA is a TOGA client running a multi-tier supply-chain commerce operation. |  |

package/knowledge/clients/compass-usa/features/asn-to-item-fulfillment.md

@@ -17,6 +17,7 @@ files:
   - dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql
   - dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql
   - dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql
+  - dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql
 related:
   - ../../../2.0/apps/_underscore/features/recursive-item-fulfillments.md
 ---
@@ -204,7 +205,9 @@ Dated one-liners, newest first.
   (`itemFulfillmentItemHasTracking()`), stopping duplicate/different tracking numbers from
   vendor ASN re-transmissions piling onto fully-fulfilled lines (qty-1 SA132898 / USB31CC1 had
   2). Distinct root cause from the 2026-06-16 cross-line contamination. SA132898 repaired by
-  `2026-06-18a` (cleanup-only; original tracking already correct). (jcardinal)
+  `2026-06-18a` and SA132881 (960-001075, same pattern) by `2026-06-18b` — both cleanup-only,
+  original tracking already correct. Two such orders surfaced the same day, so more duplicates
+  likely remain; a detection sweep (IFI item-level tracking count > fulfilled qty) is advisable. (jcardinal)
 - 2026-06-16 — Identified cross-line tracking contamination root cause: bad
   `SalesOrderItems_PurchaseOrderItems` rows (PO-local lineNumber collision in
   `_Model_Compass_PurchaseOrder`, fixed forward 2026-06-11 `ec935478`; and the worker ODP-PO

package/knowledge/clients/prudential/INDEX.md

@@ -4,5 +4,6 @@
 |-----|-----------|---------|-------|
 | [Prudential: Dell ASN units PRE/POST interceptor (legacy key + flat tracking)](features/dell-asn-units-interceptor.md) | 2.0 | After the tracking-number bridge migration, the ASN unit route was renamed (`advance-shipping-notice-units` → `advance-shipping-notice-item-units`), so the inhe | _underscore/Model/Prudential/AdvanceShippingNotice.php, dbchanges2/Client_Prudential/2026-06-10 - AsnUnitsInterceptor.sql |
 | [Prudential: Service Request Regional Address Validation](features/service-request-address-validation.md) | 2.0 | The `prePost` interceptor on `_Model_Prudential_ServiceRequest` validates `deliverToAddress` fields differently depending on which Prudential regional customer | _underscore/Model/Prudential/ServiceRequest.php |
+| [Prudential Order Shipped Email — transmit_ordershipped_updates_prudential.php](features/transmit-ordershipped-email.md) | 1.0 | Cron script that transmits "Order Shipped" updates to ServiceNow (RITM) and sends a shipped notification email to the end user. | worker/crons/toga2/prudential/transmit_ordershipped_updates_prudential.php |
 | [Prudential Financial](profile.md) | 2.0 | Prudential is a TOGA client whose device-fulfillment flow is driven by **Dell** via the Dell API (`Client_Prudential.Apis.id = 2`). |  |
 | [Prudential: Dell ASN failed POST backfill replay](workflows/dell-asn-backfill-replay.md) | 2.0 | When Dell ASN POSTs fail in bulk (e.g. |  |

package/knowledge/clients/prudential/features/transmit-ordershipped-email.md

@@ -0,0 +1,86 @@
+---
+title: Prudential Order Shipped Email — transmit_ordershipped_updates_prudential.php
+framework: "1.0"
+repo: worker
+project: Worker
+client: prudential
+type: client-feature
+status: active
+updated: 2026-06-18
+owners: ["rgirish"]
+files:
+  - worker/crons/toga2/prudential/transmit_ordershipped_updates_prudential.php
+related:
+  - ../profile.md
+---
+
+## Summary
+Cron script that transmits "Order Shipped" updates to ServiceNow (RITM) and sends a
+shipped notification email to the end user. Runs on the `notification` worker role.
+Stamps two fields on `PurchaseOrders` to track progress: `c_dtTransmittedOrderShippedUpdateToPrudential`
+and `c_dtEmailSentOrderShipped`.
+
+## How it works
+
+**Phase 1 — Transmit to ServiceNow:**
+Selects all Dell POs that have at least one ASN and have not yet been transmitted
+(`c_dtTransmittedOrderShippedUpdateToPrudential IS NULL`). For each:
+1. Calls Prudential SNOW API (`PUT /gbts/v1/sn_pcaas/ritm`) to update RITM state to "Order Shipped".
+2. Allocates units to the contact, updates asset state to "In Transit" in SNOW CMDB.
+3. Stamps `c_dtTransmittedOrderShippedUpdateToPrudential = NOW()` on the PO immediately.
+
+**Phase 2 — Send shipped email:**
+Iterates the same POs collected in Phase 1. For each:
+1. Fetches PO details via TOGa API (`GET /purchase-orders/<uuid>`).
+2. Fetches tracking number via TOGa API (`GET /tracking-numbers`).
+3. Builds and sends the shipped email based on `serviceRequestType`:
+   - **New** — "Your new hire equipment has shipped" with 3 PDF attachments (Win11 guide, return instructions, Mac setup guide).
+   - **Breakfix / Refresh** — "Your equipment has been shipped" with 2 PDF attachments (Win11 + Mac setup guide), skipped for Reclaim.
+   - **Reclaim** — "Your equipment has been shipped" with no PDF attachments.
+4. Stamps `c_dtEmailSentOrderShipped = NOW()` on the PO.
+
+## Data model
+- `Client_Prudential.PurchaseOrders.c_dtTransmittedOrderShippedUpdateToPrudential` — stamped after SNOW transmission
+- `Client_Prudential.PurchaseOrders.c_dtEmailSentOrderShipped` — stamped after email send
+- Both fields are checked by `prudential_exception_report.php` to detect discrepancies
+
+## Exception report link
+`worker/crons/notifications/reports/prudential_exception_report.php` flags any PO where
+`c_dtTransmittedOrderShippedUpdateToPrudential IS NOT NULL` AND `c_dtEmailSentOrderShipped IS NULL`
+as "Order Shipped Email Not Sent". This appears daily in the Prudential REQ Processing Report email.
+
+## Gotchas / known issues
+
+**PDF fetch crash kills entire batch (fixed 2026-06-18):**
+The New-type branch fetches 3 PDFs from S3 via `file_get_contents()`. If any S3 URL returns
+a non-200 (e.g. 403 Forbidden), PHP emits a warning which `App_Error::handleError` converts
+to an `ErrorException` — crashing the script mid-loop. Phase 1 has already stamped
+`c_dtTransmittedOrderShippedUpdateToPrudential` for all POs in the batch, but Phase 2 dies
+before writing `c_dtEmailSentOrderShipped` for any remaining POs.
+
+Fix applied: added `!== false` guard around all three `file_get_contents` calls in the
+New branch (matching the guard the non-New branch already had). If any PDF fetch fails,
+the email sends without attachments rather than crashing.
+
+**Wrong Mac PDF URL (fixed 2026-06-18):**
+The New branch was pointing to `PrudentialMacSetupGuide_15.6_v4.pdf` (403 since ~May 5 2026)
+instead of `PrudentialMacSetupGuide.pdf` (the working URL used by the non-New branch).
+
+**Re-queueing stuck POs:**
+If `c_dtEmailSentOrderShipped` is NULL but `c_dtTransmittedOrderShippedUpdateToPrudential`
+is set, the script will never re-process those POs automatically. To re-trigger:
+```sql
+UPDATE PurchaseOrders
+SET c_dtTransmittedOrderShippedUpdateToPrudential = NULL
+WHERE number IN ('P124878', ...);
+```
+Then trigger the cron manually. Do NOT null out `c_dtEmailSentOrderShipped` on already-sent
+POs or users will receive duplicate emails.
+
+**Single-PO vs batch behavior:**
+When only one New-type PO is in the queue, a crash in Phase 2 on that PO still fires the
+stamp (crash hits the next iteration). With multiple New-type POs, a crash on PO #1 kills
+all subsequent POs in the same run.
+
+## Change history
+- 2026-06-18 — Fixed 403 crash: corrected Mac PDF URL (`_15.6_v4` → `PrudentialMacSetupGuide.pdf`) and added `false` guard on all S3 fetches in New branch (rgirish)

package/knowledge/clients/prudential/profile.md

@@ -9,7 +9,7 @@ project: _Underscore
 client: prudential
 type: profile
 status: active
-updated: 2026-06-16
+updated: 2026-06-18
 owners: ["jcardinal", "rgirish"]
 files: []
 related:
@@ -38,7 +38,12 @@ order-status transmissions.
   PRE/POST translation that keeps their feed working after the tracking-number bridge migration.
 - Service request region is resolved from `Customers.name` string (`'USA'`/`'India'`/`'Ireland'`).
   Renaming those customer records in the DB would silently break regional validation routing.
+- `transmit_ordershipped_updates_prudential.php` runs in two phases. Phase 1 stamps
+  `c_dtTransmittedOrderShippedUpdateToPrudential` immediately; Phase 2 sends the email and stamps
+  `c_dtEmailSentOrderShipped`. Any exception in Phase 2 leaves `c_dtEmailSentOrderShipped` NULL
+  and the PO is never re-processed automatically. See the exception report and the transmit-ordershipped-email feature doc.
 
 ## Related docs
 - Dell ASN units interceptor.
 - 2.0 _underscore: Tracking-Number Bridge Migration.
+- features/transmit-ordershipped-email.md

package/package.json

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