toga-ai 1.0.926 → 1.0.928

package/knowledge/1.0/apps/library/features/toga2-api-client-and-bridge.md

@@ -6,7 +6,7 @@ project: Library
 client: shared
 type: feature
 status: active
-updated: 2026-09-21
+updated: 2026-10-01
 owners: [jcardinal, mhammontree, bala]
 files:
   - library/app/api/toga2.php
@@ -23,6 +23,7 @@ related:
   - ../../worker/features/netsuite-togasupply-per-client-sync.md
   - ../architecture.md
   - ./error-capture-1-0.md
+  - ../../../clients/wje/features/oneuptime-ticket-writes-monitor.md
   - ../../../clients/elite/features/togadesk-service-request-intake.md
 ---
 
@@ -145,7 +146,9 @@ A large bi-directional sync gated by **two checkpoint parameters** stored in 2.0
 
 Signature takes `$integrationType` (`TICKETS` or `REPAIR_ORDERS`) plus **seven independent enable flags** and an optional `$monitorTogadeskDepartmentIds[]`:
 - **2.0 → TOGaDesk** (`$isEnabledToga2ToTogadeskIntegration`): pages 2.0 `/tickets` and `/ticket-notes` changed since the checkpoint; routes each to `syncToga2TicketIntoTogadesk1{RepairOrder|Ticket}` by `$integrationType`. Per-ticket exceptions are caught and sent to Sentry so one bad ticket doesn't abort the batch.
-- **TOGaDesk → 2.0** (`$isEnabledTogadeskToToga2Integration`): queries the 1.0 `db_togadesk` DB directly (SQL over `repair_orders`/`repair_order_history` or `tickets`/`tickets_replies`/`comments`, using `GREATEST(...)` of reply/comment timestamps) for the client's department(s), then calls `syncTogaDesk1{RepairOrder|Ticket}IntoToga2Ticket($id)`.
+- **TOGaDesk → 2.0** (`$isEnabledTogadeskToToga2Integration`): queries the 1.0 `db_togadesk` DB directly (SQL over `repair_orders`/`repair_order_history` or `tickets`/`tickets_replies`/`comments`, using `GREATEST(...)` of reply/comment timestamps) for the client's department(s) — only the ones the cron passes (`$monitorTogadeskDepartmentIds`) — then calls `syncTogaDesk1{RepairOrder|Ticket}IntoToga2Ticket($id)`.
+  - **Link = `referenceId`.** `tickets.referenceId` = 2.0 ticket uuid; `tickets_replies.referenceId` / `comments.referenceId` = 2.0 ticket-note uuid. Written back **only after a successful POST**. Rows created by the 2.0 → 1.0 direction already carry it. So NULL/`''` `referenceId` = not (yet) in 2.0 — the basis of the [WJE ticket-writes monitor](../../../clients/wje/features/oneuptime-ticket-writes-monitor.md).
+  - A reply with a blank message falls back to `newstatus`; if still PHP-empty (NULL, `''`, `'0'`) it is skipped and never gets a `referenceId`. Comments are always sent.
 - Five further one-way 2.0 → TOGaDesk sub-syncs, each its own flag: Contacts→People, Items/Units→Assets, Predefined-Replies→TicketsPr, Ticket-Teams→Groups, Ticket-Categories→Category/Subcategory/Items.
 - Finishes by PUT-ing both checkpoint parameters back to 2.0.
 
@@ -167,6 +170,7 @@ Signature takes `$integrationType` (`TICKETS` or `REPAIR_ORDERS`) plus **seven i
 - **Two unrelated `sync_togasupply_<client>.php` families.** Files under `worker/crons/toga2/netsuite/` are the **NetSuite supply importer** (`require` the common engine). Files under `worker/crons/toga2/<client>/` (e.g. `aig/`, `wje/`) are this **bridge** (`syncWithToga`/`syncWithTogadesk`). Same filename, different integration, different parameter keys — they coexist harmlessly. Confirm which folder before editing.
 - **`syncWithToga` and the bridge build SQL by hand** with `App_Database::sqlEscape()` rather than the `App_Model` layer; follow the surrounding escaping discipline when modifying.
 - **Per-record error isolation** in the TOGaDesk sync is via `try/catch` → `\Sentry\captureException`; a thrown exception elsewhere (transport, checkpoint read) still aborts the whole run.
