toga-ai 1.0.562 → 1.0.564

package/knowledge/1.0/apps/library/INDEX.md

@@ -16,6 +16,5 @@
 | [NetSuite SuiteQL/REST API Reference](features/netsuite-suiteql-api-reference.md) | General working reference for the Agilant NetSuite integration: how to authenticate, how SuiteQL behaves, and the confirmed schema of the tables/columns/codes w | library/app/api/netsuite/rest.php, library/ssl/netsuite_ec_key.pem, test/@dave/Junk Drawer/nsq.php |
 | [NetSuite SuiteQL/REST Shim — Field Semantics](features/netsuite-suiteql-rest-shim.md) | `App_Api_Netsuite_Rest` is the REST/SuiteQL replacement for the deprecated NetSuite SOAP toolkit. | library/app/api/netsuite/rest.php |
 | [NetSuite Sync Alert Monitor (App_SystemMonitor_NetSuiteIntegration)](features/netsuite-sync-alert-monitor.md) | `App_SystemMonitor_NetSuiteIntegration` (`library/app/systemmonitor/netsuiteintegration.php`, title **"NetSuite Sync Alert"**) is a 1.0 system monitor that watc | library/app/systemmonitor/netsuiteintegration.php, worker/crons/infrastructure/system_monitors.php |
-| [App_Api_ServiceRequest — provisioning a TOGa 2.0 Service Request from 1.0](features/service-request-toga2-provisioning.md) | `App_Api_ServiceRequest` (`library/app/api/servicerequest.php`) is the shared 1.0-side class that turns a posted form into a **TOGa 2.0 Service Request** — it v | library/app/api/servicerequest.php, library/app/api/toga2.php, togadesk/desk/includes/classes/class.ticket.php |
 | [Startech PC Matic B2B Sync (library)](features/startech-pcmaticb2b-sync.md) | `library/app/api/toga2.php` handles bidirectional ticket sync for PC Matic B2B between TOGaDesk 1.0 and TOGA 2.0. | library/app/api/toga2.php, library/app/api/startechticket.php, worker/crons/toga2/startech/common_import_supporting_records.php |
 | [App_Api_Toga2 — TOGa2 API Client & 1.0↔2.0 Sync Bridge](features/toga2-api-client-and-bridge.md) | `App_Api_Toga2` (`library/app/api/toga2.php`, ~8400 lines) is the **1.0-side client for the TOGa 2 (`_underscore`/api2) public API** *and* the home of the cross | library/app/api/toga2.php, worker/crons/toga2/aig/sync_togasupply_aig.php, worker/crons/toga2/wje/sync_togasupply_wje.php, test/@Mark/AIG/test_multi_email.php |

package/knowledge/1.0/apps/worker/INDEX.md

@@ -7,10 +7,10 @@
 | [Compass Partial In-Transit & Delivered Emails (per package)](features/compass-partial-in-transit-delivered-emails.md) | Compass USA and Compass Canada send a **per-package** in-transit email (and a matching delivered email) instead of one email listing the whole order. | worker/crons/toga2/compass/update_salesorder_status_from_odp.php, worker/crons/toga2/compasscanada/update_salesorder_status_from_odp.php, worker/crons/toga2/compasscanada/workflow/3_update_salesorder_status_from_grand_and_toy.php, worker/crons/toga2/compasscanada/send_delivered_email.php, worker/crons/toga2/compasscanada/workflow/test_partial_in_transit_email.php, worker/crons/toga2/compasscanada/workflow/test_partial_delivered_email.php, library/app/client/compasscanada.php |
 | [Elite TOGA 2.0 → TOGaDeskSupport Standalone Attachment Sync](features/elite-togadesk-attachment-sync.md) | `sync_togadesk_elite_attachments.php` is a standalone cron (every 5 minutes) that syncs file attachments from TOGA 2.0 into TOGaDeskSupport for Elite. | worker/crons/toga2/elite/sync_togadesk_elite_attachments.php, worker/crons/toga2/elite/test_sync_togadesk_elite_attachments.php |
 | [Forecast2 ↔ NetSuite Reconciliation & Trueup Tooling](features/forecast2-netsuite-reconciliation.md) | CLI tools to **audit** and **repair** drift between the production `Forecast` DB (core2) and NetSuite. | test/@dave/checker.php, worker2/Component/Forecast/SaleImport/SaleImport.php, test/@dave/looper.php, test/@dave/reconcile_netsuite_totals.php, test/@dave/fixer.php, test/@dave/analyze_netsuite_forecast_diff.php, test/@dave/trueup_sales.php, test/@dave/reconcile_drift_2023plus.php, test/@dave/probe_invoice_gap_2026.php, test/@dave/probe_creditmemo_gap_detail.php, test/@dave/trueup_open_orders.php, test/@dave/loop_trueup_open_orders.php, test/@dave/trueup_opportunities.php, test/@dave/probe_sales_gap_direct.php, test/@dave/probe_missing_oo_timing.php, test/@dave/probe_missing_oo_createdby.php, test/@dave/probe_drift_so_dates.php, test/@dave/probe_profit_invoices.php, test/@dave/probe_profit_gap.php, worker/crons/toga2/forecast2/common_import_sales_from_netsuite.php, worker/crons/toga2/forecast2/periodic_forecast_discrepancy_fix_open_orders.php, worker/crons/toga2/forecast2/import_open_orders.php, worker/schedules/cron.worker.infrastructure.json |
