toga-ai 1.0.210 → 1.0.211

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.210",
+  "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",