toga-ai 1.0.302 → 1.0.304

package/knowledge/1.0/apps/togadesk/INDEX.md

@@ -5,6 +5,7 @@
 | [TOGa Desk Architecture](architecture.md) | TOGa Desk is the staff-facing support desk **and field-service platform** (analysts work at `/desk/`). | desk/index.php, desk/includes/loader.php, desk/config.php, desk/includes/controllers/actions.php, desk/includes/controllers/data.php, desk/includes/controllers/modals.php, desk/includes/classes/class.app.php, desk/includes/classes/class.ticket.php, desk/api/index.php, desk/api/resources/tickets.php, crons/tickets.php |
 | [Email-to-Ticket Intake (crons/tickets.php)](features/email-to-ticket-intake.md) | TOGa Desk ingests support email into tickets through a cron-driven IMAP poller (`crons/tickets.php`) plus a postfix pipe variant (`crons/pipe.php`). | crons/tickets.php, crons/tickets_prod.php, crons/pipe.php, desk/includes/classes/class.ticket.php |
 | [Field-Service Dispatch (central / repair orders)](features/field-service-dispatch.md) | The **central** subsystem is TOGa Desk's field-service dispatch domain: repair-order lifecycle, technician scheduling, onsite vs depot service, parts, and shipm | desk/includes/controllers/actions/central/, desk/includes/classes/class.repair.php, desk/includes/classes/class.repairhistory.php, desk/_/browser/datatable/central.php, desk/template/pages/central.php, desk/template/pages/central/view.php, desk/template/modals/central/addTracking.php, library/app/model/togadesk/repairorder.php, library/app/model/togadesk/repairordertracking.php, library/app/api/carrier/ups.php |
