toga-ai 1.0.265 → 1.0.267

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

@@ -7,6 +7,6 @@
 | [Tools MVC — Routing, CSRF & App_Database Access Patterns](features/mvc-data-access-patterns.md) | The load-bearing 1.0 (`App_`) framework conventions a developer needs when adding a page to the Tools app — URL routing, CSRF, and DB access through `App_Databa | tools/_/app/nav.php, tools/mvc/get.php |
 | [Tools Persona-Gated Navigation (App_Nav)](features/persona-gated-navigation.md) | `App_Nav` is the Tools app's two-level, **persona-gated** navigation. | tools/_/app/nav.php, tools/mvc/get.php |
 | [Tools SAML SSO Consumer & Persona-Gated Auth (App_Auth)](features/saml-sso-auth.md) | `App_Auth` is the Tools app's authentication layer: it consumes the SAML gateway `?saml=` handoff (see the 2.0 SAML downstream integration contract), establishe | tools/_/app/auth.php, tools/mvc/sso/initiate/get.php, tools/mvc/sso/get.php, tools/mvc/login/get.php, tools/mvc/login/post.php, tools/mvc/logout/get.php, tools/mvc/get.php, tools/config.production.ini, tools/config.local.ini |
-| [Talos Knowledge Base Admin UI (KB Documents + Vocabulary)](features/talos-kb-documents-admin.md) | A Tools (1.0) admin UI to browse/fix the Talos knowledge-base documents and manage the transcript-cleanup vocabulary — without a deploy. | tools/mvc/talos/kb-documents/get.php, tools/mvc/talos/kb-documents/post.php, tools/mvc/talos/vocabulary/get.php, tools/mvc/talos/vocabulary/post.php, tools/_/app/talos/s3.php, tools/_/app/worker.php, tools/_/app/nav.php |
+| [Talos Knowledge Base Admin UI (KB Documents + Vocabulary)](features/talos-kb-documents-admin.md) | A Tools (1.0) admin UI to browse/fix the Talos knowledge-base documents and manage the transcript-cleanup vocabulary — without a deploy. | tools/mvc/talos/kb-documents/get.php, tools/mvc/talos/kb-documents/post.php, tools/mvc/talos/vocabulary/get.php, tools/mvc/talos/vocabulary/post.php, tools/_/app/talos/s3.php, tools/_/app/worker.php, tools/_/app/nav.php, tools/config.production.ini, tools/config.alpha.ini |
 | [Talos Pricing UI (Onboarding, Dashboard, Benchmarks, Cost Factors + Estimator)](features/talos-pricing-ui.md) | The 1.0 (tools app) face of the **Talos Pricing Platform** — a "Talos Pricing" nav folder with four pages plus a client-side estimate engine. | tools/_/app/nav.php, tools/_/app/talos/estimator.php, tools/mvc/talos/onboarding/get.php, tools/mvc/talos/onboarding/post.php, tools/mvc/talos/pricing/get.php, tools/mvc/talos/benchmarks/get.php, tools/mvc/talos/factors/get.php, tools/mvc/talos/factors/post.php, tools/assets/css/style.css |
 | [Deploying Tools to Elastic Beanstalk (PHP 8.5 / Amazon Linux 2023)](workflows/deploy-to-elastic-beanstalk-al2023.md) | How the **Tools** 1.0 app boots on Elastic Beanstalk running `PHP 8.5 on 64bit Amazon Linux 2023/4.13.1 (aarch64)`. | tools/.ebextensions/004_http_to_https.config, tools/.ebextensions/006_mount-s3fs.config, tools/.ebextensions/007_setup_export_cache_folders.config, tools/.ebextensions/008_setup_ldap.config, tools/.ebextensions/009_setup_phpini.config, tools/.ebextensions/020_setup_git_libraries.config, tools/.ebextensions/050_register_instance_to_shared_application_load_balancer.config, tools/ebs/git.json |

package/knowledge/1.0/apps/tools/features/talos-kb-documents-admin.md

@@ -6,7 +6,7 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-06-30
+updated: 2026-07-02
 owners: [jcardinal]
 files:
   - tools/mvc/talos/kb-documents/get.php
@@ -16,6 +16,8 @@ files:
   - tools/_/app/talos/s3.php
   - tools/_/app/worker.php
   - tools/_/app/nav.php
+  - tools/config.production.ini
+  - tools/config.alpha.ini
 related:
   - ./mvc-data-access-patterns.md
   - ./persona-gated-navigation.md
@@ -37,12 +39,27 @@ Technology*) exposes two pages.
 - KB list derived from the **actual S3 sub-folders** under `development-team/` (title-cased,
   e.g. `office-depot` → "Office Depot") — not from `Team.KnowledgeBases`.
 - Lists approved docs excluding `*.metadata.json`; columns Meeting Date (`n/j/y`) / Title /
-  Size / Last modified (`n/j/y g:i A`).
+  Size / Last modified (`n/j/y g:i A`). **Last-modified is converted from S3's UTC to
+  America/Chicago (US Central) before formatting**; the sort key stays UTC ISO-8601.
 - Clickable rows open an overlay **modal** with a type-aware preview: text inline; PDF via a
   presigned S3 URL in an iframe; Office files via the Google Docs viewer (presigned URL; MS
   Office viewer noted as an alternative); unsupported → download/delete only.
-- Download + delete are icon buttons in the modal. **Delete enqueues the worker `SyncKb`
-  re-sync** so Bedrock reflects the removal.
+- Modal actions are icon buttons: download, **move**, **edit** (text docs only), and delete.
+  **Delete / move / edit each enqueue the worker `SyncKb` re-sync** so Bedrock reflects the change.
+- **Move** (right-arrow icon) opens a small centered dialog (KB picker + Move/Cancel) to re-file a
+  mis-classified doc from one KB to another. `App_Talos_S3::moveApprovedDocument` copies the `.txt`
+  and its `.metadata.json` sidecar to the destination via **get+put (NOT server-side `CopyObject` —
+  the togaiq key is denied CopyObject even same-bucket)**, rewrites the sidecar's KB-slug attribute
+  (`metadataAttributes.client.value.stringValue`), then deletes the originals. It enqueues a
+  **single** `SyncKb("source,dest")` job (worker2 syncs both sequentially — Bedrock allows one
+  in-flight ingestion per KB). Helpers `copyWithinBucket` + `putObjectBody` added.
+- **Edit** (pencil icon, text docs only) enters edit mode in the modal: a title text box, a
+  **Find & Replace** tool ported from the old `test/team/talos/kb_processor.php` (Find/Replace,
+  Match case, Whole word only, Replace All with match count), and a contents textarea, with
+  Save/Cancel top-right. The `update` action + `App_Talos_S3::updateApprovedDocument` rewrites the
+  body and, if the title changed (`sanitizeTitle`), renames the object to
+  `"YYYY-MM-DD - {title}.txt"` (date preserved), moves+updates the sidecar filename attribute,
+  deletes the old key, and enqueues a `SyncKb` re-sync.
 
 ### `/talos/vocabulary` — cleanup vocabulary manager
 Single tabbed page: Prompt Template, Applications, Clients, People, Business Terms, Examples,
@@ -53,16 +70,29 @@ prompt/replacement tables that the worker2 pipeline reads at runtime.
 
 ## Helpers
 
-- **`App_Talos_S3`** (`_/app/talos/s3.php`) — S3 client; list KB slugs; list/count approved;
-  presigned URL; get/delete; slug sanitize+lowercase; approved-prefix path guard.
+- **`App_Talos_S3`** (`_/app/talos/s3.php`) — S3 client; list KB slugs; list/count approved
+  (UTC→Central for display); presigned URL; get/delete; `moveApprovedDocument`;
+  `updateApprovedDocument`; `sanitizeTitle`; `copyWithinBucket`; `putObjectBody`; slug
+  sanitize+lowercase; approved-prefix path guard. **`client()` credential resolution:** prefers a
+  dedicated **`[talos]`** config section (the **togaiq**-capable key), falling back to `[aws]`, then
+  the SDK default chain — because `App_Talos_S3` only ever talks to **togaiq**, so it needs the
+  togaiq-account key (the tools `[aws]` key is the toga-private key, which can cross-account *read*
+  togaiq but not *write* it).
 - **`App_Worker::enqueue()`** (`_/app/worker.php`) — inserts a `Core.WorkerJobs` row and sends
-  the `{"workerJobId": id}` SQS message, so a 1.0 app can enqueue worker2 jobs.
+  the `{"workerJobId": id}` SQS message, so a 1.0 app can enqueue worker2 jobs. Requires the
+  `[worker]` (`queue_url`/`queue_region`) and `[aws]` (main-account key for SQS `SendMessage`)
+  config sections.
 
 ## Deploy prerequisites
 
 - `aws/aws-sdk-php` installed in `tools/vendor` (S3 + SQS).
-- New `tools/config.*.ini` sections (none exist yet): `[database_core2]` (writable 2.0 Core,
-  dbname `Core`), `[worker]` (`queue_url` / `queue_region`), `[aws]` (production).
+- `tools/config.production.ini` / `config.alpha.ini` sections (now added):
+  - **`[talos]`** — the **togaiq**-account S3 key (`App_Talos_S3` write path); required or move/edit/
+    delete fail with `AccessDenied`.
+  - **`[worker]`** — worker2 production SQS `queue_url` / `queue_region` (for `App_Worker::enqueue`).
+  - **`[aws]`** — main-account key for SQS `SendMessage` (toga-private key; cross-account reads
+    togaiq but cannot write it — that's why `[talos]` exists).
+  - `[database_toga2core]` — writable 2.0 Core (already present).
 - Apply the dbchanges2 `Team/2026-06-30a..e` + `Core/2026-06-30a` migrations in order.
 - Verify the Bedrock KB region / data-source name against the live account (TODOs in code).
 
@@ -70,12 +100,27 @@ prompt/replacement tables that the worker2 pipeline reads at runtime.
 
 - **KB list is derived from S3, not the DB.** The browse UI enumerates live S3 folders under
   `development-team/`; `Team.KnowledgeBases` is not the source of truth for what's shown.
-- **Delete is not just an S3 delete** — it also enqueues a worker `SyncKb` job to re-sync the
-  Bedrock data source.
-- No new secret literals introduced; credentials come from the new config sections above.
+- **Delete / move / edit are not just S3 ops** — each enqueues a worker `SyncKb` job to re-sync
+  the Bedrock data source.
+- **`App_Talos_S3` needs the togaiq-account key (`[talos]`).** The tools `[aws]` key is the
+  toga-private key: it can cross-account *read* togaiq but **cannot write** it, so move/edit/delete
+  fail `AccessDenied` without a `[talos]` section.
+- **Never use server-side `CopyObject` for togaiq** — the togaiq key is denied `CopyObject` even
+  within the same bucket; move/edit copy via get+put.
+- **Move/edit re-sync must be one `SyncKb("source,dest")` job**, not two parallel jobs — Bedrock
+  allows only one in-flight ingestion per KB and parallel syncs race.
+- No new secret literals introduced; credentials live in the config sections above (documented by
+  section/account, never by value).
 
 ## Change history
 
+- 2026-07-02 — Added **move** (re-file a doc between KBs) and **edit** (title + Find&Replace + body,
+  ported from the old `kb_processor.php`) to the doc modal, each via get+put (togaiq denies
+  `CopyObject`) and each enqueuing a single `SyncKb("source,dest")` re-sync. Fixed togaiq
+  `AccessDenied`: `App_Talos_S3::client()` now uses a dedicated `[talos]` (togaiq-account) key; added
+  `[talos]`, `[worker]`, and `[aws]` sections to `config.production.ini`/`config.alpha.ini` so
+  `App_Worker::enqueue` (SQS) works. Last-modified now displayed in US Central (converted from S3
+  UTC). (jcardinal)
 - 2026-06-30 — Built the Talos KB admin UI: `/talos/kb-documents` (S3-derived KB list, approved
   doc browser with type-aware preview modal, download + delete-with-resync) and `/talos/vocabulary`
   (tabbed prompt/vocabulary/replacements manager with transactional full-set reconciliation;

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

@@ -13,7 +13,7 @@
 | [_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 |
-| [Recursive Item Fulfillments (upstream mirroring)](features/recursive-item-fulfillments.md) | In a multi-tier supply chain a sales order (SO) spawns a purchase order (PO) that becomes another SO downstream, and so on. | _underscore/Model/Client/ItemFulfillment.php, _underscore/Model/Client/ItemFulfillmentItem.php, _underscore/Model/Client/ItemFulfillmentItemUnit.php, _underscore/Model/Client/ItemFulfillmentPackage.php, _underscore/Model/Compass/AdvanceShippingNotice.php, dbchanges2/Core/2026-02-13 - 75601 - RecursiveItemFulfillmentCreation.sql, dbchanges2/Core/2026-06-04 - RecursiveItemFulfillmentPut.sql |
+| [Recursive Item Fulfillments (upstream mirroring)](features/recursive-item-fulfillments.md) | In a multi-tier supply chain a sales order (SO) spawns a purchase order (PO) that becomes another SO downstream, and so on. | _underscore/Model/Client/ItemFulfillment.php, _underscore/Model/Client/ItemFulfillmentItem.php, _underscore/Model/Client/ItemFulfillmentItemUnit.php, _underscore/Model/Client/ItemFulfillmentPackage.php, _underscore/Model/Compass/AdvanceShippingNotice.php, dbchanges2/Core/2026-02-13 - 75601 - RecursiveItemFulfillmentCreation.sql, dbchanges2/Core/2026-06-04 - RecursiveItemFulfillmentPut.sql, dbchanges2/Client_Compass/2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql |
 | [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 |  |

package/knowledge/2.0/apps/_underscore/features/recursive-item-fulfillments.md

@@ -6,7 +6,7 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-06-19
+updated: 2026-07-02
 owners: [jcardinal, rgirish]
 files:
   - _underscore/Model/Client/ItemFulfillment.php
@@ -16,6 +16,7 @@ files:
   - _underscore/Model/Compass/AdvanceShippingNotice.php
   - dbchanges2/Core/2026-02-13 - 75601 - RecursiveItemFulfillmentCreation.sql
   - dbchanges2/Core/2026-06-04 - RecursiveItemFulfillmentPut.sql
+  - dbchanges2/Client_Compass/2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql
 related:
   - ../architecture.md
   - ../../api2/architecture.md
@@ -102,12 +103,42 @@ inheritance. Verified against prod `Client_Compass` chains (≥3 levels deep).
   upstream mirror. A later reconciling PUT cleans up stale records via set comparison. Full
   delete handling would need a `preDelete` mechanism + `PRE/DELETE` interceptor rows.
 - **Transfer-order fulfillments are explicitly excluded from the upstream walk.** `reconcileUpstreamLevel()` returns `null` immediately when the downstream IF has `transferOrderId` set (no `salesOrderId`). This is intentional for standalone TOs (GroWrk v1). When SO→TO→SO chain scenarios are needed, Phase 5 of the GroWrk transfer order plan extends this method to walk `TransferOrders_SalesOrders` bridge tables — see `clients/growrk/features/transfer-order-flow.md`.
+- **Broken SOI↔POI bridge → empty header-only duplicate IFs (root cause, guard added
+  2026-07-02).** The item walk maps a downstream IFI up via
+  `IFI.salesOrderItemId → PurchaseOrderItems_SalesOrderItems → SalesOrderItems_PurchaseOrderItems`.
+  When that upstream `SalesOrderItems_PurchaseOrderItems` bridge is **missing/broken** (the same
+  integrity class as the ~116 off-by-one Compass orders — see the Compass
+  `asn-to-item-fulfillment` doc), `$desiredItems` resolves to **zero** even though the downstream
+  IF has items. Pre-guard, step 4's eager resolve-or-create then POSTed an **empty header-only
+  upstream IF** (e.g. Compass SA133377 got duplicate empty customer-facing IFs 71724/71725
+  alongside the legit direct-ASN IF 70635). **Guard:** `reconcileUpstreamLevel` now, after
+  building `$desiredItems`, if it is empty **AND** the downstream IF has >0 ItemFulfillmentItems,
+  `error_log()`s a diagnostic and returns `null` (skips the upstream mirror) — distinguished from
+  the legitimate header-first POST case (downstream IF genuinely has 0 items), which is unchanged.
+- **Duplicate customer-facing IF: the engine only adopts an upstream IF it created itself, never a
+  pre-existing one (known gap, adoption DEFERRED).** `reconcileUpstreamLevel` finds an existing
+  upstream IF only via `upstreamItemFulfillmentId`; it does **not** adopt a pre-existing IF that
+  already sits on the upstream SO from another flow (e.g. a direct-ASN-created IF). So a broken
+  bridge could yield two customer-facing IFs on the same SO (SA133377: direct-ASN IF 70635 + a
+  mirror-created duplicate). **Naive adoption is dangerous and was intentionally not implemented:**
+  step 5's delete-stale step deletes upstream IFIs with no matching downstream group, so adopting
+  an IF while the item walk is empty/broken would **DELETE the adopted IF's legitimate line items**.
+  Requires a CTO design review before implementing adoption semantics. The 2026-07-02 broken-bridge
+  guard prevents the duplicate cascade for this failure mode without needing adoption.
 - **Out of scope:** NetSuite sync of upstream IFs; transfer-order fulfillments
   (`transferOrderId`) are skipped.
 - **Performance:** every child write re-runs a full upstream walk (read-heavy, but each
   upstream record is written at most once — idempotent). Fine for normal fulfillment sizes.
 
 ## Change history
+- 2026-07-02 — Added a **broken-bridge guard** to `reconcileUpstreamLevel`: when `$desiredItems`
+  is empty but the downstream IF has items (broken SOI↔POI bridge), it logs and returns null
+  instead of creating an empty header-only duplicate upstream IF. Root-caused on Compass SA133377
+  (SO 107609), where a broken bridge + a pre-existing direct-ASN IF produced duplicate empty
+  customer-facing IFs (71724/71725) and left the correct serial/tracking off the customer IF;
+  data repaired by `dbchanges2/Client_Compass/2026-07-02a`. Companion fix — adopting a pre-existing
+  upstream IF instead of creating a duplicate — was **DEFERRED** pending CTO review (the delete-stale
+  step would delete the adopted IF's line items when the item walk is empty). (jcardinal)
 - 2026-06-19 — Documented explicit TO exclusion in reconcileUpstreamLevel; cross-linked GroWrk transfer order plan. (rgirish)
 - 2026-06-08 — Documented the Recursive Item Fulfillments engine (interceptor-driven upstream fulfillment mirroring, bundle scaling, reconcile loop). (jcardinal)
 

package/knowledge/2.0/apps/dbchanges2/architecture.md

@@ -6,7 +6,7 @@ project: Database Changes
 client: shared
 type: architecture
 status: active
-updated: 2026-06-23
+updated: 2026-07-02
 owners: [jcardinal, mhammontree]
 files:
   - Core/
@@ -198,6 +198,41 @@ WHERE
 - Keep the single statement well under `max_allowed_packet` (64 MB default) — a few thousand
   rows is comfortably fine.
 
+## Self-referencing DELETE — wrap the subquery in a derived table
+
+MySQL forbids a `DELETE` (or `UPDATE`) whose `WHERE` subquery reads **the same table being
+modified** — it fails with **error 1093: "You can't specify target table 'X' for update in
+FROM clause."** This bites cleanup migrations that delete duplicate rows by selecting which
+rows to keep from the very table being pruned.
+
+The fix is to **materialize the subquery through an extra derived-table layer**, forcing MySQL
+to snapshot the row set before the delete runs:
+
+```sql
+-- WRONG — error 1093, ItemFulfillments is both the DELETE target and read in the subquery
+DELETE FROM ItemFulfillments
+WHERE id NOT IN (
+	SELECT MIN(id)
+	FROM ItemFulfillments
+	GROUP BY salesOrderItemId, trackingSerial
+);
+
+-- CORRECT — wrap the inner SELECT in a derived table so it is materialized first
+DELETE FROM ItemFulfillments
+WHERE id NOT IN (
+	SELECT keepId FROM (
+		SELECT MIN(id) AS keepId
+		FROM ItemFulfillments
+		GROUP BY salesOrderItemId, trackingSerial
+	) AS keep
+);
+```
+
+The extra `SELECT … FROM ( … ) AS keep` wrapper is the whole idiom: MySQL evaluates the inner
+query into a temporary derived table, so the outer `DELETE` no longer "sees" a live read of
+its own target. Used in `2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql` to prune
+duplicate `ItemFulfillments` rows.
+
 ## Relationship to the rest of 2.0
 
 `dbchanges2` is registered as a **2.0 core repo** (`role: core` in `registry.json`) — it is

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

@@ -21,7 +21,7 @@
 | [Startech Webhook Handler (worker2)](features/startech-webhook-handler.md) | Receives inbound webhook events from Startech (Easeedesk) and creates or updates the corresponding ticket in TOGA 2.0. | worker2/Worker/Startech.php |
 | [Talos (TOGa IQ) Meeting-Notes Integration & Token Auto-Refresh (consumer)](features/talos-meeting-notes-integration.md) | How a **dev tool / agent consumes Talos (TOGa IQ)** to query the team meeting-notes corpus programmatically. | .claude/skills/plan-ticket/scripts/talos.js |
 | [Talos Pricing Automation (worker2 Cron — AWS Actuals, Calibration, Monthly Report)](features/talos-pricing-automation.md) | The worker2 half of the **Talos Pricing Platform** (see the talos `pricing-cogs-model` and tools `talos-pricing-ui` docs for the other halves). | worker2/Worker/Talos/Pricing.php, worker2/Database/TalosPricingCrons.sql |
-| [Talos Transcript Ingestion Pipeline (worker2 → AWS Bedrock KBs)](features/talos-transcript-ingestion.md) | `_Worker_Team_Transcripts` (in addition to the upstream `Export` action — see [Teams Meeting Transcript Export](./teams-transcript-export.md)) now runs a fully | worker2/Worker/Team/Transcripts.php, worker2/bin/reprocess-transcripts.php, worker2/Config/production.ini, dbchanges2/Team/2026-06-30a, dbchanges2/Team/2026-06-30b, dbchanges2/Team/2026-06-30c, dbchanges2/Team/2026-06-30d, dbchanges2/Team/2026-06-30e, dbchanges2/Core/2026-06-30a |
+| [Talos Transcript Ingestion Pipeline (worker2 → AWS Bedrock KBs)](features/talos-transcript-ingestion.md) | `_Worker_Team_Transcripts` (in addition to the upstream `Export` action — see [Teams Meeting Transcript Export](./teams-transcript-export.md)) now runs a fully | worker2/Worker/Team/Transcripts.php, worker2/bin/reprocess-transcripts.php, worker2/bin/sync-knowledge-bases.php, worker2/Config/production.ini, dbchanges2/Team/2026-06-30a, dbchanges2/Team/2026-06-30b, dbchanges2/Team/2026-06-30c, dbchanges2/Team/2026-06-30d, dbchanges2/Team/2026-06-30e, dbchanges2/Core/2026-06-30a, dbchanges2/Core/2026-07-02a, dbchanges2/Team/2026-07-02a |
 | [Team Sprint Management & Reporting](features/team-sprint-management.md) | `_Worker_Team_Sprint` (file `Worker/Team/Sprint.php`) is the engine behind TOGA's internal **development-sprint process and reporting**. | worker2/Worker/Team/Sprint.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 and archives t | worker2/Worker/Team/Transcripts.php, worker2/Config/production.ini, worker2/Database/TeamsTranscriptExports.sql, dbchanges2/Core/2026-06-18a - Teams Transcript Export schedule.sql |
 | [VAPI Webhook Handler (worker2 — AI-BDR end-of-call processing)](features/vapi-webhook-handler.md) | `_Worker_Vapi` ([worker2/Worker/Vapi.php](worker2/Worker/Vapi.php)) is the **PHP side of the AI-BDR call loop** — the webhook that receives VAPI's end-of-call r | worker2/Worker/Vapi.php, worker2/Worker/Ai/Bdr/Vapi.php |

package/knowledge/2.0/apps/worker2/features/talos-transcript-ingestion.md

@@ -6,11 +6,12 @@ project: Worker
 client: shared
 type: feature
 status: active
-updated: 2026-06-30
+updated: 2026-07-02
 owners: [jcardinal]
 files:
   - worker2/Worker/Team/Transcripts.php
   - worker2/bin/reprocess-transcripts.php
+  - worker2/bin/sync-knowledge-bases.php
   - worker2/Config/production.ini
   - dbchanges2/Team/2026-06-30a
   - dbchanges2/Team/2026-06-30b
@@ -18,6 +19,8 @@ files:
   - dbchanges2/Team/2026-06-30d
   - dbchanges2/Team/2026-06-30e
   - dbchanges2/Core/2026-06-30a
+  - dbchanges2/Core/2026-07-02a
+  - dbchanges2/Team/2026-07-02a
 related:
   - ./teams-transcript-export.md
   - ./creating-worker-actions.md
@@ -45,9 +48,13 @@ sidecar written to `s3://togaiq/development-team/{kb_slug}/approved/` → raw ar
 ## Key files / entry points
 
 - `Worker/Team/Transcripts.php` — actions `Scan`, `Process(string $sourceKey)`,
