toga-ai 1.0.1052 → 1.0.1053

package/knowledge/2.0/apps/worker2/INDEX.md

@@ -56,6 +56,7 @@
 | [The two sandbox-dev worker2 environments (and how `_underscore` reaches a worker box)](features/sandbox-dev-worker-environments.md) | Two Elastic Beanstalk environments both call themselves "sandbox-dev" worker, they run **different `ENVIRONMENT` values**, they clone **different `_underscore` |
 | [Service Request → Sales Order → Purchase Order generation (Sync/ServiceRequest)](features/service-request-sales-order-generation.md) | Worker `_Worker_Sync_ServiceRequest` that turns a Service Request → Sales Order → one PO per vendor for any tenant; open for the SR→SO→PO chain, its interceptor |
 | [SSO Stability Monitor (Monitor/Operations/SsoStability)](features/sso-stability-monitor.md) | Reporter cron that GETs the saml `/healthcheck` and pushes an SSO heartbeat to a OneUptime monitor; open when working on the SSO uptime probe, its tokens, or it |
+| [Startech Entitlement Provisioning Monitor (Monitor/Startech/EntitlementProvisioning)](features/startech-entitlement-provisioning-monitor.md) | OneUptime monitor that every new entitlement on a Startech-trait client got a 2xx `/sku` call; open when it alarms or when a new client adopts `_Trait_Startech_ |
 | [Startech Webhook Handler (worker2)](features/startech-webhook-handler.md) | Inbound Startech (Easeedesk) webhook handler that creates/updates the matching TOGA 2.0 ticket; open for the webhook flow, its payload, or ticket-type/stage res |
 | [Stranded WorkerJobs (deploy-window job loss) and how to repair them](features/stranded-worker-jobs.md) | Jobs queued while worker2 restarts are dropped silently with no retry and no alert; open when a cron "never ran" or a webhook vanished. |
 | [Talos Meeting-Notes Integration & Token Auto-Refresh (consumer)](features/talos-meeting-notes-integration.md) | Consumer side of Talos: the endpoints, DevCore assistant, and JWT auto-refresh a worker2 dev tool needs to query the meeting-notes corpus; open when a tool must |

package/knowledge/2.0/apps/worker2/features/startech-entitlement-provisioning-monitor.md

@@ -0,0 +1,40 @@
+---
+title: Startech Entitlement Provisioning Monitor (Monitor/Startech/EntitlementProvisioning)
+framework: "2.0"
+repo: worker2
+project: Worker
+client: shared
+type: feature
+status: active
+updated: 2026-10-16
+owners: ["snaredla"]
+files:
+  - worker2/Worker/Monitor/Startech.php
+  - _underscore/Trait/Startech/Entitlement.php
+related:
+  - clients/pcmaticb2b/features/startech-entitlement-provisioning.md
+  - 2.0/apps/worker2/features/all-client-email-queue-monitor.md
+  - 2.0/apps/worker2/features/oneuptime-worker2-monitoring.md
+---
+
+OneUptime monitor that every new entitlement on a Startech-trait client got a 2xx `/sku` call; open when it alarms or when a new client adopts `_Trait_Startech_Entitlement`.
+
+## Summary
+
+`_Worker_Monitor_Startech::EntitlementProvisioning()` (cron `*/5`) is a push reporter. Why: provisioning fires once in `postPost` and failures only reach `error_log` ([provisioning doc](../../../../clients/pcmaticb2b/features/startech-entitlement-provisioning.md)). Scope = Startech entitlement clients only (developer decision, TRUE-82785) — not every client's entitlement errors, not the 1.0 RetailServices sync.
+
+## How it works
+
+1. **Clients detected at runtime:** `Core.Clients` → `_Model_<Client>_Entitlement` file exists + `class_uses` contains `_Trait_Startech_Entitlement`. Today only Pcmaticb2b. A new client using the trait is covered with no code change.
+2. **Hosts** per client from Core `DatabaseHosts`, same pattern as [EmailQueue](./all-client-email-queue-monitor.md); log DB registered under its real name, no alias.
+3. **Window:** entitlements with `dtCreated` 10 min to 7 days ago.
+4. **Match:** in `Logs_<Client>.Api`, a row `direction='OUT'`, `method='POST'`, `route='/sku'`, 2xx, `dtStamp` within -60s/+120s of `Entitlements.dtCreated`, and `requestPayload` `customerID` = `Contacts.c_startechUserId`. One Api row confirms one entitlement only.
+5. **Tokens:** `HIGH` = a miss under 24h old; `DEGRADED` = an older miss in the 7 days, or a client could not be read; `status=error` = no client checkable, or no client uses the trait.
+
+OneUptime import JSON: `test/@Bala/monitors/monitor-import-startech-entitlement-provisioning.json` (not committed).
+
+## Gotchas
+
+- Compare `customerID` as string — the logged payload has it sometimes quoted, sometimes int.
+- Keep the `Api` query on a narrow `dtStamp` window (`Api_dtStamp_IDX`, about 118 rows). A route-only scan uses `Api_method_IDX` (133k rows). Never range-scan Core `Logs.Api` over months — it times out. `Logs.Event` keeps only about 7 days.
+- `c_startechUserId` on the contact does not prove this entitlement was provisioned — see gotcha in the provisioning doc.

package/knowledge/INDEX.md

@@ -22,7 +22,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 ## 2.0 framework
 
 - **_underscore** (_Underscore) _(framework core)_ — 101 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
-- **worker2** (Worker) — 88 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
+- **worker2** (Worker) — 89 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 26 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 22 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)
 - **toga2-supply** (TOGa Supply) — 9 doc(s) → [2.0/apps/toga2-supply/INDEX.md](2.0/apps/toga2-supply/INDEX.md)

package/knowledge/clients/pcmaticb2b/features/startech-entitlement-provisioning.md

@@ -5,7 +5,7 @@ project: TOGa
 client: pcmaticb2b
 type: client-feature
 status: active
-updated: 2026-09-16
+updated: 2026-10-16
 owners: [snaredla]
 files:
   - _underscore/Trait/Startech/Entitlement.php
@@ -79,6 +79,9 @@ Runnable harness: `test/@srija/Startech Testing/PC Matic B2B/test_e2e_pcmaticb2b
 - **Silent failure.** On any error the trait `error_log`s and returns — no exception. If creds or endpoint are wrong, provisioning fails invisibly. Check `error_log` / the OUT log.
 - **`/sku` must be an array**, and `customerID` must be capital-D.
 - **One-way, POST-only.** No `postPut` — an entitlement created/updated through any non-POST path (or the `syncWithToga` PUT write-back) does not (re)register the SKU.
+- **Works in prod.** Every `/v2/entitlements` POST since 2026-08-14 got `/sku` 200. 43 entitlements from 2025-10 to 2026-07 (before the July fix) were never provisioned. Alerting: [provisioning monitor](../../../2.0/apps/worker2/features/startech-entitlement-provisioning-monitor.md).
+- **`c_startechUserId` is not a per-entitlement signal.** Entitlements 105 (2026-08-28) and 106 (2026-08-31) were created with no `/v2/entitlements` POST and no OptimumDesk call, but their contacts already had the id. Open: tests, or a second create path that skips Startech. Prove provisioning with the `OUT /sku` log row instead.
+- **OUT log query:** filter by a narrow `dtStamp` window (uses `Api_dtStamp_IDX`); logged `customerID` is sometimes string, sometimes int.
 - **Config drift across envs.** All three env inis must carry `[startechPcmaticb2b]`; a missing section means `_Config::startechPcmaticb2b()` returns falsy and the trait bails.
 
 ## Related

package/package.json

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