+| [Managed Service Order Create Flow (New MSO modal → tickets/add)](features/managed-service-order-create.md) | The **Managed Service Order (MSO) create flow** is how a TOGa Desk user manually creates a managed service order: pick an End User (or a Client Location), choos | desk/includes/controllers/actions/tickets/add.php, desk/template/modals/tickets/addNew.php, desk/template/pages/managed.php, desk/template/pages/getinfo.php, desk/template/footer.php, library/app/model/togadesk/repairorder.php |
 | [Ticket Email Notifications (notifications table)](features/notifications.md) | Which TOGa Desk emails fire for a given client is driven **entirely by data**, not code: the `TOGaDeskSupport.notifications` table holds one row per `(clientid, | desk/includes/classes/class.notification.php, crons/tickets.php, crons/tickets_prod.php |
 | [REST API (RPC-over-POST) & API-Key Auth](features/rest-api.md) | TOGa Desk exposes a programmatic API at `desk/api/`. | desk/api/index.php, desk/api/resources/tickets.php, desk/api/resources/assets.php, desk/api/resources/authenticate.php, desk/includes/classes/class.apikey.php, desk/includes/functions.php |
 | [SMB Contract Editing & the clientMspId Corruption Trap](features/smb-contract-editing.md) | The SMB contracts page (`/desk/?route=toga/smbcontracts&togaClientId=<id>`) edits `TOGA_*.SMBContracts` rows via a modal. | desk/template/modals/toga/smbcontracts/smbContract.php, desk/includes/controllers/modals/toga/smbcontracts/smbContract.php, desk/includes/controllers/actions/toga/smbcontracts/smbContract.php, desk/includes/controllers/actions/toga/smbcontracts/edit.php |

package/knowledge/1.0/apps/togadesk/features/managed-service-order-create.md

@@ -0,0 +1,109 @@
+---
+title: Managed Service Order Create Flow (New MSO modal → tickets/add)
+framework: "1.0"
+repo: togadesk
+project: TOGa Desk
+client: shared
+type: feature
+status: active
+updated: 2026-07-09
+owners: ["mhammontree"]
+files:
+  - desk/includes/controllers/actions/tickets/add.php
+  - desk/template/modals/tickets/addNew.php
+  - desk/template/pages/managed.php
+  - desk/template/pages/getinfo.php
+  - desk/template/footer.php
+  - library/app/model/togadesk/repairorder.php
+related:
+  - 1.0/apps/togadesk/architecture.md
+  - 1.0/apps/togadesk/features/field-service-dispatch.md
+  - 1.0/apps/togadesk/features/ticket-lifecycle.md
+---
+
+## Summary
+The **Managed Service Order (MSO) create flow** is how a TOGa Desk user manually creates a
+managed service order: pick an End User (or a Client Location), choose a Contract, add one or
+more assets, and submit. The server builds a `ManagedServiceOrder`, creates its assets, then
+one `App_Model_TogaDesk_RepairOrder` per asset. This is the **entry/creation** side; the
+downstream repair-order lifecycle (dispatch, scheduling, status) lives in
+[Field-Service Dispatch](./field-service-dispatch.md).
+
+## Key files / entry points
+- **Entry link:** `desk/template/pages/managed.php` — the "NEW MANAGED SERVICE ORDER" link opens
+  modal `tickets/addNew`.
+- **Modal:** `desk/template/modals/tickets/addNew.php` — the New MSO form. It has **no own
+  `<form>` tag**; it relies on the global `#formModal` wrapper (rendered in
+  `desk/template/footer.php`) and `$("form").submit()`. Contains the Summary field, an optional
+  inline **new End User** sub-form (name/email/phone + a `#new-user-password` field), an inline
+  **new address** sub-form, and select2 dropdowns `#enduser`, `#userlocation`, `#location`.
+- **Server action:** `desk/includes/controllers/actions/tickets/add.php` — builds the
+  `ManagedServiceOrder`, creates assets, then a `RepairOrder` per asset. `ticketType`
+  `INSTALLATION` maps the repair order to `App_Model_TogaDesk_RepairOrder::TYPE_ONSITESERVICE`.
+- **Address AJAX:** `desk/template/pages/getinfo.php` — populates the End User Address dropdown.
+
+## How it works
+1. `managed.php` opens the `tickets/addNew` modal into the global `#formModal`.
+2. The user selects an existing End User (`#enduser` → `userid`) or creates a new one inline;
+   selects an End User Address (`#userlocation`) or a Client Location (`#location`); picks a
+   Contract; and adds assets.
+3. Submit runs the modal's client-side validator, then POSTs `?action=…` to `add.php`.
+4. `add.php` builds the `ManagedServiceOrder`, creates each asset, and for each asset builds a
+   `RepairOrder`. In the `TYPE_ONSITESERVICE` branch it reads optional per-asset fields
+   (`installation`, `access-instructions`) — see the getVar gotcha below.
+
+### Address sourcing — per-person vs. client location (important)
+There are **two** address sources, and they come from different tables:
+- **End User Address dropdown (`#userlocation`)** is per **person**. `getinfo.php` (uid branch,
+  ~L152–171) runs `SELECT … FROM people_addresses INNER JOIN addresses ON addresses.id =
+  people_addresses.addressid WHERE people_addresses.peopleid = <uid>`. Addresses are stored
+  **per person** in the `addresses` table + `people_addresses` junction (`peopleid` → `addressid`)
+  in the togadesk DB (`TOGaDeskSupport` / `db_togadesk`).
+- **An empty End User Address dropdown is a legitimate data state**, not a bug — it just means
+  that person has no `people_addresses` row. The **designed fallback** is the modal's inline
+  "add new address" form (`addNewAddress()` sets the `#newAddressCount` hidden field), which
+  `add.php` (~L119–148) fully supports creating.
+- **Client Location (`#location`)** is the alternative: client/site addresses live in the
+  `locations` table keyed by `clientid`, reachable via the modal's "Select either End User or
+  Client Location" toggle (`#checkbox` → `#servicelocation`/`#location`), enabled once a Contract
+  is chosen.
+
+History: the per-person-only End User query dates to a **2021-12-06** schema migration
+(`repair_order_addresses`/`primaryaddress` → `addresses`/`isprimary`, commit `bf1abaa06`, Jeff).
+The older query — still commented in `getinfo.php` ~L95–148 — UNIONed client `locations` into the
+End User dropdown. Dropping that UNION is **long-standing, not a recent regression**.
+
+## Gotchas / known issues
+- **`App_Page::getVar($var)` THROWS when the request var is absent** — it is **not** a
+  null-returning getter. In the `TYPE_ONSITESERVICE` branch, `add.php` (~L353–354) read the
+  optional `installation` and `access-instructions` fields; the manual MSO form doesn't post
+  `installation`, so the whole create aborted with a Sentry exception. **Fix:** use
+  `App_Page::getVarIfSet($var)` (returns `null`) — or guard with `App_Page::varIsSet()` — for any
+  **optional** request field. This is a framework-wide 1.0 `App_` gotcha, not togadesk-specific
+  (`library/app/page.php` — `getVar` L354 throws, `getVarIfSet` L382 returns null,
+  `varIsSet` L404).
+- **Chrome autofill silently breaks the modal.** The modal nests a new-user sub-form (including a
+  password field) inside `#formModal`, which had no `autocomplete` attribute. Chrome's
+  password/profile autofill then filled Summary + address fields **without firing jQuery
+  change/input events and without syncing the select2 widgets**, so validation saw empty values
+  (e.g. "Please select an address" on a field that looked filled). Manual typing worked because it
+  fires the events. **Fix:** `autocomplete="off"` on `#formModal` (and the new-user/new-address/
+  Summary/select2 fields) plus `autocomplete="new-password"` on the password field (Chrome ignores
+  form-level `off` for password fields).
+- **No-saved-address submit deadlock.** When an existing End User (`userid != 0`) had no saved
+  address, the validator required `#userlocation != 0` ("Please select an address."), but the
+  dropdown was empty and the modal auto-opened the inline add-address form — an unresolvable
+  deadlock. **Fix:** the validator now also reads `newAddressCount = parseInt($('#newAddressCount')
+  .val())||0` and only blocks when `selectedValue == 0 AND newAddressCount == 0`, since the server
+  already supports the inline address.
+- The addNew modal has **no `<form>` tag of its own** — it depends entirely on the global
+  `#formModal` in `footer.php` and `$("form").submit()`. Anything that alters that global wrapper
+  (attributes, nesting) affects this flow.
+
+## Change history
+- 2026-07-09 — TRUE-80100: documented the MSO create flow (entry, server action, per-person vs.
+  client-location address sourcing) and folded in three fixes: `getVar` → `getVarIfSet` for
+  optional request vars in the `TYPE_ONSITESERVICE` branch (server crash); `autocomplete` on
+  `#formModal` + password field to stop Chrome autofill bypassing select2/events; and the
+  validator now honors `#newAddressCount` so a no-address End User can submit an inline address.
+  (mhammontree)

