toga-ai 1.0.209 → 1.0.211

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

@@ -6,7 +6,7 @@
 | [ACL Permission Chain (Record & Field Authorization)](features/acl-permission-chain.md) | Authorization in the 2.0 API is **metadata-driven**: whether a role may Create/Read/Update/Delete a record is decided by rows across **four linked tables**, not | api2/Component/Api/V2/V2.php, _underscore/Model/Core/Page.php, dbchanges2/Client/2026-06-03- BLANK_CLIENT_DATABASE.sql, dbchanges2/Client/2026-06-23b - ItemTranslationsAcl.sql |
 | [Carrier Shipping Labels (UPS/FedEx) & NetSuite Item Fulfillment](features/carrier-shipping-labels.md) | Backend mechanics behind TOGa Supply's Fulfill & Ship: buying a carrier label (UPS/FedEx), persisting it, and creating the NetSuite Item Fulfillment with tracki | _underscore/Model/Client/ItemFulfillment.php, _underscore/Model/Client/ItemFulfillments/TrackingNumber.php, _underscore/Component/Library/LabelPdf/LabelPdf.php, _underscore/Component/Library/Carriers/Ups/Ups.php, _underscore/Component/Library/Carriers/Fedex/Fedex.php, _underscore/Trait/Netsuite/ItemFulfillment.php, _underscore/Trait/Netsuite/SalesOrder.php, _underscore/Component/Library/NetSuite/NetSuite.php, _underscore/Model/Client/TrackingNumber.php, _underscore/Model/Client/ShippingMethod.php, _underscore/Model.php, _underscore/Cloud.php |
 | [Client Email Template Sending](features/email-template-sending.md) | `_Model_Client_EmailTemplate` sends a stored, client-defined email template by UUID. | _underscore/Model/Client/EmailTemplate.php, _underscore/Model/Client/EmailTemplateOutgoingEmailAddress.php, _underscore/Email.php |
-| [Forecast.Sales NetSuite import engine (real-time webhook)](features/forecast-sale-import.md) | Real-time importer that takes a NetSuite **sale** record and writes its lines into `Forecast.Sales` (the Forecast2 revenue table). | _underscore/Component/Forecast/SaleImport/SaleImport.php, _underscore/Component/Forecast/Db/Db.php, worker2/Worker/Netsuite/Invoice.php, worker2/Worker/Netsuite/CashSale.php, worker2/Worker/Netsuite/CreditMemo.php, worker2/Worker/Netsuite/CashRefund.php, worker2/Worker/Netsuite/Opportunity.php, worker2/Worker/Netsuite/SalesOrder.php |
+| [Forecast.Sales NetSuite import engine (real-time webhook)](features/forecast-sale-import.md) | Real-time importer that takes a NetSuite **sale** record and writes its lines into `Forecast.Sales` (the Forecast2 revenue table). | _underscore/Component/Forecast/SaleImport/SaleImport.php, _underscore/Component/Forecast/Db/Db.php, worker2/Worker/Netsuite/Invoice.php, worker2/Worker/Netsuite/CashSale.php, worker2/Worker/Netsuite/CreditMemo.php, worker2/Worker/Netsuite/CashRefund.php, worker2/Worker/Netsuite/Opportunity.php, worker2/Worker/Netsuite/SalesOrder.php, test/@dave/test_invoice_lifecycle.php, test/@dave/NetSuite/api-message-queue/ue_api_msg_queue_enqueue.js, test/@dave/NetSuite/api-message-queue/dev_ue_api_msg_queue_enqueue.js |
 | [_Model magic-field access (__get without __isset)](features/model-magic-field-access.md) | `_Model` exposes DB columns as "magic" properties via `__get()`, but it defines **no** `__isset()`. | _underscore/Model/Core/Model.php |
 | [NetSuite REST Client (_Component_Api_Netsuite) — record writes & SuiteQL](features/netsuite-rest-client.md) | `_Component_Api_Netsuite` is the **2.0 `_underscore` NetSuite REST client** — the shared primitive every worker2/api2 NetSuite caller uses for record GETs, Suit | _underscore/Component/Api/Netsuite/Netsuite.php |
 | [Per-Client Database Connections & the Local Logs Trap](features/per-client-database-connections.md) | When `_underscore` serves a request for a client it opens **three distinct per-client database connections**, not one. | _underscore/Database.php, _underscore/ApiRequest.php, _underscore/Model/Client/Logs/Api.php |