-| [NetSuite → TOGa Supply Per-Client Sync (thin wrappers)](features/netsuite-togasupply-per-client-sync.md) | Syncs NetSuite transactions (sales orders, purchase orders, invoices, item receipts, item fulfillments, inventory adjustments) into each TOGa Supply (2.0) clien | worker/crons/toga2/netsuite/common_sync_togasupply.php, worker/crons/toga2/netsuite/sync_togasupply_canon.php, worker/schedules/cron.worker.sync.json, dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql, library/app/api/netsuite/rest.php, library/app/systemmonitor/netsuiteintegration.php |
+| [NetSuite → TOGa Supply Per-Client Sync (thin wrappers)](features/netsuite-togasupply-per-client-sync.md) | Syncs NetSuite transactions (sales orders, purchase orders, invoices, item receipts, item fulfillments, inventory adjustments) into each TOGa Supply (2.0) clien | worker/crons/toga2/netsuite/common_sync_togasupply.php, worker/crons/toga2/netsuite/sync_togasupply_canon.php, worker/crons/toga2/netsuite/sync_togasupply_elite.php, worker/schedules/cron.worker.sync.json, dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql, library/app/api/toga2.php, library/app/api/netsuite/rest.php, library/app/framework.php, library/app/systemmonitor/netsuiteintegration.php, test/@srija/Elite Testing/Service Requests/test_sync_togasupply_elite_section.php, test/@srija/Elite Testing/Service Requests/test_diagnose_togasupply_elite.php |
 | [OneUptime Server monitor + disk/memory hygiene on the 1.0 worker EB host](features/oneuptime-server-monitor-host-hygiene.md) | The 1.0 `agilant-worker` EB environment runs on the **legacy Amazon Linux 1 PHP 7.2 platform** (Apache httpd/prefork, s3fs mounts, cron) and repeatedly went dow | worker/.ebextensions/040_disk_memory_hygiene.config, worker/.ebextensions/045_oneuptime_agent.config, worker/ebs/cron.worker.php, worker/ebs/mount-s3fs-folders.php, worker/ebs/apache_settings.php, worker/ebs/setup_phpini.php |
 | [OneUptime external uptime monitoring for 1.0 workers](features/oneuptime-worker-uptime-monitoring.md) | Every 1.0 worker box self-reports its liveness to an external OneUptime monitor once per minute by curl-POSTing to a per-worker "Incoming Request" heartbeat URL | library/app/worker.php, worker/crons/worker/worker_heartbeat.php |
 | [Prudential: Send Shipments for the Day report (daily cron)](features/send-shipments-for-the-day.md) | Daily cron (9:00 PM) that emails Prudential and Dell stakeholders an Excel report of all devices shipped that day, including tracking number, serial number, emp | worker/crons/notifications/reports/send_shipments_for_the_day.php |
 | [Diagnosing frozen 1.0 worker cron check-ins (Sentry "missed" flood)](workflows/diagnosing-frozen-cron-checkins.md) | When 1.0 worker cron timestamps freeze and Sentry project `worker1` fills with **`missed`** check-ins, the intuitive diagnosis — a wedged `App_Framework::isProc | worker/.ebextensions/cron.config, library/app/worker.php |
 | [isFulfillable Multi-Client Backfill (all togasupply clients)](workflows/isfulfillable-multi-client-backfill.md) | One-time backfill that catches up `Items.isFulfillable` on **existing** items across **all 17 togasupply clients** (AIG, Broward Sheriff, Canon, Endeavor Health | worker/crons/toga2/netsuite/backfill_isfulfillable_all_clients.php, library/app/api/toga2.php |
-| [Onboarding a Client to the NetSuite TOGa Supply Sync](workflows/onboarding-client-to-netsuite-togasupply-sync.md) | How to add a new TOGa 2 client to the per-client NetSuite → TOGa Supply importer (`worker/crons/toga2/netsuite/`). | worker/crons/toga2/netsuite/sync_togasupply.php, worker/crons/toga2/netsuite/common_sync_togasupply.php, worker/schedules/cron.worker.sync.json, dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql |
+| [Onboarding a Client to the NetSuite TOGa Supply Sync](workflows/onboarding-client-to-netsuite-togasupply-sync.md) | How to add a new TOGa 2 client to the per-client NetSuite → TOGa Supply importer (`worker/crons/toga2/netsuite/`). | worker/crons/toga2/netsuite/sync_togasupply.php, worker/crons/toga2/netsuite/common_sync_togasupply.php, worker/crons/toga2/netsuite/sync_togasupply_elite.php, worker/schedules/cron.worker.sync.json, dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql, dbchanges2/_modules/netsuite/2026-08-05 - CLEAN NETSUITE CLINET.SQL |

package/knowledge/1.0/apps/worker/features/netsuite-togasupply-per-client-sync.md

@@ -6,20 +6,27 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-08-11
-owners: ["dfranks", "bala", "jcardinal", "mhammontree"]
+updated: 2026-08-12
+owners: ["dfranks", "bala", "jcardinal", "mhammontree", "snaredla"]
 files:
   - worker/crons/toga2/netsuite/common_sync_togasupply.php
   - worker/crons/toga2/netsuite/sync_togasupply_canon.php
+  - worker/crons/toga2/netsuite/sync_togasupply_elite.php
   - worker/schedules/cron.worker.sync.json
   - dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql
+  - library/app/api/toga2.php
   - library/app/api/netsuite/rest.php
+  - library/app/framework.php
   - library/app/systemmonitor/netsuiteintegration.php
+  - test/@srija/Elite Testing/Service Requests/test_sync_togasupply_elite_section.php
+  - test/@srija/Elite Testing/Service Requests/test_diagnose_togasupply_elite.php
 related:
   - ../architecture.md
   - forecast2-netsuite-reconciliation.md
+  - ../workflows/onboarding-client-to-netsuite-togasupply-sync.md
   - ../../library/features/toga2-api-client-and-bridge.md
   - ../../../2.0/apps/_underscore/features/item-fulfillment-stage-lifecycle-and-order-status.md
+  - ../../../clients/elite/features/netsuite-togasupply-sync.md
 ---
 
 ## Summary
@@ -54,11 +61,61 @@ through the public TOGa2 API (a 1.0↔2.0 bridge).
 Each section (sales orders, POs, invoices, item receipts, item fulfillments, inventory
 adjustments) uses **adaptive time-windowing** via `startModeIteration()`/`finishModeIteration()`:
 a window stored as `<seconds>-<STATE>` in the client's `Parameters` table shrinks ÷3 when the
-prior run was left `RUNNING` (didn't finish) and grows ×3 (capped at 432000s = 5 days) when it
+prior run was left `RUNNING` (didn't finish) and grows ×3 (capped at
+`MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS`, default 432000s = 5 days) when it
 finished `IDLE`. The window state is written `RUNNING` at the **start** of each section, so a
 crash leaves it visibly RUNNING and the next run backs off. `LAST_SYNC_DATETIME_*` advances to
 the window's upper bound after each successful section.
 
+### The window cap is per-client overridable (2026-08-12)
+
+`common_sync_togasupply.php:3` is
+`defined('MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS') || define(…, 432000)` — **not** a
+`const` — so a wrapper may `const MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS = …;`
+*before* its `require_once` to widen its own catch-up window. Only Elite does (2592000 = 30 days,
+while backfilling from 2024); the other 17 wrappers inherit the 5-day default. Use this only for a
+deep backfill and put the reason in a comment next to it — at 5-day windows on a 5-minute cron,
+~858 days of history takes days of wall-clock to catch up; at 30 days it took ~90 minutes.
+
+### ⚠ A shrinking window is a BUG SIGNAL, not a load signal
+
+The single most expensive misreading of this engine. `startModeIteration()` writes
+`<seconds>-RUNNING` at the **start** of every section and `finishModeIteration()` writes `-IDLE` at
+the end; the ÷3 `REDUCE_INTERVAL_FACTOR` shrink fires only because the *previous* run never reached
+its IDLE write. **There is no timeout, memory cap, or resource limit anywhere in the script** — so
+"didn't finish" can only mean **it threw**. A collapsing window therefore means *go read Sentry*,
+never *tune the window size down*. (Corollary: a window that has grown back to the cap is positive
+evidence the section is completing.)
+
+### ⚠ A per-record API failure does NOT stop the cursor — the record is skipped forever
+
+The cursor write (`LAST_SYNC_DATETIME_*`) and `finishModeIteration()` both run **unconditionally
+after** the record loop. A record that throws mid-loop is captured to Sentry and **stepped over**,
+while the section still reports success and advances the cursor past its window. So
+**"section IDLE + cursor advancing" is not proof of a complete import** — it only proves the run
+didn't die.
+
+Proven concretely on Elite: sales order **169441** (NetSuite internal id 4624062, trandate
+2024-04-15, customer PO `BEGGS/04152024/…`) was simply absent from `Client_Elite.SalesOrders`
+because its window ran ~15 minutes before the missing-vendor fix (below) landed.
+
+**Recovery: rewind the section's cursor.** Set `NETSUITE_LAST_SYNC_DATETIME_<SECTION>` in the
+client's `Parameters` table back before the lost window. Re-import is **idempotent** — records match
+on `c_netsuiteInternal*Id` and `SalesOrders.c_netsuiteInternalSalesOrderId` carries a unique index —
+so a rewind re-PUTs what is already there and POSTs only what is missing.
+
+### Sections are NOT order-dependent — one cursor can be rewound alone
+
+Each section's `startModeIteration()` reads only **its own** `Parameters` key, and the PO section
+resolves its own sales order: `syncPurchaseOrderFromNetsuite()` calls
+`syncSalesOrderFromNetsuite()` itself (`library/app/api/toga2.php:1813`) when a PO has an
+originating order, and the link is conditional (`if ($salesOrder)` at :2221) so a PO whose order
+cannot be resolved still imports. Consequences worth knowing before you "fix" a skew:
+
+- A purchase-orders cursor running 50 days **ahead** of sales-orders is safe, not a defect.
+- Rewinding one section without touching the others is safe.
+- Which is also why the per-section operator script below is a legitimate tool rather than a hack.
+
 ### Adding a new client (the full recipe)
 
 A wrapper + schedule alone is **not enough** — the client must also be provisioned in three
@@ -127,6 +184,30 @@ them provisioned: `/customers`→`c_netsuiteInternalCustomerId`; `/countries`→
 `/shipping-methods`→`c_netsuiteInternalShipMethodId`. The names are a **convention**, not
 discovered per-client.
 
+### Manual operator scripts (built for Elite, reusable pattern)
+
+Two CLI scripts written for the Elite backfill live under
+`test/@srija/Elite Testing/Service Requests/` (they are operator tools, **not** scheduled crons —
+do not add them to `cron.worker.sync.json`):
+
+- **`test_sync_togasupply_elite_section.php`** — runs **one** section by enabling only its
+  `IS_ENABLED_INTEGRATION_*` flag with `define()` instead of `const`, so a slow section can be
+  backfilled without the earlier sections eating the run. **It is NOT a dry run — it writes the real
+  cursors.**
+- **`test_diagnose_togasupply_elite.php`** — **read-only** per-record IMPORT/SKIP match reporter for
+  a given section and date range. It deliberately does **not** call
+  `App_Framework::cronInitialization()` (that takes the process lock and exits silently, and writes a
+  `CronJobExecutions` row) and it drains/disables output buffering so `echo` actually reaches the
+  terminal.
+
+**⚠ A manual script does not mutually exclude with the scheduled cron.**
+`App_Framework::isProcessRunning()` (`library/app/framework.php:833-842`) defaults to
+`$_SERVER['SCRIPT_FILENAME']` and greps `ps -ef` for **its own filename** — so a per-section script
+with a different filename runs happily *alongside* `sync_togasupply_<client>.php`. Both then race the
+same `Parameters` cursors: whoever writes last wins and the other's window is silently skipped
+(and windows shrink). Any manual backfill must either pass the cron's filename to
+`isProcessRunning()` explicitly or be run with the cron's schedule entry disabled.
+
 ## Data model
 
 Per-client `Parameters` table (2.0 client DB, e.g. `Client_Canon.Parameters`; columns
@@ -149,6 +230,44 @@ Parameters are stored **per client DB** but accessed **through the TOGa2 API**,
 
 ## Gotchas / known issues
 
+- **A client with NEITHER a manufacturer NOR a catalog on its items used to crash the whole run
+  (fixed 2026-08-12).** `$lookupItemByClientUuidAndPartNumberUpper[$uuidClient]` and
+  `$lookupAllCatalogItemsByClientUuidAndPartNumberUpper[$uuidClient]` were only keyed **inside** the
+  items loop, so a sparse client never got the key created at all. Every `sync*FromNetsuite()` takes
+  them as `array &`, so the unset key passed as **null** →
+  `TypeError: Argument 8 passed to App_Api_Toga2::syncSalesOrderFromNetsuite() must be of the type
+  array, null given`. Both are now initialised to `[]` at `common_sync_togasupply.php:74-75`, before
+  the loop. This was **shared** code — the latent bug was reachable by any sparse client and Elite's
+  three initial items (both fields null) merely exposed it. Lesson for this engine: any per-client
+  lookup passed by reference must be initialised **outside** the loop that fills it.
+- **Countries are auto-created from the NetSuite shipping address, with a malformed code and name.**
+  `library/app/api/toga2.php:696-730` (and a duplicate at :1868-1905): when
+  `$nsShippingAddress->country` is not in `$lookupCountryByNetsuiteCountry`, the sync **POSTs
+  `/countries`**, deriving the name by splitting on non-lowercase characters and the code as
+  `substr(word1,0,1) . substr(word2,1,1)`. NetSuite's **leading underscore is never stripped**, so
+  `_unitedKingdom` → name `_united Kingdom` / code `_i`; `_canada` → `_canada` / `_C`;
+  `_australia` → `_australia` / `_A`. **Codes can collide.** An address with an *empty* country sets
+  `$isInvalidAddress = true` instead. The rows then surface in any UI that shows a country.
+  **Remedy: pre-seed `Countries`** with the correct `code`/`name` **and** the exact
+  `c_netsuiteCountry` string before the first import — see the onboarding workflow.
+  Note the direction: **NetSuite → TOGa only.** Nothing in this cron ever writes to NetSuite (every
+  NetSuite call is a `list*`/`fetch*`), and NetSuite's country list is a fixed system list that
+  cannot be extended, so there is nothing to fix on the NetSuite side.
+- **Item receipts are matched by the originating PO's customer, NOT by warehouse location.**
+  `common_sync_togasupply.php:844-905` uses the warehouse location ids only to **narrow** the SuiteQL
+  query; interest is decided from the receipt's `createdFrom` purchase order — its shipTo customer,
+  falling back to the custom field `NETSUITE_CUSTOM_FIELD_ID__END_USER_CUSTOMER`. So: a receipt from
+  a **stock PO** with no shipTo and no end-customer cannot be attributed to any client and is
+  skipped; and because the location filter is shared, receipts belonging to **other** clients at a
+  shared warehouse are returned and correctly skipped. Modelling receipts as "location-matched"
+  produces wrong diagnostics.
+- **`Units.locationId` is never populated by this sync — transaction location lives on the item
+  rows.** All 229 `Client_Elite.Units` have `locationId` NULL. `locationId` exists only on `Units`
+  and `InventoryAdjustmentItems` (not on the `*ItemUnits` bridge tables), and
+  `InventoryAdjustmentItems.locationId` **is** correctly populated (Elite: 6 rows at NetSuite
+  location 196 "Elite"/Chicago, 1 at 5 "New York"). Aggregate `_qtyOnHand` derives from
+  `ItemReceiptItems` joined through `PurchaseOrderItems` → `VendorItems`, not from
+  `Units.locationId`. When building an inventory view, read location from the **transaction items**.
 - **⚠ OPEN, UNTRACKED (found 2026-08-11): the GroWrk item-receipt sync has been failing every 5
   minutes since 2026-08-06.** `Logs.Issue` **124** for `clientId` **33**, *"Invalid API Response"* from
   `App_Api_Toga2::send()` (`library/app/api/toga2.php:3245`) via
@@ -245,6 +364,24 @@ Parameters are stored **per client DB** but accessed **through the TOGa2 API**,
 
 ## Change history
 
+- 2026-08-12 — TRUE-80499 (Elite onboarding, shared-engine work). **Fixed** the sparse-client
+  `TypeError`: the two per-client item lookups are now initialised at
+  `common_sync_togasupply.php:74-75` instead of only inside the items loop, so a client whose items
+  have neither a manufacturer nor a catalog no longer passes `null` into an `array &` parameter.
+  **Built** the per-client window override (`MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS` is now
+  `defined()||define()`, so a wrapper can widen its catch-up window; Elite uses 30 days, the other 17
+  stay at 5). Recorded four corrections that cost real diagnostic time: a **shrinking window is a bug
+  signal, not a load signal** (nothing in the script has a timeout — "didn't finish" means "threw");
+  a **per-record failure does not stop the cursor**, so the record is skipped permanently while the
+  section still reports IDLE and advances (recovery = rewind `NETSUITE_LAST_SYNC_DATETIME_<SECTION>`;
+  re-import is idempotent); **sections are independent** so one cursor can be rewound alone and a
+  skewed PO cursor is not a defect; and **item receipts are attributed via the `createdFrom` PO's
+  customer**, not by warehouse location. Also recorded the **malformed auto-created countries**
+  (`_unitedKingdom` → code `_i`), that `Units.locationId` is never populated by this sync, and the two
+  Elite operator scripts plus the `isProcessRunning()` own-filename trap that lets a manual script
+  race the scheduled cron. Client-specific results in
+  [Elite NetSuite → TOGa Supply sync](../../../clients/elite/features/netsuite-togasupply-sync.md).
+  (snaredla)
 - 2026-08-11 — TRUE-80824 (side finding, no code change): recorded an **open, untracked** failure —
   GroWrk (`clientId` 33) `syncItemReceiptFromNetsuite` has raised "Invalid API Response" from
   `App_Api_Toga2::send()` every 5 minutes since 2026-08-06 (`Logs.Issue` 124, ~288 events/day).

package/knowledge/1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md

@@ -6,14 +6,19 @@ project: Worker
 client: shared
 type: workflow
 status: active
-updated: 2026-06-16
-owners: ["dfranks"]
+updated: 2026-08-12
+owners: ["dfranks", "snaredla"]
 files:
   - worker/crons/toga2/netsuite/sync_togasupply.php
   - worker/crons/toga2/netsuite/common_sync_togasupply.php
+  - worker/crons/toga2/netsuite/sync_togasupply_elite.php
   - worker/schedules/cron.worker.sync.json
   - dbchanges2/_modules/netsuite/2026-04-01 - Parameters.sql
-related: []
+  - dbchanges2/_modules/netsuite/2026-08-05 - CLEAN NETSUITE CLINET.SQL
+related:
+  - ../features/netsuite-togasupply-per-client-sync.md
+  - ../../../clients/elite/features/netsuite-togasupply-sync.md
+  - ../../../2.0/apps/dbchanges2/workflows/client-schema-drift-audit.md
 ---
 
 ## Summary
@@ -49,6 +54,71 @@ API (`App_Api_Toga2::send`), which lands in that client's `Client_<Name>` databa
 5. **Deploy order matters:** the Parameters seed must hit prod `Client_<Name>` **before or
    with** the cron going live, or the sync 404-aborts (and throws a Sentry error) every 5
    minutes.
+6. **Seed the shared synthetic "Agilant" vendor row** — see the dedicated section below. The
+   `netsuite` dbchanges2 module does **not** do it, and without it every order carrying a customer PO
+   number fails.
+7. **Grant `AclCustomFieldPermissions` for the module's custom fields** — also below. The `netsuite`
+   module registers `CustomRecordFields` rows and adds the `c_` columns but grants **no field-level
+   ACL**, so api2 answers `403 EV-2`.
+8. **Pre-seed `Countries`** for every country the client ships to, with the correct `code`/`name`
+   **and** the exact NetSuite `c_netsuiteCountry` string (`_unitedKingdom`, `_canada`, …). If you
+   skip this, the sync auto-creates the row from the NetSuite string and derives a **malformed**
+   name and a collision-prone 2-char code — mechanics and examples in the
+   [engine doc](../features/netsuite-togasupply-per-client-sync.md).
+9. **Widen the window only if you are backfilling deep history.** A wrapper may
+   `const MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS = …;` before the `require_once` (Elite: 30
+   days while backfilling from 2024). At the 5-day default on a 5-minute cron, ~2.4 years of history
+   takes days to catch up.
+
+## The synthetic "Agilant" vendor must exist in the client's own DB (found 2026-08-06)
+
+13 of the 18 wrappers pass the **same** vendor uuid
+`10ed18ec-0999-53d9-f9db-5892d90f09d4` ("Agilant") as
+`CLIENT_CONFIGURATION['importCustomerPurchaseOrdersOnVendor']` — but `Vendors` is a **per-client
+table**, so that uuid has to exist as a row in **every** `Client_<Name>.Vendors`. **Nothing in
+`dbchanges2/_modules/netsuite/` seeds it** (verified: the uuid appears in no file in the repo).
+
+Symptom when it is missing: **every** sales order that carries a customer PO number (NetSuite
+`otherRefNum`) fails `POST /purchase-orders` with **400 `EV-12` "unable to find a unique match"** on
+the nested vendor. Orders without a customer PO import fine, so the failure looks partial and
+data-dependent rather than structural. On Elite this produced **191 Sentry events in one day**
+(`WORKER1-420`) and `PurchaseOrders` stuck at **0**; after seeding the row it went to **234**.
+
+Seed it with a `dbchanges2/Client_<Name>/<YYYY-MM-DD><letter> - <Name>AgilantVendor.sql` inserting
+the vendor with that **exact** uuid (reuse it — a fresh UUID defeats the whole shared-uuid pattern).
+
+> **The undocumented pattern to internalise: a uuid shared across clients still needs a row per
+> client database.** It reads like a global id and behaves like a per-tenant one.
+
+## The `netsuite` module grants no field-level ACL (found 2026-08-06)
+
+`dbchanges2/_modules/netsuite/2026-08-05 - CLEAN NETSUITE CLINET.SQL` inserts the
+`CustomRecordFields` rows and adds the `c_` columns but contains **zero**
+`AclCustomFieldPermissions` statements (`grep -c` = 0; the smaller
+`2026-07-10a - UnitInventoryFields.sql` *does* grant, which is why the gap is easy to miss).
+
+Symptom: api2 returns **403 `EV-2` "do not have the necessary permissions to read the specified
+fields"** — a whole-request failure, not a silently dropped field.
+
+Measured on Elite vs. a healthy client: **Elite 27 fields / 0 grants; Quad 26 / 25** grants to
+**role 1 (Base), `isWritable = 1`**. Fixed with
+`dbchanges2/Client_Elite/2026-08-06a - EliteNetsuiteCustomFieldAcl.sql`. Same failure class as the
+GroWrk incidents — the general audit playbook is
+[client schema-drift audit](../../../2.0/apps/dbchanges2/workflows/client-schema-drift-audit.md).
+
+**Post-onboarding check, per client:** every `CustomRecordFields` row added by the module should have
+exactly one grant. Count fields vs. grants and diff against a known-good client before declaring the
+onboarding done.
+
+## Recovering records the first run skipped
+
+A record that throws mid-loop is logged to Sentry and **stepped over while the cursor still
+advances** — so a clean-looking IDLE section can be missing records (see the engine doc). Recovery is
+to rewind `NETSUITE_LAST_SYNC_DATETIME_<SECTION>` in the client's `Parameters` table to before the
+bad window. Re-import is **idempotent** (matched on `c_netsuiteInternal*Id`;
+`SalesOrders.c_netsuiteInternalSalesOrderId` has a unique index) and sections are independent, so one
+cursor can be rewound alone. Expect to do this at least once on any onboarding where a provisioning
+gap was found *after* the cron started running.
 
 ## Parameters seed (the required, easily-missed step)
 The sync reads/writes per-client sync state via the TOGa2 API `/parameters` endpoint, which
@@ -103,11 +173,30 @@ the directory; no `USE`).
   end-user matching. Always probe NetSuite first.
 - **Parameters not seeded in prod** → sync throws every 5 min; surfaces as a `worker1` Sentry
   error and zero imports.
-- **Missing catalog item** on an incoming order may throw mid-run depending on the section;
-  the checkpoint does not advance past a throwing window, so it self-heals once the dependency
-  exists.
+- **⚠ CORRECTED 2026-08-12 — a failing record does NOT self-heal.** This section previously said
+  "the checkpoint does not advance past a throwing window, so it self-heals once the dependency
+  exists." **That is wrong for a per-record failure.** The cursor write and `finishModeIteration()`
+  run unconditionally *after* the record loop, so a record that throws is Sentry-logged, stepped
+  over, and **permanently skipped** while the section reports success. Only a throw that escapes the
+  loop (setup/lookup phase, transport) leaves the checkpoint behind. Fix a provisioning gap and you
+  must **rewind the cursor** — see *Recovering records the first run skipped* above.
+- **⚠ OPEN: `dbchanges2/_modules/netsuite/2026-08-05 - CLEAN NETSUITE CLINET.SQL` sits in the
+  SHARED module folder** and will run against **all 18 opted-in clients** on the next unscoped run.
+  It also carries a `CLINET` typo and **no letter suffix**, which the dbchanges2
+  `YYYY-MM-DD<letter>` contract requires. Know it is there before you trigger a module run.
 
 ## Change history
+- 2026-08-12 — TRUE-80499 (Elite): added the **three provisioning steps this workflow was missing**,
+  each found by a production failure rather than by reading the module. (1) The shared synthetic
+  **"Agilant" vendor** uuid `10ed18ec-…f09d4` must be seeded as a **row in every**
+  `Client_<Name>.Vendors` — nothing in the `netsuite` module does it, and without it every order with
+  a customer PO number 400s `EV-12` on the nested vendor (Elite: 191 Sentry events/day, PurchaseOrders
+  0 → 234 after seeding). (2) The module registers `CustomRecordFields` and the `c_` columns but grants
+  **no `AclCustomFieldPermissions`** → 403 `EV-2` (Elite 27 fields / 0 grants vs. Quad 26 / 25 to role
+  1). (3) **Pre-seed `Countries`** or the sync auto-creates malformed rows from the NetSuite string.
+  Also added the per-client backfill-window override, a **cursor-rewind recovery** procedure, and
+  **corrected** this doc's claim that a throwing record self-heals — it does not, the cursor advances
+  past it. Flagged the unsuffixed shared `CLEAN NETSUITE CLINET.SQL` as an open hazard. (snaredla)
 - 2026-06-16 — Documented the onboarding process after adding Quad (TRUE-79575): wrapper +
   schedule + the required 12-key Parameters seed; captured the `isParentCustomer` NetSuite
   probe and the local Client_/Logs_ schema requirement. (dfranks)

package/knowledge/2.0/apps/worker2/features/elite-freshservice-sync.md

@@ -139,9 +139,25 @@ To test worker2 Elite code locally against production TOGA 2 and Freshservice:
    require '_underscore.php';
    ```
 