package/knowledge/1.0/standards/backend-php.md

@@ -5,8 +5,8 @@ project: Library
 client: shared
 type: standard
 status: active
-updated: 2026-07-06
-owners: [jcardinal, rgirish]
+updated: 2026-07-09
+owners: [jcardinal, rgirish, mhammontree]
 files: []
 related:
   - ../apps/library/architecture.md
@@ -429,6 +429,26 @@ gracefully instead of dropping unrelated work or crashing the loop.
 
 * Validate and sanitize all user input (see SQL Injection Prevention and HTML escaping above).
 
+### Request variable access — `getVar` throws, `getVarIfSet` returns null
+
+`App_Page::getVar($var)` is **not** a null-returning getter — it **throws**
+`Exception("Variable '$var' does not exist in the request headers.")` when the request var is
+absent (`library/app/page.php` L354). Use it only for fields you *know* are always posted.
+
+For any **optional** request field, use `App_Page::getVarIfSet($var)` (returns `null` when
+missing, L382) or guard first with `App_Page::varIsSet($var)` (L404). Reading an optional field
+with `getVar()` aborts the whole request with an uncaught exception — this is a recurring 1.0
+crash class (e.g. TRUE-80100: an unconditional `getVar('installation')` in a create action
+crashed every submit that omitted the field).
+
+```php
+// WRONG — throws when 'installation' isn't posted
+$order->location = App_Page::getVar('installation');
+
+// CORRECT — optional field
+$order->location = App_Page::getVarIfSet('installation');
+```
+
 ### Secure Communication
 
 * Always use HTTPS to encrypt data in transit.

package/knowledge/INDEX.md

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

package/knowledge/clients/nycdoe/INDEX.md