-  `SyncKb(string $kbSlug)` (all alongside the existing `Export`).
+  `SyncKb(string $kbSlug)` (comma-separated slug list), `SyncKnowledgeBases(bool $apply=true)`
+  (all alongside the existing `Export`).
 - `bin/reprocess-transcripts.php` — standalone CLI backlog reprocessor.
-- `Config/production.ini` `[talos]` section — S3/Bedrock targets (see Configuration).
+- `bin/sync-knowledge-bases.php` — CLI entry for the Bedrock→`Team.KnowledgeBases` registry
+  sync (`--dry-run` supported).
+- `Config/production.ini` `[talos]` and `[teams]` sections — S3/Bedrock targets + the two
+  per-account S3 credential sets (see Configuration).
 - DB config + ledger tables in the `Team.*` schema (see Data model), authored in dbchanges2
   under `Team/2026-06-30a..e` + `Core/2026-06-30a`.
 
@@ -61,28 +68,56 @@ each via `_Worker::runTask('Team/Transcripts/Process', ['sourceKey' => …])`. S
 
 ### `Process(string $sourceKey)`
 Port of `kb_processor`, per transcript:
-1. Fetch the raw VTT from S3 (`toga-private`, **us-west-2**).
+1. Fetch the raw VTT from S3 (`toga-private`, **us-west-2**). Parse **date + meeting title up
+   front** (previously parsed from the filename only *after* classification).
 2. Call the TOGa IQ AI endpoint `https://api.togaiq.com/api/ai/generate`, model
    `bedrock/us.anthropic.claude-haiku-4-5-20251001-v1:0`, with an **extended** `output_schema`
    returning **both** `knowledge_doc` **and** `kb_slug` — the AI picks the single best active KB
