toga-ai 1.0.950 → 1.0.951

package/knowledge/1.0/apps/worker/features/uma-student-sync.md

@@ -43,7 +43,11 @@ UMA students reach our system through a **daily SFTP file**, not an API. `togade
 
 Nothing is sent at escalation time — an escalated ticket waits for the next run.
 
-**Ticket sync schedule** (`schedules/cron.worker.togadesk.json`, server time = Central): **once per day** — Mon–Thu `0 15 * * 1-4`, Fri `30 11 * * 5`, Sat `0 17 * * 6`, Mon `0 1 * * 1`. No Sunday run (~32 h gap Sat 17:00 → Mon 01:00). Runs take ~2 min. Fix if asked: restore an hourly (or tighter) range.
+**Ticket sync schedule** (`schedules/cron.worker.togadesk.json`, server time = Central): **once per day**, 4 separate entries kept on purpose (do not merge):
+- Mon–Thu `30 7 * * 1-4` (7:30 AM CT) — UMA wants escalations in the morning (Jonathan, TRUE-82504). **Pending deploy as of 2026-10-05**; prod still runs `0 15 * * 1-4` until the next worker deploy.
+- Fri `30 11 * * 5`, Sat `0 17 * * 6`, Mon `0 1 * * 1`.
+
+No Sunday run (~32 h gap Sat 17:00 → Mon 01:00). Runs take ~2 min. Near-real-time escalation = a separate decision (restore an hourly range).
 
 ## Health check (read-only prod, env `legacy`)
 
@@ -63,9 +67,10 @@ Nothing is sent at escalation time — an escalated ticket waits for the next ru
 - **PII.** Files hold DOB and SSN last 4. When investigating, pull only dates/file names from FileLog, never `fileData`.
 - **Hardcoded credentials — treat as leaked, rotate.** SFTP login is hardcoded in `sync_uma_customers.php`; the Ivanti API key is hardcoded in `library/app/api/uma.php`. Do not copy them anywhere.
 - Does not call `App_Database::closeConnections()`.
-- **Escalations batch once a day.** Cron entry names still say windows like "9:00–21:00" — misleading; the cron expressions are single hours. Cause: `d53e1ab35` (TRUE-61196, 2025-03-10, UTC→CST) replaced hourly ranges (`0 3-15 * * 2-5`, `0 0-15 * * 6`, `0 0-17 * * 0`, `0 1-15 * * 1`) with single hours; later TZ shifts `9732b7b50` (TRUE-74692) and `9f16ad1de` (TRUE-77365) kept single hours.
+- **Escalations batch once a day.** Only `schedule` controls run time; `name` is cosmetic (`ebs/cron.worker.php` uses it only in error messages). Old names said hourly windows like "9:00–21:00" and the Mon 1 AM entry was labeled "Sun" — TRUE-82504 renamed all 4 to their real CT/ET times (pending deploy as of 2026-10-05). Keep names in sync when changing a schedule. Cause of once-a-day: `d53e1ab35` (TRUE-61196, 2025-03-10, UTC→CST) replaced hourly ranges (`0 3-15 * * 2-5`, `0 0-15 * * 6`, `0 0-17 * * 0`, `0 1-15 * * 1`) with single hours; later TZ shifts `9732b7b50` (TRUE-74692) and `9f16ad1de` (TRUE-77365) kept single hours.
 - **`tickets.dtSynced` is not the send time.** On push the code sets it to the ticket's created timestamp; some rows show the run time instead.
 
 ## Change history
 - 2026-09-28 — Documented (TRUE-82352 investigation). Open incident: no UMA file since 2026-09-20; runs 9-21..9-27 clean with empty SFTP; togadesk worker instance changed that day but SFTP login still works from the new box — likely UMA stopped uploading, awaiting UMA confirmation. No wrong deactivations; new students and their tickets missing since 9-20. (mhammontree)
 - 2026-10-05 — TRUE-82504 escalation-batch investigation: escalations reach UMA's Ivanti once a day (prod: tickets created 9/29 20:17 → 9/30 08:21 all sent 9/30 15:01–15:02 CT; repeated 10/1). Findings delivered, no fix requested. (mhammontree)
+- 2026-10-05 — TRUE-82504 follow-up: Mon–Thu ticket sync moved `0 15` → `30 7` (morning escalations, per Jonathan); all 4 entry names fixed to real times. Branch TRUE-82504, not deployed. (mhammontree)

package/package.json

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