-4. **PHP version** — worker2 vendor targets PHP >= 8.5. Local PHP 8.1 requires a
-   temporary bypass in `vendor/composer/platform_check.php` — revert before committing.
+4. **PHP version** — worker2's Composer install targets **PHP >= 8.5**, so on a local **8.1**
+   machine every script dies in `vendor/composer/platform_check.php` before any of your code runs.
+   **The flag-based escapes do not work here** — three were tried (the `--ignore-platform-req`
+   family and friends) and none of them stopped the runtime check, because the check is a
+   *generated file* that `autoload.php` requires unconditionally; the flags only affect
+   dependency *resolution* at install time.
+   The one thing that works is **temporarily neutralizing `vendor/composer/platform_check.php`**
+   and restoring it immediately afterwards. Two properties make that safe: the file is
+   **gitignored** (so it can never be committed by accident), and it is regenerated by any
+   `composer install`/`dump-autoload`. Still, wrap it so the restore is guaranteed even if the
+   script fails — a half-bypassed vendor tree is a confusing thing to come back to. Never leave it
+   neutralized, and never "fix" this by lowering the platform requirement.
 
 ## Change history
+- 2026-08-12 — Expanded the local-PHP-version note: on a PHP 8.1 machine the **flag-based
+  `--ignore-platform-req` escapes do not help**, because `platform_check.php` is a generated file
+  required unconditionally by `autoload.php` and the flags only affect install-time resolution.
+  The working approach is to temporarily neutralize `vendor/composer/platform_check.php` with a
+  **guaranteed restore** — safe because the file is gitignored and regenerated by any
+  `composer install`. (snaredla)
 - 2026-06-11 — Redacted Elite credential constants from the doc; secret scanner added to `validate`. (snaredla)
 - 2026-06-10 — Documented `_Worker_Elite` Freshservice → TOGA 2 webhook sync (conversation/attachment handling, TOGA 2 API gotchas, local dev setup). (snaredla)

