toga-ai 1.0.244 → 1.0.246

package/knowledge/INDEX.md

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

package/knowledge/clients/prudential/INDEX.md

@@ -3,6 +3,7 @@
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
 | [Prudential: Dell ASN units PRE/POST interceptor (legacy key + flat tracking)](features/dell-asn-units-interceptor.md) | 2.0 | After the tracking-number bridge migration, the ASN unit route was renamed (`advance-shipping-notice-units` → `advance-shipping-notice-item-units`), so the inhe | _underscore/Model/Prudential/AdvanceShippingNotice.php, dbchanges2/Client_Prudential/2026-06-10 - AsnUnitsInterceptor.sql |
+| [Prudential: Dell LCH IOP transmissions (LCHRequestV2)](features/dell-lch-iop-transmissions.md) | 1.0 | Outbound order transmissions from the 1.0 worker tier to Dell's Lifecycle Hub (LCH) ITSM integration. | library/app/api/delllch.php, worker/crons/toga2/prudential/transmissions_to_dell.php, worker/crons/toga2/prudential_beta/transmissions_to_dell_india.php, worker/crons/toga2/prudential_beta/transmissions_to_dell_ireland.php, worker/crons/toga2/prudential_beta/transmissions_to_dell_usa.php |
 | [Prudential: Service Request Regional Address Validation](features/service-request-address-validation.md) | 2.0 | The `prePost` interceptor on `_Model_Prudential_ServiceRequest` validates `deliverToAddress` fields differently depending on which Prudential regional customer | _underscore/Model/Prudential/ServiceRequest.php |
 | [Prudential Order Shipped Email — transmit_ordershipped_updates_prudential.php](features/transmit-ordershipped-email.md) | 1.0 | Cron script that transmits "Order Shipped" updates to ServiceNow (RITM) and sends a shipped notification email to the end user. | worker/crons/toga2/prudential/transmit_ordershipped_updates_prudential.php |
 | [Prudential Financial](profile.md) | 2.0 | Prudential is a TOGA client whose device-fulfillment flow is driven by **Dell** via the Dell API (`Client_Prudential.Apis.id = 2`). |  |

package/knowledge/clients/prudential/features/dell-lch-iop-transmissions.md