+- **⚠ A failed ticket is never retried.** After a per-ticket exception the run still advances `TOGA_LAST_TICKET_INTEGRATION_DATETIME` past it, so the row stays unsent until someone touches the ticket again (new reply) or the checkpoint is moved back. A checkpoint-freshness check reads healthy through this — monitor NULL `referenceId` instead.
 - **Naming `fields` can SUPPRESS a nested relation that a plain request returns.** Observed 2026-08-12 on `GET /states`: a bare request comes back with the nested `country`, but adding a `fields` list drops it. This is the mirror image of the reverse-hasMany rule below — when a nested object you expected is missing, suspect the field list before the data.
 - **A reverse hasMany collection is only returned if you add it to the fetch `fields` whitelist.** The `/contacts` fetch requests an **explicit** `fields` list from the 2.0 metadata API; a reverse hasMany collection (e.g. `contactEmailAddresses.emailAddress`) is **not** returned unless added — so consuming a related collection means editing **both** the fetch field list **and** the consuming code. (The general 2.0-side metadata behavior — reverse relations resolved via the child model's `FOREIGNKEY_MODEL` and named as the camelCase plural of the child model — is a framework-level fact captured separately.)
 - **⚠ Depth alone does NOT return every reverse-hasMany collection — `GET /sales-orders` at depth 4 omits `itemFulfillmentItems` and `invoiceItems`.** Verified 2026-08-17 against prod `Logs_Compass.Api` responses (no fields whitelist): a depth-4 sales-order GET returns `salesOrderItems` and the **PO-link bridge** collections (`salesOrderItemPurchaseOrderItems`, `purchaseOrderItemSalesOrderItems`) but **not** `itemFulfillmentItems` or `invoiceItems`. So any importer code that guards on `$salesOrderItem->itemFulfillmentItems` / `->invoiceItems` from that GET is a **silent no-op** — same reverse-hasMany trap as above, with a concrete consequence: the NetSuite SO renumber fix keys off a recorded "could-not-delete" set instead of trusting those collections (see [per-client sync](../../worker/features/netsuite-togasupply-per-client-sync.md)).
@@ -180,6 +184,7 @@ Signature takes `$integrationType` (`TICKETS` or `REPAIR_ORDERS`) plus **seven i
 - **Pre-existing (low severity, out of scope): a raw-vs-escaped comparison causes a redundant UPDATE every sync.** At the update path (~line 8584) `syncContactToToga1Customer` compares `$existingCustomer['emailAddress'] !== $emailAddress` — the DB value from `App_Database::fetchRow()` is **unescaped**, while `$emailAddress` has already been through `App_Database::sqlEscape()`. For any value containing `'`, `"` or `\` the two can **never** compare equal, so that column is rewritten on **every** run. Same pattern applies to `businessName` and `phoneNumber` just above. **Predates TRUE-79401**, is a redundant write (not data loss), and was deliberately left out of that ticket's scope — recorded here so a future reader knows it is known.
 
 ## Change history
+- 2026-10-01 — Documented the `referenceId` link/write-back, blank-reply skip rule, and that a per-ticket failure advances the checkpoint (never retried). (mhammontree)
 - 2026-09-21 — Recorded a pre-existing committed JWT (dev/NYCHH token) at `toga2.php:641` inside `send()` (the sync call path); flagged to rotate + delete, location-only. (jcardinal)
 
 ## Related

package/knowledge/2.0/apps/dbchanges2/architecture.md

@@ -6,7 +6,7 @@ project: Database Changes
 client: shared
 type: architecture
 status: active
-updated: 2026-09-25
+updated: 2026-10-01
 owners: [jcardinal, mhammontree, bala, ajean]
 files:
   - Core/
@@ -238,7 +238,7 @@ This lifecycle is automated by a local browser tool — see the [TOGa 2.0 Client
 
    **Every UUID must be freshly, fully random — never derive one from another.** Do **not** take a known uuid and bump a digit (`…-0001`, `…-0002`, …), copy-and-tweak, or otherwise pattern them. When a file needs several literals, generate each one independently at random. (Patterned uuids are guessable and defeat the uniqueness guarantee.) The one intended exception is a fan-out `Client/` grant, which **reuses the same** literal per row across tenants on purpose for safe rollback — deliberate reuse, not incrementing (see the feature doc).
 
-   One earlier migration (`Core/2026-05-08 … CronJobs_WorkerCleanup_insert`) used `UUID()` — that is a known violation, not a precedent to copy. First applied correctly in `Core/2026-07-21b - Insert - SprintLockScheduled CronJob.sql`.
+   One earlier migration (`Core/2026-05-08 … CronJobs_WorkerCleanup_insert`) used `UUID()` — that is a known violation, not a precedent to copy. First applied correctly in `Core/2026-09-29a - Record sprint and design CronJobs.sql` (new rows 83–86 carry pre-generated v4 literals; the recorded prod rows keep their existing prod uuids, which predate this rule).
 7. **Guard every registration/seed insert with `NOT EXISTS` (or `INSERT IGNORE`).** Rows that register platform behavior — `ApiPayloadInterceptors`, `Core.RecordFields`/`CustomRecordFields`, cron jobs, ACL rows — must be inserted only if not already present. An **unguarded** registration is not merely non-idempotent: on a fresh environment it can run **alongside a second migration that registers the same behavior**, producing a **double registration** (e.g. two interceptor rows for the same record → the interceptor fires twice). A real instance: the Rate WH `prePost` interceptor is registered unguarded in `Client_Rate/2026-07-15 - PreInterceptor.sql` (record 191, `minDepth NULL`); a second guarded registration would have double-fired it. See `clients/rate/features/whole-home-warranty-purchase-guard.md`.
 8. **Never reference a database other than the folder's own target.** No `Core.Table` in a `Client_<Name>/` file, no `Client_X.Table` in a `Core/` file, and **no database qualifier at all** in the fan-out folders (`Client/`, `Logs_Client/`, `_modules/`). These databases are on **separate production clusters**; the query works locally and dies in production. Resolve foreign ids with a hardcoded v4 UUID literal or an in-database slug/natural key, or split the work into one file per database folder. See *Database isolation* above — enforced by the `dbchanges2-cluster-isolation` hook.
 9. **Inserting into `Core.Records` or `Core.RecordFields`? ASK the developer for the next `id`** (the developer takes it in Tools → Developers → Central IDs — the source of truth; never guess from MAX(id), branches hold unreleased ids). These are the **only two tables on the platform with team-maintained primary keys**. Write the assigned `id` as an explicit literal — **never** let `AUTO_INCREMENT` assign it. Conversely, **always hardcode** these `id`s where they are referenced, including in foreign keys (`recordId`, `recordFieldId`) from other databases. See *`Core.Records` / `Core.RecordFields`* above.

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

@@ -11,14 +11,14 @@
 | [ClickUp Connectivity Watchdog](features/clickup-connectivity-watchdog.md) | Cron watchdog that emails when the ClickUp integration goes silent in business hours; open when touching ClickUp webhook health or `_Worker_Clickup_Health`. |
 | [ClickUp Custom-Field Conventions (constant IDs, runtime option values, Task Type migration)](features/clickup-custom-field-conventions.md) | How worker2 code must reference ClickUp custom fields; open before reading/writing any ClickUp custom field or touching the Task Type migration. |
 | [ClickUp Design Sprint Automation (Final Design Outcome)](features/clickup-design-sprint-automation.md) | `_Worker_Clickup_Design` drives the design-sprint workflow in ClickUp (FDO default on create, spawn iteration / complete task on Final Design Outcome, daily rev |
-| [ClickUp General Automation (Sub-Environment reservation, Has UI / Has Code roll-ups)](features/clickup-general-automation.md) | `_Worker_Clickup_GeneralAutomation` reacts to ClickUp custom-field changes on a Task; open when working on sub-environment reservation or Has UI / Has Code roll |
+| [ClickUp General Automation (Sub-Environment reservation, Has UI / Has Code, review-field reset)](features/clickup-general-automation.md) | `_Worker_Clickup_GeneralAutomation` keeps QA/QC fields consistent on ClickUp field/status changes (sub-environment reservation, Has UI / Has Code, review-field |
 | [ClickUp GitHub-tab Auto-linking & Ticket-id Branch Naming](features/clickup-github-autolink.md) | How ClickUp surfaces branches/PRs/commits in a ticket's GitHub tab and the branch/PR-title naming that triggers it; open when naming branches for ticket work or |
 | [ClickUp Project & Opportunity Multi-List Routing](features/clickup-project-routing.md) | Routes ClickUp tasks into secondary multi-list memberships by custom-field values; open for opportunity/epic routing, the stage-is-a-list constraint, or webhook |
 | [ClickUp Rich-Text Custom Fields via Quill Delta (API)](features/clickup-richtext-api.md) | How to write formatted text into a ClickUp text/long-text custom field via the undocumented `value_richtext` Quill Delta key; open when a richtext ClickUp field |
 | [ClickUp Subtask Activity → Parent Opportunity/Epic Comments](features/clickup-subtask-activity.md) | Mirrors subtask status/comment activity up to its top-level Opportunity/Epic as one comment; open for the subtask fan-out, its dedup ledger, or structural ances |
 | [ClickUp Task Description Fluffer (Talos KB Investigation)](features/clickup-task-fluffer-talos.md) | Async worker that "fluffs" a new ClickUp task by running its name+description through the Talos `dev-core` KB agent and writing the report back; open for the fl |
 | [ClickUp Webhook Health Monitor → OneUptime (Monitor/Clickup/CheckWebhook)](features/clickup-webhook-health-monitor.md) | worker2 cron that checks the team's ClickUp webhook subscriptions and pages via a OneUptime Incoming-Request monitor; open when tuning the ClickUp webhook alarm |
-| [ClickUp Work Type Automation (Committed / Conditional / Stretch)](features/clickup-work-type-automation.md) | Auto-maintains each ClickUp task's Work Type (Committed/Conditional/Stretch) from its dependencies, status, and due date, and sets new-task defaults on taskCrea |
+| [ClickUp Work Type Automation (Committed / Conditional / Stretch)](features/clickup-work-type-automation.md) | Auto-maintains each ClickUp task's Work Type (Committed/Conditional/Stretch) from its dependencies, status, and due date, and sets sprint-list defaults (Work Ty |
 | [worker2 Codeception integration tests (2.0 test-framework pilot)](features/codeception-integration-tests.md) | First 2.0 app-level automated test suite: Codeception 5 / PHPUnit 11 in worker2 (pilot, Jeff's direction), real-DB integration tests with hard local-only safety |
 | [worker2 — Committed Secrets & Config Exposure (debt register)](features/committed-secrets-and-config-debt.md) | Standing list of credentials committed to the worker2 repo (locations only); open before adding a credential to worker2 or assuming a config value is private. |
 | [Compass VIP Support Importer (worker2)](features/compass-vip-support-importer.md) | worker2 action that ingests Compass's quarterly VIP spreadsheet and sets each VIP's support tech (`Users.c_supportedByUserId` in `Client_Compass`); open when wo |
@@ -60,7 +60,7 @@
 | [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 |
 | [Talos Pricing Automation (worker2 Cron — Usage Import, AWS Actuals, Margins, Profiles)](features/talos-pricing-automation.md) | Monthly worker2 crons that turn raw usage + AWS cost into a measured platform unit price, per-client cost, and margins; open for the pricing pipeline, its AWS c |
 | [Talos Transcript Ingestion Pipeline (worker2 → AWS Bedrock KBs)](features/talos-transcript-ingestion.md) | `_Worker_Team_Transcripts` cron pipeline ingesting Teams VTT transcripts into Talos Bedrock KBs + emailing organizer recaps; open for Export/Process/Retry/SyncK |
-| [Team Sprint Management & Reporting](features/team-sprint-management.md) | `_Worker_Team_Sprint` engine for TOGA's biweekly dev-sprint process + reporting (warnings, lock, daily dashboard, sprint-end scoring, AI release notes); open fo |
+| [Team Sprint Management & Reporting](features/team-sprint-management.md) | `_Worker_Team_Sprint` engine for TOGA's biweekly dev-sprint process + reporting (warnings, lock, daily dashboard, sprint-end scoring, AI release notes, 7 PM In |
 | [Teams Meeting Transcript Export](features/teams-transcript-export.md) | How `Team/Transcripts/Export` polls Microsoft Graph for Teams transcripts; open for the Graph organizer-resolution, GUID-vs-UPN, and Entra-permission details (t |
 | [Centralized Tracking-Status Refresh (worker2 Sync cron, all clients)](features/tracking-status-refresh.md) | Platform-wide worker2 cron polling FedEx/USPS/UPS to keep `TrackingNumbers.status` current for every provisioned client via api2 PUT; open for the dispatcher/cu |
 | [VAPI Webhook Handler (worker2 — AI-BDR end-of-call processing)](features/vapi-webhook-handler.md) | worker2 handler for VAPI's end-of-call report (writes results onto the `ContactAttempt`, dispatches the post-call action) + the outbound dialer eligibility rule |

package/knowledge/2.0/apps/worker2/features/clickup-design-sprint-automation.md

@@ -6,7 +6,7 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
+updated: 2026-10-01
 owners: ["ajean", "jcardinal"]
 files:
   - worker2/Worker/Clickup/Design.php
@@ -24,7 +24,7 @@ related:
 
 `_Worker_Clickup_Design` replaces a set of native ClickUp automations. When a task's **Final Design Outcome** (FDO) drop-down is set to an actionable value, the worker spawns an iteration task or completes the task; a daily cron reminds the Design Approver of pending reviews.
 
-**Current state (2026-09-25):** live on both design folders (`DESIGN_SPRINTS_FOLDER_IDS`: True Design Sprints `90115939842`, Design Sprints `90116585900`) + Backlog Design lists. Approve→complete and iterate→spawn verified working after the 9/21 multi-folder gate fix (commit `6dcebe0`); earlier misses on the new folder were the old single-folder gate. History of the 2026-07 no-op / no-spawn fixes (worker2 PR #98, #113 + _underscore PR #669) is in Gotchas. The native ClickUp automations masking the original no-op must stay disabled.
+**Current state (2026-10-01):** live on Design Sprints `90116585900` (`DESIGN_SPRINTS_FOLDER_IDS`) + Backlog Design lists. The old True Design Sprints folder `90115939842` was **removed** from the gate (old folders get no automation; open tasks there are closed by hand). FDO-on-create, approve→complete and iterate→spawn verified working since Jeff's 9/25 deploy; failures reported after that predated it. History of the 2026-07 no-op / no-spawn fixes (worker2 PR #98, #113 + _underscore PR #669) is in Gotchas. The native ClickUp automations masking the original no-op must stay disabled.
 
 ## How it works
 
@@ -47,7 +47,7 @@ related:
 - `Worker/Clickup.php` — routes ClickUp webhooks.
   - `shouldEmailDesignApprover($payload, $taskDetails)` — the single predicate gating the "Action Needed: Design Review" email (requires history_items[0] is a Design Approver custom_field change, task status still `iterated`, and user-driven: `user.id != -1`).
   - `taskUpdated` path (~822) and `taskStatusUpdated` path (~230) both gate the email on this predicate.
-- `Controller/ClickupDesignTest.php` — regression tests reached via the `?controller=ClickupDesignTest` route (worker2 has **no PHPUnit harness**; mirrors the `CompassPeopleTest` convention). Uses `ReflectionMethod` to reach the private methods.
+- `Controller/ClickupDesignTest.php` — regression tests (updated 2026-10-01: the new-task case now expects `in progress`) reached via the `?controller=ClickupDesignTest` route (worker2 has **no PHPUnit harness**; mirrors the `CompassPeopleTest` convention). Uses `ReflectionMethod` to reach the private methods.
 
 ### Flow
 
@@ -80,7 +80,7 @@ Configuration lives as ClickUp identifiers (folder IDs, custom-field IDs, drop-d
 - **Never use strict `===` when reading a ClickUp `drop_down` value/orderindex/id (ROOT CAUSE of the silent no-op).** ClickUp returns `value`/`orderindex` with **inconsistent int-vs-string typing** (`"2" !== 2`), so `resolveFinalDesignOutcomeOptionId` matched nothing, returned `null`, and `handleFinalDesignOutcome` hit its early return (job still `isSuccess=1`). Fixed by comparing **as strings**: `(string)$option->orderindex === (string)$field->value` (and the same for `$option->id`). **Every other** drop_down reader in `Worker/Clickup.php` relies on PHP **array-key coercion** (`$optionsByIndex[$option->orderindex]` then indexed by `$customField->value`) precisely because of this typing inconsistency — strict `===` anywhere reading a ClickUp drop_down value is a bug. The native automation `c25fd345` had been masking this no-op in prod.
 - **`taskStatusUpdated` switches on `before->status`, NOT `after->status`** (Clickup.php ~71). A `case '<status>'` in that switch fires when a task **LEAVES** that status — the in-code comment claiming "just changed TO iterated" is misleading. This is the trap behind the second spurious-email vector: the `iterated` case fired on `completeTask()`'s `iterated → complete` transition during `spawnIterationTask`. Anyone adding status-transition logic must account for this direction. The "entering iterated" trigger added this session is correctly placed under `switch ($historyItem->after->status)` (`case ...::STATUS_ITERATED` → `handleTaskEnteredIterated()`) — distinct from the `before->status` switch.
 - **Spurious "Design Review" email — fixed on a single predicate.** Both vectors (the `taskUpdated` Design-Approver-field path ~822 and the `taskStatusUpdated` `iterated` path ~230) now gate on `shouldEmailDesignApprover($payload, $taskDetails)`, which requires: `history_items[0]` is a Design Approver custom_field change, task status still `iterated`, and the change is **user-driven** (`user.id != -1`; ClickBot/automation writes carry `user.id == -1`). The dead `$isDesignApproverSet` block was removed. Consequence: a pure status change **into** iterated (approver already set, no field change) no longer emails from the status path — the legitimate review email flows from the `taskUpdated` field handler.
-- **Native automations must stay disabled once the worker is verified.** The worker replaces: `c25fd345`, `272f743e`, `a64c863a`, `7739cc41`, `08570f31`, `70b09962`. Keep sprint-readiness automations only: `10df1786`, `f6214678`. Re-enabling any of the replaced set reintroduces the duplicate+close and spurious-email behavior.
+- **Native automations must stay disabled once the worker is verified.** The worker replaces: `c25fd345`, `272f743e`, `a64c863a`, `7739cc41`, `08570f31`, `70b09962`. Keep sprint-readiness automations only: `10df1786`, `f6214678` — these existed only on the old folder and **must be rebuilt by hand on Design Sprints** (open as of 2026-10-01). Re-enabling any of the replaced set reintroduces the duplicate+close and spurious-email behavior.
 - **The spawn gate must admit Backlog Design lists — folder + name, not just the sprint folder (ROOT CAUSE of the 2026-07-15 intermittent no-spawn).** `isDesignSprintTask()` originally accepted only the True Design Sprints folder or two hardcoded `DESIGN_LIST_IDS`, so a design task in a **Backlog Design list** was silently skipped (no iteration spawned). The gate now also admits `BACKLOG_FOLDER_ID = '90116192732'` when the list name matches `DESIGN_LIST_NAME_PATTERN`. **Regex trap:** the pattern is `/(?<!non-)\bdesign\b/i` — a bare `\bdesign\b` wrongly matched **"Non-Design Overflow"** because the hyphen is itself a word boundary, so the negative-lookbehind `(?<!non-)` is required; the `\b` boundary also correctly excludes **"Redesign"**. `SendReviewReminders()` applies the same folder+pattern so new backlog Design lists get reminders without a code change.
 - **Resolve the FDO from the webhook `after` value, NOT the per-process snapshot (read-after-write race — second root cause of the 2026-07-15 failure).** `handleFinalDesignOutcome` used to resolve the outcome from the cached `getTaskDetails` snapshot fetched early in the request, which can **predate** ClickUp reflecting the drop-down write → it read the OLD value → silent skip. The webhook's authoritative new value (`history_items[].after`) is now threaded through `handleFinalDesignOutcome(..., ?string $webhookFdoValue)` → `resolveFinalDesignOutcomeOptionId(..., ?string $overrideValue)` (override wins over the snapshot value; the option *list* is still read from the snapshot). `_Worker_Clickup::extractCustomFieldAfterValue()` normalizes the `after` shape and — critically — distinguishes a **missing** `after` (→ `null` → fall back to snapshot) from an **explicit null** `after` (→ `''` sentinel → field was cleared → resolve to no outcome; do NOT act on the stale previous option). The previously-silent resolver-null return now logs a `[ClickupDesign]` breadcrumb.
 - **`_Component_Api_Clickup::send()` throws on transient failures — it no longer silently returns NULL (shared-core, `_underscore` PR #669).** The old retry loop never actually retried and returned NULL on HTTP `>= 502`, **silently dropping** the API call. Now transient failures — HTTP 502/503/504, 429, and transport-level errors (`responseCode === 0` / cURL failure) — **throw** so the worker job fails loudly and the **queue** retries; other non-2xx still throw. Retry is intentionally left to the queue (no in-worker sleep-and-retry; CTO Option C). **It throws the base `Exception`** — the same type every other `_Component_Api` client throws and the framework error handler / Sentry already track — NOT a bespoke exception class. (A `_Exception_Api_Transient` subclass was prototyped and dropped precisely because a new type sits outside the existing Sentry/error path.) Exception messages never embed the full `$response` body (task/user PII); the private `summarizeApiError()` surfaces only ClickUp `err`/`ECODE` with a bounded/truncated fallback. Affects **every** caller of `send()` across the 2.0 apps — grep `_Component_Api_Clickup::send(` before assuming a caller tolerated the old null-on-failure return.
@@ -90,3 +90,8 @@ Configuration lives as ClickUp identifiers (folder IDs, custom-field IDs, drop-d
 
 - [ClickUp Work-Type Automation](./clickup-work-type-automation.md)
 - [team-sprint-management](./team-sprint-management.md)
+
+## Change history
+- 2026-10-01 — Old True Design Sprints folder `90115939842` dropped from `DESIGN_SPRINTS_FOLDER_IDS`; natives 10df1786/f6214678 to rebuild on Design Sprints (ajean; worker2 PR #178)
+- 2026-09-21 — Multi-folder gate (commit `6dcebe0`) (jcardinal)
+- 2026-07-15 — Backlog Design lists + webhook `after` value fix (worker2 #113, _underscore #669) (ajean)

package/knowledge/2.0/apps/worker2/features/clickup-general-automation.md

@@ -1,59 +1,78 @@
 ---
-title: ClickUp General Automation (Sub-Environment reservation, Has UI / Has Code roll-ups)
+title: ClickUp General Automation (Sub-Environment reservation, Has UI / Has Code, review-field reset)
 framework: "2.0"
 repo: worker2
 project: Worker
 client: shared
 type: feature
-status: draft
-updated: 2026-09-16
-owners: [jcardinal]
+status: active
+updated: 2026-10-01
+owners: ["jcardinal", "ajean"]
 files:
   - worker2/Worker/Clickup/GeneralAutomation.php
   - worker2/Worker/Clickup.php
+  - worker2/Worker/Github.php
   - _underscore/Component/Api/Clickup/Clickup.php
 related:
   - ./qa-qc-review-pipeline.md
   - ./clickup-work-type-automation.md
   - ./clickup-custom-field-conventions.md
+  - ./team-sprint-management.md
 ---
 
-`_Worker_Clickup_GeneralAutomation` reacts to ClickUp custom-field changes on a Task; open when working on sub-environment reservation or Has UI / Has Code roll-ups.
+`_Worker_Clickup_GeneralAutomation` keeps QA/QC fields consistent on ClickUp field/status changes (sub-environment reservation, Has UI / Has Code, review-field reset to Needs Review); open when one of those fields is wrong or you add a QA/QC field rule.
 
 ## Summary
 
-**New** worker, fanned out from `_Worker_Clickup::Webhook` (shared ClickUp webhook entry). Part of the platform-wide QA/QC dev-process automation driven by the approved plan (`QA-QC Plan.txt`). **Not deployed yet** — lives on the `feature-qa-qc` branch working tree.
-
-Three reactions today:
-1. **Sub-Environment auto-reservation** — when a Task needs a reserved environment.
-2. **Has UI / Has Code roll-up** to the parent Feature.
-3. **Has Code backfill** on "Development Finished" when a PR exists.
+Action `Clickup/GeneralAutomation/Process`, fanned out from `_Worker_Clickup::Webhook` on
+`taskUpdated` / `taskStatusUpdated`. Implements the "General Automation" section of the team QA/QC
+plan as seven numbered rules (listed in the class docblock). Live in prod; Dev Sprints folder scope.
 
 ## How it works
 
-Entry: `_Worker_Clickup::Webhook` inspects the field change and fans out to `_Worker_Clickup_GeneralAutomation` (alongside the QA/QC review chain — see [qa-qc-review-pipeline](./qa-qc-review-pipeline.md)).
-
-### Sub-Environment auto-reservation
-
-- Triggers when **Client Approval Required** is set **and** Task Type = **Feature**.
-- Reserves a Greek-letter sub-environment **atomically** from the `SubEnvironments` table: a **guarded `UPDATE`** claims a free row, and the worker **retries** if the guarded update claimed nothing (another task won the race). Safe pattern instead of select-then-update, which double-books under concurrent webhooks.
-- The reserved letter is written back to the Task.
-
-### Has UI / Has Code roll-up to the parent Feature
-
-- When a child Task's **Has UI** or **Has Code** flag changes, the worker rolls the value up to the parent **Feature** task (a Feature "has code" if any child does, same for UI).
-
-### Has Code backfill on Development Finished
-
-- When a Task **enters** "Development Finished", if a **PR exists** for it the worker backfills the **Has Code** flag. Covers tasks whose Has Code was never set by hand but that clearly produced code.
+### The rules (`GeneralAutomation.php`)
+
+1. **Client Approval Required** checked → check **Reserve Sub-Environment**.
+2. **Task Type = Feature** → check Reserve Sub-Environment.
+3. Reserve Sub-Environment checked → claim the next free Greek letter from `SubEnvironments` with a
+   **guarded `UPDATE` + retry** (never select-then-update) and set **Sub-Environment**.
+4. Reserve Sub-Environment unchecked → clear Sub-Environment, release the row.
+5. A subtask's **Has UI / Has Code Changes** → roll up onto the parent Feature (any child = parent).
+6. Status → **Development Finished**, a PR exists, Has Code Changes unchecked → check it.
+7. Status **enters** `ui review` / `front-end review` / `back-end review` → reset the matching field
+   **UI Review** (`c08e3ca2…`) / **Front-end Review** (`e21c888a…`) / **Back-End Review**
+   (`227480b6…`) to **Needs Review**. Dev Sprints only, not Feature tasks (`FeatureReview` owns
+   those); skipped if already Needs Review. `QaReview` / `FeatureReview` treat Needs Review as a
+   no-op, so the reset does not loop.
+
+### PR → "Has Code Changes"
+
+- `hasPullRequest(string $customTaskId)` (public) — **exact** match on `PullRequests.title`, which
+  stores only the task custom id (`_Worker_Github::prTitleToCustomId`). A `LIKE` prefix match was a
+  false-positive risk (`TRUE-123` matched `TRUE-1234`). Shared with
+  `_Worker_Clickup::handleDevelopmentFinished`, which checks for a PR itself so it does not race rule 6.
+- `Worker/Github.php` `setHasCodeChangesFromPr()` — checks Has Code Changes when a PR row is **first
+  recorded** (task resolved via `Team.Tasks` customClickupIdentifier → clickupIdentifier). Best-effort,
+  never throws: the GitHub webhook must keep returning 200.
+
+Sprint-list defaults set on create / move (Condition, Has UI Changes, Work Type) live in
+[ClickUp work-type automation](./clickup-work-type-automation.md#sprint-list-defaults-taskcreated--taskmoved).
 
 ## Gotchas
 
-- **Reserve the sub-environment with a guarded `UPDATE` + retry, never select-then-update.** Concurrent webhooks will otherwise hand the same Greek letter to two tasks.
-- **Custom-field option VALUES are resolved at runtime, IDs are constants.** Field IDs come from the `CLICK_UP_CUSTOM_FIELD_ID__*` constants in `_Component_Api_Clickup`; dropdown option values are read at runtime from `type_config->options` (by `orderindex`, set by option id) — never hardcode an option's numeric value. See [ClickUp custom-field conventions](./clickup-custom-field-conventions.md).
+- **Reserve the sub-environment with a guarded `UPDATE` + retry, never select-then-update.**
+  Concurrent webhooks would hand the same letter to two tasks.
+- **Field IDs are constants, option VALUES are resolved at runtime** — see
+  [ClickUp custom-field conventions](./clickup-custom-field-conventions.md).
+- **Review fields always reset on entry (owner decision 2026-10-01).** Do not "keep" an old
+  Approved/Denied when a task re-enters a review status.
 
 ## Related
 
 - [QA/QC review pipeline](./qa-qc-review-pipeline.md)
 - [ClickUp Work-Type Automation](./clickup-work-type-automation.md)
 - [ClickUp custom-field conventions](./clickup-custom-field-conventions.md)
+
+## Change history
+- 2026-10-01 — Rule 7 review-field reset; Has Code Changes on first PR record; `hasPullRequest()` exact match (ajean; worker2 PR #178)
+- 2026-09-16 — Initial rules 1–6 (jcardinal)

package/knowledge/2.0/apps/worker2/features/clickup-work-type-automation.md

@@ -6,8 +6,8 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
-owners: ["jcardinal"]
+updated: 2026-10-01
+owners: ["jcardinal", "ajean"]
 files:
   - worker2/Worker/Clickup.php
   - worker2/Tests/Worker/ClickupWorkTypeTest.php
@@ -16,7 +16,7 @@ related:
   - ../workflows/clickup-credential-rotation.md
 ---
 
-Auto-maintains each ClickUp task's Work Type (Committed/Conditional/Stretch) from its dependencies, status, and due date, and sets new-task defaults on taskCreated; open when work-type promotion/demotion or taskCreated field writes misbehave.
+Auto-maintains each ClickUp task's Work Type (Committed/Conditional/Stretch) from its dependencies, status, and due date, and sets sprint-list defaults (Work Type, Condition, Has UI Changes) on create/move; open when work-type promotion/demotion or those default writes misbehave.
 
 ## Summary
 
@@ -42,12 +42,29 @@ Flow:
    - `Stretch` with a due date inside the current sprint → set Committed/Conditional as above.
 6. When a task is depended on by another (`$dependency->depends_on == $taskId`), it recurses into the blocking direction so completing a task re-evaluates the tasks it was blocking. The `$dependsOnTaskId` argument breaks two-node cycles.
 
-### New-task defaults (`taskCreated`)
+### Sprint-list defaults (`taskCreated` + `taskMoved`)
 
-- Every optional field write in `taskCreated` goes through private `setFieldSafely($taskId, $fieldLabel, callable)`: try/catch → `error_log` + Sentry. One refused field never aborts the job (the later Clickup/Fluffer/Process dispatch still runs).
-- **Work Type = Unplanned** when empty, only if the list name starts with `Sprint` AND `isTaskInQaQcScope()` (Dev Sprints folder). Option id resolved by name at runtime (`WORK_TYPE_UNPLANNED`). Non-`Sprint` lists get no Work Type write (jcardinal decision).
-- **Previous Sprint Work Type** = the Work Type name (or `Unplanned` when empty), resolved by name via the field's own options.
-- Design FDO default is dispatched from here too — see [design sprint automation](./clickup-design-sprint-automation.md).
+Applied by `applySprintEntryDefaults()` when a task is **created in**, or **moved into**, a list whose
+name starts with `Sprint` inside the Dev Sprints or Design Sprints folder
+(`isInDevOrDesignSprintsFolder()`). Backlog and other lists get nothing.
+
+- **Condition** = On Track if empty (`defaultConditionOnTrack()`), then **Previous Sprint Condition**
+  = Condition (`CLICK_UP_CUSTOM_FIELD_ID__PREVIOUS_CONDITION`).
+- **Has UI Changes** checked (Dev Sprints only).
+- **Work Type** = Unplanned if empty (Dev Sprints only; `defaultWorkTypeUnplanned()`, option resolved
+  by name).
+- **Previous Sprint Work Type** = the Work Type name (or Unplanned) — **only on sprint lists** (it used
+  to fire on Backlog too).
+- Every optional write goes through private `setFieldSafely($taskId, $fieldLabel, callable)`:
+  try/catch → `error_log` + Sentry, so one refused field never aborts the job (the later
+  Clickup/Fluffer/Process dispatch still runs). Dropdowns are set by option name
+  (`setDropdownByName()`).
+- Design FDO default is dispatched from `taskCreated` too — see
+  [design sprint automation](./clickup-design-sprint-automation.md).
+
+**Dev sprint data ingestion** (sprint tag, `ensureTaskExistsInCurrentSprint`, dependencies) requires
+the task's **HOME** folder = Dev Sprints (`isHomeFolderInQaQcScope()`), not just any list membership —
+so Design tasks multi-listed into a Dev list stay out of Dev reports (owner decision).
 
 Data model: reads/writes the `Team` database (`Tasks`, `Developers`, `Tasks_Developers`, `Sprints`) and the ClickUp REST API. The Work Type itself lives in ClickUp as a custom field (`CLICK_UP_CUSTOM_FIELD_ID__WORKTYPE`), not in the DB.
 
@@ -58,8 +75,15 @@ Data model: reads/writes the `Team` database (`Tasks`, `Developers`, `Tasks_Deve
 - **No PHPUnit harness** in worker2. The regression test `Tests/Worker/ClickupWorkTypeTest.php` is a plain-PHP script (reflection on `isStatusComplete`) run with `php Tests/Worker/ClickupWorkTypeTest.php`.
 - **ClickUp dropdown custom-field `value` is the option ORDERINDEX, not its name.** The webhook payload for a dropdown/labels custom field delivers the selected option's integer `orderindex`, *not* the option's display name. Any name-keyed lookup (e.g. `$lookupPreviousSprintWorkTypeByName`) will silently never match if fed the raw `value`. Resolve the name first via the field's own `type_config->options` — build a map keyed by `orderindex` (`$workTypesByIndex[$opt->orderindex] = $opt`) and read `->name` from it. This is the proven pattern in `_Worker_Team_Sprint::SprintLock` (`Worker/Team/Sprint.php`, the Work Type resolve ~L3894 and the POST ~L3971). Guard the lookup with `isset($workTypesByIndex[$value])` so a stale/deleted option orderindex doesn't warn.
 
+- **Home folder vs. any list.** `isTaskInQaQcScope()` matches any list the task is in (good for QA/QC
+  gates); sprint **data ingestion** must use `isHomeFolderInQaQcScope()`. Mixing them up leaks Design
+  tasks into Dev sprint reports.
 - **2026-09-21..25 outage: every taskCreated failed (~113 jobs, 0 Fluffer jobs).** The automation user lacked edit rights on Previous Sprint Work Type → HTTP 401 `ACCESS_606`; the throw killed the rest of the job. Fixed by field permissions + `setFieldSafely`. Any new optional write must use `setFieldSafely`. Account-change check: [credential rotation](../workflows/clickup-credential-rotation.md).
 
 ## Related
 
 - [ClickUp Project & Opportunity Multi-List Routing](./clickup-project-routing.md)
+
+## Change history
+- 2026-10-01 — Defaults also on taskMoved into a `Sprint*` list; Condition / Previous Sprint Condition / Has UI Changes added; Previous Sprint Work Type limited to sprint lists; ingestion gated on HOME folder (ajean; worker2 PR #178)
+- 2026-09-25 — `setFieldSafely` after the ACCESS_606 taskCreated outage (jcardinal)

package/knowledge/2.0/apps/worker2/features/committed-secrets-and-config-debt.md

@@ -6,8 +6,8 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
-owners: ["kyalamarthi"]
+updated: 2026-10-01
+owners: ["kyalamarthi", "ajean"]
 files:
   - worker2/.gitignore
   - worker2/Worker/Team/Github.php
@@ -43,7 +43,8 @@ the publish on a credential literal.
 |---|---|---|
 | GitHub personal access token, `agilantgit` account | `worker2/Worker/Team/Github.php:9` **and** `worker2/.ebextensions/git.json:4` (same token, two copies) | Committed since 2025-01-17 and present in **166 of 167 branches**, so scrubbing history is not a fix — **rotation is the only fix**. Org-wide reach. It is also interpolated into a `shell_exec` clone URL, so it shows up in the instance process list. |
 | NetSuite EC private key | `worker2/Config/netsuite_ec_key.pem` | Tracked in git as a file. |
-| TOGa Talos (`api.togaiq.com`) API key | `worker2/Worker/Team/Sprint.php:43`, used ~L422 | Still a class constant. There is **no `[togaiq]` config group yet**, so moving it means adding the config group first. |
+| TOGa Talos (`api.togaiq.com`) API key — **old** release-notes key | git history only: `worker2/Worker/Team/Sprint.php` before PR #179 (still visible at commit `8613ace`) | Code no longer uses it, but it was committed, so it **must be revoked** in TOGa Talos. Open until revoked. |
+| TOGa Talos API key — **current** (`[talos] api_key`) | `worker2/Config/production.ini` `[talos]` group (~L230) | Shared by release notes and the transcript pipeline. Committed like every `Config/*.ini` (see Summary). |
 | PayPal webhook signature verification **off** in production | `worker2/Config/production.ini:182` | Impact already written up — a caller who knows the URL can create a paid SalesOrder. See [Rate PayPal subscription webhook](../../../../clients/rate/features/paypal-subscription-purchase-webhook.md). |
 
 ### Fixed / no longer true
@@ -54,6 +55,12 @@ the publish on a credential literal.
   `Authorization` header written into `Logs.Api`, are separate open items — see
   [_ApiRequest gotchas](../../_underscore/features/apirequest-json-content-type.md#gotchas).
 
+- **TOGa Talos key in `Sprint.php`** (2026-10-01, worker2 PR #179) — the `AI_API_KEY` constant is
+  **gone**. `aiApiKey()` reads `[talos] api_key`, the same `/api/ai/generate` key the transcript
+  pipeline already uses (no new `[togaiq]` group). This removed a **second** copy of a TOGa Talos key
+  from PHP — but `[talos] api_key` is itself committed in `production.ini` (table above), so treat it
+  as a refactor, not a fix.
+
 ## Gotchas
 
 - **Config is not private here.** Moving a secret from a PHP constant into
@@ -75,3 +82,7 @@ the publish on a credential literal.
 - [Team Sprint Management & Reporting](./team-sprint-management.md)
 - [_ApiRequest — encode/decode & api-logging behavior](../../_underscore/features/apirequest-json-content-type.md)
 - [Rate PayPal Subscription Purchase & Webhook Pipeline](../../../../clients/rate/features/paypal-subscription-purchase-webhook.md)
+
+## Change history
+- 2026-10-01 — TOGa Talos release-notes key moved to `[talos] api_key`; old key listed for revocation (ajean)
+- 2026-09-21 — Register created from audit (kyalamarthi)

package/knowledge/2.0/apps/worker2/features/netsuite-opportunity-sync.md

@@ -6,7 +6,7 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
+updated: 2026-10-01
 owners: ["dfranks", "kyalamarthi", "ajean", "jcardinal"]
 files:
   - worker2/Worker/Netsuite.php
@@ -253,6 +253,11 @@ Stage/close/reopen rules: [stage sync](./netsuite-clickup-opportunity-bidirectio
 
 ## Gotchas
 
+- **Unverified: the folder filter on `GET /team/{id}/task` may be wrong here.** ClickUp documents the
+  folder filter as `project_ids[]`; `Worker/Netsuite/Opportunity.php` (~L1345) and
+  `Worker/Netsuite/OpportunityDocuments.php` (~L456) send `folder_ids[]`. If ClickUp ignores it, the
+  query returns team-wide tasks, not just the Opportunities folder. Check before trusting those scans
+  (follow-up, flagged 2026-10-01). The newer sprint code uses `project_ids[]`.
 - **⚠ The `endCustomerName` 9-day total outage — a column-existence gate does NOT protect an ORM write (2026-09-01 → 2026-09-10).** Every `Netsuite/Opportunity/post|put` job threw `There is no field called 'endCustomerName' in the '_Model_Forecast_Opportunity' model.` (`_underscore/Model.php:498`) from 2026-09-01 12:01 to 2026-09-10 15:48 CDT. **The whole NetSuite→Forecast→ClickUp opportunity sync was dead for 9 days and every job was red.**
   - **Cause — a deploy split across TWO repos.** worker2 shipped the `$values['endCustomerName']` write (PR #158) while `_underscore/Model/Forecast/Opportunity.php` had not yet declared the property. `_Model` builds its field map from **declared properties** in the constructor, so `__set` rejected the unknown field. The DB column existed (the migration had been applied) — the missing half was the model declaration, in a different repo.
   - **Blast radius:** the throw lands in `importOpportunity()` **before** the Forecast save and **before** `maybeCreateClickupTask()`, so affected opportunities got **neither** a Forecast row **nor** a ClickUp task. Measured in prod `Core.WorkerJobs`: **611 failed jobs, 310 distinct opportunities, 264 still with no ClickUp task**, 1 (NS internalId 7442501) absent from Forecast.
@@ -322,4 +327,5 @@ Stage/close/reopen rules: [stage sync](./netsuite-clickup-opportunity-bidirectio
 - [MCP Tool Usage](../../../../standalone/apps/claude/workflows/mcp-tool-usage.md) — the `toga-db` query traps hit while running the verdict census.
 
 ## Change history
+- 2026-10-01 — Flagged `folder_ids[]` vs documented `project_ids[]` filter (unverified) (ajean)
 - 2026-09-25 — Claim guards creation only; CU→NS routed by folder, link check, actor guard; orderindex-0 bug fixed (jcardinal)

package/knowledge/2.0/apps/worker2/features/oneuptime-worker2-monitoring.md

@@ -6,7 +6,7 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
+updated: 2026-10-01
 owners: ["jcardinal", "mhammontree", "bala", "rgirish"]
 files:
   - worker2/Worker/Monitor/Compass.php
@@ -18,6 +18,7 @@ files:
   - worker2/Worker/Monitor/Prudential.php
   - worker2/Worker/Monitor/Nycdoe.php
   - worker2/Worker/Monitor/Staples.php
+  - worker2/Worker/Monitor/Wje.php
   - worker2/Config/production.ini
   - worker2/Config/beta.ini
   - worker2/Config/sandbox-dev.ini
@@ -32,6 +33,7 @@ related:
   - ../../../clients/staples/features/oneuptime-sftp-folder-monitors.md
   - ../../../clients/compass-usa/features/oneuptime-ma-refresh-order-monitor.md
   - ../../../clients/compass-usa/features/oneuptime-netsuite-duplicate-sales-orders-monitor.md
+  - ../../../clients/wje/features/oneuptime-ticket-writes-monitor.md
 ---
 
 OneUptime push-metric monitor pattern for worker2 (2.0): a self-contained cron action decides pass/fail and POSTs a string token to a OneUptime Incoming Request monitor; open when building/tuning a worker2 monitor, its thresholds, or the OneUptime import JSON.
@@ -302,6 +304,13 @@ has no proven connection to the legacy `Common` DB today**, so a 2.0 monitor can
 `MaRefreshOrderExceptions` counts rows in `Client_Compass` instead. If worker2 ever gets that
 connection, a generic "1.0 cron has not checked in" monitor becomes possible.
 
+This is about `Common` only — **worker2 does read other legacy DBs.** `worker2/_.php` registers
+`TOGaDeskSupport` as `_underscore::DB_TOGADESK1` and `Vision_Log` as `DB_VISION_LOGS` at boot (from the
+`[database1]` config group), already used in prod by `Worker/Sync/SalesOrderStatus.php` and
+`Worker/Client/Aig/ClosedClaims.php`. A 2.0 monitor over TOGaDesk data is possible and preferred (it
+runs outside the 1.0 worker it watches) — e.g. the
+[WJE ticket-writes monitor](../../../clients/wje/features/oneuptime-ticket-writes-monitor.md).
+
 ### Match the lateness criterion to the flow's real time-scale
 
 The sibling Compass monitors ship 6 criteria including a DEGRADED incident at **2 missed pushes (10
@@ -559,4 +568,5 @@ production deploy.**
 - [OneUptime 1.0 worker uptime monitoring](../../../1.0/apps/worker/features/oneuptime-worker-uptime-monitoring.md) — the 1.0 push-heartbeat predecessor
 
 ## Change history
+- 2026-10-01 — Clarified worker2 reads `TOGaDeskSupport` (`DB_TOGADESK1`) — only `Common` is unreachable; added `Monitor/Wje`. (mhammontree)
 - 2026-09-25 — Added `NetsuiteDuplicateSalesOrders`, the first monitor that queries NetSuite (SuiteQL) instead of a Toga DB. (rgirish)

package/knowledge/2.0/apps/worker2/features/qa-qc-review-pipeline.md

@@ -6,8 +6,8 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-29
-owners: [jcardinal]
+updated: 2026-10-01
+owners: ["jcardinal", "ajean"]
 files:
   - worker2/Worker/Clickup/QaReview.php
   - worker2/Worker/Clickup/QcReview.php
@@ -15,10 +15,12 @@ files:
   - worker2/Worker/Clickup/StageBatch.php
   - worker2/Worker/Clickup/FeatureReview.php
   - worker2/Worker/Clickup/BeReview.php
+  - worker2/Worker/Clickup/DevFinished.php
   - worker2/Worker/Clickup.php
   - worker2/Worker/Github.php
   - _underscore/Component/Api/Clickup/Clickup.php
   - dbchanges2/Core/2026-09-09a - Insert StageBatch CronJob.sql
+  - dbchanges2/Core/2026-09-29a - Record sprint and design CronJobs.sql
   - dbchanges2/Team/2026-09-09a - Add isApproved to PullRequests.sql
 related:
   - ./clickup-general-automation.md
@@ -40,8 +42,10 @@ production** (deployed on `_production`).
 - `_Worker_Clickup_QcReview` — QC defect review + client review; also handles the **Hotfix** defect
   gate and its `DeployHotfix` entry.
 - `_Worker_Clickup_QcBatch` — a weekday 4:30pm Central CRON that batches QA-Approved tasks into QC.
-- `_Worker_Clickup_StageBatch` — the **Wed 4:30pm Central** CRON that ships "To Deploy" tasks to
-  production (the Task-flow prod-deploy piece; replaces the retired legacy status-driven merge).
+- `_Worker_Clickup_StageBatch` — batch that ships "To Deploy" tasks to production. **Not scheduled in
+  prod: Stage deploys stay manual (owner decision 2026-10-01).**
+- `_Worker_Clickup_DevFinished::CatchUp` — every-30-min safety net for missed Development Finished
+  webhooks.
 - `_Worker_Clickup_FeatureReview` — the **Feature** flow: rolls a multi-subtask feature through the
   same gates as a unit, advancing only when **all** subtasks clear a gate.
 - `_Worker_Clickup_BeReview` — **auto** BE-approve driven by GitHub PR reviews (removes the manual
@@ -79,17 +83,41 @@ when a task *left* a status; the QA/QC entry must be on entering the status.
   (matches `QaReview::changedCustomFieldIds`), each in its own try/catch; safe because each skips the
   other's task kind. Write failures are logged + Sentry, never thrown.
 
+`handleDevelopmentFinished` checks for a PR itself (`_Worker_Clickup_GeneralAutomation::hasPullRequest`)
+before picking the first review status, so it does not race the Has Code Changes backfill.
+
+**Prod flow end to end:** Development Finished → UI / FE / BE review → QA Approved → (4:30 PM QC
+Batch) QC Review → Stage or Client Review → To Deploy → **manual** deploy.
+
+### Catch-up for missed webhooks (`_Worker_Clickup_DevFinished::CatchUp`)
+
+- Cron id 86, `*/30 * * * *`. Scans Dev Sprints (`GET /team/{id}/task?project_ids[]=…&statuses[]=development finished&subtasks=true`)
+  and re-runs `_Worker_Clickup::RunDevelopmentFinished` for tasks whose **Environment** is empty, or
+  set but stuck ≥ 30 min (`STUCK_THRESHOLD_SECONDS`).
+- Fresh re-fetch per task (`getTaskDetails($id, true)`); skips tasks updated in the last 2 min
+  (`RECENT_UPDATE_GUARD_SECONDS`) so it does not race a live webhook.
+- Per-task `catch (Exception)` is **on purpose** (CSO decision, CodeRabbit agreed): each task is
+  independent and is retried next run; code errors (`Error`) still fail loud. Rescans from page 0
+  after a trigger (moved tasks shift pages); `MAX_PAGES` caps fetches. Returns
+  `{isSuccess, checked, triggered, failed}`.
+- First run 2026-10-01 moved 10 tasks stuck since the 9/12–9/20 webhook outage (all → `qa approved`,
+  since neither Has UI nor Has Code was checked).
+
 ### QA review chain (`_Worker_Clickup_QaReview`)
 
 - Three ordered review fields: **UI → FE (front-end) → BE (back-end)**.
-- **Approve** advances to the next review field.
+- **Approve** advances to the next review field. Entering a review status resets its field to
+  **Needs Review** ([general automation](./clickup-general-automation.md) rule 7); `QaReview` /
+  `FeatureReview` ignore Needs Review, so there is no loop.
 - **Deny** sends the task to **Rework** and **reverts** the task's changes from the QA/QC branch.
 - **Unit-test gate is a STUB today.** `runUnitTests()` currently returns `true`. Real gating (Cypress /
   Postman / Codeception) is pending — do not treat the gate as enforcing anything yet.
 
 ### QC batch promotion (`_Worker_Clickup_QcBatch`)
 
-- Weekday **4:30pm Central** CRON (registered by `Core/2026-09-08e - Insert QcBatch CronJob.sql`).
+- Weekday **4:30pm Central** CRON, prod id 75 (`Core/2026-09-08e - Insert QcBatch CronJob.sql`).
+  It was `isActive = 0` in prod until 2026-09-29a turned it on — until then QA Approved tasks never
+  moved to QC.
 - Moves **QA-Approved** tasks → **QC-Task**.
 - **Skips the run if QC is still busy** (does not pile a new batch on top of an in-progress one).
 
@@ -122,16 +150,15 @@ when a task *left* a status; the QA/QC entry must be on entering the status.
   safe. The actual prod merge goes through `MergeTaskToProduction` — see
   [QA/QC branch automation](./qa-qc-branch-automation.md).
 
-### Stage cron (`_Worker_Clickup_StageBatch`)
+### Stage batch (`_Worker_Clickup_StageBatch`) — not scheduled
 
-- The **Wed 4:30pm Central** batch (`'30 16 * * 3'`, seeded by
-  `Core/2026-09-09a - Insert StageBatch CronJob.sql`) that ships **"To Deploy"** tasks to production.
-- `Process` loops `Team.Tasks` "to deploy" rows and dispatches **one `DeployTask` per task**, so each
-  stays under the 300s worker cap and a re-run **resumes via the deploy-claim** (no double deploy).
-  `DeployTask` ships via `MergeTaskToProduction` then the shared finalize (`markProductionDeployed` +
-  `releaseSubEnvironment`).
-- Replaces the **retired** legacy status-driven prod-merge (the old `to deploy` / `hotfix review`
-  switch cases in `Worker/Clickup.php`).
+- **Stage deploys stay manual (owner decision 2026-10-01).** Do not add or turn on a StageBatch cron
+  row without the owner, even though `Core/2026-09-09a - Insert StageBatch CronJob.sql` exists.
+- When run: `Process` loops `Team.Tasks` "to deploy" rows and dispatches **one `DeployTask` per task**
+  (stays under the 300s worker cap; a re-run resumes via the deploy-claim). `DeployTask` ships via
+  `MergeTaskToProduction` then finalizes (`markProductionDeployed` + `releaseSubEnvironment`).
+- Replaces the **retired** legacy status-driven prod-merge (old `to deploy` / `hotfix review` cases in
+  `Worker/Clickup.php`).
 
 ### Feature flow (`_Worker_Clickup_FeatureReview`)
 
@@ -157,7 +184,12 @@ when a task *left* a status; the QA/QC entry must be on entering the status.
   the fan-out, `handleDevelopmentFinished`, `QcBatch`, and the taskCreated Work Type default. A task
   outside that folder is ignored — verify the folder before expecting the flow to run.
 - **Dev Finished with neither Has UI Changes nor Has Code Changes checked → `qa approved` (skips
-  review).** Intended (jcardinal confirmed); do not "fix".
+  review).** Intended (jcardinal confirmed); do not "fix". Sprint-list defaults now check Has UI
+  Changes on Dev tasks, and a recorded PR checks Has Code Changes, so this path is now rare.
+- **A missed Development Finished webhook used to strand the task.** CatchUp now recovers it within
+  30 min. It skips multi-listed tasks whose HOME folder is still the old True Dev Sprints folder —
+  same gap as `ResetInProgress`, see
+  [team-sprint-management](./team-sprint-management.md#gotchas).
 - **A Feature advances only when ALL subtasks clear a gate** — a single lagging subtask holds the whole
   feature. Subtasks carry no code; only the feature branch does.
 - **`_underscore CLICK_UP_CUSTOM_FIELD_ID__CLIENT_REVIEW` was repointed** to the Dev Sprints
@@ -186,3 +218,7 @@ when a task *left* a status; the QA/QC entry must be on entering the status.
 - [ClickUp general automation](./clickup-general-automation.md)
 - [QA/QC branch automation](./qa-qc-branch-automation.md)
 - [ClickUp custom-field conventions](./clickup-custom-field-conventions.md)
+
+## Change history
+- 2026-10-01 — DevFinished CatchUp (cron 86); QC Batch turned on (id 75); review fields reset to Needs Review on entry; Stage deploys confirmed manual (ajean; worker2 PR #178, dbchanges2 PR #504)
+- 2026-09-25 — Scope narrowed to Dev Sprints `90116585845` (jcardinal)

package/knowledge/2.0/apps/worker2/features/team-sprint-management.md

@@ -6,23 +6,25 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-09-25
-owners: ["jcardinal", "kyalamarthi"]
+updated: 2026-10-01
+owners: ["jcardinal", "kyalamarthi", "ajean"]
 files:
   - worker2/Worker/Team/Sprint.php
   - worker2/Config/production.ini
   - _underscore/Model/Team/Sprint.php
+  - dbchanges2/Core/2026-09-29a - Record sprint and design CronJobs.sql
 related:
   - ../architecture.md
   - ./creating-worker-actions.md
   - ./clickup-work-type-automation.md
   - ./clickup-project-routing.md
+  - ./clickup-general-automation.md
   - ./committed-secrets-and-config-debt.md
   - ../workflows/sprint-clickup-folder-repoint.md
   - ../workflows/php-runtime-upgrade-dependency-audit.md
 ---
 
-`_Worker_Team_Sprint` engine for TOGA's biweekly dev-sprint process + reporting (warnings, lock, daily dashboard, sprint-end scoring, AI release notes); open for sprint actions, the scoring model, or Power BI-parity dashboard SQL.
+`_Worker_Team_Sprint` engine for TOGA's biweekly dev-sprint process + reporting (warnings, lock, daily dashboard, sprint-end scoring, AI release notes, 7 PM In Progress reset); open for sprint actions, their cron schedule, the scoring model, or Power BI-parity dashboard SQL.
 
 ## Summary
 
@@ -50,11 +52,13 @@ everything.
 ### Key files / entry points
 - `Worker/Team/Sprint.php` — the entire feature (one abstract class, static methods).
 - `initialize()` — registers the `Logs_True` DB connection used for ClickUp API logging.
-- ClickUp config lives in class constants: `CLICKUP_TEAM_ID` and `CLICKUP_DEV_SPRINTS_FOLDER_ID` (the
-  folder whose child lists are the sprints). The API token is **no longer** a constant here — all 6
-  call sites use `_Component_Api_Clickup::accessToken()`, reading `[clickup] token` from config.
-- AI config constants: `AI_API_ENDPOINT` (TOGa Talos `…/api/ai/generate`), `AI_MODEL_ID`
-  (`bedrock/us.anthropic.claude-haiku-4-5-…`), temperature, max-tokens, timeout.
+- ClickUp config: `CLICKUP_TEAM_ID`; Dev Sprints folder via public `devSprintsFolderId()` — reads
+  `[clickup] sprint_folder_id`, falls back to `CLICKUP_DEV_SPRINTS_FOLDER_ID` (`90116585845`);
+  `CLICKUP_DESIGN_SPRINTS_FOLDER_ID` (`90116585900`, used only by `ResetInProgress`). Token via
+  `_Component_Api_Clickup::accessToken()` (`[clickup] token`).
+- AI config: `AI_API_ENDPOINT` (TOGa Talos `…/api/ai/generate`), `AI_MODEL_ID`
+  (`bedrock/us.anthropic.claude-haiku-4-5-…`), temperature, max-tokens, timeout. Key via private
+  `aiApiKey()` → `[talos] api_key` (the same key the transcript pipeline uses); throws if missing.
 - Report distribution: `SEND_LEADERSHIP_REPORTS_TO` (leadership email list); `SEND_EMAILS_FROM` /
   `SEND_EMAILS_FROM_NAME`.
 
@@ -62,29 +66,38 @@ everything.
 `_Worker_Team_Sprint::SprintEnd`. New actions are only reachable once registered as a `CronJobs` row
 (or webhook route). See [creating-worker-actions](./creating-worker-actions.md).
 
-### The sprint lifecycle (and which action runs when)
-A sprint runs ~14 days. Across the cycle these actions fire (scheduled as crons):
-
-1. **Sprint launch day, 8:30 AM** — `SendSprintEndWarnings` and `SendSprintLockWarnings` email every
-   developer who had a task in the latest sprint, reminding them to (a) finalize the *previous*
-   sprint's task data before the 9:00 AM End capture, and (b) get their *new* sprint commitments ready
-   to lock before the 9:45 AM launch ceremony.
-2. **~9:00 AM** — `SprintEnd` captures and scores the just-finished sprint, emails reports, and
-   (optionally) sends release notes.
-3. **~9:45 AM (after launch ceremony)** — `SprintLock` freezes the new sprint's plan. In production
-   this is now invoked via the scheduled self-gating wrapper `SprintLockScheduled` (see below), not by
-   a cron that targets `SprintLock` directly — because the launch day is **every other Wednesday** and
-   cron cannot express a biweekly schedule.
-4. **Daily during the sprint** — `SprintDaily` emails leadership a progress dashboard.
-
-Most methods accept an optional `$sprint` number; when omitted they resolve the relevant sprint by
-date via `getSprint()` (which returns the sprint whose `dateStart…dateEnd` range contains today, or,
-for end-of-sprint, the previous sprint).
+### The sprint lifecycle — cron schedule (prod `Core.CronJobs`, Central time)
+All rows are recorded in git by `dbchanges2/Core/2026-09-29a - Record sprint and design CronJobs.sql`
+(PR #504, applied to prod). Sprints launch **every other Wednesday**; cron cannot say "biweekly", so
+weekly rows **self-gate in PHP** against `Sprints`.
+
+| Id | Action | Schedule | Gate |
+|----|--------|----------|------|
+| 9 | `Team/Sprint/SprintDaily` | `0 9 * * 1-5` | skips if no `Sprints` row covers today |
+| 11 | `Team/Sprint/SprintEnd` | `0 9 * * 1` (Monday) | skips if previous sprint ended > 10 days ago (the mid-sprint Monday) |
+| 40 | `Team/Sprint/SprintLockScheduled` | `0 10 * * 3` | runs only if a sprint ended yesterday |
+| 83 | `Team/Sprint/SendSprintLockWarningsScheduled` | `30 8 * * 3` | same gate as SprintLockScheduled |
+| 84 | `Team/Sprint/SendSprintEndWarningsScheduled` | `30 8 * * 1` | same gate as SprintEnd |
+| 85 | `Team/Sprint/ResetInProgress` | `0 19 * * 1-5` | none (weekdays incl. holidays) |
+
+(Id 21 = Design review reminders, id 86 = `Clickup/DevFinished/CatchUp` — see
+[design automation](./clickup-design-sprint-automation.md) and
+[QA/QC pipeline](./qa-qc-review-pipeline.md).)
+
+Most methods accept an optional `$sprint` number; when omitted they resolve it via `getSprint()` —
+the sprint whose `dateStart…dateEnd` contains today, `ORDER BY dateStart DESC, id DESC`. It returns
+**null** when no row matches; every caller returns a skip message instead of fataling.
+
+Every action returns a string to `Core.WorkerJobs.output` — skips say why; `SprintDaily`, `SprintEnd`,
+and the warning actions return a JSON summary (e.g.
+`{"isSuccess":true,"sprint":2,"tasksCaptured":74,"emailSent":true}`). Read the output column to tell
+a good run from one that did nothing.
 
 ### Public actions (entry points)
 
-#### `SendSprintEndWarnings()` / `SendSprintLockWarnings()`
-Look up the latest `Sprints` row, find every distinct developer with a task in that sprint
+#### `SendSprintEndWarnings()` / `SendSprintLockWarnings()` (+ `…Scheduled` wrappers)
+The crons call the `…Scheduled` wrappers, which apply the gates in the table above and then call
+these. Look up the latest `Sprints` row, find every distinct developer with a task in that sprint
 (`Developers ⋈ Tasks_Developers ⋈ Tasks`), and email each a templated reminder. End-warning = "clean
 up your data before the 9:00 AM End capture"; Lock-warning = "have your commitments ready before the
 9:45 AM lock; work added after lock is treated as unplanned/interrupt work." Both send via the
@@ -94,7 +107,10 @@ up your data before the 9:00 AM End capture"; Lock-warning = "have your commitme
 Freezes the sprint's plan at launch time. Optionally re-captures ClickUp data first, then for each
 task records the **"at lock" baseline** — `workTypeAtLock`, `sprintPointsAtLock`, `statusAtLock` — and
 initializes the per-sprint tracking counters (rework events, unjustified status/work-effort changes,
-in-progress time). These at-lock values are what later metrics measure *against*. If the target sprint
+in-progress time). These at-lock values are what later metrics measure *against*. Per task it also
+copies ClickUp **Condition → Previous Sprint Condition** (`CLICK_UP_CUSTOM_FIELD_ID__PREVIOUS_CONDITION`)
+then resets **Condition = On Track** — each write in its own try/catch so one refused field does not
+stop the lock. First lock running this code: 2026-10-14 (the 9/30 lock ran the old code). If the target sprint
 list cannot be found in ClickUp it emails a leadership alert. With `$generateSprintLockReport`, emits
 an Excel lock report of committed/conditional/unplanned/stretch points and tasks. When
 `$allowUnplannedTasks` is false, tasks appearing after lock with an UNPLANNED work type are flagged.
@@ -109,10 +125,8 @@ Otherwise it returns a skip message (captured to `Core.WorkerJobs.output`) and d
 `SprintLock()` itself is unchanged — this only decides *whether* to run it today. Action path
 `Team/Sprint/SprintLockScheduled` → `_Worker_Team_Sprint::SprintLockScheduled`.
 
-**Deploy coupling.** The worker2 code deploy and the `Core.CronJobs` row insert must land
-**together** (no committed migration seeds it — see Gotchas) — the cron row references the
-`Team/Sprint/SprintLockScheduled` action, which must exist in the deployed code or the scheduled job
-fails when it fires.
+**Deploy coupling.** Deploy worker2 **before** applying any `CronJobs` row that names a new action —
+otherwise the job fails when it fires.
 
 #### `SprintDaily($sprint = null, …)`
 In-sprint **leadership dashboard**, read-only with respect to metrics. Optionally re-captures ClickUp
@@ -127,14 +141,17 @@ Emailed to the leadership list as `TeamSprintDailyReport_Sprint{N}_{date}.xlsx`.
 
 #### `SprintEnd($sprint = null, …)`
 The largest method and the heart of the feature. Phases:
-1. **Resolve** the target (previous) sprint and its developers; optionally call `CaptureSprintEnd()` to
-   sync the final ClickUp state into `DB_TEAM`.
+1. **Resolve** the target (previous) sprint. The 10-day mid-sprint skip runs **before**
+   `CaptureSprintEnd()` — capture writes back to ClickUp, so it must not run on the middle Monday
+   (it used to, and overwrote the last sprint's data). Then optionally capture.
 2. **Score every developer** across the four metrics below.
 3. **Per-developer report workbook** (Dashboard, Team Summary, Sprint History, Task Detail, and a
    Score-Trends chart over the last `SPRINTS_BACK_FOR_AVERAGES` sprints), emailed to each developer.
 4. **Leadership summary workbook** (team-wide dashboard, all-developer summary with a *recommended
    commitment* for next sprint, and stalled-task detail), emailed to leadership.
-5. Optionally call the release-notes generator.
+5. Optionally call `SendReleaseNotes()`. Its real result sets `releaseNotesSent` /
+   `releaseNotesError` (capped at 300 chars) in the JSON summary; a failure there is caught, so
+   SprintEnd still returns.
 
 #### `SendReleaseNotes($sprint = null)`
 Pulls every **completed** task in the sprint (`statusNow IN (…DONE)`) into a CSV of `workType,
@@ -143,6 +160,14 @@ with a detailed system prompt that rewrites technical task titles into business-
 stakeholder-grouped HTML release notes. The returned HTML (code fences stripped) is emailed to the
 leadership list as "Sprint N Release Notes".
 
+#### `ResetInProgress(): string`
+7 PM weekdays: moves every **In Progress** task and subtask back to **To Do** in Dev Sprints
+(`devSprintsFolderId()`) and Design Sprints (`90116585900`). No notification. Uses ClickUp
+`GET /team/{id}/task` with `project_ids[]` (the documented folder filter — **not** `folder_ids[]`)
+plus a home-folder check, rescans from page 0 after writes (moved tasks shift pages), throttles
+writes (`RESET_IN_PROGRESS_THROTTLE_MICROSECONDS`), and caps page fetches per folder
+(`RESET_IN_PROGRESS_MAX_ITERATIONS`).
+
 ### The scoring model (Sprint End)
 Each developer receives four 0–100 sub-scores and a weighted **Final Score**:
 
@@ -339,45 +364,38 @@ see [TOGa Talos Sprint Dashboard API](../../api2/features/sprint-dashboard-api.m
   **next** sprint's start (exclusive); the code stores `dateEnd` minus one day. **Proper fix for a
   future ticket:** take the number from the name but the dates from the list object's `start_date` /
   `due_date` (epoch ms), already fetched for the date-window match.
-- **The tooling cannot bootstrap from an empty `Sprints` table — it deadlocks.** `SprintDaily`
-  (~L4806), `SprintEnd` (~L473-474) and `SendSprintEndWarnings` (~L218) all call `getSprint()`
-  **before** the `Capture*` method that would create the `Sprints` row, and `getSprint()`
-  (~L5702-5740) does `fetchRow()` with **no null check** — so on an empty table every entry point
-  fatals with `Attempt to read property "id" on null`. The thing that creates the row is never
-  reached. **Workaround (proven in production 2026-09-16):** `INSERT` one `Sprints` row by hand
-  (`sprint`, `dateStart`, `dateEnd`); `CaptureSprintDaily`'s "ensure the sprint record exists" block
-  (~L3478) self-heals from there. Anyone truncating these tables hits this — see
+- **An empty `Sprints` table still cannot bootstrap itself.** Every entry point calls `getSprint()`
+  before the `Capture*` that would create the row. Since PR #178 it **skips with a message** instead
+  of fataling (`Attempt to read property "id" on null`), but it still never creates the row. Fix:
+  `INSERT` one `Sprints` row by hand (`sprint`, `dateStart`, `dateEnd`); `CaptureSprintDaily`
+  self-heals from there. See
   [Repointing the sprint tooling](../workflows/sprint-clickup-folder-repoint.md).
-- **`getSprint()` uses `LIMIT 1` with no `ORDER BY`** (~L5717 and ~L5721, both branches). With
-  duplicate sprint numbers it returns an **arbitrary** row — a live violation of the
-  deterministic-`LIMIT 1` rule in
-  [backend-php standards](../../../standards/backend-php.md#a-limit-1-on-a-non-unique-key-must-have-a-deterministic-order-by).
+- **`_underscore` `_Model_Team_Sprint` "last 4 sprints" math must not go below sprint 1.** After the
+  numbering restart, `sprint - 4` underflowed the unsigned sprint column (MySQL Error 1690) and
+  `SprintDaily` failed every day 9/22–9/30. Fixed on `_production` by `pastSprintsRange()`
+  (TRUE-82292). Any new "N sprints back" math must clamp at 1.
 - **`SprintLock` is NOT a safe way to repopulate empty tables.** It captures before it reads, so it
   looks like a bootstrap (its `getSprint()` call is gated behind `$generateSprintLockReport`), but
   its capture block (~L4016-4030) **writes back to ClickUp for every task** — sets Previous Sprint
-  Work Type and sets "Added at sprint launch" = true. Run outside the real launch ceremony it
+  Work Type, "Added at sprint launch" = true, and the Condition copy/reset. Run outside the real launch ceremony it
   corrupts those fields across the whole sprint.
-- **The ClickUp "Condition" field (On Track) is retired (2026-09-25).** Not in the QA/QC plan, not in
-  the Dev Sprints folder, never read by code. The `SprintLock` write was removed (it would fail on the
-  new folder). `CLICK_UP_CUSTOM_FIELD_ID__CONDITION` / `CONDITION__ON_TRACK` still exist in
-  `_underscore` but are unused — do not add new writes.
-- **`SprintDaily` returns nothing on success** — a production run reads `Successfully Executed
-  (4.255 seconds): <no return message>`, so a run that worked is indistinguishable from one that
-  never fired. Breaks the return-on-both-paths rule in the
-  [worker2 architecture](../architecture.md); fix by returning a structured summary.
-- **The Team/Sprint cron rows are not in git.** Nothing in `dbchanges2/Core/` registers
-  `Team/Sprint/%` (searched 2026-09-21), despite this doc previously listing a `CronJobs
-  (SprintLockScheduled seed)` file. A concrete case of "a committed migration records intent, not
-  deployed state" ([framework-rules](../../../standards/framework-rules.md)) — read the real
-  schedule from `Core.CronJobs` in the target environment.
-- **The dev-sprints folder id lives in THREE places** — the `Sprint.php` constant, the
-  `Monitor/Oneuptime.php` fallback, and `[clickup] sprint_folder_id` in `Config/production.ini`.
-  They must move together, and `Worker/Clickup/Design.php`'s own Design-Sprints folder must not move
-  with them. Procedure:
+- **Condition and Previous Sprint Condition are live fields (2026-10-01).** The 9/25 "Condition
+  retired" call was reversed by the owner. Both fields now exist on the Dev Sprints and Design Sprints
+  lists (Previous Sprint Condition used to exist only on the old True Design Sprints folder). Writers:
+  `SprintLock` (above) and the webhook defaults in
+  [ClickUp general automation](./clickup-general-automation.md). Any task in a sprint list without
+  these fields (or **"Added at Sprint Launch"**) fails the lock write — the 9/30 lock first failed
+  with `[FIELD_115]` on that field, retry succeeded.
+- **`ResetInProgress` skips multi-listed tasks whose HOME folder is the old True Dev Sprints folder**
+  (owner accepted for now). The same gap exists in `Clickup/DevFinished/CatchUp`. Fix: walk the
+  folder's lists with `include_timl=true` instead of the team-task filter.
+- **The dev-sprints folder id: change `[clickup] sprint_folder_id` first.** `Sprint.php` reads it via
+  `devSprintsFolderId()`; the `Sprint.php` constant and the `Monitor/Oneuptime.php` fallback are only
+  fallbacks but should still move with it. Design folder ids must not move with them. Procedure:
   [Repointing the sprint tooling](../workflows/sprint-clickup-folder-repoint.md).
-- **Credentials.** The ClickUp token now comes from config (`_Component_Api_Clickup::accessToken()`);
-  the TOGa Talos AI key is **still a hardcoded constant** at `Sprint.php:43`. Locations and remediation
-  status: [committed secrets register](./committed-secrets-and-config-debt.md).
+- **Credentials.** Both come from config now: ClickUp `[clickup] token`, TOGa Talos `[talos] api_key`
+  (PR #179). The old hardcoded TOGa Talos key is still in git history and must be revoked — see the
+  [committed secrets register](./committed-secrets-and-config-debt.md).
 - **Worker contract.** Like all 2.0 workers this must return cleanly and commit writes via the
   `_Db`/transaction layer to be durable — uncommitted captures can be silently dropped.
 - **ClickUp pagination returns duplicate tasks — the sync loop must be idempotent.** ClickUp's
@@ -406,3 +424,8 @@ see [TOGa Talos Sprint Dashboard API](../../api2/features/sprint-dashboard-api.m
 - [PHP Runtime Upgrade on Elastic Beanstalk](../workflows/php-runtime-upgrade-dependency-audit.md)
 - [TOGa Talos Sprint Dashboard API](../../api2/features/sprint-dashboard-api.md) — the productionized Record Scripts.
 - [Record Scripts](../../api2/features/record-scripts.md)
+
+## Change history
+- 2026-10-01 — getSprint() deterministic + null-safe; JSON run summaries; SprintEnd skips before capture; release-notes key from `[talos] api_key`; SprintLock copies/resets Condition; new ResetInProgress + scheduled warning wrappers; cron rows recorded in dbchanges2 (ajean; worker2 PR #178, #179)
+- 2026-09-25 — Condition write removed from SprintLock (reversed 2026-10-01) (jcardinal)
+- 2026-09-16 — Repointed to the Dev Sprints folder; tables reset (kyalamarthi)

package/knowledge/2.0/apps/worker2/features/wje-freshservice-sync.md

@@ -6,8 +6,8 @@ project: Worker
 client: wje
 type: client-feature
 status: active
-updated: 2026-09-16
-owners: ["snaredla"]
+updated: 2026-10-01
+owners: ["snaredla", "mhammontree"]
 files:
   - worker2/Worker/Wje.php
   - _underscore/Component/Api/Wje/Wje.php
@@ -24,9 +24,11 @@ files:
   - worker/crons/toga2/wje/sync_togasupply_wje.php
   - worker/crons/notifications/reports/wje/wje_common.php
   - library/app/systemmonitor/wje.php
+  - worker2/Worker/Monitor/Wje.php
   - dbchanges2/Client_Wje/2024-10-04 - WjeOnboarding.sql
 related:
   - clients/wje/profile.md
+  - clients/wje/features/oneuptime-ticket-writes-monitor.md
   - 2.0/apps/worker2/features/elite-freshservice-sync.md
   - 1.0/apps/library/features/toga2-api-client-and-bridge.md
   - 2.0/apps/worker2/features/startech-webhook-handler.md
@@ -62,7 +64,7 @@ a **daily batch import** of supporting records. A separate 2-minute cron bridges
   `crons/toga2/wje/sync_togasupply_wje.php` (2-min Togadesk bridge),
   `crons/notifications/reports/wje/{wje_monthly_report,wje_quarterly_report,wje_common}.php`.
 - **Models:** `_underscore/Model/Wje/*` (8 classes, see Data model).
-- **Monitoring:** `library/app/systemmonitor/wje.php` (`App_SystemMonitor_WJE`).
+- **Monitoring:** `library/app/systemmonitor/wje.php` (`App_SystemMonitor_WJE`, Freshservice/webhook errors); `worker2/Worker/Monitor/Wje.php` ([TOGaDesk → 2.0 write monitor](../../../clients/wje/features/oneuptime-ticket-writes-monitor.md)).
 
 ### Real-time webhook (`_Worker_Wje::Webhook`)
 
@@ -115,7 +117,7 @@ asset type "Laptop", urgencies (Low/Normal/High/Critical), system params
 `TOGADESK_LAST_TICKET_INTEGRATION_DATETIME` / `TOGA_LAST_TICKET_INTEGRATION_DATETIME`.
 
 Hardcoded IDs: `CLIENT_UUID_WJE=c2f5180f-…`, `API_UUID_WJE=4750650f-…` (and `API_SECRET_WJE`) in
-`worker2/Worker/Wje.php`; TOGaDesk client `153`, dept `269` (internal `290`); default group
+`worker2/Worker/Wje.php`; TOGaDesk client `153`, dept `269` (dept `290` is defined but not synced TOGaDesk → 2.0 — see `clients/wje/profile.md`); default group
 `13000155420` / agent `13000771757`; category form field `13000126389`.
 
 ## Gotchas
@@ -134,6 +136,9 @@ Hardcoded IDs: `CLIENT_UUID_WJE=c2f5180f-…`, `API_UUID_WJE=4750650f-…` (and
 - **W12** TicketStages use Freshservice status codes (Open=2 … Closed=5); status sync depends on those matching live Freshservice statuses.
 - Secrets (`API_SECRET_WJE`, the Freshservice password) are hardcoded in source — read them from the file when needed; never copy the values into docs or commits.
 
+## Change history
+- 2026-10-01 — Corrected dept 290 (not synced 1.0 → 2.0); linked the new ticket-writes monitor. (mhammontree)
+
 ## Related
 
 - `clients/wje/profile.md` — WJE client profile + the 2-min Togadesk bridge sync.

package/knowledge/2.0/apps/worker2/workflows/sprint-clickup-folder-repoint.md

@@ -6,8 +6,8 @@ project: Worker
 client: shared
 type: workflow
 status: active
-updated: 2026-09-21
-owners: ["kyalamarthi"]
+updated: 2026-10-01
+owners: ["kyalamarthi", "ajean"]
 files:
   - worker2/Worker/Team/Sprint.php
   - worker2/Worker/Monitor/Oneuptime.php
@@ -33,15 +33,20 @@ constant edit. Done once on 2026-09-16 under TRUE-82052 (worker2 + dbchanges2).
    name with a regex that requires the year; a list created as `Sprint 1 (9/16 - 9/30)` does not
    match and the run fatals. See
    [team-sprint-management → gotchas](../features/team-sprint-management.md#gotchas).
-2. **Update all three copies of the folder id — they must move together**, or the tooling
-   split-brains:
-   - `CLICKUP_DEV_SPRINTS_FOLDER_ID` — `worker2/Worker/Team/Sprint.php` (~L10)
-   - `CLICKUP_SPRINTS_FOLDER_ID_FALLBACK` — `worker2/Worker/Monitor/Oneuptime.php` (~L25)
-   - `[clickup] sprint_folder_id` — `worker2/Config/production.ini` (~L270); the escalation cron
-     reads this and it **wins** over the Oneuptime fallback.
+2. **Update the folder id everywhere it lives:**
+   - `[clickup] sprint_folder_id` — `worker2/Config/production.ini`. **Primary:** `Sprint.php`
+     (`devSprintsFolderId()`, also used by ResetInProgress and DevFinished CatchUp) and the
+     escalation cron read it.
+   - `CLICKUP_DEV_SPRINTS_FOLDER_ID` — `worker2/Worker/Team/Sprint.php` (fallback only).
+   - `CLICKUP_SPRINTS_FOLDER_ID_FALLBACK` — `worker2/Worker/Monitor/Oneuptime.php` (fallback only).
+   - `_Worker_Clickup::QA_QC_FOLDER_IDS` — `worker2/Worker/Clickup.php` (QA/QC + sprint-default scope).
 
-   Do **not** touch `DESIGN_SPRINTS_FOLDER_ID` in `worker2/Worker/Clickup/Design.php` — Design
-   Sprints is a different folder with its own id.
+   Design Sprints is a different folder: `DESIGN_SPRINTS_FOLDER_IDS` (`Worker/Clickup/Design.php`)
+   and `CLICKUP_DESIGN_SPRINTS_FOLDER_ID` (`Sprint.php`) move only when Design moves.
+
+   **Also add the sprint custom fields to the new folder's lists** — at least Condition, Previous
+   Sprint Condition, Work Type, Previous Sprint Work Type, and "Added at Sprint Launch". A missing
+   field fails SprintLock (`[FIELD_115]`, seen 2026-09-30) and the webhook defaults.
 3. **Run the reset migration alone, on a fresh connection**, against the `Team` database:
    `dbchanges2/Team/2026-09-16a - Reset sprint tables for new ClickUp folder.sql`. It truncates
    child → parent (`Tasks_Developers` → `Tasks` → `Sprints`) wrapped in
@@ -55,8 +60,10 @@ constant edit. Done once on 2026-09-16 under TRUE-82052 (worker2 + dbchanges2).
    [creating-worker-actions](../features/creating-worker-actions.md)). From there
    `CaptureSprintDaily`'s own "ensure the sprint record exists" block (~L3478) keeps `Sprints`
    current on its own.
-6. **Verify in the DB, not from the reply.** `SprintDaily` returns nothing on success, so a good run
-   reads `Successfully Executed (…): <no return message>`. Confirm `Sprints` / `Tasks` repopulated.
+6. **Verify.** `SprintDaily` returns a JSON summary to `Core.WorkerJobs.output` (e.g.
+   `"tasksCaptured":74`); a skip message means no `Sprints` row covers today. Confirm `Sprints` /
+   `Tasks` repopulated.
+7. **Old folder:** no automation runs there. Close its open tasks by hand.
 
 ## Gotchas
 
@@ -68,12 +75,16 @@ constant edit. Done once on 2026-09-16 under TRUE-82052 (worker2 + dbchanges2).
 - **Truncate throws away sprint history.** The alternative is renumbering the old rows. On
   2026-09-16 the developer chose truncate and declined a backup — if history matters next time,
   renumber, or back up `Sprints` / `Tasks` / `Tasks_Developers` first.
-- **The cron rows are not in git.** No committed migration seeds the `Team/Sprint/%` `CronJobs`
-  rows, so after a repoint the live schedule can only be read from `Core.CronJobs` in the target
-  environment.
+- **Cron rows do not need changing.** They name actions, not folders. Schedule is recorded in
+  `dbchanges2/Core/2026-09-29a - Record sprint and design CronJobs.sql` — see
+  [team-sprint-management](../features/team-sprint-management.md#the-sprint-lifecycle--cron-schedule-prod-corecronjobs-central-time).
 
 ## Related
 
 - [Team Sprint Management & Reporting](../features/team-sprint-management.md)
 - [Creating Worker Actions](../features/creating-worker-actions.md)
 - [dbchanges2 Architecture](../../dbchanges2/architecture.md)
+
+## Change history
+- 2026-10-01 — Folder id now config-first (`devSprintsFolderId()`); field-setup step; cron rows now in git (ajean)
+- 2026-09-16 — First repoint, TRUE-82052 (kyalamarthi)

package/knowledge/INDEX.md

@@ -20,7 +20,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 ## 2.0 framework
 
 - **_underscore** (_Underscore) _(framework core)_ — 94 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
-- **worker2** (Worker) — 80 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
+- **worker2** (Worker) — 81 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/wje/INDEX.md

@@ -2,4 +2,5 @@
 
 | Doc | Framework | Summary |
 |-----|-----------|---------|
-| [Wiss, Janney, Elstner Associates, Inc.](profile.md) | 2.0 | WJE (Wiss, Janney, Elstner / "WJE IT") Freshservice help-desk client, single hardcoded tenant; open for the three sync paths and the TOGaDesk bridge ids/default |
+| [WJE: TOGaDesk → TOGa 2 ticket-writes monitor (Monitor/Wje/TicketWritesToToga2)](features/oneuptime-ticket-writes-monitor.md) | 2.0 | worker2 OneUptime push monitor counting WJE TOGaDesk tickets/replies/comments never written to TOGa 2 (NULL referenceId); open when working on WJE bridge monito |
+| [Wiss, Janney, Elstner Associates, Inc.](profile.md) | 2.0 | WJE (Wiss, Janney, Elstner / "WJE IT") Freshservice help-desk client, single hardcoded tenant; open for the three sync paths, the TOGaDesk bridge ids/department |

package/knowledge/clients/wje/features/oneuptime-ticket-writes-monitor.md

@@ -0,0 +1,80 @@
+---
+title: "WJE: TOGaDesk → TOGa 2 ticket-writes monitor (Monitor/Wje/TicketWritesToToga2)"
+framework: "2.0"
+repo: worker2
+project: Worker
+client: wje
+type: client-feature
+status: active
+updated: 2026-10-01
+owners: ["mhammontree"]
+files:
+  - worker2/Worker/Monitor/Wje.php
+  - dbchanges2/Core/2026-09-30b - Insert WJE Ticket Writes Monitor CronJob.sql
+  - worker/crons/toga2/wje/sync_togasupply_wje.php
+  - library/app/api/toga2.php
+related:
+  - ../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md
+  - ../../../1.0/apps/library/features/toga2-api-client-and-bridge.md
+  - ../../../2.0/apps/worker2/features/wje-freshservice-sync.md
+  - ../profile.md
+---
+worker2 OneUptime push monitor counting WJE TOGaDesk tickets/replies/comments never written to TOGa 2 (NULL referenceId); open when working on WJE bridge monitoring, its departments, or clearing a stuck ticket.
+
+## Summary
+`Monitor/Wje/TicketWritesToToga2` (`_Worker_Monitor_Wje`, TRUE-80523) watches the 1.0 → 2.0 half of the WJE TOGaDesk bridge. It follows the shared [OneUptime push-metric pattern](../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md) — read that for payload contract, criteria, and provisioning.
+
+- **Status 2026-10-01:** committed on branch `TRUE-80523` (worker2 + dbchanges2 + worker comment), **not deployed**. Cron seed ships `isActive = 0`; `$ONEUPTIME_URL` is still empty (push credential — never record it).
+- Runs in worker2, outside the 1.0 worker it watches. Reads `TOGaDeskSupport` via `_underscore::DB_TOGADESK1` (see [worker2 legacy DB access](../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md)).
+- OneUptime monitor name: **"WJE Ticket Writes to TOGa 2"**.
+
+## How it works
+
+### Why a backlog, not a checkpoint-freshness check
+The bridge catches a per-ticket exception → Sentry only, and **still advances `TOGA_LAST_TICKET_INTEGRATION_DATETIME` past it**. The failed ticket is never retried unless touched again. A checkpoint-age monitor would read healthy. A row with NULL `referenceId` catches both a dead cron and silent per-ticket failures (link model: [bridge doc](../../../1.0/apps/library/features/toga2-api-client-and-bridge.md)).
+
+### What it counts
+WJE rows (`tickets.clientid = 153`) in `tickets`, `tickets_replies`, `comments` where `referenceId` is NULL or `''`, created on/after `BACKLOG_CUTOFF_DATE = '2025-05-01'`, in the configured departments, minus `excludedTicketNumbers`.
+
+Skip rules mirror `syncTogaDesk1TicketIntoToga2Ticket` in `library/app/api/toga2.php` (~L12280-12290): a reply with a blank message falls back to `newstatus` and is skipped if still PHP-empty (NULL, `''`, `'0'`) — it never gets a `referenceId`, so the monitor skips it too. Comments are always sent.
+
+### Decision + payload
+- `alarm: HIGH` when any counted row is `>= alertThresholdMinutes` old; else `alarm: OK`.
+- `status: error` on DB failure (payload carries **only** `errorClass` + `errorNumber` — the exception message can hold SQL, DB host, DB user) and on empty `departmentIds` (`error: no_departments_configured`).
+- Body: `latePendingCount`, `pendingCount`, per-type counts, `oldestPendingMinutes`, `alertThresholdMinutes`, `lateTicketNumbers` (top 10), `departmentIds`, `excludedTicketCount`.
+
+### Parameters (`Core.CronJobs.parameters`, no deploy to change)
+`{"alertThresholdMinutes":15,"departmentIds":[269],"excludedTicketNumbers":[]}`
+- `departmentIds` PHP default is `[]` **on purpose** — the DB row is the only home of the list. Missing list → `status: error`, never a silent hardcoded dept. The cron comment in `sync_togasupply_wje.php` points here; keep the two in step if the sync's departments change.
+- `excludedTicketNumbers` — TOGaDesk ticket numbers the team gives up on, so one permanently failing ticket does not hold the alarm red.
+
+### Clear a stuck ticket (runbook)
+1. Fix the cause (Sentry has the exception).
+2. Add a reply to the ticket in TOGaDesk so the sync picks it up again — or move the checkpoint back.
+3. If abandoning it, add its ticket number to `excludedTicketNumbers`.
+
+### Activation (in order)
+1. Create the OneUptime Incoming Request monitor with **body rules only**: Contains `"alarm":"HIGH"` → Offline + incident; Contains `"status":"error"` → Offline + incident; Contains `"alarm":"OK"` → Online.
+2. Paste its URL into `$ONEUPTIME_URL`.
+3. Push and deploy worker2.
+4. Run the Core seed `2026-09-30b - Insert WJE Ticket Writes Monitor CronJob.sql`.
+5. Test HIGH: set `departmentIds` to `[290]` (has old unsent rows), hand-run. Restore `[269]`, hand-run to see recovery.
+6. Set `isActive = 1`.
+7. Only then add the not-received 10/15 min rules (see the activation-ordering trap in the shared doc).
+
+## Gotchas
+- **Dept 269 is very low volume** (Sept 2026: 3 tickets, 7 replies, 2 comments). "No writes" is normal — this is why it is a backlog monitor, not a "writes stopped" monitor.
+- **Blind spot: field-only edits.** Priority/assignee change on an already-linked ticket creates no row, so a failed push is invisible. Status changes are covered (they arrive as replies).
+- **Clock is US/Central.** `TOGaDeskSupport` `NOW()` and row timestamps are both server US/Central (the `_underscore` driver sets no session `time_zone`). Spring DST can false-alarm once; autumn can delay an alarm up to 1h.
+- **Pre-cutoff history never drains:** 21 sendable unsent dept-269 rows 2024-12 → 2025-04-22 (early integration). That is why the cutoff is 2025-05-01.
+- **Query cost (prod, verified):** `tickets` via index_merge(departmentid, clientid); `tickets_replies` via `ticketid` index; `comments` has **no** `ticketid` index → full scan of ~13k rows (acceptable). Timestamp columns have no `ON UPDATE`.
+- **Do not add 290 casually.** Dept 290 is not synced 1.0 → 2.0 today (see [profile](../profile.md)); pointing the monitor at it would alarm on the known backlog, not a new failure.
+- **The ClickUp TRUE-80523 description is fabricated** (Talos auto-generated) — see [MCP tool usage gotcha](../../../standalone/apps/claude/workflows/mcp-tool-usage.md). Trust this doc and the code.
+
+## Related
+- [OneUptime push-metric monitors for 2.0 workers](../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md) — shared pattern
+- [App_Api_Toga2 bridge](../../../1.0/apps/library/features/toga2-api-client-and-bridge.md) — `syncWithTogadesk`, `referenceId` write-back
+- [WJE profile](../profile.md)
+
+## Change history
+- 2026-10-01 — Created: monitor built on branch TRUE-80523, not deployed, cron `isActive = 0`. (mhammontree)

package/knowledge/clients/wje/profile.md

@@ -4,22 +4,26 @@ framework: "2.0"
 apps:
   - worker
   - library
+  - worker2
+  - dbchanges2
 project: Library
 client: wje
 type: profile
 status: active
-updated: 2026-09-16
-owners: [jcardinal]
+updated: 2026-10-01
+owners: [jcardinal, mhammontree]
 files:
   - worker/crons/toga2/wje/sync_togasupply_wje.php
   - worker2/Worker/Wje.php
   - worker/crons/toga2/wje/import_supporting_records.php
+  - worker2/Worker/Monitor/Wje.php
 related:
   - ../../1.0/apps/library/features/toga2-api-client-and-bridge.md
   - ../../2.0/apps/worker2/features/wje-freshservice-sync.md
+  - ./features/oneuptime-ticket-writes-monitor.md
 ---
 
-WJE (Wiss, Janney, Elstner / "WJE IT") Freshservice help-desk client, single hardcoded tenant; open for the three sync paths and the TOGaDesk bridge ids/defaults.
+WJE (Wiss, Janney, Elstner / "WJE IT") Freshservice help-desk client, single hardcoded tenant; open for the three sync paths, the TOGaDesk bridge ids/departments, and its monitor.
 
 ## Summary
 
@@ -31,9 +35,19 @@ Data moves between WJE and TOGA on three paths:
 
 1. **Real-time Freshservice webhook** → `_Worker_Wje::Webhook` (worker2) — creates/updates tickets, contacts, assets, groups, categories, and conversation notes, keyed by `c_wje*` custom fields.
 2. **Daily batch import** (`worker/crons/toga2/wje/import_supporting_records.php`) — imports canned responses, requesters, assets, groups, and the 3-level category hierarchy.
-3. **2-minute TOGaDesk bridge** (`App_Api_Toga2::syncWithTogadesk`) — the cron `worker/crons/toga2/wje/sync_togasupply_wje.php` enables the **full** set of bridge sub-syncs (tickets both directions, ticket-notes, contacts→people, items/units→assets, predefined-replies, ticket-teams→groups, ticket-categories) for TOGaDesk client id 153, department 269 (plus internal-tickets department 290).
+3. **2-minute TOGaDesk bridge** (`App_Api_Toga2::syncWithTogadesk`) — the cron `worker/crons/toga2/wje/sync_togasupply_wje.php` enables the **full** set of bridge sub-syncs (tickets both directions, ticket-notes, contacts→people, items/units→assets, predefined-replies, ticket-teams→groups, ticket-categories) for TOGaDesk client id 153. **TOGaDesk → 2.0 syncs department 269 only.**
+
+Monitoring: [ticket-writes monitor](./features/oneuptime-ticket-writes-monitor.md) alarms when a dept-269 TOGaDesk row is not written to 2.0.
+
+## TOGaDesk departments
+
+- **269** — tickets created in TOGaDesk (`153000xxx` numbers). Very low volume. Synced TOGaDesk → 2.0.
+- **290** — WJE Freshservice tickets that arrive in TOGaDesk **from** 2.0 (ticket number = Freshservice INC number, e.g. `65239`; ~100-200/month, all carry `referenceId`). The cron defines `TOGADESK_WJE_INTERNAL_TICKETS_DEPARTMENT_ID = 290` but never passes it (`$monitorTogadeskDepartmentIds` not passed), so 290 is **not** synced TOGaDesk → 2.0. Confirmed with Jonathan 2026-09-30: only 269 is synced today.
+
+**⚠ Known gap (not fixed):** a reply or comment typed in TOGaDesk on a dept-290 ticket is never written to 2.0 and never reaches WJE. Verified: ticket `65239`, a reply on 2026-08-18 has NULL `referenceId` and is absent from `Client_Wje.TicketNotes`. Since 2026-01 ~49 replies + 10 comments are stuck. **If 290 is ever added to the sync, its first run pushes that whole old backlog to WJE at once — decide what to do with it first.**
 
 ## Related
 
-- **[wje-freshservice-sync](../../2.0/apps/worker2/features/wje-freshservice-sync.md)** — full integration: webhook handler, import cron, `c_wje*` models, API clients, schema, reports, monitoring, gotchas.
+- **[wje-freshservice-sync](../../2.0/apps/worker2/features/wje-freshservice-sync.md)** — full integration: webhook handler, import cron, `c_wje*` models, API clients, schema, reports, gotchas.
 - **[toga2-api-client-and-bridge](../../1.0/apps/library/features/toga2-api-client-and-bridge.md)** — the `syncWithTogadesk` bridge mechanism.
+- **[oneuptime-ticket-writes-monitor](./features/oneuptime-ticket-writes-monitor.md)** — the 1.0 → 2.0 write monitor.

package/knowledge/standalone/apps/claude/workflows/mcp-tool-usage.md

@@ -6,8 +6,8 @@ project: Claude Harness
 client: shared
 type: workflow
 status: active
-updated: 2026-09-25
-owners: ["jcardinal", "tcox", "ajean"]
+updated: 2026-10-01
+owners: ["jcardinal", "tcox", "ajean", "mhammontree"]
 files:
   - claude/.claude/skills/kickoff/SKILL.md
   - claude/.claude/skills/capture/SKILL.md
@@ -106,6 +106,7 @@ SELECT name, clientIdentifier FROM Clients WHERE name LIKE '%<keyword>%';
 - **⚠ "Beta" is `dev-sandbox`, NOT `client-beta`.** For the beta API tier (`api.beta.togahub.com`), `Core.DatabaseHosts` maps environment `beta` for `Client_*` schemas to the **dev-sandbox** cluster — so "the beta database" and "the dev-sandbox database" are the same host. The MCP's `client-beta` environment exposes **no schemas** and querying it looks like the data is missing. Query **`dev-sandbox`** whenever someone says "beta". Any frontend pointed at `VITE_API=https://api.beta.togahub.com/v2` is therefore reading/writing dev-sandbox data. (2024-era onboarding SQL shows beta on a us-west-2 `client-cluster`; that has since been consolidated — trust `Core.DatabaseHosts`, not old migrations.)
 - **⚠ The write-blocker is a naive string scan — it rejects `UPDATE`/`REPLACE` even inside a string literal.** `toga_query` refuses the whole statement if those words appear anywhere in it, so a read-only query like `… WHERE output LIKE '%skipped update%'` fails validation. **A column alias trips it too** — `… AS updateDisabled` is rejected on the same scan, so the alias has to be renamed (`skippedDisabled`), not just the predicate. Work around it by matching on a fragment that avoids the keyword (`LIKE '%disabled%'`, `LIKE '%skipped%'`), or by pulling the rows and filtering client-side — don't conclude the data isn't there.
 - **Production sessions render in US/Central (UTC−5); most other timestamps you're comparing are UTC.** GitHub/API/webhook timestamps are UTC, so a naive `dtStamp` vs. commit-time comparison is off by five hours — enough to make a healthy worker fleet look dead. Anchor both sides to UTC (or `CONVERT_TZ`) before drawing a conclusion about "when did this last run".
+- **⚠ Talos auto-generated "KB investigation" text on a ClickUp ticket can be fabricated.** TRUE-80523's description called WJE "Write Job Entry" and cited a CloudWatch/Datadog ADR, a DLQ, and a Migration Sprint retro — none exist. Treat such write-ups as unverified; check every name and source against the code, this KB, and the data before acting on it.
 - **`local` is not this MCP.** If someone means their own machine's database, use the `mysql` CLI via shell, not `toga-db`.
 - **The client roster is wider than `registry.json`, and identifiers are not guessable.** `Core.Clients` held **46 clients** on 2026-07-30 against 17 in `registry.json`. A client absent from the registry is normal, not an error — the registry tracks clients whose *code knowledge* has been captured, not the full book of business. Identifiers do not follow from the display name, so **look them up, never construct them**:
 
@@ -123,6 +124,7 @@ SELECT name, clientIdentifier FROM Clients WHERE name LIKE '%<keyword>%';
   Schema names are **case-sensitive** — copy the exact value from `toga_list_schemas` or `Core.Clients`. `Client_Aig` works; `Client_AIG` and `client_aig` do not.
 
 ## Change history
+- 2026-10-01 — Added gotcha: Talos auto-generated ClickUp ticket write-ups can invent sources (TRUE-80523). (mhammontree)
 - 2026-09-25 — corrected the "TOGa IQ" row: it now names the separate `toga25-iq` app, not the `talos` codebase (rebrand) (jcardinal)
 
 ## Related

package/package.json

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