package/knowledge/INDEX.md

@@ -4,11 +4,11 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 ## 1.0 framework
 
-- **library** (Library) _(framework core)_ — 18 doc(s) → [1.0/apps/library/INDEX.md](1.0/apps/library/INDEX.md)
-- **worker** (Worker) — 21 doc(s) → [1.0/apps/worker/INDEX.md](1.0/apps/worker/INDEX.md)
+- **library** (Library) _(framework core)_ — 17 doc(s) → [1.0/apps/library/INDEX.md](1.0/apps/library/INDEX.md)
+- **worker** (Worker) — 22 doc(s) → [1.0/apps/worker/INDEX.md](1.0/apps/worker/INDEX.md)
 - **dbchanges** (Database Changes) _(framework core)_ — 1 doc(s) → [1.0/apps/dbchanges/INDEX.md](1.0/apps/dbchanges/INDEX.md)
 - **worker1.5** (Worker 1.5) — 0 doc(s) → [1.0/apps/worker1.5/INDEX.md](1.0/apps/worker1.5/INDEX.md)
-- **togadesk** (TOGa Desk) — 13 doc(s) → [1.0/apps/togadesk/INDEX.md](1.0/apps/togadesk/INDEX.md)
+- **togadesk** (TOGa Desk) — 12 doc(s) → [1.0/apps/togadesk/INDEX.md](1.0/apps/togadesk/INDEX.md)
 - **togaview** (TOGa View) — 7 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)
 - **walmarttechservices** (Walmart Tech Services) — 1 doc(s) → [1.0/apps/walmarttechservices/INDEX.md](1.0/apps/walmarttechservices/INDEX.md)
@@ -19,7 +19,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 ## 2.0 framework
 
 - **_underscore** (_Underscore) _(framework core)_ — 54 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
-- **worker2** (Worker) — 49 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
+- **worker2** (Worker) — 48 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 22 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 8 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)
 - **toga2-supply** (TOGa Supply) — 6 doc(s) → [2.0/apps/toga2-supply/INDEX.md](2.0/apps/toga2-supply/INDEX.md)

package/knowledge/clients/elite/INDEX.md

