toga-ai 1.0.138 → 1.0.140

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

@@ -9,4 +9,4 @@
 | [Monitoring Framework (Orchestrator + Child Monitors)](features/monitoring-framework.md) | A unified, DB-driven monitoring framework for business-critical data flows (Compass POs, Prudential asset imports, AIG closed claims, …). | worker2/Worker/Monitor.php, worker2/Worker/Monitors/, worker2/Worker/Notification/Email.php, dbchanges2/Core/2026-05-21 - Monitors.sql |
 | [NetSuite → TOGA Opportunity Sync (API Message Queue + worker2 webhook)](features/netsuite-opportunity-sync.md) | Outbound sync from NetSuite to TOGA for the record types the Forecast2 importer pulls (opportunities first; sales/items/etc. | worker2/Worker/Netsuite.php, worker2/Worker/Netsuite/Opportunity.php, worker2/Controller/Index.php, _underscore/Worker.php, test/@dave/NetSuite/api-message-queue/lib_amq_queue.js, test/@dave/NetSuite/api-message-queue/ue_api_msg_queue_enqueue.js, test/@dave/NetSuite/api-message-queue/ue_amq_drain.js, test/@dave/NetSuite/api-message-queue/ss_amq_drain.js, test/@dave/NetSuite/api-message-queue/DEPLOY_RUNBOOK.md, test/@dave/clickup/backfill_opportunity_numbers.php, test/@dave/clickup/probe_opportunity_fields.php, test/@dave/probe_clickup_desc_match.php, worker/crons/toga2/forecast2/common_import_sales_from_netsuite.php |
 | [NetSuite → Forecast Open-Orders Sync (salesOrder webhook → OpenOrderItems)](features/netsuite-salesorder-open-orders-sync.md) | Webhook-driven, single-record port of the legacy open-orders importer (TRUE-79142). | worker2/Worker/Netsuite/SalesOrder.php, worker2/Worker/Netsuite.php, test/@dave/probe_salesorder_rest_shape.php, test/@dave/probe_open_order_lines.php, test/@dave/check_so_status.php, test/@dave/check_so_history.php, test/@dave/probe_so_rest_lines.php, worker/crons/toga2/forecast2/import_open_orders.php, worker/crons/toga2/forecast2/common_import_sales_from_netsuite.php |
-| [Teams Meeting Transcript Export](features/teams-transcript-export.md) | `_Worker_Team_Transcripts` (action `Team/Transcripts/Export`) polls Microsoft Graph for Teams meeting transcripts produced by a set of organizers, classifies ea | worker2/Worker/Team/Transcripts.php, worker2/Config/production.ini |
+| [Teams Meeting Transcript Export](features/teams-transcript-export.md) | `_Worker_Team_Transcripts` (action `Team/Transcripts/Export`) polls Microsoft Graph for Teams meeting transcripts produced by a set of organizers, classifies ea | worker2/Worker/Team/Transcripts.php, worker2/Config/production.ini, worker2/Database/TeamsTranscriptExports.sql, dbchanges2/Core/2026-06-18a - Teams Transcript Export schedule.sql |

package/knowledge/2.0/apps/worker2/features/teams-transcript-export.md

@@ -6,11 +6,13 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-06-12
+updated: 2026-06-18
 owners: ["ajean"]
 files:
   - worker2/Worker/Team/Transcripts.php
   - worker2/Config/production.ini
+  - worker2/Database/TeamsTranscriptExports.sql
+  - dbchanges2/Core/2026-06-18a - Teams Transcript Export schedule.sql
 related:
   - ../architecture.md
   - ./creating-worker-actions.md
@@ -20,8 +22,9 @@ related:
 
 `_Worker_Team_Transcripts` (action `Team/Transcripts/Export`) polls Microsoft Graph for
 Teams meeting transcripts produced by a set of organizers, classifies each meeting by
-client (from the meeting title), and archives the raw WebVTT to S3. Scheduled via three
-`Core.CronJobs` rows (weekdays 10:00 / 13:00 / 17:30 Central).
+client (from the meeting title), and archives the raw WebVTT to S3. Scheduled via a single
+`Core.CronJobs` row firing weekdays at 9:30 / 11:30 / 13:30 / 14:30 / 15:30 / 16:30 / 17:30
+Central (`30 9,11,13,14,15,16,17 * * 1-5`).
 
 ## Key files / entry points
 
@@ -29,6 +32,9 @@ client (from the meeting title), and archives the raw WebVTT to S3. Scheduled vi
 - `Config/production.ini` `[teams]` section — Entra app creds, organizer source, S3 target.
 - `[teamsClientAliases]` config section — alias → canonical client name for classification.
 - Ledger table `Team.TranscriptExports` (DB alias `_underscore::DB_TEAM`, core cluster).
+- `Backfill(bool $dryRun = true, int $limit = 0)` — re-files already-misdated S3 objects (see *Gotchas*).
+- DDL + cron seed: `worker2/Database/TeamsTranscriptExports.sql`; prod schedule change:
+  `dbchanges2/Core/2026-06-18a - Teams Transcript Export schedule.sql`.
 
 ## How it works
 
@@ -51,9 +57,17 @@ Per run, after acquiring a Graph client-credentials token:
 3. `getAllTranscripts(meetingOrganizerUserId='{guid}', startDateTime, endDateTime)`
    over an incremental window (`MAX(dtCreated)` watermark from the ledger, else `now − lookbackDays`),
    following `@odata.nextLink`.
-4. Per new transcript (dedup by `transcriptIdentifier`): fetch meeting `subject`+`startDateTime`
-   (cached per meeting), classify, download VTT (`?$format=text/vtt`), `putObject` to S3, insert
-   ledger row.
+4. Per new transcript (dedup by `transcriptIdentifier`): fetch meeting `subject` (cached per
+   meeting) for classification, classify, download VTT (`?$format=text/vtt`), `putObject` to S3,
+   insert ledger row.
+
+**Archive date source (important):** the S3 path date and `dtMeeting` come from the
+transcript's own **`createdDateTime`**, NOT the meeting's `startDateTime`. For a recurring
+meeting, `getMeeting()` (`onlineMeetings/{id}`) returns the **series-anchor** start (the first
+occurrence), so `startDateTime` misfiles every occurrence under one frozen — sometimes future —
+date. `createdDateTime` is stamped minutes after the actual occurrence, so it dates the archive
+correctly. `getMeeting()` is therefore used only for the subject. `dtExported` uses
+`UTC_TIMESTAMP()` (not `NOW()`) so all three timestamps are UTC.
 
 **Classification:** case-insensitive substring match of the meeting title against active
 `Core.Clients` names + `[teamsClientAliases]`, longest needle wins, min length 3. No match → `general`.
@@ -88,6 +102,20 @@ process is identical for all.
 
 ## Gotchas / known issues
 
+- **Recurring meetings return the SERIES-ANCHOR `startDateTime`.** Graph's
+  `onlineMeetings/{id}` gives the first-occurrence (or even a future) start for a recurring
+  series, not the occurrence that was recorded. Driving the archive date off it misfiled every
+  occurrence under one frozen date and produced future-dated folders (e.g. a 6-17 occurrence
+  filed under `…/2026-06-03/…`; a "Rebranding Weekly Sync" under `2026-06-19/`). Fixed by
+  dating off the transcript's `createdDateTime`. The transcript object does **not** carry the
+  occurrence start, so `createdDateTime` (≈ minutes after the meeting) is the best reliable
+  signal. The `Backfill()` action re-files objects already written under the wrong date:
+  recomputes the correct key purely from ledger columns (no Graph calls), `copyObject` →
+  `deleteObject` (idempotent — `NoSuchKey` + `doesObjectExist` treats an already-moved row as a
+  no-op), then updates `s3Key` + `dtMeeting`. Run `dryRun:true` first, inspect `sample[]`, then
+  `dryRun:false` (optional `limit` for a first batch). `$limit` caps candidates touched, not
+  rows scanned, so a run of failures stops at `$limit` instead of sweeping the table.
+
 - **`getAllTranscripts` requires an AAD object-id (GUID), NOT a UPN.** Passing a UPN
   (e.g. `ajean@togatech.com`) returns the opaque `HTTP 400 BadRequest / "UnknownError"`.
   This is the single most likely cause of an export failure.
@@ -124,6 +152,10 @@ Policy gap; a `400` only on a UPN means the id was never resolved to a GUID. (A
 
 ## Change history
 
+- 2026-06-18 — Fixed recurring-meeting date misfiling: archive date + `dtMeeting` now come from
+  the transcript `createdDateTime`, not the series-anchor `meeting->startDateTime` (worker2 PR
+  #82). Added `Backfill()` to re-file existing misdated S3 objects; `dtExported` → `UTC_TIMESTAMP()`.
+  Rescheduled to weekdays 9:30–17:30 CT, one consolidated cron row (dbchanges2 PR #398). (ajean)
 - 2026-06-12 — **Merged (PR #78) and verified in production**: a real `Team/Transcripts/Export`
   run returned 6/6 organizers, 33 found, 33 exported, 0 errors (classified 30 general / 3 Elite).
   Added fail-fast on unresolvable organizers (`resolveUserId` → null, loop throws clear error

package/knowledge/INDEX.md

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

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

@@ -3,3 +3,4 @@
 | 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 |

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

@@ -0,0 +1,62 @@
+---
+title: SEO / AEO / GEO — Prerendering, Single-Source Meta & Structured Data
+framework: "standalone"
+repo: togatech
+project: TOGA Technology Website
+client: shared
+type: feature
+status: active
+updated: 2026-06-18
+owners: ["ajean"]
+files:
+  - 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
+related: []
+---
+
+## Summary
+Makes togatech.com visible and citable to search engines **and** AI answer engines (ChatGPT/Perplexity/Claude search, Google AI Overviews). The site is a CSR-only Vite/React SPA, so non-JS crawlers saw an empty `<div id="root">`. This feature fixes a production de-indexing bug and adds **build-time prerendering** so every static route ships real HTML, plus single-source per-page meta and JSON-LD structured data. Shipped on branches `fix-seo-deindex-emergency` (PR #29) and `feature-seo-aeo-prerender` (PR #30) — **not yet merged/deployed** as of 2026-06-18.
+
+## Key files / entry points
+- `vite.config.ts` — `robotsPlugin()` now gates on **Vite `mode`** (was `NODE_ENV && VITE_ENV`).
+- `scripts/prerender.mjs` — post-build headless-Chrome (Puppeteer) snapshot; chained into the `build` script.
+- `src/routes.config.json` — single source of static route paths (consumed by the prerender; intended for sitemap too).
+- `src/main.tsx` — `hydrateRoot` when a route was prerendered, else `createRoot`.
+- `src/components/SEO/{Seo.tsx,JsonLd.tsx,schema.ts}` — shared head + JSON-LD; per-page `meta` lives in each page's `viewModel/FIELDS/*.json`.
+
+## How it works
+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 && node scripts/prerender.mjs`. 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).
+
+## 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`).
+
+## Client variations
+None — uniform.
+
+## Gotchas / known issues
+- **De-indexing bug (root cause):** `robotsPlugin` required `NODE_ENV && VITE_ENV==="production"`, but build scripts set neither → every build shipped `robots.dev.txt` (`Disallow: /`). **Do NOT gate robots on `NODE_ENV`** — `vite build` sets it to `production` for *every* mode, which would expose beta/gamma. Gate on Vite `mode`.
+- **`.npmrc` has `ignore-scripts=true`** → the `postbuild` lifecycle hook never fires. Prerender is therefore chained directly in the `build` script, not a `postbuild` hook.
+- **Prerender tooling:** `vite-react-ssg` supports React Router **6 only** (project is RR 7.9); `react-snap` is stale (2022) and won't launch on Node 24. Hence a custom Puppeteer snapshot. Puppeteer's Chrome must be installed at build time: `npx puppeteer browsers install chrome`.
+- **Prerender fail-fast:** a route that never mounts (`#root > *` times out) aborts the build with `process.exit(1)` — otherwise it would snapshot the empty shell (no SEO/JSON-LD) and still exit 0.
+- **🔴 Hosting requirement:** CloudFront/S3 must serve each prerendered `dist/<route>/index.html` for its path; a blanket SPA rewrite to root `index.html` serves the empty shell and defeats the prerender.
+- **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.
+
+## Change history
+- 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).

package/package.json

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