toga-ai 1.0.562 → 1.0.563

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/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)
+- **library** (Library) _(framework core)_ — 17 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)
 - **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,10 +2,8 @@
 
 | 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 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 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.562",
+  "version": "1.0.563",
   "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)