toga-ai 1.0.303 → 1.0.305

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

@@ -21,4 +21,5 @@
 | [Surface Resolver (_Model_Core_Surface::resolve — replaces Page::meta)](features/surface-resolver.md) | The runtime for the platform-wide **Surface** UI presentation layer: 9 `_underscore` models plus a cached resolver, `_Model_Core_Surface::resolve(&$api, string | _underscore/Model/Core/Surface.php, _underscore/Model/Client/AclRecordScript.php, _underscore/Model/Core/RecordScript.php, dbchanges2/Core/2026-06-30a - SurfaceMetaGroupAndSalesOrderSections.sql, dbchanges2/Client/2026-06-30a - SurfaceMetaGroupAcl.sql, dbchanges2/Client_Quad/2026-07-01a - GrantSurfacesMetaGroupScriptAcl.sql, dbchanges2/Client_CompassCanada/2026-07-01a - GrantSurfacesMetaGroupScriptAcl.sql, dbchanges2/Core/2026-06-29b - SurfaceMetaPublicReadAcl.sql, dbchanges2/Client/2026-06-29c - SurfaceRecordScriptAcl.sql, dbchanges2/Core/2026-06-29c - SurfaceDebugPhpMethodFix.sql, _underscore/Model/Core/SurfaceElement.php, _underscore/Model/Core/Action.php, _underscore/Model/Core/Vocabulary.php, _underscore/Model/Core/VocabularyTerm.php, _underscore/Model/Core/Message.php, _underscore/Model/Client/SurfaceOverride.php, _underscore/Model/Client/MessageTranslation.php, _underscore/Model/Client/ThemeToken.php, _underscore/Model/Core/Page.php |
 | [Tracking-Number Bridge Migration (ASN / Item Fulfillment / Item Receipt)](features/tracking-number-bridges.md) | Shipment tracking numbers used to live as **scalar FK columns** (`trackingNumberId`, `returnTrackingNumberId`) directly on the lowest-level "unit"/"item" tables | api2/Component/Api/V2/V2.php, _underscore/Model/Client/AdvanceShippingNoticeItemUnit.php, _underscore/Model/Client/AdvanceShippingNoticeItemUnits/TrackingNumber.php, _underscore/Model/Client/ItemFulfillmentItemUnits/TrackingNumber.php, _underscore/Model/Client/ItemFulfillment.php, _underscore/Model/Prudential/AdvanceShippingNotice.php, _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Trait/Netsuite/ItemFulfillment.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client/2026-06-10 - TrackingNumberBridges.sql, dbchanges2/Core/2026-06-10 - TrackingNumberBridges.sql, dbchanges2/Client_Prudential/2026-06-15 - ItemFulfillmentTrackingNumberAclLogicGroups.sql, dbchanges2/Client_Quad/2026-06-18a - ItemFulfillmentItemReceiptTrackingNumberAclLogicGroups.sql, dbchanges2/Client_Nychh/2026-06-19b - ItemFulfillmentItemReceiptTrackingNumberAclLogicGroups.sql, dbchanges2/Client_Nychh/2026-06-19a - FixItemFulfillmentTableViewTrackingAndRoot.sql, dbchanges2/Client_Quad/2026-06-19a - FixItemFulfillmentTableViewTrackingAndRoot.sql |
 | [Units for Items for Purchase Orders — Data Structure](features/units-for-items-for-purchase-orders.md) | Describes how unit (serialized inventory) data is linked to sales-order and purchase-order line items behind the `units-for-items-for-purchase-orders` TableView |  |
+| [Refreshing a Local Dev Database from Beta (dev-sandbox)](workflows/local-db-refresh-from-beta.md) | How to reset a local 2.0 dev database from the **beta / dev-sandbox** environment: dump each schema (`Core`, `Client_<Id>`, `Logs_<Id>`, …) from the beta host, | api2/Config/, _underscore/Loader.php, _underscore/Model/Client/BundleTranslation.php, api2/Component/Api/V2/V2.php, toga25-supply/sync_compasscanada_schema.sql |
 | [Running a 2.0 App Locally (browser, end-to-end via api2)](workflows/running-a-2.0-app-locally.md) | The full dependency chain required to run a 2.0 client app **through the browser**, end-to-end, against a **local `api2`** (e.g. | _underscore/Environment.php, _underscore/Config.php, _underscore/Database.php, _underscore/Route.php, api2/Component/Api/V2/V2.php, api2/index.php, api2/.htaccess |

package/knowledge/2.0/apps/_underscore/features/per-client-database-connections.md

@@ -7,13 +7,14 @@ client: shared
 type: feature
 status: active
 updated: 2026-07-09
-owners: ["dfranks", "jcardinal", "mhammontree"]
+owners: ["dfranks", "jcardinal", "mhammontree", "apeterson"]
 files:
   - _underscore/Database.php
   - _underscore/ApiRequest.php
   - _underscore/Model/Client/Logs/Api.php
 related:
   - ../architecture.md
+  - ../workflows/local-db-refresh-from-beta.md
 ---
 
 ## Summary
@@ -84,9 +85,10 @@ registration is region-aware in `api2/Controller/Index.php`; the alias const is
   For logs, structure-only is enough (you never need prod log rows locally):
   `mysqldump -h reader1.logs.database.togahub.com -u admin -p<pw> --no-data --no-tablespaces
   --set-gtid-purged=OFF --column-statistics=0 Logs_<Id> | mysql -u root Logs_<Id>` (create the
-  empty DB first). Data DB comes from `reader1.client.database.togahub.com` (see the local-DB
-  refresh notes). This is a **local-environment** gap, not a code bug — do not "fix" it by
-  disabling logging in shared code.
+  empty DB first). Data DB comes from `reader1.client.database.togahub.com`, or refresh the whole
+  set from beta — see [Refreshing a local dev DB from beta](../workflows/local-db-refresh-from-beta.md).
+  This is a **local-environment** gap, not a code bug — do not "fix" it by disabling logging in
+  shared code.
 - Related 1.0 analogue: the legacy `App_` worker has the same hazard writing to `Logs.API`
   (`db_logs`) — the laptop trap there is documented separately in the worker NetSuite bootstrap
   notes.
@@ -94,6 +96,8 @@ registration is region-aware in `api2/Controller/Index.php`; the alias const is
 ## Change history
 
 - 2026-07-09 — Linked the new [Running a 2.0 app locally](../workflows/running-a-2.0-app-locally.md) runbook, which frames these three connections as one requirement of a full local browser run. (mhammontree)
+- 2026-07-09 — Linked the new [local-DB-refresh-from-beta workflow](../workflows/local-db-refresh-from-beta.md)
+  from the logs-trap fix (refreshing all local schemas from beta covers the missing `Logs_<Id>`). (apeterson)
 - 2026-07-07 — Noted the new shared **Cache** cluster (`Databases` id 145, alias `DB_CACHE`,
   region-aware) added for the api2 cross-client retrieval engine. (jcardinal)
 - 2026-06-18 — Documented after the `Logs_Growrk`/`Logs_Aig` local 500s while testing the

package/knowledge/2.0/apps/_underscore/features/tracking-number-bridges.md

@@ -6,8 +6,8 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-06-19
-owners: ["jcardinal", "mhammontree", "dfranks"]
+updated: 2026-07-09
+owners: ["jcardinal", "mhammontree", "dfranks", "apeterson"]
 files:
   - api2/Component/Api/V2/V2.php
   - _underscore/Model/Client/AdvanceShippingNoticeItemUnit.php
@@ -156,9 +156,20 @@ returnTrackingNumber: {...} }]`, and an IFIU's as `itemFulfillmentItemUnitTracki
     (`Client_Nychh/2026-06-19b - ...`, all of 317-322) so far. Each new client is whack-a-mole until
     the chain is folded back into the base migration + blank-client template.
 
