toga-ai 1.0.702 → 1.0.704

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

@@ -314,16 +314,21 @@ Parameters are stored **per client DB** but accessed **through the TOGa2 API**,
   checkbox `custbody_stocking_order`, read by `App_Api_Toga2::isTransferOrder()`/`isStockingOrder()`
   — **not** a dollar/hold heuristic. Full mechanics, PO bridges, and origin-location resolution:
   [NYCHH NetSuite → TransferOrders import](../../../clients/nychh/features/netsuite-transfer-order-import.md).
-- **Transfer-order integration clients (beyond NYCHH's stocking-flag routing).** GroWrk, Adyen, and Elite
-  run transfer-order integration (wrapper toggle reported as `IS_ENABLED_INTEGRATION_TRANSFER_ORDERS=true`)
-  and are the clients exercised by the shared `syncTransferOrderFromNetsuite` / `getTransferOrderItemsByUuid`
-  fixes (2026-08-30 above). These orders **masquerade as NetSuite sales orders** ($0, `holdInvoice` for
-  GroWrk) and are split into `TransferOrders` vs `SalesOrders` by `App_Api_Toga2::isTransferOrder()`.
-  The **routing SIGNAL is per-client**: NYCHH routes by the `custbody_stocking_order` stocking flag (above),
-  while GroWrk's own signal is `holdInvoice + total === 0` — do **not** assume one universal rule.
-  (⚠ Confirm the exact enable-flag name for GroWrk/Adyen/Elite against the wrappers: the stocking-flag const
-  `IS_ENABLED_TRANSFER_ORDER_STOCKING_FLAG_ROUTING` is documented as NYCHH-only, so
-  `IS_ENABLED_INTEGRATION_TRANSFER_ORDERS` is either a distinct toggle or a loose name for it.)
+- **Transfer-order integration is governed by TWO DISTINCT wrapper flags — a master enable switch and a
+  NYCHH-only classification-mode switch (do not conflate them).**
+  - **`IS_ENABLED_INTEGRATION_TRANSFER_ORDERS`** — the master "do transfer-order integration at all"
+    switch, defined in every `sync_togasupply_*.php` launcher. `true` for **GroWrk, Adyen, Elite, and
+    NYCHH**; `false` for the rest. These are the clients exercised by the shared
+    `syncTransferOrderFromNetsuite` / `getTransferOrderItemsByUuid` fixes (2026-08-30 above).
+  - **`IS_ENABLED_TRANSFER_ORDER_STOCKING_FLAG_ROUTING`** — a **separate classification-mode** switch,
+    **NYCHH-only** (`sync_togasupply_hh.php`), that makes `App_Api_Toga2::isTransferOrder()` classify by
+    the NetSuite `custbody_stocking_order` checkbox instead of the legacy rule.
+
+  These orders **masquerade as NetSuite sales orders** and are split into `TransferOrders` vs
+  `SalesOrders` by `isTransferOrder()`. The classification **SIGNAL is per-client**: **NYCHH** routes by
+  the `custbody_stocking_order` stocking flag (above); **GroWrk / Elite / Adyen** use the **legacy rule**
+  (`holdInvoice AND total === 0`). Do **not** assume one universal signal — the master enable is shared,
+  the classification mode is not.
 - `isParentCustomer` — `true` walks NetSuite child customers (`listChildCustomers`); `false`
   syncs the single customer. Prudential-EDI and the live Quad wrapper use `false`.
 - The original combined-array entries used `App_Api_Toga2::CLIENT_UUID_*` consts for Quad and
@@ -658,6 +663,22 @@ Parameters are stored **per client DB** but accessed **through the TOGa2 API**,
   `/locations` for the unit's own location before the write**, mirroring the existing item-line location
   create one level up. Shared/general fix (any client running serialized item receipts), surfaced by
   **GroWrk** location **1569**. Deployed.
+  - **The inventory-ADJUSTMENT unit path now has the SAME auto-create (fixed 2026-08-30) — it did not
+    before, which froze GroWrk.** `syncInventoryAdjustmentFromNetsuite`'s serialized-unit processing took
+    the unit's location from the inventory number's `custitemnumber_location` (the unit's own current
+    location, falling back to the adjustment line location), but — unlike `syncItemReceiptFromNetsuite` —
+    **never auto-created a missing warehouse**, so `POST /units` failed **EV-12** "unable to find a unique
+    match" on `location` (`searchCriteria c_netsuiteInternalLocationId=1596`; **0 rows** in
+    `Client_Growrk.Locations` for 1596), leaving `NETSUITE_EXECUTION_MODE_INVENTORY_ADJUSTMENTS` stuck at
+    `1-RUNNING`. **Fix:** capture the unit location's NAME (`$unitNetsuiteLocationName` from the
+    `custitemnumber_location` ref, carried in `$unitsToGet` as `netsuiteLocationName`) and, before **both**
+    unit-location reference points (the per-unit PUT-create path and the batch `POST /units` path),
+    `POST /locations` when the id is not already in `$lookupWarehouseByNetsuiteLocationInternalId` and a
+    name is present — same payload as the receipt sync (`name`, `c_netsuiteInternalLocationId`,
+    `locationType = WAREHOUSE_LOCATION_TYPE_UUID`, `isActive=true`, `allowReceiving`/`allowSending=false`),
+    then register it in the warehouse lookup. Guarded by `!isset(lookup[id]) && !empty(name)` so it fires
+    only for genuinely-missing locations and never duplicates. Shared 1.0 path — benefits all
+    serialized-adjustment clients.
 
 - **⚠ The exact api2 rejection detail lives in `Logs_<Client>.Api`, not `Logs.Event` (which TRUNCATES
   it).** When a section throws on an api2 non-success, `Logs.Event` records the error envelope but
@@ -737,6 +758,14 @@ Parameters are stored **per client DB** but accessed **through the TOGa2 API**,
 
 ## Change history
 
+- 2026-08-30 — **Inventory-adjustment serialized-unit path now auto-creates a missing unit warehouse
+  (`library`).** `syncInventoryAdjustmentFromNetsuite` took the unit's location from the inventory
+  number's `custitemnumber_location` but never created a missing warehouse (unlike
+  `syncItemReceiptFromNetsuite`), so `POST /units` failed EV-12 on `location` for GroWrk location **1596**
+  (0 rows in `Client_Growrk.Locations`), stuck `INVENTORY_ADJUSTMENTS` at `1-RUNNING`. Fix captures the
+  location NAME (`netsuiteLocationName`) and `POST /locations` before both the PUT-create and batch
+  `POST /units` paths — guarded `!isset(lookup[id]) && !empty(name)`, same payload as the receipt sync —
+  then registers it in the warehouse lookup. Shared path (all serialized-adjustment clients). (jcardinal)
 - 2026-08-30 — **Rebuilt GroWrk transfer-order integration + shared IF/inventory-adjustment fixes (all in
   `library/app/api/toga2.php`).** Root-caused the shared `syncTransferOrderFromNetsuite` **non-idempotency**
   to api2 never inlining `transferOrderItems` (`transfer-orders` has no `InherentRecordChildren` row) — the

package/package.json

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