-   from the supplied list, or `general`. The system prompt is **assembled at runtime** from DB
-   tables: a template body with `{{APPLICATIONS}}`/`{{CLIENTS}}`/`{{PEOPLE}}`/`{{BUSINESS_TERMS}}`/`{{EXAMPLES}}`
-   placeholders filled from `Team.TranscriptPromptTerms`.
+   from the supplied list, or `general`. The **meeting title is passed into**
+   `callAICleaningAPI` and surfaced as a `MEETING TITLE:` block; the classifier instruction
+   **prioritizes the title** (often the only KB signal on short transcripts). **Classification
+   rule: customer over company** — `toga-technology` is our *own* company, so a meeting involving
+   both a customer and TOGA staff must classify to the **customer** KB; pick `toga-technology`
+   only for purely-internal meetings; fall back to `general` when neither can be determined. The
+   system prompt is **assembled at runtime** from DB tables: a template body with
+   `{{APPLICATIONS}}`/`{{CLIENTS}}`/`{{PEOPLE}}`/`{{BUSINESS_TERMS}}`/`{{EXAMPLES}}`
+   placeholders filled from `Team.TranscriptPromptTerms`. The active template body also
+   **excludes personal/social/non-work content** and must never emit a "Personal Notes" section
+   (see Change history / the 2026-07-02a Team migration).
 3. Apply DB-driven text replacements from `Team.TranscriptReplacements` (`:c` case-sensitive,
    `:w` whole-word, `:cw`) via `preg_replace_callback` **so replacement backrefs stay literal**.
 4. Build the approved name `"{YYYY-MM-DD} - {Title Case}.txt"`.