package/knowledge/2.0/apps/_underscore/features/forecast-sale-import.md

@@ -6,7 +6,7 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-06-25
+updated: 2026-06-26
 owners: [dfranks]
 files:
   - _underscore/Component/Forecast/SaleImport/SaleImport.php
@@ -17,9 +17,14 @@ files:
   - worker2/Worker/Netsuite/CashRefund.php
   - worker2/Worker/Netsuite/Opportunity.php
   - worker2/Worker/Netsuite/SalesOrder.php
+  - test/@dave/test_invoice_lifecycle.php
+  - test/@dave/NetSuite/api-message-queue/ue_api_msg_queue_enqueue.js
+  - test/@dave/NetSuite/api-message-queue/dev_ue_api_msg_queue_enqueue.js
 related:
   - ../architecture.md
   - ../../worker2/architecture.md
+  - ../../worker2/features/netsuite-salesorder-open-orders-sync.md
+  - ./netsuite-rest-client.md
 ---
 
 ## Summary
@@ -144,7 +149,51 @@ events as specific **subtypes** (`inventoryItem`, `nonInventoryResaleItem`, `kit
 would be needed only for a future real-time item webhook, **not** for this Sales importer
 (which keeps items fresh via the hourly item pull cron plus the inline self-heal).
 
+## Local testing harness (`test/@dave/test_invoice_lifecycle.php`)
+A CLI that boots worker2/_underscore (chdir to `worker2/` then `require index.php`) and drives a
+**full NetSuite invoice lifecycle** through the live `_underscore` REST client
+(`_Component_Api_Netsuite`) to exercise this importer end-to-end against a local Forecast mirror.
+Actions: `check | create | get | update | delete | sync | recent | amq | deployments | locations`.
+
+- **Fixture:** customer **58** ("8 Test Company") + item **103741** ("Test Other Charge for Sale",
+  maps to local `Forecast.Items` id 25), **rate 0** → a **$0 invoice that still yields one Sales
+  row** (the engine does **not** skip a $0 line — revenue `0.00` is written; same as the cron's
+  Sales section). Confirms create→insert, edit→update (tracked-column change-detection), and
+  delete→`removeAll` all land in local `Forecast.Sales`.
+- It carries its **own** `createInvoiceRecord()` that POSTs via `_ApiRequest` and parses the
+  `Location` header with a **correct** regex (delimiter `~`) — a deliberate workaround for the live
+  `_Component_Api_Netsuite::createRecord()` `#`-delimiter bug (see the
+  [REST client doc](./netsuite-rest-client.md)); the framework was **not** edited this session.
+- `amq` action SuiteQLs the AMQ custom record; `deployments` SuiteQLs `scriptdeployment`+`script`
+  to show which enqueuer fires per record type (used to find the dual-deployment trap below).
+
 ## Gotchas / known issues
