toga-ai 1.0.389 → 1.0.391

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

@@ -4,7 +4,7 @@
 |-----|---------|-------|
 | [Proposed — git-sourced base+overlay JSON authoring for the Surface layer](architecture/surface-authoring-proposal.md) | A **proposal / handoff recommendation** (not implemented) that the Surface layer's *authoring* model move off hand-authored SQL against the `SurfaceOverrides` E | _underscore/Model/Core/Surface.php, _underscore/Model/Client/SurfaceOverride.php |
 | [_underscore Framework Architecture](architecture.md) | `_underscore` is the shared PHP backend framework for **all 2.0 applications**. | _underscore/_underscore.php, _underscore/Loader.php, _underscore/Framework.php, _underscore/Model.php, _underscore/Database.php, _underscore/Query.php, _underscore/Route.php, _underscore/Component.php |
-| [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 |
+| [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, _underscore/Model/Client/TrackingNumber.php, dbchanges2/Client/2026-06-03- BLANK_CLIENT_DATABASE.sql, dbchanges2/Client/2026-06-23b - ItemTranslationsAcl.sql |
 | [Address Validation (carrier waterfall + validateAddress scripted endpoint)](features/address-validation.md) | `_Model_Client_Address::validateAddress` verifies a US address against a **carrier waterfall (USPS → FedEx → UPS)** and returns a single canonical, carrier-norm | _underscore/Model/Client/Address.php |
 | [_ApiRequest ENCODE__JSON now sends Content-Type: application/json](features/apirequest-json-content-type.md) | `_ApiRequest::execute()`'s `ENCODE__JSON` branch json-encoded the request body but never set a `Content-Type` header. | _underscore/ApiRequest.php |
 | [Assortment Name Translation (AssortmentTranslations sidecar)](features/assortment-name-translation.md) | Serves Assortment (product-grouping) **names** in multiple languages by adding a per-language **sidecar** table `AssortmentTranslations`, reusing the platform's | _underscore/Model/Client/AssortmentTranslation.php, dbchanges2/Client/2026-06-26a - AssortmentTranslations.sql, dbchanges2/Core/2026-06-26a - AssortmentTranslationsRecord.sql, dbchanges2/Client/2026-06-26b - AssortmentTranslationsAcl.sql |

package/knowledge/2.0/apps/_underscore/features/acl-permission-chain.md

@@ -6,11 +6,12 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-07-02
+updated: 2026-07-21
 owners: ["jcardinal", "mhammontree"]
 files:
   - api2/Component/Api/V2/V2.php
   - _underscore/Model/Core/Page.php
+  - _underscore/Model/Client/TrackingNumber.php
   - dbchanges2/Client/2026-06-03- BLANK_CLIENT_DATABASE.sql
   - dbchanges2/Client/2026-06-23b - ItemTranslationsAcl.sql
 ---
@@ -112,10 +113,11 @@ Worked example: the reprint API `GET /v2/tracking-numbers/reprint`
 Client-DB `AclRecordScripts` grant (migrations in `dbchanges2`) before it stopped 403ing — see the
 carrier-shipping-labels feature doc.
 
-## Add a writable field to a V2 record (3-file migration)
+## Add a writable field to a V2 record (FOUR requirements)
 
-Adding a persisted, API-writable field to an existing V2 record is a **three-file migration set**
-— miss any one and the API rejects the write with a specific code (see the
+Making a field persisted **and** API-writable on an existing V2 record takes **four** things —
+three migration files plus a code change in the generated model. Miss any one and the API
+rejects the write with a **specific code** (see the
 [V2 API error codes](../../api2/features/v2-api-error-codes.md) map):
 
 1. **Core `RecordFields` registration** (`dbchanges2/Core/`) — register the field name + type
@@ -130,11 +132,30 @@ Adding a persisted, API-writable field to an existing V2 record is a **three-fil
    writable sibling field** on the same record — pick a sibling that actually has explicit
    `AclFieldPermissions` rows (e.g. on `TrackingNumbers`, `containsBattery` has them, whereas
    `requiresSignature` had none), and resolve `roleId` by subselect.
+4. **Generated model-class declaration** (`_underscore/Model/Client/<Name>.php`) — the field must
+   be declared on the **generated** PHP model class, e.g.
+   `public $needsReturnLabel = self::FIELD_BOOLEAN;`. **Without it the API returns `EO-1`**
+   ("There is no field called 'X' in the '_Model_Client_Y' model"). This is a **code**
+   requirement, not a migration, so it is the one most easily missed when the DB side is already
+   complete — see the branch-mismatch gotcha below.
 
 Worked example (TRUE-79191, `TrackingNumbers.signatureType`): `Core/... - TrackingNumberSignatureTypeRecordField.sql`
 (RecordField, `STRING`), `Client/... - TrackingNumberSignatureType.sql` (guarded `ALTER TABLE`),
-`Client/... - TrackingNumberSignatureTypeFieldPermission.sql` (cloned `containsBattery`'s grants).
-This mirrors the earlier `needsReturnLabel` / `returnAddressId` 3-file sets.
+`Client/... - TrackingNumberSignatureTypeFieldPermission.sql` (cloned `containsBattery`'s grants),
+plus the `signatureType` declaration on `_underscore/Model/Client/TrackingNumber.php`. This
+mirrors the earlier `needsReturnLabel` / `returnAddressId` sets.
+
+**⚠ EO-1 is usually a cross-repo git BRANCH MISMATCH, not a DB gap.** An `EO-1` "no field called
+'X' in the model" with the DB column + `Core.RecordFields` both present means the field isn't in
+the generated model class the running `_underscore` is loading — most often because the repos are
+on **different branches** (`_underscore` on a branch whose generated `Model/Client/<Name>.php`
+predates the field the DB already has). **Fix:** put all the feature's repos (`_underscore`,
+`api2`, `dbchanges2`, `toga2-supply`) on the **same** feature branch before chasing migrations.
+On a local dev box with PHP opcache disabled, a branch switch takes effect immediately (files are
+read fresh per request) — no Apache restart needed. Concrete case: `TrackingNumbers.needsReturnLabel`
+(migrations `2026-07-02b` Client column + Core RecordField, `2026-07-02c` client AclFieldPermission)
+threw EO-1 purely because `_underscore` was on a branch whose generated `TrackingNumber.php` lacked
+the field.
 
 ## Checklist (so the chain is never half-built)
 
@@ -144,9 +165,18 @@ This mirrors the earlier `needsReturnLabel` / `returnAddressId` 3-file sets.
 - [ ] `AclLogicGroupExpressions` row binding the group to the expression.
 - [ ] `AclFieldPermissions` rows for every field that must be readable/writable.
 - [ ] For `aclDatabase = 'CLIENT'` records: rows go in client DB(s); resolve `roleId` by subselect.
+- [ ] The field is declared on the **generated** `_underscore/Model/Client/<Name>.php` (else `EO-1`),
+      and every repo is on the **same branch** so the generated model matches the DB.
 
 ## Change history
 
+- **2026-07-21** — TRUE-79191: promoted the writable-field recipe from **3-file** to **FOUR
+  requirements** — added the **generated model-class declaration** (`_underscore/Model/Client/<Name>.php`,
+  e.g. `public $needsReturnLabel = self::FIELD_BOOLEAN;`) as the 4th, whose absence returns **`EO-1`**
+  ("no field called 'X' in the '_Model_Client_Y' model"). Documented that EO-1 with a fully migrated DB
+  is usually a **cross-repo git branch mismatch** (`_underscore` on a branch whose generated model
+  predates the field) — fix is to align all fulfill/ship repos on one branch (opcache-disabled dev
+  picks up the switch immediately). Concrete: `TrackingNumbers.needsReturnLabel`. (mhammontree)
 - **2026-07-17** — TRUE-79191: added the **"add a writable field to a V2 record" 3-file migration**
   recipe (Core `RecordFields` → `EV-8` if missing; guarded Client column; Client `AclFieldPermissions`
   → `EV-9` if missing, cloned from a writable sibling like `containsBattery`), worked example

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

@@ -12,6 +12,6 @@
 | [TableView row-filtering via apiWhereClause (options.where grammar, end to end)](features/tableview-apiwhereclause-row-filtering.md) | `TableViews.apiWhereClause` (TEXT, nullable) is the sanctioned, code-free way to restrict or exclude rows from a 2.0 table view. | api2/Component/Api/V2/V2.php, _underscore/Model/Client/TableView.php, toga2-supply/src/api/toga.ts |
 | [TableView field/column metadata (TableViewFields, hidden projected columns)](features/tableview-field-metadata.md) | The columns of a 2.0 table view are defined by DB metadata, not code. | _underscore/Model/Client/TableView.php, api2/Component/Api/V2/V2.php, dbchanges2/Client/2026-07-20 - ItemsUuidForPurchaseOrderItemsTableView.sql |
 | [Tickets API (/v2/tickets)](features/tickets-api.md) | The generic ticket endpoint of the 2.0 REST API. | Component/Api/V2/V2.php |
-| [V2 API error/message codes (EV/EZ troubleshooting map)](features/v2-api-error-codes.md) | The V2 JSON engine (`Component/Api/V2/V2.php`) returns short **message codes** in the response `error` field, grouped by family: `EN-*` authentication, `EZ-*` a | api2/Component/Api/V2/V2.php |
+| [V2 API error/message codes (EV/EZ troubleshooting map)](features/v2-api-error-codes.md) | The V2 JSON engine (`Component/Api/V2/V2.php`) returns short **message codes** in the response `error` field, grouped by family: `EN-*` authentication, `EZ-*` a | api2/Component/Api/V2/V2.php, _underscore/Model/Client/TrackingNumber.php |
 | [AWS CodePipeline Deployment via CodeConnections (GitHub → Elastic Beanstalk)](workflows/codepipeline-codeconnections-deploy.md) | 2.0 apps (`api2`, `_underscore`) are deployed through **AWS CodePipeline**. |  |
 | [New Environment Configuration & Provisioning (api2)](workflows/environment-configuration-and-provisioning.md) | What it takes for a 2.0 API environment (e.g. | api2/Config/<environment>.ini, api2/Controller/Index.php, dbchanges2/Core/2026-06-16a - DatabaseHosts for new QA QC stage demo environments.sql, dbchanges2/Logs/, _underscore/Route.php |

package/knowledge/2.0/apps/api2/features/v2-api-error-codes.md

@@ -6,10 +6,11 @@ project: API
 client: shared
 type: feature
 status: active
-updated: 2026-07-17
+updated: 2026-07-21
 owners: [mhammontree]
 files:
   - api2/Component/Api/V2/V2.php
+  - _underscore/Model/Client/TrackingNumber.php
 related:
   - ../../_underscore/features/acl-permission-chain.md
   - scripted-api-post-body-args.md
@@ -33,6 +34,7 @@ migration instead of re-deriving it. All field/script ACL rows live in the **CLI
 | **EV-6** | Resource / route not found | A **scripted-API** route segment is being treated as a record uuid because no Record Script matches — i.e. the `Core.RecordScripts` route row is missing | Register the `Core.RecordScripts` row (`recordId`, `method`, `route`, `phpMethod`) |
 | **EV-8** | Request field does not exist | A field sent in the payload isn't registered as a **`Core.RecordFields`** row for that record | Register the field in `Core.RecordFields` (see the "add a field to a V2 record" recipe in the ACL doc) |
 | **EV-9** | No permission to write field | The field exists but the caller's role has no **`AclFieldPermissions`** grant (`isWritable=1`) in the CLIENT DB | Add the `AclFieldPermissions` row for the role (clone a writable sibling field's grant) |
+| **EO-1** | Operation failed — identifier "There is no field called 'X' in the '_Model_Client_Y' model" | The DB column **and** `Core.RecordFields` exist, but the **generated model class** `_underscore/Model/Client/<Name>.php` doesn't declare the field. This is the **4th** requirement beyond the 3-file migration — and most often it's a **cross-repo git branch mismatch** (`_underscore` on a branch whose generated model lacks a field the DB/RecordFields already carry) | Declare the field in the generated model class (`public $field = self::FIELD_*`) and put all related repos (`_underscore`, `api2`, `dbchanges2`, `toga2-supply`) on the **same** feature branch — see the ACL doc's writable-field recipe |
 | **EZ-1** | Unauthorized record/script dispatch | Missing **`AclRecordScripts`** (scripted APIs) or the **`AclRecordPermissions`** four-table chain (records) for the caller's role | Grant `AclRecordScripts` (scripts) or complete the record-CRUD chain |
 | **EV-5** | Duplicate `transactionId` | The globally-unique `transactionId` was reused | Send a fresh unique `transactionId` per request |
 | **EV-12** | Record's parent not synced | (Fulfill & Ship) POST `/item-fulfillments` when the Sales Order isn't synced into Toga yet | `GET /sales-orders/syncNetsuiteSalesOrder?netsuiteInternalSalesOrderId=<id>` first |
@@ -48,6 +50,13 @@ migration instead of re-deriving it. All field/script ACL rows live in the **CLI
 3. **EV-6 vs EZ-1** are the two halves of exposing a scripted API: EV-6 = no `Core.RecordScripts`
    route (the segment falls through to record lookup); EZ-1 = the route exists but there's no
    `AclRecordScripts` dispatch grant for the caller's role.
+4. **EO-1 ("no field called 'X' in the model") is NOT a DB problem.** EV-8 means the Core
+   `RecordFields` registration is missing; EO-1 means the DB column and RecordFields are both
+   present but the **generated PHP model class** lacks the field. Before touching migrations,
+   confirm every fulfill/ship repo is on the **same branch** — a mismatched `_underscore`
+   branch (whose generated `Model/Client/<Name>.php` predates the field) reproduces EO-1 with the
+   DB fully migrated. On a local dev box with PHP opcache disabled a branch switch takes effect
+   immediately (files are read fresh per request) — no Apache restart needed.
 
 ## Related recipes
 
@@ -62,5 +71,9 @@ migration instead of re-deriving it. All field/script ACL rows live in the **CLI
   discovered wiring the Signature Type field and the `addresses/validate` scripted route on Fulfill
   & Ship — each code mapped to the missing migration (RecordField / AclFieldPermissions /
   RecordScripts / AclRecordScripts) and the resolve-role-by-sibling technique. (mhammontree)
-</content>
-</invoke>
+- 2026-07-21 — TRUE-79191: added **EO-1** ("There is no field called 'X' in the '_Model_Client_Y'
+  model") to the map — the DB column + `Core.RecordFields` are present but the **generated model
+  class** `_underscore/Model/Client/<Name>.php` doesn't declare the field (the 4th requirement
+  beyond the 3-file migration), most often a **cross-repo git branch mismatch**; fix is to align
+  all fulfill/ship repos on one branch. Concrete: `TrackingNumbers.needsReturnLabel`. Also fixed
+  stray tag text at end of file. (mhammontree)

package/knowledge/2.0/apps/toga-blox/INDEX.md

@@ -9,3 +9,4 @@
 | [Primary Table templates (server/client, sizing, virtualization)](features/primary-table-templates.md) | `src/templates/PrimaryTable/` is the **production, wired-up table** built on the [Table component](table.md). | toga-blox/src/templates/PrimaryTable/PrimaryTable.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableServerTemplate.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableClientTemplate.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableHeaderCell.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableBodyCell.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableRow.tsx, toga-blox/src/templates/PrimaryTable/PrimaryTableExpandableRow.tsx, toga-blox/src/templates/PrimaryTable/types.ts |
 | [TableRecordModal (record-detail modal shell)](features/table-record-modal.md) | `TableRecordModal` is a **generic, presentational modal shell** for showing a single table record (row) in detail — typically opened from a table row click. | toga-blox/src/components/TableRecordModal/TableRecordModal.tsx, toga-blox/src/components/TableRecordModal/index.ts, toga-blox/src/components/TableRecordModal/tableRecordModal.module.css |
 | [Table component (cells, action cells, filters & sorts, hooks, theming)](features/table.md) | The `Table` component (`src/components/Table/`) is the **TanStack Table v8** building block behind the [Primary Table templates](primary-table-templates.md). | toga-blox/src/components/Table/index.ts, toga-blox/src/components/Table/types.ts, toga-blox/src/components/Table/utils/buildTanstackColumns.tsx, toga-blox/src/components/Table/utils/resolveCellType.tsx, toga-blox/src/components/Table/components/cellTypes, toga-blox/src/components/Table/components/actionCells, toga-blox/src/components/Table/components/columnFiltersAndSorts, toga-blox/src/components/Table/hooks, toga-blox/src/components/Table/themeConfig |
+| [Dynamic npm Publish Pipeline (branch → channel)](workflows/dynamic-publish-pipeline.md) | How `@agilant/toga-blox` (checkout folder `toga-blox-npm`, registry repo key `toga-blox`) publishes a per-environment npm **channel** (dist-tag) from a `_<mode> | toga-blox/.github/workflows/publish.yml, toga-blox/src/utils/getFontAwesomeIcon.tsx |

package/knowledge/2.0/apps/toga-blox/workflows/dynamic-publish-pipeline.md

@@ -0,0 +1,88 @@
+---
+title: Dynamic npm Publish Pipeline (branch → channel)
+framework: "2.0"
+repo: toga-blox
+project: TOGa Blox
+client: shared
+type: workflow
+status: active
+updated: 2026-07-21
+owners: [jcardinal]
+files:
+  - toga-blox/.github/workflows/publish.yml
+  - toga-blox/src/utils/getFontAwesomeIcon.tsx
+related:
+  - ../architecture.md
+  - ../../toga2-commerce/workflows/amplify-build-and-deploy.md
+---
+
+## What it is
+
+How `@agilant/toga-blox` (checkout folder `toga-blox-npm`, registry repo key `toga-blox`)
+publishes a per-environment npm **channel** (dist-tag) from a `_<mode>` release branch. As of
+2026-07-21 the `publish.yml` workflow is **fully dynamic** — there is no per-branch hardcoded
+logic. Use this doc when adding a new environment channel, debugging a channel that won't
+resolve in a consuming app's build, or touching `publish.yml`.
+
+## How it works
+
+### Branch → channel (1:1, load-bearing)
+
+- Trigger is `on.push.branches: ['_*']` — **any** underscore-prefixed branch publishes.
+- The npm dist-tag (channel) is derived by stripping the one leading underscore from the
+  branch name: pushing `_sandbox-client` publishes `@agilant/toga-blox@sandbox-client`.
+  Branch mode == channel, strictly one-to-one.
+- **Every** branch (including `_production`) publishes a **prerelease** version
+  `X.Y.Z-<mode>.<run>` under dist-tag `<mode>`. There is no longer a production special case.
+  Verified live: `production:1.0.315-production.96`, `sandbox-client:1.0.315-sandbox-client.97`.
+
+### What was removed (and why it's safe)
+
+- The old workflow hardcoded a branch list (`_production/_gamma/_beta/_qc-security`) with a
+  production special case: `_production` published dist-tag `latest` with a plain (non-prerelease)
+  version, committed the version bump back, and git-tagged. **All of that is gone.**
+- **Consequence:** the workflow no longer maintains the `@latest` npm tag. This is fine because
+  consumers never install bare `npm install @agilant/toga-blox`; they install by explicit
+  `@<mode>` channel (commerce's `amplify.yml`) or by a pinned/ranged version in `package.json`.
+
+### The cross-repo publish-then-build model (key mental model)
+
+A GitHub branch and an npm channel are **unrelated**. Creating a `_<mode>` branch in a *consuming
+app* repo (e.g. `toga2-commerce`) only tells Amplify what to build — it does **not** create a
+blox channel. A channel exists **only** when this repo (`toga-blox-npm`) publishes with
+`npm publish --tag <mode>`, which `publish.yml` now does automatically for any `_<mode>` branch.
+
+**Correct order to stand up a new environment:**
+1. Create + push `_<mode>` in `toga-blox-npm` → channel publishes. Verify with
+   `npm view @agilant/toga-blox dist-tags`.
+2. Then the app's `_<mode>` Amplify build succeeds, because `npm install @agilant/toga-blox@<mode>`
+   resolves.
+
+This publish-before-build ordering is the ongoing cost of the strict 1:1 model: every
+environment needs its own maintained `_<mode>` branch in `toga-blox-npm`.
+
+## Gotchas
+
+- **Publish before build.** `npm install @agilant/toga-blox@<mode>` fails `ETARGET No matching
+  version` in the app build until this repo has published that channel. GitHub Actions runs the
+  workflow version *on the pushed branch*, so the branch must carry the current `publish.yml`.
+- **FontAwesome v7 `style`-prop TS2322** (fixed 2026-07-21 in `getFontAwesomeIcon.tsx`, and a
+  reusable pattern for any consumer). FA v7 types the `FontAwesomeIcon` `style` prop as
+  `CSSProperties & CSSVariables`, where `CSSVariables` requires a `--fa-*` custom-property index
+  signature that plain `React.CSSProperties` lacks. Cast the passed style to
+  `React.CSSProperties & Record<\`--${string}\`, string>` — the value type must be `string`
+  (**not** `string | number`; `CSSVariables` requires `string`). Runtime and function signature
+  are unchanged, so it is safe for the ~40 consumers.
+- **Secret hygiene done right.** `publish.yml` writes a transient `.npmrc` at build time from
+  GitHub secrets (`${NODE_AUTH_TOKEN}` / FontAwesome token) — it never commits tokens. This is
+  the pattern the consuming apps should follow (see the commerce workflow's secret-hygiene note).
+
+## Change history
+- 2026-07-21 — Made `publish.yml` fully dynamic: trigger `_*`, branch→dist-tag by stripping the
+  leading underscore (mode == channel 1:1), every branch (incl. `_production`) publishes a
+  `X.Y.Z-<mode>.<run>` prerelease; removed the `_production`→`latest` special case (workflow no
+  longer maintains `@latest`); resolved a stash/merge conflict by keeping the dynamic path and
+  dropping the redundant hardcoded `_qc-security` case. Fixed `getFontAwesomeIcon.tsx` FA v7
+  TS2322. Documented the cross-repo publish-then-build model. (jcardinal)
+</content>
+</invoke>

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

@@ -6,7 +6,7 @@ project: TOGa Commerce
 client: shared
 type: workflow
 status: active
-updated: 2026-06-18
+updated: 2026-07-21
 owners: ["jcardinal"]
 files:
   - toga2-commerce/amplify.yml
@@ -15,50 +15,52 @@ files:
   - toga2-commerce/.github/workflows/sync-stage-environments.yml
 related:
   - ../../toga2-supply/workflows/amplify-build-and-deploy.md
+  - ../../toga-blox/workflows/dynamic-publish-pipeline.md
 ---
 
 ## Summary
 
 How `toga2-commerce` (React + Vite, "commerce2-react") builds and deploys on **AWS Amplify**.
-Same branch-per-environment model as `toga2-supply` (see related doc), with one important
-difference: commerce's build scripts **install a per-environment `@agilant/toga-blox` channel**
-before building, so the Amplify build must run the npm scripts (not a raw `vite build`), and the
-matching blox dist-tag must exist on npm first.
-
-## Deployment model — one branch per environment (mirrors toga2-supply)
-
-- Branches are **underscore-prefixed** (`_production`, `_beta`, `_gamma`, `_qc-security`); the
-  Vite mode is the same name **without** the underscore.
-- Repo-root `amplify.yml` drives every branch's build. It sets
-  `NODE_OPTIONS=--max-old-space-size=8192`, strips the leading `_` from `$AWS_BRANCH` to get the
-  mode, **fails loudly if `.env.<mode>` is missing**, then maps the mode → the matching npm build
-  script via a `case` (production→`npm run build`, alpha→`buildAlpha`, beta→`buildBeta`,
-  gamma→`buildGamma`, qc-security→`buildQcSecurity`; unmapped → `exit 1`). Single-line command, LF
-  only (`.gitattributes` pins `*.yml` to `eol=lf`).
+Same single-shared-`amplify.yml`, branch-per-environment model as `toga25-supply` (mode derived
+from `AWS_BRANCH`), but with commerce-specific build constraints preserved: it **dynamically
+installs a per-environment `@agilant/toga-blox` channel** (channel == mode, strict 1:1), needs a
+larger heap, and pulls FontAwesome Pro. As of 2026-07-21 the build is **inline and fully dynamic**
+(no per-branch `case`, no `npm run <script>`), so one DRY spec serves all ~21 environments.
+
+## Deployment model — one dynamic `amplify.yml` for every branch
+
+- Branches are **underscore-prefixed** `_<mode>`; the Vite mode is the same name **without** the
+  underscore, derived at build time from `$AWS_BRANCH`. **Fails loudly** if the branch lacks the
+  leading underscore or `.env.<mode>` is missing — a misconfigured branch can never silently ship
+  as production. Single-line commands, LF only (`.gitattributes` pins `*.yml` to `eol=lf`).
+- The build is **inline in `amplify.yml`**, NOT `npm run <script>`, so the per-mode `package.json`
+  build scripts are untouched. Steps: dynamic `npm install "@agilant/toga-blox@$MODE"
+  --legacy-peer-deps`, FontAwesome Pro install, `npm install` (not `npm ci`) `--legacy-peer-deps`,
+  `npx tsc -b` (tsconfig is composite / project references), then `npx vite build --mode "$MODE"`.
+  `node_modules` is cached.
+- **`NODE_OPTIONS="--max-old-space-size=8192"` must be re-exported in the `build` phase**, not
+  just `preBuild` — the memory-heavy Rollup step runs in `build`, and Amplify may use a separate
+  shell per phase, so the default heap OOMs otherwise.
 - `sync-stage-environments.yml` fans `_stage` → `_qc-security` on push.
 
 ## blox per-environment channel + the publish chain
 
-Unlike supply (which pins blox via a normal dependency), each commerce build script installs a
-**blox dist-tag** matching the environment:
-`"buildQcSecurity": "npm install @agilant/toga-blox@qc-security --legacy-peer-deps && tsc && vite build --mode qc-security"`.
+Unlike supply (which pins blox via a normal dependency), commerce installs a **blox dist-tag
+matching the mode**: `npm install "@agilant/toga-blox@$MODE" --legacy-peer-deps` — no hardcoded
+channel list, resolved from `$MODE` at build time.
 
-Those dist-tags are produced by the **`agilantsolutions/toga-blox-npm`** repo's
-`.github/workflows/publish.yml`, which auto-publishes on push to specific branches and maps
-**branch → dist-tag** (one-to-one, underscore stripped): `_production`→`latest`, `_beta`→`beta`,
-`_gamma`→`gamma`, and (added 2026-06-18) `_qc-security`→`qc-security`. So enabling a new channel
-is a two-part change: (1) add the branch + its `elif` case to `publish.yml`, push it onto that
-branch, and let it publish; (2) reference `@agilant/toga-blox@<channel>` in the app's build script.
+Those channels are produced by the **`toga-blox-npm`** repo's now-fully-dynamic
+`.github/workflows/publish.yml`, which publishes `@agilant/toga-blox@<mode>` for any pushed
+`_<mode>` branch (branch → dist-tag, underscore stripped, 1:1). See the
+[toga-blox dynamic publish pipeline](../../toga-blox/workflows/dynamic-publish-pipeline.md) for the
+full cross-repo publish-then-build model. **The channel must exist before the app build runs.**
 
-## Steps (to stand up a new environment, e.g. QC Security)
+## Steps (to stand up a new environment)
 
-1. In `toga-blox-npm`: add the branch to `on.push.branches` and an `elif` case (version suffix +
-   `DIST_TAG`) in `publish.yml`; create the publish branch **from** a branch that has the updated
-   workflow (e.g. `_qc-security` from `_production`); push → it publishes `@agilant/toga-blox@qc-security`.
-   Verify: `npm dist-tag ls @agilant/toga-blox`.
-2. In `toga2-commerce`: add a `build<Env>` script (blox `@<channel>` install + `--legacy-peer-deps`
-   + `tsc` + `vite build --mode <mode>`); add the `case` arm in `amplify.yml`; commit `.env.<mode>`.
-3. Connect the Amplify branch; push; watch for the `Branch '...' -> Vite mode '...'` echo.
+1. In `toga-blox-npm`: create + push `_<mode>` → `publish.yml` publishes `@agilant/toga-blox@<mode>`
+   automatically. Verify: `npm view @agilant/toga-blox dist-tags`.
+2. In `toga2-commerce`: commit `.env.<mode>` (public base URLs only, no secrets).
+3. Connect the Amplify branch `_<mode>`; push; the inline spec derives the mode and builds.
 
 ## Systems involved
 
@@ -83,12 +85,22 @@ branch, and let it publish; (2) reference `@agilant/toga-blox@<channel>` in the
   peers: `@tanstack/react-table@^8`, `react-table@^7.8.0`, `react-table-sticky@^1.1.3`. Check
   `npm view @agilant/toga-blox@<tag> peerDependencies` against commerce deps when a resolve error
   appears.
-- **Secret hygiene:** commerce's committed `.npmrc` has historically held live FontAwesome + npm
-  publish tokens. Rotate and untrack — keep tokens in env vars (`${NODE_AUTH_TOKEN}` /
-  `${FONTAWESOME_NPM_TOKEN}`) as the blox `publish.yml` does.
+- **Secret hygiene (open remediation):** `toga2-commerce/.npmrc` is **git-tracked** — it is listed
+  in `.gitignore` but was committed before that, so git still tracks it, and it holds a live
+  FontAwesome registry token and a live npm auth token in plaintext. Remediation: (1) **rotate both
+  tokens** (treat as compromised); (2) `git rm --cached .npmrc`; (3) move the tokens to Amplify
+  environment variables and write a **transient `.npmrc` at build time** from
+  `$FONTAWESOME_NPM_AUTH_TOKEN` — exactly what blox's `publish.yml` already does. Never document the
+  token values.
 
 ## Change history
 
+- 2026-07-21 — Reworked `amplify.yml` to a **fully dynamic inline build** (no per-branch `case`, no
+  `npm run <script>`): derive mode from `$AWS_BRANCH`, dynamic `npm install
+  "@agilant/toga-blox@$MODE"`, `npx tsc -b` (composite), `npx vite build --mode "$MODE"`. Re-export
+  `NODE_OPTIONS=--max-old-space-size=8192` in the **build** phase (Rollup OOM). Publish chain now
+  dynamic (any `_<mode>` branch in toga-blox-npm). Flagged the git-tracked `.npmrc` live-token issue
+  with rotate/untrack/transient-`.npmrc` remediation. (jcardinal)
 - 2026-06-18 — Initial Amplify setup: added `amplify.yml` (8192 heap, underscore-strip, fail-loud,
   case→npm script), `.gitattributes` (LF), `sync-stage-environments.yml`; added `buildQcSecurity`
   with `@qc-security` blox channel + `--legacy-peer-deps` (and same flag on alpha/beta/gamma);

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

@@ -3,5 +3,5 @@
 | Doc | Summary | Files |
 |-----|---------|-------|
 | [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/components/ui/BaseInput/UnitSelect.tsx, toga2-supply/src/pages/EditShipment/view/modals/SerialNumbersModal.tsx, 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/view/components/SelectedShipmentItemsTable.tsx, toga2-supply/src/pages/EditShipment/view/helpers/ShipmentDetailsForm/renderEditShipmentFormInput.tsx, toga2-supply/src/pages/EditShipment/viewModel/FIELDS/DUMMYUPDATESHIPMENTFIELDS.json, toga2-supply/src/pages/EditShipment/helpers/ShipmentDetailsForm/renderEditShipmentFormInput.tsx, toga2-supply/tailwind.config.cjs, toga2-supply/src/pages/EditShipment/view/modals/ReturnShippingModal.tsx, toga2-supply/src/styles/index.scss, toga2-supply/src/components/ui/BaseInput/BaseInput.tsx, toga2-supply/src/pages/EditShipment/api/UpdateShipmentApi.ts, toga2-supply/src/pages/EditShipment/viewModel/signatureTypes.ts, toga2-supply/src/pages/EditShipment/view/modals/SelectReturnAddressModal.tsx, toga2-supply/src/pages/EditShipment/helpers/ShipmentDetailsForm/formatShipmentData.ts, toga2-supply/src/pages/EditShipment/types.ts, toga2-supply/src/pages/Shipments/view/ShipmentsPage.tsx, toga2-supply/src/pages/Shipments/view/components/ShipmentsCardTableForm/ShipmentsCardTableForm.tsx, toga2-supply/src/pages/Shipments/api/ShipmentsApi.ts, toga2-supply/src/pages/Shipments/types.ts, toga2-supply/src/pages/FulfilledShipments/view/FulfilledShipmentsPage.tsx, toga2-supply/src/components/ui/CardTable/CardTable.tsx, toga2-supply/src/components/ui/CardTable/types.ts, toga2-supply/src/assets/pen-line.svg, _underscore/Model/Client/ItemFulfillment.php, _underscore/Trait/Netsuite/ItemFulfillment.php, _underscore/Component/Library/Carriers/Ups/Ups.php |
+| [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/components/ui/Tables/BasicTable/BasicTable.tsx, toga2-supply/src/pages/ShipmentItems/view/forms/ShipmentItemsTable.tsx, toga2-supply/src/pages/EditShipment/view/components/forms/EditShipmentForm.tsx, toga2-supply/src/components/ui/BaseInput/UnitSelect.tsx, toga2-supply/src/pages/EditShipment/view/modals/SerialNumbersModal.tsx, 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/view/components/SelectedShipmentItemsTable.tsx, toga2-supply/src/pages/EditShipment/view/helpers/ShipmentDetailsForm/renderEditShipmentFormInput.tsx, toga2-supply/src/pages/EditShipment/viewModel/FIELDS/DUMMYUPDATESHIPMENTFIELDS.json, toga2-supply/src/pages/EditShipment/helpers/ShipmentDetailsForm/renderEditShipmentFormInput.tsx, toga2-supply/tailwind.config.cjs, toga2-supply/src/pages/EditShipment/view/modals/ReturnShippingModal.tsx, toga2-supply/src/styles/index.scss, toga2-supply/src/components/ui/BaseInput/BaseInput.tsx, toga2-supply/src/pages/EditShipment/api/UpdateShipmentApi.ts, toga2-supply/src/pages/EditShipment/viewModel/signatureTypes.ts, toga2-supply/src/pages/EditShipment/view/modals/SelectReturnAddressModal.tsx, toga2-supply/src/pages/EditShipment/helpers/ShipmentDetailsForm/formatShipmentData.ts, toga2-supply/src/pages/EditShipment/types.ts, toga2-supply/src/pages/Shipments/view/ShipmentsPage.tsx, toga2-supply/src/pages/Shipments/view/components/ShipmentsCardTableForm/ShipmentsCardTableForm.tsx, toga2-supply/src/pages/Shipments/api/ShipmentsApi.ts, toga2-supply/src/pages/Shipments/types.ts, toga2-supply/src/pages/FulfilledShipments/view/FulfilledShipmentsPage.tsx, toga2-supply/src/components/ui/CardTable/CardTable.tsx, toga2-supply/src/components/ui/CardTable/types.ts, toga2-supply/src/assets/pen-line.svg, _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/.gitattributes, toga2-supply/.github/workflows/sync-stage-environments.yml, toga2-supply/.env.qc-security |

package/knowledge/2.0/apps/toga2-supply/features/fulfill-and-ship.md

@@ -6,9 +6,12 @@ project: TOGa Supply
 client: shared
 type: feature
 status: active
-updated: 2026-07-17
+updated: 2026-07-21
 owners: [mhammontree]
 files:
+  - toga2-supply/src/components/ui/Tables/BasicTable/BasicTable.tsx
+  - toga2-supply/src/pages/ShipmentItems/view/forms/ShipmentItemsTable.tsx
+  - toga2-supply/src/pages/EditShipment/view/components/forms/EditShipmentForm.tsx
   - toga2-supply/src/components/ui/BaseInput/UnitSelect.tsx
   - toga2-supply/src/pages/EditShipment/view/modals/SerialNumbersModal.tsx
   - toga2-supply/src/pages/ShipmentItems/view/ShipmentItemsPage.tsx
@@ -123,6 +126,10 @@ success/failure.
   `shipToAddressUuid` / `returnAddressUuid`.
 - **Decision:** a confirmation dialog was added even though the Pending-card trash deletes
   **without** one, because this is a large, explicit, destructive button.
+- **Destructive-red confirm button (2026-07-21).** `SupplyFormGuardrail` defaults
+  `rightButtonClasses` to the primary blue (`#3F5DCA`). The delete-shipment confirm passes a
+  **crimson-700 (`#D60027`)** destructive style to signal the permanent-delete impact. Crimson-700 is
+  the app's destructive red; there is **no** crimson-800 token, so the hover uses a darker hex directly.
 
 ## Update Info / Edit Shipment form (config-driven; Figma-alignment pass 2026-07)
 
@@ -216,6 +223,22 @@ bare string** — see the gotcha below before wiring a new select field.
 12px check glyph. This is the **shared** checkbox, so the change applies **app-wide**, not just to
 the shipment forms — audit other consumers when touching it.
 
+### Mint-green "dirty field" border on the fulfill/ship forms (2026-07-21, Figma node 3554-5206)
+
+A field changed from its saved value shows a **mint-600 (`#2CB224`) border**; it clears on save
+(Update Info navigates away, the return modal closes). Implemented in `BaseInput.tsx` +
+`renderEditShipmentFormInput.tsx`:
+- **Opt-in only.** The mint styling is gated behind the existing **`hasDirtyValidation`** prop, so it
+  activates only on forms that pass it (enabled here via `renderEditShipmentFormInput`) — no app-wide
+  spread onto every `BaseInput`.
+- **Dirty detection keys off `input.valueKey`.** `mint-600` = `#2CB224` in `tailwind.config.cjs`,
+  matching the Figma token.
+- **⚠ `dirtyFields` lookup must use the field's real key.** `BaseInput`'s dirty check was looking up
+  `dirtyFields["undefined.message"]` (always `undefined`) for uuid-less fields, so **no** field ever
+  showed the mint border. Fix: key `isFieldDirty` off `input.valueKey`. Also — programmatic `setValue`
+  for a user-meaningful prefill (e.g. the warehouse-address prefill) must pass `{ shouldDirty: true }`
+  or RHF reports the field clean and the border never appears (see the RHF `isDirty` gotcha below).
+
 ## Signature Type — 4-level enum (2026-07)
 
 Signature moved from a **boolean `requiresSignature`** to a **4-level `signatureType` enum**:
@@ -472,6 +495,37 @@ the call 403s and returns no label.
   remove/relabel the nav link; (B) add a global "All Pending Shipments" view — drop the SO filter
   (client scoping is automatic from the JWT), but each row must then carry its own SO `internalId`
   for the edit/fulfill links.
+- **⚠ `BasicTable` headers misalign from their column values unless you pass a HORIZONTAL
+  `headerCellPadding` (recurring).** `BasicTable` renders through daisyUI's `table` class, whose base
+  `:where(th,td)` applies ~16px horizontal cell padding. Body cells override it with
+  `cellPadding="px-2"` (8px), but headers by default override only the **vertical** padding — so header
+  text sits 8px off from the column values (and the select-all checkbox misaligns with the row
+  checkboxes). **Always pass a horizontal `headerCellPadding` (e.g. `"px-2 py-3"`) that matches
+  `cellPadding`.** Two related items fixed alongside: (1) a **sticky** header showed a doubled seam
+  before scroll (a real CSS `border` **plus** a box-shadow) — use a **box-shadow-only** seam for sticky
+  headers and add a left inset seam for the first column; column dividers `2px`→`1px` to match Figma;
+  (2) a cell that **double-pads** (e.g. a serial cell carrying its own `px-2`) must drop the extra
+  padding so it aligns at the same 8px gutter. Files: `components/ui/Tables/BasicTable/BasicTable.tsx`,
+  `ShipmentItems/view/forms/ShipmentItemsTable.tsx`, `EditShipment/view/components/SelectedShipmentItemsTable.tsx`.
+- **⚠ React Hook Form `formState.isDirty` read ONLY inside an event handler is stale (`false`).**
+  `formState` is a **Proxy** that subscribes to a key only if you **read it during render**. Reading
+  `formState.isDirty` exclusively inside a handler (e.g. a modal close/backdrop handler) returns a
+  stale `false`, so a backdrop click closed the return modal without the save/discard guardrail firing.
+  **Fix: destructure/read `isDirty` during render** and use that value in the handler. Corollary: a
+  programmatic `setValue` for a user-meaningful prefill must pass `{ shouldDirty: true }` or the form
+  still reads "clean" (also affects the mint dirty-border above). File:
+  `EditShipment/view/modals/ReturnShippingModal.tsx`.
+- **⚠ api2 V2 field SELECTORS are dot-paths of REAL DB column names — a wrong name silently returns
+  nothing.** V2 responses select fields by dot-path (e.g.
+  `"itemFulfillmentItems.salesOrderItem.item.skuNumber"`). The real `Items` columns are **`skuNumber`
+  / `upcCode`**; requesting `item.sku` / `item.upc` (which don't exist) returns **no value, no error**
+  — the field just comes back empty. (Manufacturer worked only because `manufacturer.name` is the
+  correct relation name.) When a field renders blank, verify the selector matches the actual DB column,
+  not a guessed alias, and keep the name consistent across the API request, the response mapping, the
+  component read, and the TS types. Concrete fix (SKU/UPC not displaying): standardized on
+  `skuNumber`/`upcCode` across `EditShipment/api/UpdateShipmentApi.ts`,
+  `view/components/forms/EditShipmentForm.tsx`, `SelectedShipmentItemsTable.tsx`, `types.ts`, and
+  `ShipmentItems/view/forms/ShipmentItemsTable.tsx` + `types.ts`.
 
 ## Remaining work
 
@@ -534,6 +588,16 @@ not the base `_Model_Client_ItemFulfillment`. Tested with GroWrk; UPS support wa
 for Compass and is not yet in prod.
 
 ## Change history
+- 2026-07-21 — TRUE-79191 (toga2-supply UI fixes + Figma polish): documented three durable, reusable
+  gotchas — (1) **`BasicTable` header/value misalignment** (daisyUI base `:where(th,td)` ~16px padding;
+  always pass a horizontal `headerCellPadding` matching `cellPadding`, box-shadow-only seam for sticky
+  headers, drop double-padding on self-padded cells); (2) **RHF `formState.isDirty` is stale when read
+  only inside an event handler** (Proxy subscribes on render-time reads only) — read it during render;
+  `setValue` prefills need `{ shouldDirty: true }`; (3) **api2 V2 field selectors are dot-paths of real
+  DB column names** — `item.sku`/`item.upc` silently returned nothing; the real columns are
+  `skuNumber`/`upcCode`. Built the **mint-600 (#2CB224) dirty-field border** (opt-in via
+  `hasDirtyValidation`; fixed the `dirtyFields["undefined.message"]` bug by keying off `input.valueKey`)
+  and gave the **Delete Shipment** confirm a crimson-700 (#D60027) destructive button. (mhammontree)
 - 2026-07-17 — TRUE-79191 (David design-review pass, toga2-supply UI): documented four durable,
   app-wide component gotchas — (1) **`BaseInput` react-select menus now portal to `<body>`**
   (`menuPortalTarget` + `menuPortal zIndex 9999`) so a sibling scroll box can't clip them, and the

package/knowledge/2.0/standards/frontend-deploy.md

@@ -5,10 +5,11 @@ project: _Underscore
 client: shared
 type: standard
 status: active
-updated: 2026-07-17
+updated: 2026-07-21
 owners: [jcardinal]
 related:
   - ../apps/toga25-supply/workflows/amplify-deployment.md
+  - ../apps/toga-blox/workflows/dynamic-publish-pipeline.md
 ---
 
 ## Scope
@@ -34,3 +35,25 @@ Applies to all 2.0 Vite + React/TS frontends deployed on AWS Amplify.
 
 ## Node
 - Vite 7 requires Node 20.19+ or 22.12+ (Node 22 recommended). Pin via `.nvmrc` if needed.
+
+## Per-environment library channel (optional; when an app installs a versioned shared lib)
+
+Some 2.0 frontends install a **per-environment channel** of a shared npm library instead of a
+single pinned version (e.g. `toga2-commerce` installs `@agilant/toga-blox@$MODE`, channel == mode,
+strict 1:1). When an app does this:
+
+- The library's own release repo must publish the channel **before** the app build runs — a
+  `_<mode>` branch in the *app* repo only tells Amplify what to build; it does not create a
+  channel. Install-by-channel fails `ETARGET No matching version` until the library has published.
+  See `../apps/toga-blox/workflows/dynamic-publish-pipeline.md`.
+- Install the channel dynamically from the derived mode (`npm install "@lib@$MODE"`), not from a
+  hardcoded per-branch list, so one `amplify.yml` serves every environment.
+- `--legacy-peer-deps` may be required when the app's and library's peer ranges diverge; when it
+  is used, npm will not auto-install the library's peers, so any peer not already in the app's
+  dependencies must be added explicitly.
+
+## Build memory / heap
+
+For memory-heavy Rollup builds, set `NODE_OPTIONS=--max-old-space-size=<MB>` and **re-export it in
+the `build` phase**, not only `preBuild` — Amplify may use a separate shell per phase, so a
+preBuild-only export leaves the Rollup step on the default heap and it OOMs.

package/knowledge/INDEX.md

@@ -30,7 +30,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **ai-bdr** (AI-BDR) — 8 doc(s) → [2.0/apps/ai-bdr/INDEX.md](2.0/apps/ai-bdr/INDEX.md)
 - **toga2-commerce** (TOGa Commerce) — 9 doc(s) → [2.0/apps/toga2-commerce/INDEX.md](2.0/apps/toga2-commerce/INDEX.md)
 - **toga25-supply** (TOGa 2.5 Supply) — 10 doc(s) → [2.0/apps/toga25-supply/INDEX.md](2.0/apps/toga25-supply/INDEX.md)
-- **toga-blox** (TOGa Blox) — 7 doc(s) → [2.0/apps/toga-blox/INDEX.md](2.0/apps/toga-blox/INDEX.md)
+- **toga-blox** (TOGa Blox) — 8 doc(s) → [2.0/apps/toga-blox/INDEX.md](2.0/apps/toga-blox/INDEX.md)
 - **bdr** (BDR) — 0 doc(s) → [2.0/apps/bdr/INDEX.md](2.0/apps/bdr/INDEX.md)
 
 ## standalone framework

package/package.json

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