toga-ai 1.0.1069 → 1.0.1071

package/knowledge/2.0/apps/_underscore/features/calculated-column-filter-options.md

@@ -6,11 +6,13 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-09-18
-owners: [apeterson]
+updated: 2026-10-17
+owners: [apeterson, jcardinal]
 files:
   - _underscore/Model/Client/TableView.php
   - _underscore/Model/Compass/SalesOrder.php
+  - _underscore/Model/Client/Certification.php
+  - _underscore/Model/Client/UserCertification.php
   - _underscore/Model.php
 related:
   - sales-order-status-filter-surface.md
@@ -34,7 +36,10 @@ Before this, `filterOptions` in table meta was filled in **only** for `TYPE__STA
 column whose options are **live data** (e.g. the list of active Admin users): seeding a surface
 element per user would go stale constantly.
 
-First and only consumer today: the Compass **Assigned Admin** column on the sales-orders table.
+Consumers: Compass **Assigned Admin** (live data, below); `_Model_Client_Certification::_complianceStateFilterOptions()`
+and `_Model_Client_UserCertification::_statusFilterOptions()` (fixed enum list: loop the model's
+state constant, `slug` = `name` = the value; the front end labels it from language data). Use the
+enum shape for any status-like calc column.
 
 ## How it works
 
@@ -56,7 +61,7 @@ an empty dropdown. Same contract as `getStatusFilterOptions()`.
 throws when a `FIELD_SQL` field has no static of the same name — that is why `_assignedAdmin()`
 exists. The seam just adds a `FilterOptions` suffix to the same name-derived rule.
 
-It is a **no-op for every existing column**: nothing else declares a `<field>FilterOptions` static.
+It is a **no-op** for any column whose model declares no `<field>FilterOptions` static.
 
 ### The Compass example
 
@@ -161,10 +166,11 @@ generic version at roughly **4–5** such columns, driven by real examples.
   the same pattern `_assignedManager()` already uses.
 - **Matching a role by its human-readable `name` is fragile** (flagged by `sql-reviewer`): a client
   renaming the `Admin` role silently empties the list. A stable role id would be sturdier.
-- **⚠ Filtering a calculated column lands in HAVING, not WHERE.**
-  `api2/Component/Api/V2/V2.php` `splitWhereExpressionsIntoWhereHaving` routes a where on a
-  calculated field into `HAVING`, so the `_assignedAdmin` correlated subquery is evaluated for every
-  row surviving the WHERE, **before LIMIT** — and again for the pagination count query. On a large
+- **⚠ Filter with the BARE calc name** (`_complianceState:eq:AT_RISK`) — it is inlined into
+  `WHERE`. The table-prefixed form (`Table._x`) goes to `HAVING` and returns 500 / `EO-1`. Mechanism:
+  [V2 REST query contract](../../api2/features/v2-rest-query-contract.md). Either way the expression
+  (here the `_assignedAdmin` correlated subquery) is evaluated **per row, before LIMIT** — and again
+  for the pagination count query. On a large
   Compass `SalesOrders` table this can be slow, and it will not fail loudly (api2's Apache gateway
   timeout is 1800s). This is pre-existing behaviour of filtering **any** calculated column, not new
   here, and it was **not** measured with `EXPLAIN` at production size. The cheaper target would be

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

@@ -17,6 +17,7 @@
 | [Record Scripts (computed/aggregate /v2 endpoints — the authoring contract)](features/record-scripts.md) | The authoring contract for a Record Script — a `public static` model method that becomes a read-only computed/aggregate `/v2` endpoint (double-nested envelope, |
 | [V2 Request Logging & Where Requests Land (client vs core log DB)](features/request-logging.md) | Where each V2 request lands (client vs core/writer Logs), when it leaves no row at all (PRE-interceptor throw, uncaught fatal), the apiproxy-retry / duplicate-t |
 | [POST + JSON-body args for scripted APIs](features/scripted-api-post-body-args.md) | How the V2 engine runs a Record Script for a POST and lets scripted args arrive in the JSON body (to avoid HTTP 414 on large values); open when a scripted API n |
+| [Session currency (audience.currency + JWT id.currency)](features/session-currency.md) | How api2 resolves the user's currency once per session and returns it as `audience.currency` (ISO code or null) and JWT `id.currency`; open when a front end nee |
 | [TOGa Talos Sprint Dashboard API (Record Scripts)](features/sprint-dashboard-api.md) | The six api2 Record Scripts on `_Model_Team_Sprint` that serve the internal TOGa Talos sprint dashboard from the `Team` schema; open when consuming/registering |
 | [Surface action-state via the surface=<slug> request option (M2M-safe)](features/surface-meta-option.md) | The opt-in `surface=<slug>` GET option that attaches per-record UI action state under `meta.surface` (never `data`); open when wiring the Surface layer to a scr |
 | [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. |

package/knowledge/2.0/apps/api2/features/language-translation-layer.md

@@ -6,7 +6,7 @@ project: API
 client: shared
 type: feature
 status: active
-updated: 2026-10-09
+updated: 2026-10-17
 owners: ["jcardinal", "bala"]
 files:
   - api2/Component/Api/V2/V2.php
@@ -102,7 +102,7 @@ Placement is load-bearing: the `id.language` mutation happens **after** client-D
 - **Per-row cost on translatable-join lists (site 5).** `getTranslatedFieldValue` dereferences the source model key via `_Model __get`, forcing a full row load, so ~2 queries per row (source + sidecar) for non-English translatable-join lists — consistent with the feature's per-row-load tradeoff. Candidate future optimization: let the helper accept a known id instead of a live `_Model`.
 - **Pre-existing (not introduced by site 5): `join=`/`ojoin=` identifiers are unvalidated.** Table/alias/ON-clause identifiers flow from the query string into SQL with no validation/escaping (`V2.php` ~L3416-3463, `parseOptionsJoin` ~L7874-7920). The new PK-select line reuses the same already-tainted `$tableAlias` as the adjacent pre-existing lines, so it adds no new injection class — but the underlying tainted-identifier path is a standing concern flagged for separate follow-up.
 - Reading a possibly-absent magic field off a generic `_Model` needs `array_key_exists(...)` + `__get` — `isset()`/`?? null` always read false/null. See [_Model magic-field access](../../_underscore/features/model-magic-field-access.md); this was the cause of the uuid not appearing in the fallback warning.
-- **Refresh re-resolution is user-token-only.** If you extend the JWT with new audience-shaped claims, remember the refresh path rebuilds context from the *existing* token (uuid/app-uuid/personas) — it does not re-read anything the token doesn't carry.
+- **Refresh re-resolution is user-token-only.** `audience.currency` reuses this cascade + refresh path — see [Session currency](./session-currency.md). If you extend the JWT with new audience-shaped claims, remember the refresh path rebuilds context from the *existing* token (uuid/app-uuid/personas) — it does not re-read anything the token doesn't carry.
 - Migrations not yet executed at time of writing; needs live verification.
 
 ## Related

package/knowledge/2.0/apps/api2/features/session-currency.md

@@ -0,0 +1,62 @@
+---
+title: Session currency (audience.currency + JWT id.currency)
+framework: "2.0"
+repo: api2
+project: API
+client: shared
+type: feature
+status: active
+updated: 2026-10-17
+owners: ["jcardinal"]
+files:
+  - api2/Component/Api/V2/V2.php
+  - api2/Component/Api/V2/Response/Response.php
+  - _underscore/Model/Client/Currency.php
+  - _underscore/Model/Client/UserGlobalSetting.php
+  - _underscore/Model/Client/ItemPrice.php
+  - dbchanges2/Core/2026-10-02a - PriceDefaultCurrency.sql
+  - dbchanges2/Client/2026-10-02a - AllClients PriceCurrency.sql
+related:
+  - ./language-translation-layer.md
+  - ../../toga25-blox/features/money-formatting.md
+  - ../../../../clients/quad/features/multi-currency-item-pricing.md
+---
+How api2 resolves the user's currency once per session and returns it as `audience.currency` (ISO code or null) and JWT `id.currency`; open when a front end needs the session currency, a currency setting is ignored, or WZ-5 appears.
+
+## Summary
+
+Every authenticated api2 response carries `audience.currency` — a 3-letter ISO code (`USD`) or `null`. The same value is in the JWT `id.currency` claim. It is resolved at sign-in and on `/auth/refresh`, exactly like `audience.language` (one value per session, no per-request cost). Front ends format money with it through blox — see [money formatting](../../toga25-blox/features/money-formatting.md). Uniform across clients.
+
+## How it works
+
+**Cascade.** Settings slug `currency` (`Core.Settings` id 14, uuid `daa25a05-c1c7-4dcc-6a7c-c79a3c02b92a`; `Core.DefaultGlobalSettings` value `USD`, seeded by `dbchanges2/Core/2026-10-02a - PriceDefaultCurrency.sql`, present in prod Core — verified 2026-10-17). Walked by the same `resolveSettingValue()` 8-layer cascade as language (DefaultGlobal → … → UserApp, `isOverridable = 0` locks, first persona wins) — see [Language Translation Layer → Language resolution](./language-translation-layer.md#how-it-works).
+
+**Two stored shapes — both valid, storage left as-is.**
+- Core default = ISO code (`USD`).
+- Client / persona / user rows = a Client `Currencies.uuid`. Commerce and Quad read that uuid (`_underscore` `UserGlobalSetting` / `ItemPrice` treat the value uuid-first, then code) — do not convert stored rows to codes.
+
+**Validation (V2.php).**
+1. Value looks like a uuid → load `_Model_Client_Currency` by uuid on the user's **own client connection** and return `Currencies.code`. Never a Core↔Client join (separate clusters).
+2. Otherwise accept only `^[A-Z]{3}$`.
+3. `''` = not set (next layer wins).
+4. Unusable value → re-resolve with client-level layers only (default + client, no persona/user); still nothing → `null` + warning **WZ-5** (`Response.php`, `{currency}` placeholder, value cut to 64 chars). Never fails the sign-in or refresh.
+
+**Token paths.**
+- Sign-in: resolved, put in `id.currency`, echoed as `audience.currency`.
+- `/auth/refresh` (user tokens only): re-resolved like language, so a change shows on the next refresh.
+- View-as: keeps the delegator's validated currency. A delegator token from before this change (no `currency` key) resolves normally.
+- API-key auth: `null`.
+
+## Gotchas
+
+- `Client_Quad` has a `ClientGlobalSettings` currency row with value `''` — counts as not set, falls through to the Core `USD` default.
+- Local `Client_True` / `Client_Elite` `Currencies` tables are empty, so a uuid-valued setting resolves to null + WZ-5 locally. Prod has USD via `dbchanges2/Client/2026-10-02a - AllClients PriceCurrency.sql`. That file has one-time schema steps — do not re-run the whole file locally; insert the row by hand.
+- Changing a user's currency (UI, `isOverridable` fan-out, own-row ACL write guard) is not built yet — later ticket. Mirror the language write guard in [API Payload Interceptors](./api-payload-interceptors.md#own-row-guards-in-a-pre-interceptor) when it is.
+
+## Related
+
+- [Language Translation Layer](./language-translation-layer.md) — the shared cascade + refresh mechanics.
+- [Money formatting (toga25-blox)](../../toga25-blox/features/money-formatting.md) — the front-end consumer.
+
+## Change history
+- 2026-10-17 — Added `audience.currency` / `id.currency`, resolved at sign-in + refresh; uuid → code on the client connection; WZ-5 fallback. Proven by a real local sign-in + refresh. TRUE-82878 (jcardinal)

package/knowledge/2.0/apps/api2/features/tableview-field-metadata.md

@@ -6,7 +6,7 @@ project: API
 client: shared
 type: feature
 status: active
-updated: 2026-10-15
+updated: 2026-10-17
 owners: [apeterson, bala, jcardinal]
 files:
   - _underscore/Model/Client/TableView.php
@@ -140,6 +140,7 @@ So the visible failure is a broken SQL query while the actual defect is one miss
 - **Flag columns are NULLable** — guard flag migrations with `COALESCE(col, 0) = 0`, never `col = 0`, or the UPDATE matches 0 rows and looks like caching.
 - **`type`/`precision` are canonical (Core-wide), not per-view.** Editing `Core.RecordFields` changes every view/client that shows the field; there is no per-view type override. `isCopyable`, `isSortable`, `isFilterable`, `isGroupable`, `isVisible` are the per-view knobs (on `TableViewFields`).
 - **`TableView::meta()` contains a hand-written `SELECT` that names `TableViewFields` columns explicitly.** So a new column on that table is required by **two** mechanisms — the model property *and* that query — and a grep for the property alone under-reports what a missing column breaks.
+- **⚠ Type `SELECT` only on a JOINED FK column.** `meta()`'s `TYPE__SELECT` branch reads `$tableViewJoins[$tableAlias]->record` (`TableView.php` ~L265-272); a main-table column has no join alias, so it breaks at runtime. For an enum column on the main table, expose a calc label field (e.g. `_status`) with a `<field>FilterOptions` static — see [calculated-column filter options](../../_underscore/features/calculated-column-filter-options.md).
 - **`isGroupable` has no migration** — omit it from new TableView migrations (fails on prod/beta) until the fan-out migration lands. Composite unique keys read as unconstrained in `information_schema.COLUMNS`; use `information_schema.STATISTICS` / `SHOW INDEX`.
 
 ## Related
@@ -151,4 +152,5 @@ So the visible failure is a broken SQL query while the actual defect is one miss
 - [TableView joins](../../_underscore/features/tableview-joins.md)
 
 ## Change history
+- 2026-10-17 — `SELECT` type is safe only on a joined FK column; main-table enum → calc label + FilterOptions. (jcardinal)
 - 2026-09-23 — Recorded that `Core.RecordFields.type` drives display/filter only and never sorting; that `NUMBER` on a text column blanks non-numeric rows (Compass `kit 205-207` bundles) while `BOOLEAN` fixes genuinely blank flag columns; and that the flag columns are NULLable so a `= 0` migration guard matches nothing. (apeterson)

package/knowledge/2.0/apps/api2/features/v2-rest-query-contract.md

@@ -56,6 +56,10 @@ controller.
   (`V2.php` ~L3673–3682). **Prefer bare for ascending:** the query string is parsed *without*
   urldecoding (see Encoding rules), so a client that percent-encodes the `+` as `%2B` sends a
   field literally named `%2Bfield` and the sort is silently dropped. Bare has no such failure mode.
+- **Multi-sort = comma list** (`sort=-dateIssued,uuid`; `parseOptionsSort` ~L10888 explodes on `,`;
+  a blox `sort: [...]` array is sent comma-joined). **Offset paging (`page`) is only stable with a
+  unique last key** — add `uuid` as the tie-breaker, or rows with equal sort values shuffle between
+  pages.
 - **A LIST select is `SELECT SQL_CALC_FOUND_ROWS DISTINCT <table>.<primaryKey>`** (`V2.php:3884`;
   the aggregate-fields path is the one exception). Two consequences: (a) join fan-out collapses to
   one row per record, so **duplicate child rows are invisible in the response** — a duplicate join
@@ -382,9 +386,10 @@ Mechanism, read from `api2/Component/Api/V2/V2.php`:
 1. `buildWhereExpressionsFromOptions` (~L6953) **deliberately does not prepend the default table**
    to a field starting with `_` — its own comment says *"add the default table if not specified and
    is not a calculated field."*
-2. `buildWhereClauseFromWhereExpressions` (~L7069) sees the leading `_` and **inlines the field's own
-   SQL expression** straight into the `WHERE` clause. That is the working path.
-3. `splitWhereExpressionsIntoWhereHaving` (~L8622) routes to `HAVING` **only when the field contains
+2. `validateWhereFieldReference` (~L8704-8741) accepts a bare calc name on the primary table.
+3. `buildWhereClauseFromWhereExpressions` (~L9225-9234) sees the leading `_` and **inlines the field's
+   own SQL expression** straight into the `WHERE` clause. That is the working path.
+4. `splitWhereExpressionsIntoWhereHaving` (~L11286) routes to `HAVING` **only when the field contains
    `._`** — i.e. only the table-**prefixed** form. That form targets a joined-table select alias
    (`PurchaseOrderItems__qtyAvailable`, built ~L3984) which **does not exist for the main table**,
    and ~L4116 also appends the `HAVING` to the `$sqlProhibited` COUNT query, which has no such alias
@@ -411,9 +416,11 @@ production — `toga2-supply/src/api/toga.ts` L906-919 (`_status` OR group) and
 **Zero** occurrences of the table-prefixed form exist in any repo — nobody has ever used it
 successfully.
 
-> ⚠ **Scope this to `where` only.** It says nothing about `group` or `sort` on a calculated field;
-> `group=_status` is separately known to fail. And `where` still never prunes a nested child array
-> (see below).
+> **`sort` on a calculated field also works** (bare name, calc branch of `ORDER BY` above).
+> **`group=_status` fails.** `where` still never prunes a nested child array (see below).
+> A TableView column over a calc field can be `isFilterable` — a code comment saying "calc fields
+> are not filterable" records a choice, not an engine limit. Dropdown options:
+> [calculated-column filter options](../../_underscore/features/calculated-column-filter-options.md).
 
 #### ⚠ `in` instead of an OR-chain of `contains` shortens the SQL - it does NOT make the filter fast
 
@@ -618,6 +625,7 @@ If you need the behaviour, loop uuids client-side. Point 3 is the durable, non-o
   [V2 request logging](request-logging.md).
 
 ## Change history
+- 2026-10-17 — Multi-sort comma list + `uuid` tie-breaker for stable paging; sort on calc works; refreshed where-path line refs. (jcardinal)
 - 2026-10-17 — POST create = 201, PUT/DELETE = 200 (TRUE-82889). (jcardinal)
 - 2026-10-15 — Security: `where` on an unreadable field still filters under default `identifier_acl_mode=log` (hash guessing); dotted FK path in `where` = `EV-8`, use a join alias (TRUE-82836). Folded older history. (jcardinal)
 - 2026-09-24 — `depth`/`calcDepth` ignored inside the base64 `_` blob; field three levels under an inherent child dropped (TRUE-82138). (apeterson)

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

@@ -4,6 +4,7 @@
 |-----|---------|
 | [TOGa Blox 2.5 — Architecture](architecture.md) | Shared React+TS SOURCE library for the new platform apps (new platform apps first; replaces toga-blox for all apps over time); read the ADR for full detail, not |
 | [Contact primary email/phone save (updateContactChannels) — table calls only](features/contact-channels-save.md) | How a contact edit form saves the contact's primary email and phone without nested writes; use it (do not rebuild it) in any app that edits a contact's email/ph |
+| [Money formatting (useSessionCurrency / formatMoney / useFormatMoney)](features/money-formatting.md) | The one money formatter for every platform app (session currency + session language via Intl); open before showing any money amount or adding a money column. |
 | [Old blox (toga-blox) straight port inside toga25-blox](features/old-blox-port.md) | Old `@agilant/toga-blox` code copied unchanged into toga25-blox (blox-v1 layer); open before touching any old component, its checks/config, or merging Storybook |
 | [GitHub Actions → AWS role via OIDC (trust policy + sub claim)](workflows/github-actions-aws-oidc-role.md) | How a GitHub Actions job assumes an AWS IAM role with OIDC, and the `sub` claim trap; open before creating or debugging any GitHub-to-AWS role ("Not authorized |
 | [Moving an old app from @agilant/toga-blox onto toga25-blox](workflows/moving-an-old-app-onto-toga25-blox.md) | Planned steps to switch an old app off the `@agilant/toga-blox` npm package onto toga25-blox source with zero import edits; open before moving any old app. |

package/knowledge/2.0/apps/toga25-blox/features/money-formatting.md

@@ -0,0 +1,45 @@
+---
+title: Money formatting (useSessionCurrency / formatMoney / useFormatMoney)
+framework: "2.0"
+repo: toga25-blox
+project: TOGa Blox 2.5
+client: shared
+type: feature
+status: active
+updated: 2026-10-17
+owners: ["jcardinal"]
+files:
+  - toga25-blox/src/core/format/formatMoney.ts
+  - toga25-blox/src/core/auth/useSessionCurrency.ts
+  - toga25-blox/src/core/http/currencyStore.ts
+  - toga25-blox/src/data-table/record-table/cellRegistry.tsx
+  - toga25-blox/src/data-table/record-table/ColumnHeaderControls.tsx
+related:
+  - ../../api2/features/session-currency.md
+  - ../architecture.md
+---
+The one money formatter for every platform app (session currency + session language via Intl); open before showing any money amount or adding a money column.
+
+## Summary
+
+`formatMoney(value, {currency, locale})` and the hook `useFormatMoney()` are THE money formatter for every platform app. The currency comes from `useSessionCurrency()` (api2 `audience.currency` — see [session currency](../../api2/features/session-currency.md)); the locale is the session language. Never hard-code a currency or a `$` in front-end code.
+
+## How it works
+
+- `currencyStore.ts` keeps `audience.currency` from each api2 response (wired in `apiClient.ts`, `credentials.ts`, `auth/session.ts`). `useSessionCurrency()` returns the ISO code or `null`.
+- `formatMoney` uses `Intl.NumberFormat` with the session language as locale and the ISO code as currency. It does not use `Currencies.symbol` / `position` — Intl places the symbol per language.
+- `null` or invalid currency → the number with no symbol (never a guessed `$`).
+- Record-table default cells format money through `cellContext.formatMoney` — a money column needs no custom cell.
+- **Right-aligned columns:** set `align: "right"` on a blox column (header + cells; the label stays first in tab order). Do not write app CSS that reaches into blox table internals to align a column.
+
+**Which currency for an amount (decided 2026-10-17, jcardinal):**
+- A stored amount with no currency column of its own is in its **owning client's** currency.
+- Multi-client listings use the session currency for now — all clients are USD.
+- Formatting by owning client must be built **before any client goes non-USD** (tracked follow-up).
+
+## Gotchas
+
+- Quad stores many currencies per item — its listings render per-currency text, not one formatted number. See [Quad multi-currency item pricing](../../../../clients/quad/features/multi-currency-item-pricing.md).
+
+## Change history
+- 2026-10-17 — Added session currency + shared money formatter; record-table money cells and `align: "right"` columns. TRUE-82878 (jcardinal)

package/knowledge/2.0/standards/frontend.md

@@ -5,7 +5,7 @@ project: _Underscore
 client: shared
 type: standard
 status: active
-updated: 2026-10-05
+updated: 2026-10-17
 owners: [jcardinal, apeterson, tcox]
 files: []
 related:
@@ -755,6 +755,17 @@ Copy from there rather than reinventing.
 
 ---
 
+## 24. Money display — **MUST**
+
+- Format every money amount with toga25-blox `useFormatMoney()` / `formatMoney()` (session
+  currency from api2 `audience.currency`, session language as locale). Never hard-code a
+  currency code or `$`, and never build the symbol from `Currencies.symbol`/`position`.
+- Money columns: use the record-table default money cell and blox column `align: "right"` —
+  no app CSS reaching into blox table internals.
+- Detail + the "owning client's currency" decision: [Money formatting](../apps/toga25-blox/features/money-formatting.md).
+
+---
+
 # Part 3 — Open items
 
 *(Described and flagged. NOT prescribed as settled.)*

package/knowledge/INDEX.md

@@ -23,7 +23,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 - **_underscore** (_Underscore) _(framework core)_ — 104 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
 - **worker2** (Worker) — 90 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
-- **api2** (API) — 26 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
+- **api2** (API) — 27 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 22 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)
 - **toga2-supply** (TOGa Supply) — 9 doc(s) → [2.0/apps/toga2-supply/INDEX.md](2.0/apps/toga2-supply/INDEX.md)
 - **saml** (SAML SSO Gateway) — 9 doc(s) → [2.0/apps/saml/INDEX.md](2.0/apps/saml/INDEX.md)
@@ -34,7 +34,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **toga25-supply** (TOGa 2.5 Supply) — 26 doc(s) → [2.0/apps/toga25-supply/INDEX.md](2.0/apps/toga25-supply/INDEX.md)
 - **toga25-iq** (TOGa IQ) — 1 doc(s) → [2.0/apps/toga25-iq/INDEX.md](2.0/apps/toga25-iq/INDEX.md)
 - **toga25-desk** (TOGa Desk 2.5) — 1 doc(s) → [2.0/apps/toga25-desk/INDEX.md](2.0/apps/toga25-desk/INDEX.md)
-- **toga25-blox** (TOGa Blox 2.5) — 5 doc(s) → [2.0/apps/toga25-blox/INDEX.md](2.0/apps/toga25-blox/INDEX.md)
+- **toga25-blox** (TOGa Blox 2.5) — 6 doc(s) → [2.0/apps/toga25-blox/INDEX.md](2.0/apps/toga25-blox/INDEX.md)
 - **toga-blox** (TOGa Blox) — 15 doc(s) → [2.0/apps/toga-blox/INDEX.md](2.0/apps/toga-blox/INDEX.md)
 
 ## standalone framework

package/package.json

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