@@ -0,0 +1,124 @@
+---
+title: "Prudential: Dell LCH IOP transmissions (LCHRequestV2)"
+framework: "1.0"
+repo: worker
+project: Worker
+client: prudential
+type: client-feature
+status: active
+updated: 2026-06-30
+owners: ["rgirish"]
+files:
+  - library/app/api/delllch.php
+  - worker/crons/toga2/prudential/transmissions_to_dell.php
+  - worker/crons/toga2/prudential_beta/transmissions_to_dell_india.php
+  - worker/crons/toga2/prudential_beta/transmissions_to_dell_ireland.php
+  - worker/crons/toga2/prudential_beta/transmissions_to_dell_usa.php
+related:
+  - ../profile.md
+  - dell-asn-units-interceptor.md
+---
+
+## Summary
+
+Outbound order transmissions from the 1.0 worker tier to Dell's Lifecycle Hub (LCH) ITSM
+integration. As of Dell's **May 2025 IOP spec update**, the deprecated `LCHRequest` endpoint
+was replaced by **`LCHRequestV2`** — a re-shaped payload with an explicit `requestEvent`
+field. All four Prudential transmission scripts (3 beta regional + 1 production) and the 1.0
+library client (`App_Api_Delllch`) were migrated. The OAuth and base-URL layer is unchanged;
+only the request route and payload schema changed.
+
+This is the **outbound** counterpart to the 2.0 inbound Dell ASN flow (see
+`dell-asn-units-interceptor.md`).
+
+## How it works
+
+- **Route:** `api/v2/request/LCHRequest` → **`api/v2/request/LCHRequestV2`** in all four
+  transmission scripts.
+- **Base URL / auth unchanged:** OAuth 2.0 `client_credentials` flow and base endpoints
+  (`iopv2/` prod, `iopv2np/` test) in `App_Api_Delllch::initialize()` are unchanged.
+- **Event model (the key change):** the new schema adds a required **`requestEvent`** field —
+  `'Create'` for new orders, `'Update'` for updates, `'Cancel'` for cancellations. This
+  replaces the old overloaded `svcOrderType` that previously signalled both the SR type AND
+  the event (`'CANCEL'`/`'UPDATE'`). In V2, `requestType` carries the SR type only
+  (Refresh / Breakfix / Reclaim / Bulk).
+- **Optional pre-submission validation:** `App_Api_Delllch::validateLCHRequestV2(array $payload, bool $isProduction = true): mixed`
+  calls `api/v2/validate/LCHRequestV2` — returns 200 on a valid payload, `422` with a
+  `problems[]` / `issues[]` array on schema violations. Useful for debugging a new payload
+  shape before sending a real order.
+
+### Payload schema migration (old → new)
+
+| Old (`LCHRequest`) | New (`LCHRequestV2`) |
+| --- | --- |
+| `svcOrderReqNumber` | `requestNumber` |
+| `svcOrderType` (overloaded: type + event) | `requestType` (Refresh/Breakfix/Reclaim/Bulk only) + `requestEvent` (Create/Update/Cancel) |
+| `svcOrderPriority` | `priority` |
+| `customerName` / `customerTelephone` / `customerEmail` / `employeeID` / `employeeType` (flat) | `employee{}` object: `employee.name` / `.phone` / `.email` / `.id` / `.type` |
+| `addresses[]` with `Ship To` element | `shipAddress{}` flat object |
+| `addresses[]` with `Return To` element | `returnAddress{}` flat object (`addressTo`, `careOf`, `address1`, `address2`, `city`, `state`, `postalCode`, `countryCode`) |
+| `returnItems[].itemType` / `.itemSerialNumber` / `.itemAssetTag` | `returnItems[].type` / `.serialNumber` / `.assetTag` |
+| `updateDate` (UPDATE events) | `deliveryDate` |
+| `updateReason` | `reason` |
+
+**Removed fields (no longer in the V2 schema):** `lob`, `msgID`, `deviceType`,
+`organizationalUnit`, `shippingMethod`, `profile`, `imageType`, `modeledAfter`,
+`hdRetentionIndicator`, `cidCoverage`, `cidCaseIndicator`.
+
+### SR-type / branch behavior
+
+- **LABEL SR type:** old code set `svcOrderType='RECLAIM'` mid-payload; new code sets
+  `requestType='Reclaim'` in the LABEL branch.
+- **RECLAIM:** `kitProfile='PACKAGING'` for all countries.
+- **THIN CLIENT guard removed:** the old `if deviceType == 'THIN CLIENT' then deviceType = 'LAPTOP'`
+  mapping was deleted — `deviceType` no longer exists in the V2 schema.
+
+### Country-specific logic (preserved across the migration)
+
+- **India:** `employee.type='NA'` hardcoded for all SR types. India device tier map
+  (`Knowledge Worker`→`Standard Notebook`, `Developer`→`Developer Notebook`) preserved in the
+  BREAKFIX / REFRESH / else branches.
+- **Ireland / USA:** `employee.type` initialised to `'STANDARD'` at base payload.
+  Brownfield/Apple device lookups via ServiceNow (`App_Api_Prudential::send()`) preserved.
+  Return address uses the `returnAddress{}` flat object built from
+  `$returnToAddress` / `$returnToAddressApple` arrays via `array_merge()` with an `addressTo`
+  override.
+
+## Deployment order (Prudential standard: beta before production)
+
+Beta scripts (`crons/toga2/prudential_beta/`) are migrated and verified **first**; only then
+is the production script (`crons/toga2/prudential/transmissions_to_dell.php`,
+`$inProduction = true`) touched. Beta scripts run against the beta DB
+(`db_beta_toga2core` / `db_client_prudential`) so failures never reach live customer orders.
+This is the established pattern for all Prudential script changes.
+
+## Verification plan
+
+1. Run beta scripts against the beta DB; check `Logs_Prudential` API table for the outbound
+   request body and Dell's 200/202 response.
+2. Optionally call `App_Api_Delllch::validateLCHRequestV2()` on a sample payload to pre-check
+   the schema before sending a real order.
+3. After beta passes a full order cycle (New → shipped), confirm the production script is live.
+
+## Gotchas
+- `requestType` is the SR type only (Refresh/Breakfix/Reclaim/Bulk) — do **not** put the event
+  there. Event signalling moved to the separate required `requestEvent` field
+  (Create/Update/Cancel). Conflating them is the easiest way to reproduce the old overloaded
+  `svcOrderType` bug under the new schema.
+- Dell deprecated `LCHRequest`; any script still POSTing to the old route will fail. All four
+  transmission scripts must point at `LCHRequestV2`.
+- The removed fields (e.g. `deviceType`, `lob`, `imageType`) will be rejected by V2 validation —
+  do not reintroduce them.
+
+## Change history
+- 2026-06-30 — Migrated all Prudential Dell transmissions (3 beta regional + production) and
+  `App_Api_Delllch` from deprecated `LCHRequest` to `LCHRequestV2` per Dell's May 2025 IOP
+  spec: re-shaped payload (employee/ship/return objects, renamed return-item keys), new
+  required `requestEvent` event field replacing overloaded `svcOrderType`, removed dropped
+  fields and the THIN CLIENT device guard, added `validateLCHRequestV2()` pre-submission
+  validation helper. Country-specific (India/Ireland/USA) device-tier and address logic
+  preserved. (rgirish)
+
+## Related docs
+- Prudential: Dell ASN units interceptor (inbound 2.0 counterpart).
+- Prudential profile.

