toga-ai 1.0.127 → 1.0.128

package/knowledge/2.0/apps/toga2-supply/INDEX.md

@@ -4,4 +4,4 @@
 |-----|---------|-------|
 | [TOGa Supply (toga2-supply) Architecture](architecture.md) | `toga2-supply` is the **React + Vite frontend** for TOGa Supply — warehouse fulfillment tooling (shipment selection, fulfill & ship against carrier APIs, NetSui | toga2-supply/src/api/toga.ts, toga2-supply/src/pages/ShipmentItems/view/ShipmentItemsPage.tsx, toga2-supply/src/pages/EditShipment/view/EditShipmentPage.tsx, toga2-supply/src/pages/EditShipment/api/UpdateShipmentApi.ts, toga2-supply/src/pages/Shipments/view/components/ShipmentsCardTableForm/ShipmentsCardTableForm.tsx |
 | [Fulfill & Ship](features/fulfill-and-ship.md) | Fulfill & Ship lets a warehouse user select sales-order line items, enter serials, pick a carrier/method, and in one action: create the Item Fulfillment records | toga2-supply/src/pages/ShipmentItems/view/ShipmentItemsPage.tsx, toga2-supply/src/pages/EditShipment/view/EditShipmentPage.tsx, toga2-supply/src/pages/EditShipment/view/components/forms/EditShipmentForm.tsx, toga2-supply/src/pages/EditShipment/api/UpdateShipmentApi.ts, toga2-supply/src/pages/Shipments/view/components/ShipmentsCardTableForm/ShipmentsCardTableForm.tsx, toga2-supply/src/pages/Shipments/api/ShipmentsApi.ts, _underscore/Model/Client/ItemFulfillment.php, _underscore/Trait/Netsuite/ItemFulfillment.php, _underscore/Component/Library/Carriers/Ups/Ups.php |
-| [AWS Amplify Build & Deploy (non-prod environments)](workflows/amplify-build-and-deploy.md) | How `toga2-supply` (React + Vite) builds and deploys on **AWS Amplify**. | toga2-supply/amplify.yml, toga2-supply/.github/workflows/sync-stage-environments.yml, toga2-supply/.env.qc-security |
+| [AWS Amplify Build & Deploy (non-prod environments)](workflows/amplify-build-and-deploy.md) | How `toga2-supply` (React + Vite) builds and deploys on **AWS Amplify**. | toga2-supply/amplify.yml, toga2-supply/.gitattributes, toga2-supply/.github/workflows/sync-stage-environments.yml, toga2-supply/.env.qc-security |

package/knowledge/2.0/apps/toga2-supply/workflows/amplify-build-and-deploy.md

@@ -10,6 +10,7 @@ updated: 2026-06-18
 owners: ["jcardinal"]
 files:
   - toga2-supply/amplify.yml
+  - toga2-supply/.gitattributes
   - toga2-supply/.github/workflows/sync-stage-environments.yml
   - toga2-supply/.env.qc-security
 related:
@@ -75,6 +76,23 @@ _stage ──▶ Amplify ──▶ build --mode stage
 
 ## Edge cases & escalation
 
+- **Console build spec silently overrides the repo `amplify.yml`.** A build spec saved in the
+  Amplify console (App settings → Build settings) **takes precedence over the repo-root
+  `amplify.yml`**. Symptom seen: the log ran the custom `preBuild` (`NODE_OPTIONS=8192`,
+  `npm ci --legacy-peer-deps`) but the `build` phase started and completed instantly with **zero
+  commands** (`# Starting phase: build` → `# Completed phase: build`, no `# Executing command:`
+  lines), producing no `dist/` → `CustomerError: Artifact directory doesn't exist: dist`. Cause:
+  the console spec had the custom `preBuild` but an **empty `build` phase**, and it won over the
+  repo file. Fix: either paste the full spec (with the build command) into the console editor, or
+  remove the console override so Amplify uses the repo `amplify.yml`. Diagnostic: if you don't see
+  the `Branch '...' -> Vite mode '...'` echo in the build log, the build phase isn't running.
+- **`amplify.yml` must be LF, not CRLF.** A CRLF-terminated `amplify.yml` (easy to produce on
+  Windows) can break Amplify's parsing of a multi-line `- |` block-scalar command — the simple
+  one-line `preBuild` entries survive but the block-scalar `build` command is dropped, giving the
+  same empty-build symptom as above. Mitigations applied: `.gitattributes` pins `*.yml`/`*.yaml`
+  to `eol=lf`, and the build step is written as a **single-line** command (no block scalar) to
+  remove the parsing fragility entirely. `core.autocrlf` is `false` in this repo, so bytes commit
+  as-is — keep the file LF.
 - **Silent wrong-endpoint trap (caused a production outage):** When Vite is given a `--mode`
   with no matching `.env.<mode>`, it **silently falls back to the base `.env`** (which points at
   beta) instead of erroring. An `amplify.yml` that built `--mode "$AWS_BRANCH"` therefore ran
@@ -96,6 +114,10 @@ _stage ──▶ Amplify ──▶ build --mode stage
 
 ## Change history
 
+- 2026-06-18 — Diagnosed empty-`build`-phase failure (`Artifact directory doesn't exist: dist`):
+  console build spec overrides the repo `amplify.yml`, and CRLF can drop the block-scalar build
+  command. Switched build step to a single-line command, added `.gitattributes` pinning `*.yml`
+  to LF. (jcardinal)
 - 2026-06-18 — Fixed production-breaking deploy: `amplify.yml` now strips the leading `_` from
   `$AWS_BRANCH` to get the Vite mode and **fails loudly** if `.env.$MODE` is missing (was
   silently falling back to beta); heap set to 8192; sync workflow targets underscore-prefixed

package/package.json

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