+- **`Client_CompassCanada` is missing these bridge tables on *beta* (local drift).** Beta's
+  `Client_CompassCanada` lacks 17 tables that prod has — including the `*_TrackingNumbers`
+  bridges and `AdvanceShippingNoticeItemUnits` — so any local DB reset **from beta** reintroduces
+  the drift and a SalesOrders record load 500s with **1146 "table doesn't exist"** (the
+  `_trackingNumbers` computed field joins the bridges). Fix locally by re-running
+  `toga25-supply/sync_compasscanada_schema.sql` against `Client_CompassCanada` (local-only — prod
+  already has the tables). See the
+  [local-DB-refresh-from-beta workflow](../workflows/local-db-refresh-from-beta.md).
 - **Porting the item-fulfillment TableView fix to another client is two independent decisions, not a copy-paste.** The **re-root** (Units 31 → ItemFulfillmentItems 29 + OUTER unit chain) is universally portable and fixes the "0 records" bug everywhere. The **tracking source is client-specific**: Compass writes one tracking number per item fulfillment at the **item level (318)**, so its views read 318. Other clients populate different bridge levels — verify with `SELECT COUNT(*)` per bridge before choosing. As of 2026-06-19, **record 318 is empty in `Client_Nychh` and `Client_Quad`**; their tracking lives at the **IF/shipment level (317)** (covers IFIs: NYCHH 7955/10049 ≈ 79%, Quad 4878/4967 ≈ 98%) and the **unit level (319)** (≈ 7–9% — serialized only). Copying Compass's 318 join into a client that doesn't write 318 yields a structurally-correct view with permanently blank tracking until 318 is backfilled. (NYCHH's pre-fix view pointed at the now-deleted record 41 = old IF-level/package bridge, i.e. it originally intended IF-level 317.)
 
 ## Change history
+- 2026-07-09 — Noted that `Client_CompassCanada` is missing these bridge tables on **beta**, so a local
+  reset from beta reintroduces the 17-table drift (1146 on SalesOrders load); fix locally with
+  `sync_compasscanada_schema.sql`. Cross-linked the new local-DB-refresh-from-beta workflow. (apeterson)
 - 2026-06-19 — **NYCHH** hit the bridge ACL gap in prod: 403 EZ-1 on `item-fulfillment-tracking-numbers` (DEBUG "No ACL Logic Groups defined", aclRecordPermissionId 318 = record 317, roleId 1, appId NULL). Confirmed all 6 bridge perms (ids 318-323, records 317-322) had 0 logic groups; added the chain via `Client_Nychh/2026-06-19b - ItemFulfillmentItemReceiptTrackingNumberAclLogicGroups.sql` (all 6 bridges, idempotent anti-joins, RANDOM_BYTES uuids, slug='all'/sqlExpression='1', record ids derived from AclRecordPermissions). Same fix pattern as Quad 2026-06-18a / Prudential 2026-06-15. (jcardinal)
 - 2026-06-19 — Applied the Compass item-fulfillment TableView fix to **NYCHH** and **Quad** (`Client_Nychh`/`Client_Quad` `2026-06-19a - FixItemFulfillmentTableViewTrackingAndRoot.sql`): re-rooted views 12 & 13 at ItemFulfillmentItems, item-level tracking via 318, preserving Quad's three Units-level custom columns. Confirmed read-only that record 318 is empty for both clients (tracking blank until backfilled) — their data is at 317 (IF-level, ~79%/~98% coverage) and 319 (unit-level); recorded the portability gotcha. (jcardinal)
 - 2026-06-18 — Quad's NetSuite TOGa Supply sync (`sync_togasupply_quad.php`) hit the bridge ACL gap in prod: 403 EZ-1 on `item-fulfillment-tracking-numbers` (Sentry 7559037554, 46×, since the 2026-06-15 deploy). Confirmed `Client_Quad` perms 380-385 (recs 317-322, role 1) had 0 logic groups; added the chain via `Client_Quad/2026-06-18a - ItemFulfillmentItemReceiptTrackingNumberAclLogicGroups.sql` (all 6 bridges, idempotent, RANDOM_BYTES uuids). Noted the gap surfaces via the per-client sync, not only UI reads. (dfranks)

package/knowledge/2.0/apps/_underscore/workflows/local-db-refresh-from-beta.md

@@ -0,0 +1,103 @@
+---
+title: Refreshing a Local Dev Database from Beta (dev-sandbox)
+framework: "2.0"
+repo: _underscore
+project: _Underscore
+client: shared
+type: workflow
+status: active
+updated: 2026-07-09
+owners: ["apeterson"]
+files:
+  - api2/Config/
+  - _underscore/Loader.php
+  - _underscore/Model/Client/BundleTranslation.php
+  - api2/Component/Api/V2/V2.php
+  - toga25-supply/sync_compasscanada_schema.sql
+related:
+  - ../features/per-client-database-connections.md
+  - ../features/tracking-number-bridges.md
+---
+
+## Summary
+
+How to reset a local 2.0 dev database from the **beta / dev-sandbox** environment: dump each
+schema (`Core`, `Client_<Id>`, `Logs_<Id>`, …) from the beta host, drop+recreate the local
+schema, and re-import. This is the "local-DB refresh" the
+[per-client DB connections](../features/per-client-database-connections.md) doc points at. The
+procedure is routine, but the **beta sandbox user is a managed account without `SUPER`/`RELOAD`**,
+so the naive `mysqldump` invocation fails — and a reset pulls Core state that can leave the local
+API broken until two known side-effects are fixed (see Gotchas).
+
+Connection endpoints (beta host, port, schema names) live in **api2 `Config/*.ini`** under the
+`[database]` blocks. Read them there — **never record credential values in knowledge or commits.**
+
+## Steps
+
+Order matters — dump first so a failed dump never wipes a local schema it can't refill.
+
+1. **Get on the company VPN.** The beta DB host (`dev.sandbox.database.togahub.com`) is
+   firewalled — reachable **only** on the VPN. Off-VPN a direct connect just times out (it is not
+   an auth error), which is the usual first red herring.
+2. **Per schema, dump → drop → recreate → import**, looping over the schemas you need
+   (`Core`, `Client_<Id>`, and any `Logs_<Id>`/`Archive_<Id>` you run locally):
+   ```bash
+   for DB in Core Client_Compass Client_CompassCanada Client_Quad Client_Nychh; do
+     mysqldump -h dev.sandbox.database.togahub.com -u admin -p<pw> \
+       --skip-lock-tables --no-tablespaces --set-gtid-purged=OFF \
+       --routines --triggers "$DB" > "/tmp/$DB.sql" || break
+     mysql -u root -e "DROP DATABASE IF EXISTS \`$DB\`; CREATE DATABASE \`$DB\`;"
+     mysql -u root "$DB" < "/tmp/$DB.sql"
+   done
+   ```
+   The `|| break` is load-bearing: if the dump fails, stop before the `DROP` so you never destroy
+   a local schema you cannot refill.
+3. **Bring the local `_underscore` checkout up to the branch beta was built from** (see the
+   missing-model gotcha) and **re-apply local-only client schema fixes** (see the CompassCanada
+   drift gotcha).
+4. **Smoke-test** one API request per refreshed client before relying on the reset.
+
+## Gotchas / known issues
+
+- **Beta `admin` lacks `RELOAD` → `--single-transaction` fails.** The managed sandbox account
+  cannot `FLUSH TABLES WITH READ LOCK`, so the default `mysqldump --single-transaction` dies with
+  `Couldn't execute 'FLUSH TABLES WITH READ LOCK': Access denied ... (1045)`. **Fix:** drop
+  `--single-transaction` and take a **non-locking** dump instead:
+  `--skip-lock-tables --no-tablespaces --set-gtid-purged=OFF --routines --triggers`. (Add
+  `--column-statistics=0` if your client's mysqldump is newer than the server.)
+- **A reset can 500 *every* request with a missing `_Model_Client_*` autoload.** Beta's `Core`
+  registers models in `Core.Records`/`RecordFields`, and `api2/Component/Api/V2/V2.php`
+  (`processRoutePairs`, ~line 3454) iterates **every** registered model and dereferences its
+  `::TABLE`. If beta registers a model whose PHP class is **newer than your local `_underscore`
+  checkout**, the `_underscore/Loader.php` autoloader throws
+  `Could not find required file for '_Model_Client_BundleTranslation'` and the whole API 500s.
+  Models are **hand-written committed source** (no generator, no cache), so the fix is a **git
+  pull of the missing file**, not a cache clear — e.g. bring
+  `_underscore/Model/Client/BundleTranslation.php` in from branch `TRUE-80065`
+  (commit `ef6ebd80`). General rule: after a beta reset, sync `_underscore` to (at least) the
+  branch beta was built from.
+- **Resetting `Client_CompassCanada` reintroduces the 17-table schema drift.** CompassCanada on
+  **beta** is missing 17 tables that **prod** has (`AdvanceShippingNoticeItemUnits`, the
+  `*_TrackingNumbers` bridges, TransferOrder link tables, `Customers_Catalogs`), so a reset wipes
+  the prior local fix and a SalesOrders record load 500s with **1146 "table doesn't exist"** (the
+  `_trackingNumbers` computed field joins those tables). **Fix:** re-run
+  `toga25-supply/sync_compasscanada_schema.sql` against `Client_CompassCanada` (17 ×
+  `CREATE TABLE IF NOT EXISTS`). **Local-only — do NOT replay to beta/prod** (prod already has
+  them). **Operator trap:** the file uses **unqualified** table names, so you must have
+  `Client_CompassCanada` selected as the active DB in your client — a standalone `USE` line run
+  as a separate statement does **not** carry over, and the tables land in the wrong schema. See
+  [tracking-number-bridges](../features/tracking-number-bridges.md) for the bridge tables.
+- **The logs-DB write trap still applies.** A reset only refreshes the schemas you loop over; if
+  you skip `Logs_<Id>` the first request 500s (`Unknown database 'logs_<id>'`) on the logging
+  write. See [per-client DB connections](../features/per-client-database-connections.md).
+- **Committed dbchanges2 seeds usually survive a reset.** Beta already carries the committed
+  `Core` change-sets (e.g. the Surface-layer seeds), so a later replay of *committed* changes is
+  largely a no-op. Only ad-hoc changes that were never committed to dbchanges2 need re-applying
+  after a reset.
+
+## Change history
+
+- 2026-07-09 — Initial capture: non-locking `mysqldump` recipe (beta `admin` lacks `RELOAD`), the
+  VPN-only beta host, and the two recurring post-reset side-effects — a missing `_Model_Client_*`
+  autoload 500 (pull the model file, no cache) and the CompassCanada 17-table drift
+  (`sync_compasscanada_schema.sql`, local-only). (apeterson)

package/knowledge/INDEX.md

@@ -17,7 +17,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 ## 2.0 framework
 
-- **_underscore** (_Underscore) _(framework core)_ — 27 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
+- **_underscore** (_Underscore) _(framework core)_ — 28 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
 - **worker2** (Worker) — 27 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 10 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 3 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)

package/knowledge/clients/nychh/profile.md

@@ -5,13 +5,14 @@ apps:
   - _underscore
   - api2
   - toga2-supply
+  - toga25-supply
   - dbchanges2
 project: _Underscore
 client: nychh
 type: profile
 status: active
-updated: 2026-06-19
-owners: ["jcardinal"]
+updated: 2026-07-09
+owners: ["jcardinal", "apeterson"]
 files: []
 related:
   - ../../2.0/apps/_underscore/features/tracking-number-bridges.md

package/knowledge/sessions/2026-07-09-true-80100-mso-create-fix-mhammontree.md

@@ -0,0 +1,64 @@
+---
+type: session
+slug: true-80100-mso-create-fix
+title: Fix errors creating a manual managed service order (togadesk)
+author: mhammontree
+repos: [togadesk]
+framework: "1.0"
+client: shared
+status: active
+created: 2026-07-09
+updated: 2026-07-09
+---
+
+# Session: true-80100-mso-create-fix
+**Date:** 2026-07-09
+**Project/Repo:** togadesk (1.0)
+**Task:** Fix TRUE-80100 — errors creating a manual managed service order (MSO) in togadesk; reported against the Northwell Health client but the defects are general to the shared MSO create flow.
+
+---
+
+## What WORKED
+<!-- Include specific file paths and evidence -->
+- **Server crash fix** — `desk/includes/controllers/actions/tickets/add.php:353-354`: changed `App_Page::getVar('installation')` and `getVar('access-instructions')` to `App_Page::getVarIfSet(...)`. Root cause: `App_Page::getVar()` (library/app/page.php:354) THROWS `Exception("Variable 'X' does not exist in the request headers.")` when the var is absent; the manual MSO form omits `installation`, so the onsite-service (TYPE_ONSITESERVICE) branch crashed. `getVarIfSet()` (page.php:382) returns null instead. Evidence: matched the original Sentry trace (getVar → add.php:353 → require chain); after fix, **Test 1** (user WITH an address) created the MSO successfully with no exception.
+- **Submit-validation deadlock fix** — `desk/template/modals/tickets/addNew.php` submit handler (~line 3284): validator now reads `newAddressCount = parseInt($('#newAddressCount').val())||0` and only blocks when `selectedValue==0 && newAddressCount==0`. Root cause: an existing End User with no saved address got an empty `#userlocation` dropdown + an auto-opened inline add-address form, but the validator required a non-zero dropdown pick and ignored the inline address — unresolvable deadlock. Evidence: **Test 2** (user with NO address → filled inline add-address form) created the MSO successfully.
+- **Chrome autofill hardening** — added `autocomplete` attributes: `autocomplete="off"` on `#formModal` (`desk/template/footer.php:9`); `autocomplete="new-password"` on `#new-user-password`; `autocomplete="off"` on the new-user fields, new-address fields (address1/2, city, state, zip), Summary (`#subject`), and the select2 dropdowns (`#enduser`, `#userlocation`, `#location`) in `addNew.php`. Root cause: the password field made Chrome autofill Summary/address fields (blue highlight) without firing change/input events or syncing select2, so validation saw empty values. Defensive — cannot regress the create flow. Not independently re-tested (users filled fields manually in both tests).
+- **Address data model confirmed** — the End User Address dropdown is sourced per-person from `people_addresses INNER JOIN addresses ON addresses.id = people_addresses.addressid WHERE people_addresses.peopleid = <uid>` (`desk/template/pages/getinfo.php:152-171`, db_togadesk / TOGaDeskSupport). Confirmed live: a user WITH a `people_addresses` row populates the dropdown and selects fine. Empty dropdown = that person has no `people_addresses` row (legitimate data state), not a bug.
+- **Knowledge captured & pushed** — `/capture` published to `_main`: new feature doc `1.0/apps/togadesk/features/managed-service-order-create.md` and an elevated update to `1.0/standards/backend-php.md` (getVar-throws rule). validate OK (28 repos), index 233 docs.
+- **Code pushed** — all three fixes committed and pushed to branch `TRUE-80100` in the togadesk repo; local togadesk is checked out on `TRUE-80100`.
+
+## What did NOT work — DO NOT RETRY THESE
+<!-- Exact failure reasons — do not vague-ify -->
+- **Do NOT restore the commented-out `locations` UNION in getinfo.php** (getinfo.php:95-148) as a "fix" for the empty End User Address dropdown. The empty dropdown is NOT a regression: git blame shows the per-person-only query dates to the 2021-12-06 schema migration `repair_order_addresses/primaryaddress` → `addresses/isprimary` (commit bf1abaa06, Jeff). Client/site addresses intentionally live in the `locations` table and are reached via the modal's "Select either End User or Client Location" toggle (`#checkbox` → `#servicelocation`/`#location`), enabled once a Contract is chosen. Empty per-person dropdown is expected; inline add-address is the designed fallback.
+- **Do NOT fix only add.php:353 and leave :354.** Line 354 (`access-instructions`) is the identical unguarded `getVar` on the next line and would throw immediately after 353 is fixed — both must use `getVarIfSet`.
+
+## Not tried yet (candidates for next session)
+- Independently verify the autofill fix in an incognito Chrome window (both create tests were done with manual field entry, so fix #2 was never actually exercised against live autofill).
+- Optional pre-merge hygiene: `php -l` on the 3 changed files and a `php-reviewer` pass (never run this session).
+- Sweep the rest of the MSO create block in add.php for OTHER unconditional `getVar()` reads that could throw the same way (departmentid, priority, deliveryc, warrentyStartDate, deviceAge, etc.) — deferred per developer ("just the reported crash"). Only revisit if a NEXT-field crash surfaces.
+- PR review/merge of branch `TRUE-80100` (not started).
+
+## Current file state
+| File | Status | Notes |
+|------|--------|-------|
+| desk/includes/controllers/actions/tickets/add.php | Modified, committed on TRUE-80100 | Lines 353-354 `getVar`→`getVarIfSet` |
+| desk/template/footer.php | Modified, committed on TRUE-80100 | `autocomplete="off"` on `#formModal` (line 9) |
+| desk/template/modals/tickets/addNew.php | Modified, committed on TRUE-80100 | Validator deadlock fix (~3284) + `autocomplete` attrs on new-user/new-address/Summary/select2 fields |
+| desk/template/pages/getinfo.php | Read-only (no change) | Investigated only — confirmed per-person address query is correct/by-design |
+| knowledge/1.0/apps/togadesk/features/managed-service-order-create.md | Created, pushed to _main | New feature doc (MSO create flow + 3 fix gotchas) |
+| knowledge/1.0/standards/backend-php.md | Modified, pushed to _main | Added getVar-throws rule (elevated, approved) |
+
+## Decisions made
+- **Guard the read in add.php rather than fix the form to always post `installation`** (developer choice). Rationale: immediate, minimal, matches the surrounding guarded pattern; `location` becomes null when absent, which is acceptable for onsite-service. Rejected: form-side fix (larger surface) and "both".
+- **Empty End User Address dropdown is by-design, not a code bug.** Rationale: confirmed via git blame (2021 per-person migration) + live test (a user with an address works); client locations are a separate intentional path via the toggle. Rejected: restoring the `locations` UNION.
+- **Promote the getVar-throws rule to the elevated 1.0 backend-php standard** (developer approved). Rationale: `getVar` throwing vs `getVarIfSet` returning null is App_-framework-wide, not togadesk-specific; it's a recurring 1.0 crash class.
+- **No client doc for Northwell.** Rationale: Northwell was only the reporting client; the defects and knowledge are shared/internal to the togadesk MSO flow.
+
+## Blockers
+none — all three fixes verified for the two create paths and pushed; knowledge published.
+
+## Exact next step
+> This task is essentially complete. If anything remains: open branch `TRUE-80100` for PR review/merge, and optionally verify the autofill fix (#2) in an incognito Chrome window since both create tests used manual field entry (autofill was never exercised).
+
+---
+_Saved by /session-save on 2026-07-09_

package/package.json

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