package/knowledge/clients/prudential/profile.md

@@ -6,16 +6,19 @@ apps:
   - api2
   - dbchanges2
   - websocket
+  - worker
+  - library
 project: _Underscore
 client: prudential
 type: profile
 status: active
-updated: 2026-06-29
+updated: 2026-06-30
 owners: ["jcardinal", "rgirish"]
 files: []
 related:
   - features/dell-asn-units-interceptor.md
   - features/service-request-address-validation.md
+  - features/dell-lch-iop-transmissions.md
 ---
 
 ## Summary
@@ -33,6 +36,9 @@ order-status transmissions.
 - **Outbound (worker crons):** `transmissions_to_netsuite.php`, `transmit_ordershipped_updates_prudential.php`,
   `transmit_closecomplete_updates_prudential.php`, `transmit_order_delivered_updates_from_fedex_toga2.php`,
   `update_tracking_number_from_netsuite_to_toga.php`, `manually_insert_ASN.php`.
+- **Outbound (Dell LCH ITSM):** `transmissions_to_dell.php` (prod) + `prudential_beta/transmissions_to_dell_{india,ireland,usa}.php`
+  POST to Dell's LCH `LCHRequestV2` endpoint via the 1.0 `App_Api_Delllch` client. See the
+  Dell LCH IOP transmissions feature doc.
 
 ## Gotchas
 - Dell will not change their payload shape — see the Dell ASN units interceptor feature doc for the
@@ -46,5 +52,6 @@ order-status transmissions.
 
 ## Related docs
 - Dell ASN units interceptor.
+- Dell LCH IOP transmissions (LCHRequestV2, outbound 1.0).
 - 2.0 _underscore: Tracking-Number Bridge Migration.
 - features/transmit-ordershipped-email.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.244",
+  "version": "1.0.246",
   "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/sessions/2026-06-23-team-shared-sessions-jcardinal.md