+- **Testing locally pollutes PROD unless you UNDEPLOY the prod AMQ enqueuer first.** Each sale
+  transaction type has **TWO** NetSuite UE enqueuer deployments: **"AMQ — Enqueuer"**
+  (`customscript_ue_amq_enqueue`, **RELEASED** → posts to **prod** `webhook.togahub.com`) and
+  **"AMQ development script"** (`customscript2619` → ngrok via `DEV_OVERRIDE`/`debugWrap`). A
+  **RELEASED** deployment fires for **all** actors **including the REST/M2M integration user**, so a
+  REST-driven test invoice hits **prod too**. Observed first run: test-invoice edits flowed to prod
+  and a $0 row was written to **prod** `Forecast.Sales` — by the **legacy 5-min pull cron**, NOT the
+  webhook (prod worker2 has no invoice handler deployed yet, so prod `Netsuite/Invoice/*` jobs
+  watchdog-timeout at 300s, `isSuccess=0`). **To isolate a local test, undeploy the prod enqueuer**
+  for the record types under test (invoice/cashSale/cashRefund/creditMemo/journalEntry); the second
+  full create→update→delete run was then cleanly isolated (zero prod `Logs.Webhook`/`Forecast.Sales`
+  for the test id). The **dev** enqueuer's `debugWrap` envelope
+  `{action,parameters:{payload,headers}}` is required because a local worker2 has no
+  `WebhookIngestion` Lambda to wrap the raw body.
+- **No local app logs for debug-path webhooks — verify arrival via the ngrok inspector, and decode
+  the body.** The legacy `{action,parameters}` debug path writes **no** `WorkerJobs`/`Logs.Webhook`
+  locally. Confirm inbound arrival at the ngrok request inspector
+  `http://127.0.0.1:4040/api/requests/http` — but its **raw body is base64**, so decode the body
+  (after the `\r\n\r\n`) before grepping for `internalId`/`eventType`. The inspector buffer is
+  **ephemeral** (rotates/clears) — watch it live while triggering.
+- **Sales create webhook races NetSuite REST read-after-write lag** — the handler GETs the invoice
+  before its line sublist materializes → **0 lines → 0 rows**. Same gotcha as the SalesOrder
+  open-orders sync (see that doc's read-after-write-lag gotcha); it self-heals on the next edit
+  webhook or the daily discrepancy-fix.
+- **Local _underscore boots on PHP 8.0.30 (xampp8)** — the floor enforced in `_underscore.php` is
+  **8.0.0**, not 8.1.
 - **`_Component_*` classes must live under the `_underscore` framework root, never a project
   repo.** The autoloader rejects a `_Component_*`/`_Model_*` loaded from a project path
   (e.g. `./` under worker2) with "namespace … has not been defined" — at **class-load
@@ -154,6 +203,19 @@ would be needed only for a future real-time item webhook, **not** for this Sales
 - The cron's sign handling is not portable here — see Sign convention.
 
 ## Change history
+- 2026-06-26 — **Verified the full create→update→delete webhook lifecycle end-to-end on a local box**
+  (ngrok tunnel → local worker2 → local `Forecast.Sales`), driving a real **$0** NetSuite invoice
+  through create→insert, edit→update (tracked-column change-detection), delete→`removeAll`; confirmed
+  a $0 line is **not** skipped (one revenue-`0.00` row). Built the reusable harness
+  `test/@dave/test_invoice_lifecycle.php` (boots worker2/_underscore, drives the lifecycle via
+  `_Component_Api_Netsuite`; `amq`/`deployments` SuiteQL actions). Recorded durable testing gotchas:
+  the **dual AMQ enqueuer** RELEASED-fires-for-the-REST-user prod-pollution trap (undeploy the prod
+  enqueuer to isolate; prod's $0 row came from the legacy 5-min pull cron, not a prod webhook —
+  prod has no invoice handler so its `Netsuite/Invoice/*` jobs watchdog-timeout `isSuccess=0`); no
+  local app logs on the debug `{action,parameters}` path (verify via the ngrok inspector at
+  `:4040`, body is base64, buffer ephemeral); the Sales create webhook shares the SalesOrder
+  read-after-write line-sublist race; and local _underscore's PHP floor is 8.0.0. No production code
+  change. (dfranks)
 - 2026-06-25 — **Verified `sync()` end-to-end across all four sale types** (prod NS reads, local Forecast
   writes; 40+ records spanning invoice/cashSale/creditMemo/cashRefund): revenue reconciled **to the penny**
   against an independent SuiteQL `SUM(-foreignamount)` oracle on every record; the uniform sign factor held

package/knowledge/2.0/apps/_underscore/features/netsuite-rest-client.md

@@ -57,10 +57,12 @@ through `_ApiRequest` directly (mirroring `send()`'s auth/endpoint/header setup)
 > reads the class-`#` as a premature closing delimiter and the whole pattern **always throws
 > `preg_match(): Unknown modifier ']'`**. This fires *after* the record is already created, so the
 > create succeeds in NetSuite but `createRecord()` raises and the caller never gets the new id —
-> it breaks the entire outbound create/push path. **Fix direction:** change the delimiter so `#`
+> it breaks the entire outbound create/push path **for any record type** (observed on `journalentry`
+> and again on `invoice` create). **Fix direction:** change the delimiter so `#`
 > isn't both delimiter and class member, e.g. `~/(\d+)(?:[?#]|$)~`. Interim workaround used in
-> probes: recover the new id by regex-parsing the thrown exception message (the `Location` value
-> is in it). Confirmed live 2026-06-25.
+> probes and in `test/@dave/test_invoice_lifecycle.php`: parse the new internalId off the `Location`
+> value carried in the thrown exception message (the lifecycle harness ships its own correct
+> `~`-delimited parse to sidestep this without editing the framework). Confirmed live 2026-06-26.
 
 ### Update — reuse `send('PATCH', $route, $body)`
 

package/knowledge/INDEX.md

@@ -33,7 +33,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 ## standalone framework
 
-- **togatech** (TOGA Technology Website) — 2 doc(s) → [standalone/apps/togatech/INDEX.md](standalone/apps/togatech/INDEX.md)
+- **togatech** (TOGA Technology Website) — 4 doc(s) → [standalone/apps/togatech/INDEX.md](standalone/apps/togatech/INDEX.md)
 - **forward** (Forwarder) — 4 doc(s) → [standalone/apps/forward/INDEX.md](standalone/apps/forward/INDEX.md)
 
 ## Clients

package/knowledge/standalone/apps/togatech/INDEX.md

@@ -3,4 +3,5 @@
 | Doc | Summary | Files |
 |-----|---------|-------|
 | [TOGA Technology Website Architecture](architecture.md) | The public-facing TOGA Technology corporate/marketing website. | togatech/src/main.tsx, togatech/src/App.tsx, togatech/src/routes.tsx, togatech/src/lib/api.ts, togatech/src/lib/contentful.ts, togatech/src/themeConfig/ThemeContext.tsx, togatech/vite.config.ts, togatech/package.json |
-| [SEO / AEO / GEO — Prerendering, Single-Source Meta & Structured Data](features/seo-aeo-geo-prerender.md) | Makes togatech.com visible and citable to search engines **and** AI answer engines (ChatGPT/Perplexity/Claude search, Google AI Overviews). | togatech/vite.config.ts, togatech/scripts/prerender.mjs, togatech/src/routes.config.json, togatech/src/main.tsx, togatech/src/App.tsx, togatech/src/components/SEO/Seo.tsx, togatech/src/components/SEO/JsonLd.tsx, togatech/src/components/SEO/schema.ts, togatech/public/robots.prod.txt, togatech/public/sitemap.xml, togatech/public/llms.txt |
+| [SEO / AEO / GEO — Prerendering, Single-Source Meta & Structured Data](features/seo-aeo-geo-prerender.md) | Makes togatech.com visible and citable to search engines **and** AI answer engines (ChatGPT/Perplexity/Claude search, Google AI Overviews). | togatech/vite.config.ts, togatech/scripts/prerender.mjs, togatech/src/routes.config.json, togatech/src/main.tsx, togatech/src/App.tsx, togatech/src/components/SEO/Seo.tsx, togatech/src/components/SEO/JsonLd.tsx, togatech/src/components/SEO/schema.ts, togatech/src/components/templates/AppLayout.tsx, togatech/src/pages/WhatWeDo/WhatWeDoPage.tsx, togatech/src/pages/WhatWeDo/viewModel/FIELDS/WHATWEDOPAGEFIELDS.json, togatech/src/pages/About/AboutPage.tsx, togatech/src/pages/Contact/ContactPage.tsx, togatech/src/pages/OurPlatform/OurPlatformPage.tsx, togatech/public/robots.prod.txt, togatech/public/sitemap.xml, togatech/public/llms.txt |
+| [Creating Pull Requests on togatech](workflows/creating-pull-requests.md) | How to open a PR against `agilantsolutions/togatech`. | togatech/.git/config |

package/knowledge/standalone/apps/togatech/features/seo-aeo-geo-prerender.md

@@ -6,7 +6,7 @@ project: TOGA Technology Website
 client: shared
 type: feature
 status: active
-updated: 2026-06-19
+updated: 2026-06-26
 owners: ["ajean", "jcardinal"]
 files:
   - togatech/vite.config.ts
@@ -17,6 +17,12 @@ files:
   - togatech/src/components/SEO/Seo.tsx
   - togatech/src/components/SEO/JsonLd.tsx
   - togatech/src/components/SEO/schema.ts
+  - togatech/src/components/templates/AppLayout.tsx
+  - togatech/src/pages/WhatWeDo/WhatWeDoPage.tsx
+  - togatech/src/pages/WhatWeDo/viewModel/FIELDS/WHATWEDOPAGEFIELDS.json
+  - togatech/src/pages/About/AboutPage.tsx
+  - togatech/src/pages/Contact/ContactPage.tsx
+  - togatech/src/pages/OurPlatform/OurPlatformPage.tsx
   - togatech/public/robots.prod.txt
   - togatech/public/sitemap.xml
   - togatech/public/llms.txt
@@ -37,7 +43,15 @@ Makes togatech.com visible and citable to search engines **and** AI answer engin
 1. **robots:** `robotsPlugin` copies `robots.prod.txt` only when `mode === "production"`; beta/gamma/dev get `robots.dev.txt` (`Disallow: /`). `robots.prod.txt` carries an explicit AI-bot allow-list (GPTBot, ClaudeBot, PerplexityBot, …) + `https://` sitemap.
 2. **prerender:** `npm run build` = `tsc && vite build && npx puppeteer browsers install chrome && node scripts/prerender.mjs` (the Chrome-install step was added 2026-06-19 — see gotchas). The script serves `dist/` (reading the original shell once, serving it for all nav routes), snapshots each route in headless Chrome, and writes `dist/<route>/index.html`. Runs in a real browser, so **no SSR/window guards needed**.
 3. **meta:** each page renders `<Seo {...FIELDS.meta} />` — title/description/keywords/canonical/OG/Twitter from one place per page; canonical/OG URLs derived from one `SITE_URL`. `<JsonLd>` (Helmet `<script type="application/ld+json">`) is baked into the snapshot.
-4. **structured data:** Organization + WebSite site-wide (AppLayout), per-page BreadcrumbList (Seo), platform SoftwareApplication (OurPlatform), LocalBusiness×5 (from Contact locations), Person (from About team) — all **derived from existing FIELDS** (single source).
+4. **structured data:** all JSON-LD now lives in **one module — `src/components/SEO/schema.ts`** (the single source of truth), derived from `FOOTERFIELDS.json` (socials/email/phone) and each page's FIELDS JSON, so editing footer/content updates schema automatically. Exports and their render sites (emitted via `<JsonLd>`/Helmet):
+   - `organizationSchema` + `websiteSchema` → **AppLayout** (all pages).
+   - `serviceSchemas` (4 `Service` nodes) → **WhatWeDoPage**.
+   - `platformSchema` (`SoftwareApplication` for the TOGa Platform) → **OurPlatformPage**.
+   - `aboutPageSchema` (`AboutPage`) + `personSchemas` (per leader) → **AboutPage**.
+   - `contactPageSchema` (`ContactPage`) + `localBusinessSchemas` (per office, from `CONTACTPAGEFIELDS.map.locations`) → **ContactPage**.
+   - **Entity graph linked by `@id`:** Organization is `${SITE_URL}/#organization`, WebSite `/#website`, logo `/#logo`. Service/Person/LocalBusiness reference the org via `provider`/`worksFor`/`parentOrganization` `@id`; AboutPage/ContactPage set `isPartOf` the website and `about` the org. Use `@id` cross-references — do not inline duplicate org nodes.
+   - `organizationSchema.logo` is an `ImageObject` (`@id` `/#logo`, `url`, `contentUrl`, `caption "TOGA Technology"`); width/height are intentionally omitted because the logo is an SVG.
+   - `personSchemas` de-dupes a leader who appears in both `boardMembers` and `members` in `ABOUTPAGEFIELDS`, keyed on lowercased trimmed name (a `Set`) — naive emission produced duplicate `Person` nodes.
 
 ## Data model
 None (static marketing site). All copy/meta/NAP/leaders come from `*FIELDS*.json`; structured data is derived from `FOOTERFIELDS.json`, `CONTACTPAGEFIELDS.json` (`map.locations`), and `ABOUTPAGEFIELDS.json` (`teamMembers`).
@@ -57,10 +71,15 @@ None — uniform.
 - **og:image dedupe:** static OG/Twitter tags were removed from `index.html` because `<Seo>` emits per-page ones (Helmet appends rather than replacing pre-existing static tags → duplicates otherwise).
 - **Verified data corrections:** real positioning is *integrated IT services + the ERA TOGa Platform*; real socials are LinkedIn `/toga-tech` + YouTube + Instagram (no Twitter/GitHub/Crunchbase); contact is `website@togatech.com` / `+1 (212) 736-0111`; **5** offices. Prior planning docs had several wrong specifics — verify schema/llms.txt against FIELDS before shipping.
 - **Build size:** JS bundle is ~14.8 MB (4.9 MB gzip) — a real CWV/LCP risk; code-splitting is a separate follow-up.
+- **FIELDS JSON is component-coupled — no free-prose body slot:** each page's `*FIELDS*.json` is shaped to specific components (hero, cardScroll, businessProblems, kpi, carousel), so there is **no place to drop a long prose block**. An audit's "rewrite to 900 words" is not structurally possible without building new components — you can only sharpen titles/descriptions/keywords/card copy that already have slots. (`/our-platform` was left unchanged: it is already content-dense — 7 app modules + 4 stacks + testimonials + KPIs — and the original audit under-counted because that content is JS-rendered.)
+- **`personSchemas` duplicate guard:** a leader can be in both `boardMembers` and `members` in `ABOUTPAGEFIELDS` — `personSchemas` must de-dup by lowercased trimmed name, or it emits duplicate `Person` nodes.
+- **🔴 Brand name is "TOGA Technology" only — never "Agilant":** an earlier draft adding `alternateName: "Agilant"` / "(formerly Agilant)" to the org schema was explicitly reverted. Do not reintroduce "Agilant" in schema, copy, or meta. (Captured as a team brand standard — see Related docs.)
 
 ## Change history
+- 2026-06-26 — SEO improvement effort (PRs #33–#36 → `_production`; SEO health ~61→78 est.). Centralized all JSON-LD into `src/components/SEO/schema.ts` (org/website/platform/service×4/about/contact/localBusiness/person, `@id`-linked graph), de-duped Person nodes, logo→`ImageObject`, sharpened `/what-we-do` meta+copy, added `<lastmod>` to all 7 sitemap URLs. Recorded brand constraint ("TOGA Technology" only, never "Agilant") and the component-coupled-FIELDS limit. (ajean)
 - 2026-06-19 — Merged SEO/AEO into `_production` (resolved ContactPage conflict: reCAPTCHA + Seo/JsonLd, dropped Helmet). Fixed Amplify build: committed `package-lock.json` (npm ci EUSAGE) and added `npx puppeteer browsers install chrome` to the build before prerender. (jcardinal)
 - 2026-06-18 — Initial SEO/AEO/GEO implementation: robots mode-gate + AI allow-list + sitemap/llms; Puppeteer prerender (fail-fast); shared `<Seo>` single-source meta + canonical; JSON-LD (Organization/WebSite/Breadcrumb/SoftwareApplication/LocalBusiness×5/Person×12). PRs #29 + #30, pending merge. (ajean)
 
 ## Related docs
 - standalone/apps/togatech/architecture.md (update its Build/deploy section once PR #30 merges — robotsPlugin gating + prerender step).
+- standalone/apps/togatech/workflows/creating-pull-requests.md — how PRs get opened on this repo (gh CLI is unauthenticated; uses curl + osxkeychain token; base `_production`).

package/knowledge/standalone/apps/togatech/workflows/creating-pull-requests.md

@@ -0,0 +1,47 @@
+---
+title: Creating Pull Requests on togatech
+framework: "standalone"
+repo: togatech
+project: TOGA Technology Website
+client: shared
+type: workflow
+status: active
+updated: 2026-06-26
+owners: ["ajean"]
+files:
+  - togatech/.git/config
+related:
+  - standalone/apps/togatech/features/seo-aeo-geo-prerender.md
+---
+
+## Summary
+How to open a PR against `agilantsolutions/togatech`. The local `gh` CLI is **not usable**
+for this repo (it lacks the `read:org` scope), so PRs are created with a raw GitHub REST
+call authenticated by the token already sitting in the macOS keychain. **Base branch is
+`_production`, not `_main`** (`_main` is stale) — feature branches are cut from `_production`.
+
+## How it works
+1. Branch off `_production` (e.g. `feature/seo-schema`), commit, and push the branch.
+2. Pull the GitHub token from the osxkeychain credential helper rather than relying on `gh`:
+   ```
+   TOKEN=$(printf 'protocol=https\nhost=github.com\n\n' | git credential fill | sed -n 's/^password=//p')
+   ```
+3. POST to the PR API with that token:
+   ```
+   curl -s -X POST \
+     -H "Authorization: token $TOKEN" \
+     -H "Accept: application/vnd.github+json" \
+     https://api.github.com/repos/agilantsolutions/togatech/pulls \
+     -d '{"title":"...","head":"<branch>","base":"_production","body":"..."}'
+   ```
+4. The response JSON contains `html_url` for the new PR. Merge follows the normal review flow.
+
+## Gotchas / known issues
+- **`gh pr create` fails** here — the authenticated `gh` session lacks `read:org`. Do not
+  burn time re-authing `gh`; use the curl path above.
+- **Base is `_production`.** Targeting `_main` opens a PR against a stale branch. (This matches
+  the `worker2` mainline convention — mainline is `_production`, not `_main`.)
+- **Never echo `$TOKEN`** into logs, commit messages, or PR bodies — it is a live credential.
+
+## Change history
+- 2026-06-26 — Documented the curl-based PR flow (gh unauthenticated; base `_production`), captured during the SEO improvement effort (PRs #33–#36). (ajean)

package/knowledge/standalone/standards/brand-naming.md

@@ -0,0 +1,35 @@
+---
+title: Brand Naming — "TOGA Technology" only
+framework: "standalone"
+repo: togatech
+project: TOGA Technology Website
+client: shared
+type: standard
+status: active
+updated: 2026-06-26
+owners: ["ajean"]
+files:
+  - togatech/src/components/SEO/schema.ts
+related:
+  - standalone/apps/togatech/features/seo-aeo-geo-prerender.md
+---
+
+# Brand Naming — "TOGA Technology" only
+
+The company is referenced **only** as "TOGA Technology" in all code, schema, meta, and
+copy. **Never** use "Agilant" — not as a brand name, not as `alternateName`, and not in
+any "(formerly Agilant)" framing.
+
+## Why
+During the 2026-06 SEO effort an earlier draft added `alternateName: "Agilant"` and a
+"(formerly Agilant)" note to the Organization JSON-LD and org description. This was
+**explicitly reverted by the owner**. Surfacing the legacy name in structured data and
+copy is off-brand and creates the wrong entity association for search/AI answer engines.
+
+## Applies to
+- Schema.org JSON-LD (`src/components/SEO/schema.ts`) — no `alternateName: "Agilant"`.
+- Page meta (titles, descriptions), on-page copy, `llms.txt`, and any FIELDS JSON.
+- Any future SEO/content/AEO work on togatech.
+
+## Change history
+- 2026-06-26 — Standard recorded after reverting an "Agilant" alternateName/"formerly" draft in the org schema. (ajean)

package/package.json

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