-5. Upload to `s3://togaiq/development-team/{kb_slug}/approved/` (**us-east-1**) plus a
-   `{name}.txt.metadata.json` Bedrock sidecar.
-6. Archive the raw VTT to `…/{kb_slug}/archive/{date}/`, then delete the source.
+5. Upload to `s3://togaiq/development-team/{kb_slug}/approved/` (**us-east-1**, togaiq account
+   client) plus a `{name}.txt.metadata.json` Bedrock sidecar.
+6. Archive the raw VTT to `…/{kb_slug}/archive/{date}/` via **get(raw) + put(talos)** (NOT
+   `CopyObject` — source and dest are in **different AWS accounts**, so cross-account
+   `CopyObject` is impossible), then delete the source.
 7. AWS Bedrock `startIngestionJob` on that KB's data source (retry 5×30s on
    `ConflictException` / throttling). **If `kb_slug === 'general'`, sync ALL active KBs.**
 
+### `SyncKnowledgeBases(bool $apply=true)` (cron)
+Keeps `Team.KnowledgeBases` current with **Bedrock as the source of truth** — the table only
+had the KBs that existed as S3 folders at build time (`general`, `office-depot`), so the AI
+classifier could never pick a KB (e.g. `elite`) that wasn't already a candidate. Lists all
+Bedrock KBs (`listKnowledgeBases`, via helper `listAllKnowledgeBases()`), filters to the
+`{kb_prefix}*` prefix (`development-team-`), derives the slug, and **upserts**: new rows insert
+`isActive=1` (`isGeneral=1` only for `general`), name title-cased, `bedrockKbId` cached; existing
+rows keep their name/flags and only refresh `bedrockKbId`. **Nothing is deleted or deactivated.**
+CLI entry `bin/sync-knowledge-bases.php` (`--dry-run`). Cron: `Core.CronJobs` row action
+`Team/Transcripts/SyncKnowledgeBases`, schedule `0 5 * * *` (daily 05:00 CT), `maxExecutionTime`
+300 (dbchanges2 `Core/2026-07-02a`; depends on the 2026-05-14 `maxExecutionTime` migration).
+
 Idempotency + status are tracked in `Team.TranscriptProcessing`
 (`pending/cleaned/uploaded/archived/synced/failed`).
 
 ### `SyncKb(string $kbSlug)`