@@ -1,69 +0,0 @@
----
-type: session
-slug: team-shared-sessions
-title: Team-shared sessions + skill discovery
-author: jcardinal
-repos: [_underscore]
-framework: "2.0"
-client: shared
-status: active
-created: 2026-06-23
-updated: 2026-06-23
----
-
-# Session: team-shared-sessions
-**Date:** 2026-06-23
-**Project/Repo:** toga-tech harness (team `claude` repo) — not an application repo
-**Task:** Make /session-save and /session-resume store sessions in the team knowledge repo (knowledge/sessions/) so one developer can save an in-progress session and another can resume it, with automatic push/pull, a way to list sessions, and manual delete of stale ones — plus a /team-skills discovery skill.
-
----
-
-## What WORKED
-- Added five subcommands to `knowledge.js` (committed to `_main`, `44f740d`): `session-save`, `session-list`, `session-show`, `session-delete`, `skills`. Verified: `node -c knowledge.js` passes; `skills --installed=d:/WWW/.claude/skills` correctly flags `worker2-action` as local-only; `session-list` empty + populated both render.
-- Key design win confirmed during exploration: `knowledge/sessions/` rides the existing `publish` git rails for free, AND `allDocs()` only walks `1.0/ 2.0/ standalone/ clients/`, so `validate`/`index` ignore `sessions/` with zero exemption code. `node knowledge.js validate` → "OK (24 repos)" with a session file present.
-- `session-list`/`show`/`delete` read from `origin/<branch>` via `git ls-tree`/`git show` after a `git fetch` — shows teammates' pushed sessions without touching the working tree. Verified working-tree fallback when origin has none.
-- All three `session-save` guard paths reject BEFORE any push: outside-dir → `ABORT_OUTSIDE_SESSIONS`; missing keys → `INVALID — missing frontmatter: ...`; planted `AKIA...` key → `SECRET — line N: AWS access key id`.
-- Rewrote `skills/session-save/SKILL.md` (team-by-default + local fallback) and `skills/session-resume/SKILL.md` (fetch-first; `latest`/`<slug-or-id>`/`list`/`delete <id>`; briefing names the author).
-- Created `skills/team-skills/SKILL.md` (read-only discovery; pairs with `/sync-team-skills`).
-- Updated `scripts/hooks/session-start.js`: time-boxed (3500ms) `teamSessions()` peek that prints available team sessions; fails silent offline. `node -c` passes; runs clean (silent when no sessions — correct).
-- Documented `type: session` + `knowledge/sessions/` in `knowledge/CONVENTIONS.md`.
-- Synced all skills to `d:\WWW\.claude\skills` via `node sync-skills.js d:/WWW` (9 skills incl. team-skills) and copied the updated hook locally.
-- Committed only the 6 intended files + new `team-skills/` to `_main` and pushed (had to `git stash push -- CLAUDE.md` first because of a pre-existing unstaged CLAUDE.md edit; popped it back after).
-
-## What did NOT work — DO NOT RETRY THESE
-- `git rebase origin/_main` failed with `error: cannot rebase: You have unstaged changes` because `CLAUDE.md` had a PRE-EXISTING (not-ours) modification in the team repo working tree. FIX that worked: `git stash push -- CLAUDE.md`, rebase+push, then `git stash pop`. Do NOT commit CLAUDE.md to "fix" this — that edit is not ours.
-- Do NOT treat `toga-tech/.claude/skills/` as the source of truth — it is untracked/gitignored (a local install). The COMMITTED source is the root-level `skills/`, `knowledge.js`, `sync-skills.js`, `scripts/hooks/`. Editing `.claude/` copies would not ship.
-
-## Not tried yet (candidates for next session)
-- Optional: `knowledge.js skills --write-readme` (or fold into `sync-skills.js`) to regenerate the stale README skill table from frontmatter automatically. Explicitly deferred this session.
-- End-to-end cross-developer resume has only been simulated locally (origin had no sessions during testing). Once this very session file is pushed, verify `/session-resume team-shared-sessions` from a fresh clone / another machine.
-- `session-list` does a network `git fetch` (6s timeout) on every call; the startup hook bounds it to 3.5s. Consider a `--no-fetch` fast path for the hook if startup latency is felt in practice.
-
-## Current file state
-| File | Status | Notes |
-|------|--------|-------|
-| toga-tech/knowledge.js | Modified, committed `44f740d` | +session-* and skills subcommands, shared `pushStaged()` helper |
-| toga-tech/skills/session-save/SKILL.md | Modified, committed | team-by-default save + push, local fallback |
-| toga-tech/skills/session-resume/SKILL.md | Modified, committed | fetch-first; latest/slug/list/delete; author in briefing |
-| toga-tech/skills/team-skills/SKILL.md | Created, committed | new discovery skill |
-| toga-tech/scripts/hooks/session-start.js | Modified, committed | team-session startup peek |
-| toga-tech/knowledge/CONVENTIONS.md | Modified, committed | type: session schema + sessions/ layout |
-| d:/WWW/.claude/skills/* + hooks/toga/session-start.js | Synced locally | for immediate local use (gitignored install) |
-| toga-tech/CLAUDE.md | Pre-existing unstaged edit (NOT ours) | left untouched; was stashed/popped during push |
-
-## Decisions made
-- Store sessions under `knowledge/sessions/` (not a new top-level dir) — reuses `publish` staging + `npx toga-ai` distribution with no new git plumbing. Rejected: separate branch per session (merge complexity), separate sync mechanism.
-- One file per session named `YYYY-MM-DD-<slug>-<author>.md` — author suffix prevents slug collisions between developers.
-- Team-by-default save; local `~/.claude/session-data` only as offline/no-clone fallback. (User decision.)
-- Cleanup = manual delete + age flagging (`STALE` > 14 days); no auto-deletion. (User decision.)
-- SessionStart hook surfaces team sessions with a timeout-guarded fetch. (User decision.)
-- Sessions are NOT knowledge docs: they get their own lightweight frontmatter + secret scan in `session-save`, and are deliberately excluded from `validate`/`index` (free, via `allDocs()` scope).
-
-## Blockers
-none
-
-## Exact next step
-> From a fresh clone or another machine, run `/session-resume team-shared-sessions` and confirm it fetches and renders this session's briefing — the real cross-developer round-trip that was only simulated locally this session.
-
----
-_Saved by /session-save on 2026-06-23_