@@ -3,5 +3,5 @@
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
 | [NYCDOE Ticket Hold-Status Sync (ServiceNow ⇄ TOGaDesk)](features/hold-status-sync.md) | 1.0 | DOE ticket **hold** status must round-trip between ServiceNow (SNOW) and TOGaDesk and **stay held** — holds are SLA-bearing in both systems. | worker/crons/sync/nycdoe/send_ticket_updates.php, worker/crons/sync/nycdoe/process_tickets.php, worker/crons/sync/nycdoe/send_request_item_updates.php, library/app/model/togadesk/repairorder.php, library/app/api/nycdoev2.php, togadesk/desk/includes/classes/class.repair.php |
-| [NYCDOE ServiceNow / ASN Integration](features/servicenow-integration.md) | 1.0 | The NYCDOE/ServiceNow integration mirrors DOE's ServiceNow tickets (Incidents + RITMs) into local tables, turns vendor shipment notices into NetSuite Sales Orde | worker/crons/sync/nycdoe/import_asn.php, worker/crons/sync/nycdoe/import_inc.php, worker/crons/sync/nycdoe/legacy_import_asn.php, worker/crons/sync/nycdoe/legacy_process_asn_queue.php, worker/crons/sync/nycdoe/process_tickets.php, worker/crons/sync/nycdoe/1_send_asn_to_netsuite.php, worker/crons/sync/nycdoe/2_send_serials_to_netsuite.php, worker/crons/sync/nycdoe/3_create_installation_ticket.php, worker/crons/sync/nycdoe/send_ticket_updates.php, worker/crons/sync/nycdoe/send_request_item_updates.php, worker/crons/sync/nycdoe/send_nycdoe_proof_of_delivery.php, worker/crons/sync/nycdoe/sync_nycdoe_locations.php, worker/crons/sync/nycdoe/receive_edi_purchase_orders.php, worker/crons/sync/nycdoe/send_edi_open_invoices.php, worker/crons/notifications/nycdoe/, worker/schedules/cron.worker.sync.json, worker/schedules/cron.worker.notification.json, library/app/api/nycdoe.php, library/app/api/nycdoev2.php, library/app/asnprocessor/manufacturer.php, library/app/asnprocessor/apple.php, library/app/asnprocessor/lenovo.php, library/app/asnprocessor/lexmark.php, library/app/asnprocessor/acer.php, library/app/edi.php |
+| [NYCDOE ServiceNow / ASN Integration](features/servicenow-integration.md) | 1.0 | The NYCDOE/ServiceNow integration mirrors DOE's ServiceNow tickets (Incidents + RITMs) into local tables, turns vendor shipment notices into NetSuite Sales Orde | worker/crons/sync/nycdoe/import_asn.php, worker/crons/sync/nycdoe/import_inc.php, worker/crons/sync/nycdoe/legacy_import_asn.php, worker/crons/sync/nycdoe/legacy_process_asn_queue.php, worker/crons/sync/nycdoe/process_tickets.php, worker/crons/sync/nycdoe/1_send_asn_to_netsuite.php, worker/crons/sync/nycdoe/2_send_serials_to_netsuite.php, worker/crons/sync/nycdoe/3_create_installation_ticket.php, worker/crons/sync/nycdoe/test_multi_po_receipt_resolution.php, worker/crons/sync/nycdoe/send_ticket_updates.php, worker/crons/sync/nycdoe/send_request_item_updates.php, worker/crons/sync/nycdoe/send_nycdoe_proof_of_delivery.php, worker/crons/sync/nycdoe/sync_nycdoe_locations.php, worker/crons/sync/nycdoe/receive_edi_purchase_orders.php, worker/crons/sync/nycdoe/send_edi_open_invoices.php, worker/crons/notifications/nycdoe/, worker/schedules/cron.worker.sync.json, worker/schedules/cron.worker.notification.json, library/app/api/nycdoe.php, library/app/api/nycdoev2.php, library/app/asnprocessor/manufacturer.php, library/app/asnprocessor/apple.php, library/app/asnprocessor/lenovo.php, library/app/asnprocessor/lexmark.php, library/app/asnprocessor/acer.php, library/app/edi.php, library/app/netsuite.php |
 | [New York City Department of Education](profile.md) | 1.0 | NYC DOE (New York City Department of Education) is a TOGA client whose entire integration runs in the **1.0 worker tier** (~30 cron scripts under `worker/crons/ |  |

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.302",
+  "version": "1.0.304",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",