@@ -2,11 +2,10 @@
 
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
-| [Elite — \"New Service Request\" button on TOGa Desk 1.0 tickets](features/desk-service-request-creation.md) | 1.0 | TRUE-80497. | togadesk/desk/includes/controllers/modals/tickets/serviceRequest.php, togadesk/desk/includes/controllers/actions/tickets/serviceRequest.php, togadesk/desk/template/modals/tickets/serviceRequest.php, togadesk/desk/includes/classes/class.ticket.php, library/app/model/togadesk/ticket.php, library/app/api/servicerequest.php, dbchanges2/Client_Elite/2026-08-11a - EliteServiceRequestTicketUnique.sql, test/@srija/Elite Testing/Service Requests/test_elite_desk_service_request.php |
+| [Elite — NetSuite → TOGa Supply inbound sync (TRUE-80499 onboarding)](features/netsuite-togasupply-sync.md) | 1.0 | Elite is the 18th client on the shared NetSuite → TOGa Supply importer ([engine](../../../1.0/apps/worker/features/netsuite-togasupply-per-client-sync.md)). | worker/crons/toga2/netsuite/sync_togasupply_elite.php, worker/crons/toga2/netsuite/common_sync_togasupply.php, worker/schedules/cron.worker.sync.json, _underscore/Model/Elite/SalesOrder.php, _underscore/Model/Elite/PurchaseOrder.php, _underscore/Model/Elite/ItemReceipt.php, dbchanges2/Client_Elite/_modules.txt, test/@srija/Elite Testing/Service Requests/test_sync_togasupply_elite_section.php, test/@srija/Elite Testing/Service Requests/test_diagnose_togasupply_elite.php |
 | [Elite SalesOrder → NetSuite Push (postPost/postPut interceptors → worker2)](features/salesorder-netsuite-push.md) | 2.0 | Elite orders created in Toga are pushed into NetSuite **event-driven**, not on a cron. | _underscore/Model/Elite/SalesOrder.php, _underscore/Model/Elite/ServiceRequest.php, worker2/Worker/Netsuite/SalesOrder.php, dbchanges2/Core/2026-08-06a - Service request and sales order payload interceptors.sql |
 | [Elite — Sales Order stage change posts a reply on the TOGa Desk (1.0) ticket](features/salesorder-status-togadesk-reply.md) | 2.0 | When an Elite sales order's **stage** changes, a reply is posted on the originating **TOGa Desk (1.0)** ticket so the requester sees progress where they raised | worker2/Worker/Sync/SalesOrderStatus.php, _underscore/Model/Elite/SalesOrderStatus.php, _underscore/Model/Elite/SalesOrder.php |
-| [Elite — Service Request → Sales Order → status back to TOGa Desk 1.0](features/service-request-to-salesorder-pipeline.md) | 2.0 | Once a Service Request exists in 2.0 (raised from [TOGa Desk](./desk-service-request-creation.md) or in supply2), an interceptor-driven chain turns it into a Sa | worker2/Worker/Sync/ServiceRequest.php, worker2/Worker/Sync/SalesOrderStatus.php, _underscore/Model/Elite/ServiceRequest.php, _underscore/Model/Elite/SalesOrder.php, test/@srija/Elite Testing/Service Requests/test_elite_chain_toga2.php |
 | [Elite — supply2 frontend scope (Inventory + Service Requests, both built)](features/supply2-scope.md) | 2.0 | Scope for onboarding Elite to the `toga2-supply` frontend (host `ELITE`). | toga2-supply/ELITE-CLIENT-TASK-NOTES.md, toga2-supply/src/pages/Orders/view/OrderView/viewModel/FIELDS/ELITE/BASEFIELDS.json, toga2-supply/src/pages/Orders/viewModel/FIELDS/ELITE/BASE.json, toga2-supply/src/pages/Inventory/viewModel/FIELDS/DUMMYGROUPOPTIONS.ts, toga2-supply/src/hooks/useFetchData.tsx, toga2-supply/src/components/ui/Toaster.tsx, toga2-supply/src/pages/Inventory/viewModel/FIELDS/DUMMYGROUPOPTIONS.ts, toga2-supply/src/pages/Inventory/viewModel/FIELDS/INVENTORYPAGEFIELDS.ts, toga2-supply/src/pages/Inventory/viewModel/index.ts, toga2-supply/src/pages/Inventory/listing/InventoryPage.tsx, toga2-supply/src/pages/Inventory/listing/InventoryRouter.tsx, toga2-supply/src/pages/Inventory/listing/InventorySubTablePage.tsx, toga2-supply/src/utils/resolveClientHostName.ts, toga2-supply/src/utils/convertConstructorColumnTitles.ts, toga2-supply/src/pages/Orders/OrdersPage.tsx, toga2-supply/src/pages/Orders/viewModel/FIELDS/ELITE/BASE.json, toga2-supply/src/pages/Orders/viewModel/useOrdersPageViewModel.ts, toga2-supply/src/pages/Orders/api/OrdersApi.ts, toga2-supply/src/pages/Orders/view/OrderView/viewModel/useOrderDetailsViewModel.ts, toga2-supply/src/components/ui/Tables/PrimaryTable/helperFunctions/renderModalContent.tsx, toga2-supply/src/components/layout/SlideMenu/SlideMenu.tsx, toga2-supply/package.json |
 | [Elite — stale TableView config (11 dead Core.RecordFields across 9 views)](features/supply2-tableview-config-drift.md) | 2.0 | `Client_Elite`'s `TableViewJoins` predate **two** platform bridge-table migrations and still reference **11 deleted `Core.RecordFields` ids (211, 321, 932, 358, | dbchanges2/Client_Elite/, dbchanges2/Client_Nychh/2026-06-19a - FixItemFulfillmentTableViewTrackingAndRoot.sql |
 | [Elite — raising a Service Request from a TOGa Desk ticket (App_Api_ServiceRequest)](features/togadesk-service-request-intake.md) | 1.0 | An Elite agent raises a **Service Request** from a TOGa Desk (1.0) ticket via a modal. | library/app/api/servicerequest.php, library/app/model/togadesk/ticket.php, togadesk/desk/includes/classes/class.ticket.php, togadesk/desk/template/modals/tickets/serviceRequest.php, togadesk/desk/includes/controllers/modals/tickets/serviceRequest.php, togadesk/desk/includes/controllers/actions/tickets/serviceRequest.php, dbchanges2/Client_Elite/2026-08-11a - EliteServiceRequestTicketUnique.sql, test/@srija/Elite Testing/Service Requests/test_elite_desk_service_request.php |
-| [Elite](profile.md) | 2.0 | Elite is a managed-services client that uses **Freshservice** as their helpdesk platform. | worker2/Worker/Elite.php, worker2/Worker/Sync/ServiceRequest.php, library/app/api/toga2.php, library/app/api/servicerequest.php, _underscore/Model/Elite/SalesOrder.php, _underscore/Model/Elite/ServiceRequest.php, togadesk/desk/includes/classes/class.ticket.php |
+| [Elite](profile.md) | 2.0 | Elite is a managed-services client that uses **Freshservice** as their helpdesk platform. | worker2/Worker/Elite.php, worker2/Worker/Sync/ServiceRequest.php, library/app/api/toga2.php, library/app/api/servicerequest.php, _underscore/Model/Elite/SalesOrder.php, _underscore/Model/Elite/ServiceRequest.php, togadesk/desk/includes/classes/class.ticket.php, worker/crons/toga2/netsuite/sync_togasupply_elite.php |

package/knowledge/clients/elite/features/netsuite-togasupply-sync.md

@@ -0,0 +1,141 @@
+---
+title: "Elite — NetSuite → TOGa Supply inbound sync (TRUE-80499 onboarding)"
+framework: "1.0"
+repo: worker
+project: Worker
+client: elite
+type: client-feature
+status: active
+updated: 2026-08-12
+owners: ["snaredla"]
+files:
+  - worker/crons/toga2/netsuite/sync_togasupply_elite.php
+  - worker/crons/toga2/netsuite/common_sync_togasupply.php
+  - worker/schedules/cron.worker.sync.json
+  - _underscore/Model/Elite/SalesOrder.php
+  - _underscore/Model/Elite/PurchaseOrder.php
+  - _underscore/Model/Elite/ItemReceipt.php
+  - dbchanges2/Client_Elite/_modules.txt
+  - test/@srija/Elite Testing/Service Requests/test_sync_togasupply_elite_section.php
+  - test/@srija/Elite Testing/Service Requests/test_diagnose_togasupply_elite.php
+related:
+  - ../profile.md
+  - ../../../1.0/apps/worker/features/netsuite-togasupply-per-client-sync.md
+  - ../../../1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md
+  - ./salesorder-netsuite-push.md
+  - ./supply2-scope.md
+  - ../../growrk/features/units-netsuite-custom-fields.md
+---
+
+## Summary
+
+Elite is the 18th client on the shared NetSuite → TOGa Supply importer
+([engine](../../../1.0/apps/worker/features/netsuite-togasupply-per-client-sync.md)). This doc records
+what is **Elite-specific**; everything about how the engine works, and the two provisioning gaps this
+onboarding discovered, lives in the engine and
+[onboarding workflow](../../../1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md)
+docs.
+
+**Direction matters:** this is the **inbound** half (NetSuite → TOGa). The **outbound** push of Elite
+orders *into* NetSuite is a separate, event-driven path — see
+[salesorder-netsuite-push](./salesorder-netsuite-push.md). Nothing in this cron ever writes to
+NetSuite.
+
+**Backfill result (2026-08, April 2024 → Aug 2026, ~90 minutes):** 257 SalesOrders (0 missing a
+NetSuite id), 234 PurchaseOrders, 201 ItemFulfillments, 29 ItemReceipts, 2 InventoryAdjustments,
+153 Items, 229 Units, 1042 Contacts, 806 Addresses.
+
+## What was built
+
+| Piece | Detail |
+|---|---|
+| **Wrapper** | `worker/crons/toga2/netsuite/sync_togasupply_elite.php` — `isParentCustomer` **false**, NetSuite customer internal id **36443**, end-user-customer custom field **3149** |
+| **Schedule** | `cron.worker.sync.json`, `*/5 * * * *`, `active: 1` |
+| **Client models** | 18 new `_underscore/Model/Elite/*.php` trait models (see below) |
+| **Schema** | `dbchanges2/Client_Elite/_modules.txt` opts into `_modules/netsuite` |
+| **Warehouse locations** | `2026-08-05b` (NetSuite **196** "Elite"/Chicago) and `2026-08-06d` (NetSuite **5** "New York") — both confirmed to carry real Elite inventory-adjustment activity before seeding |
+| **Vendor + ACL fixes** | `2026-08-06e - EliteAgilantVendor.sql`, `2026-08-06a - EliteNetsuiteCustomFieldAcl.sql` — the two module gaps, [written up in the workflow](../../../1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md) |
+
+### The 18 trait models are pure convention — and fail SILENTLY
+
+Each is only `class _Model_Elite_X extends _Model_Client_X { use _Trait_Netsuite_X; }`:
+Country, Customer, InventoryAdjustment, Invoice, Item, ItemFulfillment, ItemFulfillmentItemUnit,
+ItemFulfillmentStage, ItemReceipt, Location, PaymentTerm, PurchaseOrder, SalesOrder, SalesOrderItem,
+SalesOrderStage, ShippingMethod, Subsidiary, Vendor.
+
+Resolution is **pure class-name string substitution off the JWT client slug** —
+`api2/Component/Api/V2/V2.php:2878-2886` reads `jwtPayload.id.client.slug` and does
+`str_replace('_Model_Client_', '_Model_Elite_', …)` then `class_exists()`; the same block repeats at
+:3148, :3744 and :4177 for nested/sort paths. **If `class_exists` fails, it falls back to the base
+`_Model_Client_X` with no error, no log, and a 200 response** — the `c_netsuite*` fields simply are
+not there. So a typo'd filename or class name presents as "the sync ran and imported nothing useful",
+never as a failure.
+
+The mirror-image trap is the one that bit GroWrk: once the model **does** resolve, every `c_` field
+the trait declares must exist as a column, a `CustomRecordFields` row **and** an ACL grant, or reads
+500/403 — see [GroWrk NetSuite-module custom fields](../../growrk/features/units-netsuite-custom-fields.md).
+
+### Elite-only wrapper deviations
+
+- **`MAX_TIME_WINDOW_TO_FETCH_FROM_NETSUITE_SECONDS = 2592000` (30 days)**, vs. the 5-day default the
+  other 17 wrappers inherit — Elite is backfilling from 2024 and 5-day windows on a 5-minute cron were
+  too slow. This is only possible because the shared engine now `define()`s the cap instead of
+  `const`-ing it. **Reduce it to the default once the backfill is caught up.**
+- **`IS_ENABLED_INTEGRATION_INVOICES = false` — TEMPORARY.** The invoice section scans the whole
+  NetSuite transaction table per window, kept running out of time, and **starved the item-receipt and
+  item-fulfillment sections that follow it** — which are what `_qtyOnHand` derives from. Re-enable
+  once inventory has caught up. (Note the invoice section is also capped at `now − 86400s` by design,
+  so it always trails.)
+- **`MIN_DATETIME_TO_CHECK_FOR_NETSUITE_DATA = '2018-01-01'`**, with the real start controlled by the
+  seeded `Parameters` cursors.
+
+## Gotchas / known issues
+
+- **⚠ Two files named `sync_togasupply_elite.php`, both scheduled.**
+  `worker/crons/toga2/netsuite/sync_togasupply_elite.php` (`*/5`) is **this** supply importer;
+  `worker/crons/toga2/elite/sync_togasupply_elite.php` (`*/2`) is the older
+  `syncWithToga`/`syncWithTogadesk` desk bridge with its own parameter keys. They coexist harmlessly
+  but **confirm the folder before editing** — this is the generic name collision the engine doc warns
+  about, now real for Elite.
+- **⚠ `Client_Elite` has TWO active `Apis` rows** (Agilant `id 1`, Elite `id 2`). `getClientContext()`
+  does `LIMIT 1` with **no `ORDER BY`**, so a worker can authenticate as the wrong client. Not yet
+  fixed; be explicit about which api uuid/secret you pass.
+- **⚠ `Client_Elite.Countries` needs a cleanup migration.** Three rows were auto-created by the sync
+  from the NetSuite strings before `Countries` was pre-seeded, with malformed codes/names:
+  `_unitedKingdom` → `_united Kingdom` / `_i`, `_canada` → `_canada` / `_C`, `_australia` →
+  `_australia` / `_A`. Fix `code`/`name` to `GB`/`CA`/`AU` **without touching `c_netsuiteCountry`** —
+  that string is the sync's match key and must keep NetSuite's exact value (leading underscore
+  included). Mechanics in the
+  [engine doc](../../../1.0/apps/worker/features/netsuite-togasupply-per-client-sync.md).
+  This matters for Elite specifically because **Elite ships internationally** (see the shipping
+  decision on the [profile](../profile.md)).
+- **⚠ The four migrations named above (`2026-08-05b`, `2026-08-06a`, `2026-08-06d`, `2026-08-06e`) are
+  NOT in the `dbchanges2` checkout** — absent from `_main`'s working tree and from
+  `origin/TRUE-80499` as of 2026-08-12. They may be uncommitted on another machine/branch. Exactly the
+  GroWrk situation ("production is ahead of the repo"): until they are committed, the next
+  environment or client provisioned from `dbchanges2` re-creates this drift. **Do not re-write them
+  from memory — find the branch.**
+- **`Units.locationId` is NULL for all 229 Elite Units.** The sync never populates it; transaction
+  location lives on `InventoryAdjustmentItems.locationId` (populated: 6 rows at NetSuite 196, 1 at 5).
+  Any Elite inventory table view must read location from the transaction items.
+- **Sales order 169441 was missing from the first backfill** (NetSuite id 4624062, 2024-04-15,
+  customer PO `BEGGS/04152024/…`) because its window ran ~15 minutes before the vendor fix. It is the
+  worked example for the engine's cursor-advances-past-a-failed-record behaviour — recovered by
+  rewinding `NETSUITE_LAST_SYNC_DATETIME_SALES_ORDERS`.
+
+## Change history
+
+- 2026-08-12 — TRUE-80499: **onboarded Elite to the NetSuite → TOGa Supply importer.** Built the
+  wrapper (customer 36443, `isParentCustomer` false, 30-day window, invoices temporarily disabled),
+  the schedule entry, 18 `_Model_Elite_*` netsuite trait models, the `_modules/netsuite` opt-in, and
+  the two warehouse Locations (NetSuite 196 Chicago, 5 New York). Fixed the two module gaps that
+  blocked it (missing shared "Agilant" `Vendors` row → 400 `EV-12` on every customer-PO order, 191
+  Sentry events/day, PurchaseOrders 0 → 234; and 27 custom fields with 0 ACL grants → 403 `EV-2`) —
+  both generalised into the
+  [onboarding workflow](../../../1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md).
+  Full backfill April 2024 → Aug 2026 completed in ~90 minutes (257 SalesOrders / 234 PurchaseOrders /
+  201 ItemFulfillments / 29 ItemReceipts / 153 Items / 229 Units / 1042 Contacts / 806 Addresses).
+  Recorded the silent `class_exists` fallback in client-model resolution, the duplicate
+  `sync_togasupply_elite.php` filename across two integrations, the two active `Apis` rows vs.
+  `getClientContext()`'s unordered `LIMIT 1`, the `Countries` cleanup still owed, and that the four
+  dbchanges2 migrations are not in the repo checkout. (snaredla)

package/knowledge/clients/elite/features/togadesk-service-request-intake.md

@@ -154,6 +154,16 @@ wrong-country address.
 select2 state list kept emptying the dropdown — the file's own comment records this. The
 server-side pair check is the guard; the modal stays as-is.
 
+### …and that is the ONLY address rule Elite wants (confirmed 2026-08-12)
+
+Elite confirmed (via Bala): **no address validation — Elite ships internationally.** So the modal
+must **not** enforce US state/postal formats and **must not** copy Prudential's `_unitedStates`
+hardcoding. The country/state **pair** check above stays, because it is a correctness guard (a 2.0
+`Addresses` row derives its country from its state), not a US-format rule — and the country must still
+resolve to a real `Countries` row for the downstream NetSuite push. Elite also **dictates the shipping
+method on the Sales Order: FedEx only.** Both rules and their reference orders are on the
+[Elite profile](../profile.md#shipping-rules-confirmed-with-elite-by-bala-2026-08-12).
+
 ## Test harness
 
 `test/@srija/Elite Testing/Service Requests/test_elite_desk_service_request.php` (PHP **7.2**)
@@ -204,6 +214,12 @@ them, so it proves everything *after* the permission check, not the check itself
 
 ## Change history
 
+- 2026-08-12 (shipping rules) — Recorded Elite's confirmed shipping decisions (via Bala): the
+  **shipping method is dictated on the Sales Order and is FedEx only**, and there is deliberately
+  **no address validation** because Elite ships internationally — so the modal must not enforce US
+  state/postal formats and must not reuse Prudential's `_unitedStates` hardcoding. The country/state
+  pair check stays (correctness, not US-format), and the country must still resolve to a `Countries`
+  row for the NetSuite push. (snaredla)
 - 2026-08-12 (later pass) — Recorded the **button gate** itself
   (`isEliteServiceRequestTicket()`: client 163 + department 299 + custom field 88 = `Service
   Request`; the button **replaces** "New Part Request" on those tickets, and the 2.0 uuid comes from

package/knowledge/clients/elite/profile.md

@@ -2,6 +2,7 @@
 title: Elite
 framework: "2.0"
 apps:
+  - worker
   - worker2
   - library
   - toga2-supply
@@ -24,7 +25,9 @@ files:
   - _underscore/Model/Elite/SalesOrder.php
   - _underscore/Model/Elite/ServiceRequest.php
   - togadesk/desk/includes/classes/class.ticket.php
+  - worker/crons/toga2/netsuite/sync_togasupply_elite.php
 related:
+  - features/netsuite-togasupply-sync.md
   - 2.0/apps/worker2/features/elite-freshservice-sync.md
   - 1.0/apps/library/features/elite-freshservice-sync.md
   - features/supply2-scope.md
@@ -49,6 +52,27 @@ on beta as of 2026-08-10; see [supply2-scope](features/supply2-scope.md). The ba
 dbchanges2 **PR #454** (TRUE-80499, snaredla24, 2026-08-05) added the **netsuite** module to
 `Client_Elite/_modules.txt` — the supply-chain schema layer is arriving.
 
+**Elite is live on the inbound NetSuite → TOGa Supply sync as of 2026-08-12 (TRUE-80499).** A
+`*/5` worker cron backfilled April 2024 → Aug 2026 in ~90 minutes (257 sales orders, 234 purchase
+orders, 201 item fulfillments, 153 items, 229 units) — this is what adds **`worker`** (1.0) to
+Elite's app scope. Elite-specific config, the still-owed `Countries` cleanup, and the two active
+`Apis` rows hazard are in [netsuite-togasupply-sync](features/netsuite-togasupply-sync.md).
+
+## Shipping rules (confirmed with Elite by Bala, 2026-08-12)
+
+Two client rules that constrain every order-creation surface (the desk Service Request modal, the
+supply2 order forms, and the NetSuite push):
+
+- **Elite dictates the shipping method on the Sales Order, and it is FedEx only** — the shipping-method
+  field must accept FedEx carrier values only.
+- **No address validation.** Elite ships **internationally**, so **do not port Prudential's
+  `_unitedStates` hardcoding** and the SR modal must **not** enforce US state/postal formats.
+  Reference sales orders: **285264, 285379, 285346**.
+
+The country still has to resolve to a real `Countries` row for the NetSuite push to succeed — "no
+address validation" means no US-format enforcement, not "any string goes." Full reasoning is recorded
+in `test/@srija/DOCS/ELITE/ELITE_SR_PLAN_BALA.md` and `ELITE_SR_PLAN_COMBINED.md`.
+
 Elite's service-request data model: `ServiceRequests` is the record the `service-requests` table
 view is built on (joining Tickets / Customers / ServiceRequestTypes / SalesOrders, with
 `SalesOrders.serviceRequestId = ServiceRequests.id`). **That relationship is 1:N, not 1:1**

package/package.json

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

package/knowledge/1.0/apps/library/features/service-request-toga2-provisioning.md

@@ -1,135 +0,0 @@
----
-title: App_Api_ServiceRequest — provisioning a TOGa 2.0 Service Request from 1.0
-framework: "1.0"
-repo: library
-project: Library
-client: shared
-type: feature
-status: active
-updated: 2026-08-12
-owners: [snaredla]
-files:
-  - library/app/api/servicerequest.php
-  - library/app/api/toga2.php
-  - togadesk/desk/includes/classes/class.ticket.php
-related:
-  - ./toga2-api-client-and-bridge.md
-  - ./app-class-placement-base-contracts.md
-  - ../../../clients/elite/features/desk-service-request-creation.md
----
-
-## Summary
-
-`App_Api_ServiceRequest` (`library/app/api/servicerequest.php`) is the shared 1.0-side class that
-turns a posted form into a **TOGa 2.0 Service Request** — it validates and normalises the posted
-values, resolves the related 2.0 records it needs, refuses a duplicate, and POSTs the Service
-Request with its nested units in a single request. All transport goes through
-[`App_Api_Toga2::send()`](./toga2-api-client-and-bridge.md); this class holds no 1.0 table and does
-no SQL.
-
-First consumer is the Elite "New Service Request" button in TOGa Desk (see
-[Elite desk Service Request creation](../../../clients/elite/features/desk-service-request-creation.md)),
-but the class itself is client-agnostic — the caller passes the API endpoint in.
-
-## Key files / entry points
-
-`abstract class App_Api_ServiceRequest` — public:
-
-- `buildFromPostedValues(array $postedValues, string $ticketUuid, ?string $overrideWithApiEndpoint = null): array`
-  — validates + normalises the modal post into the 2.0 payload array (throws on a validation
-  failure; the caller converts that into the UI message).
-- `searchTicketFromToga2(string $ticketUuid, ?string $overrideWithApiEndpoint = null)` — the
-  **duplicate guard**: does a Service Request already exist for this ticket?
-- `createServiceRequestInToga2(array $serviceRequest, ?string $overrideWithApiEndpoint = null)` —
-  the POST (parent + nested units).
-- `describeApiFailureMessage($response): string` — turns a 2.0 failure response into an
-  agent-readable message.
-
-Private: `isStateInCountry()`, `findContactUuidByEmailAddress()`, `cleanPostedValue()`.
-
-## How it works
-
-1. **Build** — `buildFromPostedValues()` trims/length-caps every posted value
-   (`cleanPostedValue()`), resolves the requester contact by email, checks the selected state
-   really belongs to the selected country, and assembles the parent payload plus one nested
-   `serviceRequestUnits` entry per line.
-2. **Duplicate guard** — `searchTicketFromToga2()` looks the ticket uuid up in 2.0 before creating
-   anything.
-3. **Create** — `createServiceRequestInToga2()` POSTs **parent + nested `serviceRequestUnits` in
-   ONE request**. Related records inside that payload resolve by **natural key** — the request type
-   by *name*, the item by *partNumber* — while **customer, state and ticket are matched by uuid**.
-4. The caller (TOGa Desk) maps the outcome to its own status code and writes the ticket
-   history/reply.
-
-## The failure-check contract — `empty($response->isSuccess)` is always safe
-
-This is the load-bearing fact behind three bugs fixed on 2026-08-12, and it is not obvious from the
-call site.
-
-`App_Api_Toga2::send()` (`library/app/api/toga2.php`, ~L432–450) **always returns a response object
-that carries `isSuccess`**:
-
-- it returns early **only** when `isSuccess` is true;
-- when `isSuccess` is false and `$throwExceptionOnApiError = false`, it falls through the retry loop
-  and ends at `return $response` — **a failure arrives as a return value, not an exception**;
-- if the response is not an object, or lacks the `isSuccess` property at all, it **throws**.
-
-Therefore anything `send()` hands back can be checked with `empty($response->isSuccess)` — including
-GETs. There is no "successful response without the property" case to defend against.
-
-**The bug class this prevents:** every helper here calls `send()` with
-`$throwExceptionOnApiError = false`, so a network blip, an auth failure or a 500 comes back as a
-*response*. Code that reads straight past it to `$response->data->{resource}` sees "no records" and
-concludes **"the thing does not exist"** — the most dangerous possible misreading for a lookup.
-
-## Fixed 2026-08-12 — three silent failures, one root cause
-
-| Lookup | Old behavior on API failure | Consequence |
-|---|---|---|
-| duplicate Service Request | returned `null` | read as "no duplicate exists" → **a second Service Request on a ticket that already had one** |
-| contact by email | returned `null` | read as "no contact exists" → **a duplicate contact created in 2.0** for someone 2.0 already held |
-| state-belongs-to-country | returned `false` | a blip told the agent *"the selected state does not belong to the selected country"* — a **false accusation of bad input** |
-
-`isStateInCountry()` now returns **`?bool` as a tri-state**: `true` confirmed, `false` a genuine
-mismatch, **`null` unconfirmed** (exception or empty result). The submission is refused in both the
-`false` and `null` cases — the difference is the **message**: only `false` blames the input, `null`
-says the check could not be completed. Do not collapse this back into a `bool`.
-
-## 2.0 API rules this class had to learn the hard way
-
-- **Naming `fields` on `GET /states` SUPPRESSES the nested country.** A plain request returns the
-  nested `country`; adding a `fields` list drops it. If a nested relation vanishes, suspect the
-  field list before suspecting the data.
-- **Post a state by UUID, never by code.** `WA` and `NT` each belong to **two** countries, and the
-  API matches on code alone. `States.countryId` has `isIdentifier = 0`, so the nested country cannot
-  disambiguate it either — the uuid is the only unambiguous handle.
-- **Natural-key resolution inside a nested write:** type by name, item by partNumber. Only
-  customer / state / ticket go by uuid.
-
-## Gotchas / known issues
-
-- **A uuid is environment-scoped.** Any flow that reads uuids from one 2.0 environment and posts
-  them to another will fail or, worse, resolve to a different record. Read and write against the
-  **same** endpoint — see the hardcoded-endpoint gotcha in the
-  [Elite desk feature](../../../clients/elite/features/desk-service-request-creation.md).
-- **This class extends nothing, deliberately.** Extending `App_Api` silently inherits the 1.0
-  fulfilment-vendor contract. See
-  [where a new App_ class goes](./app-class-placement-base-contracts.md).
-- **Credentials.** Elite's `CLIENT_UUID_ELITE` / `API_UUID_ELITE` / `API_SECRET_ELITE` are class
-  constants on `App_Api_Toga2` (`library/app/api/toga2.php`). Read them from source; never
-  reproduce the values. An API secret living in a git-tracked constant is a standing concern — see
-  the credentials gotcha on [the transport doc](./toga2-api-client-and-bridge.md).
-
-## Change history
-
-- 2026-08-12 — TRUE-80497: created `App_Api_ServiceRequest` as the shared 1.0→2.0 Service Request
-  provisioner. Recorded the `send()` failure contract (**`empty($response->isSuccess)` is always a
-  safe check, including on GETs**) and fixed **three** silent failures that all came from reading
-  past a failure response returned under `$throwExceptionOnApiError = false`: the duplicate-SR
-  lookup and the contact lookup both reported "does not exist" (allowing a second SR and a
-  duplicate contact), and the state/country check reported a genuine mismatch for an exception or
-  empty result. `isStateInCountry()` now returns `?bool` — `null` = unconfirmed, with its own
-  message; both `null` and `false` still refuse. Also recorded the 2.0 rules: `fields` on
-  `GET /states` suppresses the nested country; states must be posted by uuid (`WA`/`NT` are
-  ambiguous across countries and `States.countryId` has `isIdentifier = 0`); parent + nested
-  `serviceRequestUnits` post in one request with type/item resolved by natural key. (snaredla)

package/knowledge/clients/elite/features/desk-service-request-creation.md

@@ -1,136 +0,0 @@
----
-title: "Elite — \"New Service Request\" button on TOGa Desk 1.0 tickets"
-framework: "1.0"
-repo: togadesk
-project: TOGa Desk
-client: elite
-type: client-feature
-status: active
-updated: 2026-08-12
-owners: [snaredla]
-files:
-  - togadesk/desk/includes/controllers/modals/tickets/serviceRequest.php
-  - togadesk/desk/includes/controllers/actions/tickets/serviceRequest.php
-  - togadesk/desk/template/modals/tickets/serviceRequest.php
-  - togadesk/desk/includes/classes/class.ticket.php
-  - library/app/model/togadesk/ticket.php
-  - library/app/api/servicerequest.php
-  - dbchanges2/Client_Elite/2026-08-11a - EliteServiceRequestTicketUnique.sql
-  - test/@srija/Elite Testing/Service Requests/test_elite_desk_service_request.php
-related:
-  - ../../../1.0/apps/library/features/service-request-toga2-provisioning.md
-  - ../../../1.0/apps/togadesk/features/ticket-lifecycle.md
-  - ../../../1.0/apps/togadesk/workflows/standalone-test-scripts.md
-  - ./service-request-to-salesorder-pipeline.md
-  - ../profile.md
----
-
-## Summary
-
-TRUE-80497. Elite agents used to raise Service Requests **by hand, outside the desk**. A ticket that
-qualifies now shows a **"New Service Request"** button that opens a modal and creates the Service
-Request directly in **TOGa 2.0**, writing the resulting number back to the ticket history and as a
-reply.
-
-On a qualifying ticket the button **replaces** the existing **"New Part Request"** button — it is
-not an extra button. Every other Elite department keeps the parts flow untouched.
-
-## The gate — three conditions, one helper
-
-`App_Model_TogaDesk_Ticket::isEliteServiceRequestTicket(int $clientId, int $departmentId, ?string $ticketTypeValue): bool`
-(`library/app/model/togadesk/ticket.php`) is the single source of truth. It is `true` only when
-**all three** hold:
-
-| Condition | Constant |
-|---|---|
-| `tickets.clientid` = 163 (Elite) | `TOGADESK_CLIENT_ID__ELITE` |
-| `tickets.departmentid` = 299 (Elite Helpdesk – Contact Center) | `TOGADESK_DEPARTMENT_ID__ELITE_CONTACT_CENTER` |
-| custom field 88 "Ticket Type" = `Service Request` | `TOGADESK_CUSTOM_FIELD_ID__ELITE_TICKET_TYPE` + `ELITE_TICKET_TYPE__SERVICE_REQUEST` |
-
-The template, the modal controller **and** `Ticket::createEliteServiceRequest()` all call the same
-helper rather than repeating the three ids — re-checked server-side because the button being hidden
-is not a security control.
-
-## How it works
-
-1. **Modal controller** (`controllers/modals/tickets/serviceRequest.php`) re-checks the gate,
-   resolves the ticket's 2.0 uuid from `tickets.referenceId`, then runs its lookups against 2.0
-   (customer/contact, states, countries, request types, items, existing Service Request) and
-   renders `template/modals/tickets/serviceRequest.php`.
-2. **Action controller** (`controllers/actions/tickets/serviceRequest.php`) is a thin shim: it calls
-   `Ticket::createEliteServiceRequest($_POST)` and reroutes on the returned statuscode.
-3. **`Ticket::createEliteServiceRequest()`** (`class.ticket.php`) owns the desk half only — gate,
-   ticket lookup, history and reply. Validation, duplicate detection and the API calls belong to
-   [`App_Api_ServiceRequest`](../../../1.0/apps/library/features/service-request-toga2-provisioning.md).
-4. On success it writes a `TicketHistory` line (`Service Request created <number> (<type>, N units)`)
-   and adds a reply authored by `ELITE_DEFAULT_AGENT = 35876` (Agilant Helpdesk /
-   serviceops@togatech.com — the same author as the other machine-written replies on Elite tickets).
-   The reply passes the ticket's **current** status as `newStatus`, so creating a Service Request
-   does not silently move the ticket to *In Progress*.
-
-## Statuscodes: 1705 = success, 11 = failure
-
-`ELITE_SERVICE_REQUEST_STATUS__SUCCESS = 1705` is Elite's own success message row;
-`ELITE_SERVICE_REQUEST_STATUS__FAILURE = 11` is the generic "cannot add item" failure, with the
-detail written to the ticket history.
-
-**Two paths return 1705 without creating anything, and both are correct:**
-
-- the **duplicate guard** — a Service Request already exists for this ticket, so the desired end
-  state is already true. A second submit is a **duplicate-safe SUCCESS**, not an error.
-- a **create that succeeded but whose reply write failed** — the `addReply()` call is wrapped in
-  try/catch and the exception is deliberately swallowed, so a reply failure can never report a
-  successful create as a failure.
-
-## One Service Request per ticket (Elite only)
-
-Decided 2026-08-11. The application-level duplicate guard is not sufficient on its own — two
-simultaneous submissions can both pass it — so the rule is enforced in the database by a **UNIQUE
-index on `ServiceRequests.ticketId`**:
-`dbchanges2/Client_Elite/2026-08-11a - EliteServiceRequestTicketUnique.sql`.
-
-- Applied to **dev-sandbox**; **NOT yet applied to production**.
-- **Elite-only.** Other clients may legitimately raise more than one Service Request per ticket —
-  do not promote this index to a shared/Core migration.
-
-## Gotchas / known issues
-
-- **⚠ The endpoint is hardcoded to PRODUCTION, in TWO constants that must stay in sync.**
-  `Ticket::ELITE_SERVICE_REQUEST_CREATE_ENDPOINT` (`class.ticket.php`) and
-  `ELITE_SERVICE_REQUEST_LOOKUP_ENDPOINT` (the modal controller) are both
-  `https://api.togahub.com/v2`. They **must** match: the modal reads customer / state / item uuids
-  from the lookup endpoint and the create posts those same uuids, and **a uuid from one environment
-  does not exist in another**. The consequence is deliberate but sharp — **every environment
-  (alpha/beta/stage) writes Service Requests into production.** Change one constant and you must
-  change the other in the same commit.
-- **A 2.0 list route returns an array; a single-record response returns a bare object.** The modal
-  controller normalises this (wraps the object) — new lookups must do the same or they break on the
-  one-result case.
-- **`tickets.referenceId` is the bridge to 2.0.** No `referenceId` ⇒ no 2.0 ticket uuid ⇒ the modal
-  cannot proceed.
-- **The desk half had never been executed before 2026-08-12.** See the harness below.
-
-## Test harness
-
-`test/@srija/Elite Testing/Service Requests/test_elite_desk_service_request.php` (PHP **7.2**)
-exercises the desk half from the CLI: the button gate, `referenceId` resolution, the six modal
-lookups, the duplicate guard, and — under `--run` — a real create with history/reply verification.
-
-**It cannot test the permission gate.** `createEliteServiceRequest()` calls `isOwner()`, which reads
-the `$isAdmin` / `$liu` globals and **redirects + exits** when they are absent; the harness seeds
-them, so everything it proves is *after* the permission check. See
-[standalone test-script bootstrap](../../../1.0/apps/togadesk/workflows/standalone-test-scripts.md).
-
-## Change history
-
-- 2026-08-12 — TRUE-80497: built the Elite "New Service Request" button, modal, action and
-  `Ticket::createEliteServiceRequest()`, gated by
-  `App_Model_TogaDesk_Ticket::isEliteServiceRequestTicket()` (client 163 + department 299 + custom
-  field 88 = `Service Request`) and **replacing** the "New Part Request" button on those tickets.
-  Recorded the statuscode semantics (1705 success / 11 failure, with the duplicate guard and a
-  swallowed reply failure both returning 1705), the **one-Service-Request-per-ticket** rule enforced
-  by a UNIQUE index on `ServiceRequests.ticketId`
-  (`dbchanges2/Client_Elite/2026-08-11a`, dev-sandbox only — **not yet in production**), and the
-  ⚠ hardcoded production endpoint pair that makes every environment write to production. Added the
-  PHP 7.2 desk harness (`test/@srija/…/test_elite_desk_service_request.php`) for a path that had
-  never been executed. (snaredla)

package/knowledge/clients/elite/features/service-request-to-salesorder-pipeline.md

@@ -1,109 +0,0 @@
----
-title: "Elite — Service Request → Sales Order → status back to TOGa Desk 1.0"
-framework: "2.0"
-repo: worker2
-project: Worker
-client: elite
-type: client-feature
-status: active
-updated: 2026-08-12
-owners: [snaredla]
-files:
-  - worker2/Worker/Sync/ServiceRequest.php
-  - worker2/Worker/Sync/SalesOrderStatus.php
-  - _underscore/Model/Elite/ServiceRequest.php
-  - _underscore/Model/Elite/SalesOrder.php
-  - test/@srija/Elite Testing/Service Requests/test_elite_chain_toga2.php
-related:
-  - ./salesorder-netsuite-push.md
-  - ./desk-service-request-creation.md
-  - ../../../2.0/apps/api2/features/api-payload-interceptors.md
-  - ../../../2.0/apps/worker2/features/creating-worker-actions.md
-  - ../../../2.0/apps/worker2/features/netsuite-salesorder-outbound-push.md
-  - ../profile.md
----
-
-## Summary
-
-Once a Service Request exists in 2.0 (raised from
-[TOGa Desk](./desk-service-request-creation.md) or in supply2), an interceptor-driven chain turns it
-into a Sales Order and reports the order's status back to the 1.0 desk ticket:
-
-1. `_Model_Elite_ServiceRequest::postPost` queues
-   **`Sync/ServiceRequest/GenerateSalesOrderFromServiceRequest`** (worker2).
-2. That action generates the Sales Order (and, where vendors are resolvable, purchase orders),
-   moving the Service Request to the **Exception** stage when it cannot.
-3. `_Model_Elite_SalesOrder` queues the NetSuite push — a separate feature, see
-   [SalesOrder → NetSuite push](./salesorder-netsuite-push.md).
-4. **`Sync/SalesOrderStatus/PostSalesOrderStatusToTogadesk1`** writes the order status back as a
-   reply on the originating 1.0 desk ticket, with a dedupe guard so a repeated push does not
-   double-post.
-
-Every hop is registered data (`ApiPayloadInterceptors`) plus a queued action **string** — which is
-where the two durable hazards below come from.
-
-## ⚠ Renaming a worker action is a TWO-REPO, single-deploy change
-
-The 2026-08-12 rename `GenerateSalesOrder` → `GenerateSalesOrderFromServiceRequest` touches:
-
-- the **method** — `worker2/Worker/Sync/ServiceRequest.php`
-- the **dispatch string** — `\_Worker::runTask(action: 'Sync/ServiceRequest/GenerateSalesOrderFromServiceRequest', …)`
-  in `_underscore/Model/Elite/ServiceRequest.php:44`
-
-**They must land and deploy together.** If either ships alone, `runTask` dispatches to a name that
-no longer exists and **Sales Order generation stops silently** — `postPost` wraps `runTask` in
-try/catch + `error_log`, so the Service Request saves and nothing else happens, with no user-visible
-error. The same coupling applies to `Sync/SalesOrderStatus/PostSalesOrderStatusToTogadesk1`.
-
-Treat an action name like a database column rename: see the multi-producer rename rule in
-[creating worker actions](../../../2.0/apps/worker2/features/creating-worker-actions.md).
-
-## The NetSuite actions in this chain
-
-`Netsuite/SalesOrder/CreateNetSuite` (new order) and `Netsuite/SalesOrder/UpdateNetSuite` (changed
-order) are the real queued actions. **There is no `Netsuite/SalesOrder/Push`** — do not write that
-string into a migration, a test or a doc.
-
-## Verifying the chain — `test_elite_chain_toga2.php`
-
-`test/@srija/Elite Testing/Service Requests/test_elite_chain_toga2.php` (PHP 8.1) exists because the
-interceptor layer is a **single point of silent failure**: the Service Request is created, nothing
-downstream happens, and no error is raised anywhere. It asserts, in order:
-
-1. **every queued action string resolves to a real `class::method`** (the rename hazard above);
-2. the `_underscore` models queue **those same strings**;
-3. `ApiPayloadInterceptors` rows exist for **record 35 (service-requests)** and **record 14
-   (sales-orders)**, and — critically — that each row's **derived** method name
-   (`strtolower(prePostProcessing) . ucfirst(strtolower(httpMethod))`) actually **exists on the
-   model**. A registered row whose derived method is missing **500s every request on that route**;
-4. Sales Order / Purchase Order / NetSuite / desk-reply state after a run;
-5. a **repeat** status push, to prove the dedupe guard holds.
-
-Reusable beyond Elite — the same three checks (string resolves, producer matches, interceptor row +
-derived method exist) catch the entire silent-failure class. Background on the mechanism:
-[API payload interceptors](../../../2.0/apps/api2/features/api-payload-interceptors.md).
-
-## Gotchas / known issues
-
-- **Duplicated client-context helper, already drifted.** `getClientContextFromCore()` exists in both
-  `Worker/Sync/ServiceRequest.php` and `Worker/Sync/SalesOrderStatus.php`, and as
-  `getClientContext()` in `Worker/Netsuite/SalesOrder.php`. Only the **ServiceRequest** copy has
-  `ORDER BY id ASC` on the `Apis` credential query — the other two pick a **non-deterministic API
-  credential row** (Netsuite/SalesOrder.php even documents the flaw in a comment). **Not yet
-  extracted**; recorded as a known issue, see the
-  [outbound push doc](../../../2.0/apps/worker2/features/netsuite-salesorder-outbound-push.md).
-- **The interceptor registration is per-environment DATA.** "It didn't fire in <env>" is a `SELECT`
-  on that client's `ApiPayloadInterceptors`, never a code question.
-
-## Change history
-
-- 2026-08-12 — TRUE-80497/80501: documented the Elite Service Request → Sales Order → desk-status
-  chain. Recorded the **two-repo rename constraint** (the worker method in
-  `worker2/Worker/Sync/ServiceRequest.php` and the `runTask` dispatch string in
-  `_underscore/Model/Elite/ServiceRequest.php:44` must deploy together or Sales Order generation
-  stops silently), that the real NetSuite actions are `CreateNetSuite`/`UpdateNetSuite` (**no
-  `Push`**), and the drifted duplicate client-context helper (`ORDER BY id ASC` present in only one
-  of three copies → non-deterministic API credential). Added the PHP 8.1 chain harness
-  `test_elite_chain_toga2.php`, which verifies action strings resolve, producers match, and each
-  interceptor row's **derived** method name exists (a missing one 500s every request on the route).
-  (snaredla)