-On-demand single-KB re-sync (used by the Tools delete flow — see
+On-demand re-sync used by the Tools delete/move/edit flows (see
 [Talos KB Documents Admin](../../../1.0/apps/tools/features/talos-kb-documents-admin.md)).
+`$kbSlug` now accepts a **comma-separated slug list** and syncs each KB **sequentially** with
+`KB_SYNC_DELAY_SECONDS` spacing. This exists because **Bedrock allows only one in-flight
+ingestion per KB** — a move that fired two independent parallel `SyncKb` workers raced and one
+was dropped (only the destination synced). The Tools move now enqueues a **single**
+`SyncKb("source,dest")` job so both KBs sync in one job, in order.
 
 ### `bin/reprocess-transcripts.php` (CLI backlog reprocessor)
 Standalone CLI that bootstraps `_underscore`, lists existing raw transcripts under the
@@ -109,7 +144,10 @@ PKs `INT UNSIGNED` to match the existing Talos Team-table family.
 - **`Team.TranscriptPromptTemplate`** — `name, bodyText` (w/ placeholders), `instruction, model,
   temperature, maxTokens, timeoutSeconds, isActive`. One active row seeded from the `.ini` system prompt.
 - **`Team.KnowledgeBases`** — `slug, name, isGeneral, bedrockKbId, isActive`. Seeded `general` +
-  `office-depot`. NOTE: the Tools browse UI derives the **live** KB list from S3 folders, not this table.
+  `office-depot`, but now **auto-kept-current from Bedrock** by the daily `SyncKnowledgeBases`
+  action (Bedrock is the source of truth; the table is a cache/allowlist of classifier
+  candidates). NOTE: the Tools *browse* UI still derives its live KB list from S3 folders, not
+  this table.
 - **`Team.TranscriptProcessing`** — `sourceKey UNIQUE(255), kbSlug, approvedKey, archiveKey,
   status` ENUM (`pending/cleaned/uploaded/archived/synced/failed`), `aiModel, failureReason,
   dtProcessed`. Pipeline ledger + idempotency.
@@ -122,10 +160,22 @@ PKs `INT UNSIGNED` to match the existing Talos Team-table family.
 `worker2/Config/production.ini` `[talos]`: `s3_bucket=togaiq`, `s3_region=us-east-1`,
 `bedrock_region=us-east-1`, `kb_prefix=development-team-`, `s3_root_path=development-team/`.
 
+**Two S3 credential sets — one per AWS account (see the cross-account gotcha):**
+- `[teams]` `s3_access_key_id` / `s3_secret_access_key` — the **toga-private** key (raw
+  transcripts, us-west-2). Read by `s3Client()` / `getS3Client()`.
+- `[talos]` `s3_access_key_id` / `s3_secret_access_key` — the **togaiq** key (approved/archive
+  KB bucket, us-east-1). Read by `getTalosS3Client()` and `getBedrockClient()`.
+
+Credential **values live only in the deployed `production.ini`** — documented here by section
+and account, never by value. Pre-existing plaintext keys should be rotated (separate track).
+
 ## Gotchas / known issues
 
-- **Cross-region S3.** The raw bucket `toga-private` is **us-west-2** while `togaiq` is
-  **us-east-1**. `Process()` uses two S3 clients; the archive step is a **cross-region copy**.
+- **Cross-ACCOUNT S3 (root cause of repeated PutObject/CopyObject `AccessDenied`).** `toga-private`
+  (raw, us-west-2) and `togaiq` (KB bucket, us-east-1) live in **different AWS accounts** — **no
+  single IAM key can write to both.** Credentials are therefore **per-bucket**: `[teams]` key for
+  toga-private, `[talos]` key for togaiq. Because it spans accounts, **`CopyObject` is impossible**;
+  the archive step is a **get(raw) + put(talos)**, not a server-side copy.
 - **`[talos]` keys were added to `production.ini` only** — the beta/development configs still
   need them before the pipeline runs in those environments.
 - **`general` KB fans out.** A `Process()` classified as `general` (or a `general` sync) triggers
@@ -143,6 +193,15 @@ PKs `INT UNSIGNED` to match the existing Talos Team-table family.
 
 ## Change history
 
+- 2026-07-02 — Fixed cross-**account** S3 creds: `toga-private` and `togaiq` are separate AWS
+  accounts, so credentials are now per-bucket (`[teams]` vs `[talos]` in `production.ini`) and the
+  archive step is get+put instead of the impossible cross-account `CopyObject`. Built
+  `SyncKnowledgeBases` (Bedrock→`Team.KnowledgeBases` upsert) + `bin/sync-knowledge-bases.php` and a
+  daily `0 5 * * *` cron so the classifier's candidate KB list stays current. `SyncKb` now takes a
+  comma-separated slug list and syncs sequentially (Bedrock allows one in-flight ingestion per KB;
+  parallel syncs raced). Classification: meeting title now passed to and prioritized by the AI, and
+  customer-over-company (a customer meeting stays with the customer even when TOGA staff attend).
+  Prompt template surgically updated to exclude personal/social content ("Personal Notes"). (jcardinal)
 - 2026-06-30 — Built the automated cron-driven ingestion pipeline (`Scan`/`Process`/`SyncKb`) +
   the `bin/reprocess-transcripts.php` backlog CLI, porting the manual `kb_processor.php`. Added
   the `Team.*` config/ledger schema (DB-editable replacements, prompt terms, prompt template, KB

package/knowledge/clients/compass-usa/INDEX.md

@@ -2,7 +2,7 @@
 
 | Doc | Framework | Summary | Files |
 |-----|-----------|---------|-------|
-| [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) | 2.0 | For Compass USA, posting an AdvanceShippingNotice (ASN) auto-creates the ItemFulfillment (IF) on the upstream SalesOrder. | _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Model/Compass/PurchaseOrder.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client_Compass/2026-06-11 - AsnItemTrackingNumberAcl.sql, dbchanges2/Client_Compass/2026-06-15b - BackfillSA132781ItemFulfillmentTracking.sql, dbchanges2/Client_Compass/2026-06-16 - CleanupSA132763CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql, dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql, dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql |
+| [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) | 2.0 | For Compass USA, posting an AdvanceShippingNotice (ASN) auto-creates the ItemFulfillment (IF) on the upstream SalesOrder. | _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Model/Compass/PurchaseOrder.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client_Compass/2026-06-11 - AsnItemTrackingNumberAcl.sql, dbchanges2/Client_Compass/2026-06-15b - BackfillSA132781ItemFulfillmentTracking.sql, dbchanges2/Client_Compass/2026-06-16 - CleanupSA132763CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql, dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql, dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql, dbchanges2/Client_Compass/2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql |
 | [Compass: Item-Fulfillment TableViews (for-sales-order-items & for-sales-orders, tracking via bridge)](features/item-fulfillment-tracking-tableview.md) | 2.0 | Two sibling Compass TableViews in `Client_Compass` display fulfilled items in toga2-supply, both driven by `TableViews` / `TableViewJoins` / `TableViewFields` c | dbchanges2/Client_Compass/2026-06-10 - ItemFulfillmentsForSalesOrderItemsTableView.sql, dbchanges2/Client_Compass/2026-06-11 - ItemFulfillmentsForSalesOrdersTableView.sql, dbchanges2/Client_Compass/2026-06-15a - FixItemFulfillmentTrackingNumberJoins.sql |
 | [Compass MITS PO → SO Item Linking](features/mits-po-to-so-item-linking.md) | 2.0 | MITS sends Compass inbound Purchase Orders (`POST /v2/purchase-orders`) against a Sales Order (`mitsSalesOrder`). | _underscore/Model/Compass/PurchaseOrder.php, worker/crons/toga2/compass/workflow/3a_import_office_depot_purchase_orders.php |
 | [Compass MITS PO Transmission to Vendors](features/mits-po-transmission-to-vendors.md) | 2.0 | The 1.0 worker cron `2_transmit_mits_purchase_orders_to_vendors.php` transmits Compass PurchaseOrders to their vendors (Office Depot, Strategic Systems, Compass | worker/crons/toga2/compass/workflow/2_transmit_mits_purchase_orders_to_vendors.php, library/app/client/compass.php |

package/knowledge/clients/compass-usa/features/asn-to-item-fulfillment.md

@@ -5,7 +5,7 @@ project: _Underscore
 client: compass-usa
 type: client-feature
 status: active
-updated: 2026-06-30
+updated: 2026-07-02
 owners: [jcardinal, bala]
 files:
   - _underscore/Model/Compass/AdvanceShippingNotice.php
@@ -18,6 +18,7 @@ files:
   - dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql
   - dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql
   - dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql
+  - dbchanges2/Client_Compass/2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql
 related:
   - ../../../2.0/apps/_underscore/features/recursive-item-fulfillments.md
   - ../../../2.0/apps/_underscore/features/item-fulfillment-stage-lifecycle-and-order-status.md
@@ -207,6 +208,18 @@ Compass Canada (`Model/Compass/Canada/`) is a separate sub-client. The Compass c
 
 ## Change history
 Dated one-liners, newest first.
+- 2026-07-02 — Repaired SA133377 (SO 107609, line 1 MD7F4LL/A-S): the customer IF (IFI 276821)
+  had no serial and the wrong tracking (`522944658493` — the first of two tracking-only vendor
+  ASNs on PO 103641 that reconciled onto the direct-ASN IF 70635) instead of `873840444805`
+  (the real device unit 63108 / serial SKRX9Y4W537 arrived up the mirror chain from downstream
+  IF 71723). Migration `2026-07-02a` adds the missing IFIU + correct unit-level tracking, swaps
+  the stale header/item tracking, and retires the empty duplicate IF 71725 (idempotent, sql-reviewer
+  SAFE). Root cause was a broken `SalesOrderItems_PurchaseOrderItems` bridge on the downstream
+  shipped SO item (PO item 179306, no upstream bridge — same off-by-one integrity class as the
+  ~116 orders above) feeding the recursive mirror engine, which then created empty duplicate
+  customer-facing IFs; forward engine guard added in the
+  [Recursive Item Fulfillments](../../../2.0/apps/_underscore/features/recursive-item-fulfillments.md)
+  doc (2026-07-02). (jcardinal)
 - 2026-06-30 — `resolveOrCreateItemFulfillment` now resolves the shipped `ItemFulfillmentStage` by
   status slug and sets `itemFulfillmentStage` on the IF payload, so ASN-created fulfillments land
   shipped (not stage-less) on both Compass USA + Canada. Part of the platform-wide IF stage

package/package.json

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