toga-ai 1.0.524 → 1.0.526

package/knowledge/1.0/apps/tools/features/errors-curation-console.md

@@ -95,6 +95,62 @@ curated text, affected clients) right, with an always-present Type chip.
 - Header chip order is **Issue / Environment / Type / Urgency** — Type was moved ahead of Urgency so
   urgency finishes the row at the far right.
 
+### Issue-detail layout rules (2026-08-04)
+
+**⚠ Never size anything inside `.issue-split-main` with a viewport media query.** The context
+cards live inside the app sidebar *and* beside the curation aside, so the grid gets only a
+fraction of the window — at a 1240px viewport the grid has roughly **540px**. A `min-width: 1180px`
+media query happily drew **three** columns into it. A viewport query cannot see the chrome around
+the element; **any grid in the two-column issue layout must break on its own width.**
+
+The context grid does that with no media queries, no container queries and no markup change:
+
+```css
+--context-card-min: 480px;
+grid-template-columns: repeat(auto-fit,
+    minmax(min(100%, max(var(--context-card-min), (100% - 28px) / 3)), 1fr));
+```
+
+The floor is `max(readable minimum, one third of the available width)`, measured against the grid
+itself: **<974px → 1 column, 974px+ → 2, 1468px+ → 3, and never 4**, because past that point the
+one-third term wins and grows with the container. `min(100%, …)` stops the floor exceeding the
+container on a phone; `28px` is the two 14px gaps three columns cost. The previous
+`repeat(auto-fit, minmax(320px, 1fr))` packed in **five** columns on a wide monitor (this page is
+full-bleed — `.app-content` `max-width` is overridden to `none`), leaving every card too narrow for
+its own content, so `SERVER`'s paths and `RUNTIME`'s `include_path` wrapped to four lines and each
+card grew its own scrollbar.
+
+`.context-card-body` `max-height` went **340px → 510px** — at 340px even a modest group scrolled, so
+an inner scrollbar was the normal state. The ceiling stays so one enormous group (`SERVER`, or the
+`GLOBALS` dump) cannot set the height of the whole board.
+
+**The CONTEXT heading names which occurrence it came from** — `CONTEXT   1Q-557 at 2026-08-04
+18:07:04`: the event reference (the same identifier the Events table uses) plus that event's
+`dtCreated`, in the subtle text token with the reference in semibold mono. This matters because the
+context and stack trace are the **most recent** event's — an issue that has fired 700 times has 700
+different contexts, and nothing on the page previously said which one you were reading.
+
+Two implementation constraints worth keeping:
+
+- It is a **flex row (`.context-heading`) wrapping the `h3` and the caption**, baseline-aligned —
+  *not* a `<span>` inside the `h3`, which inherits `text-transform: uppercase` and the heavier
+  weight and would have rendered "1Q-557 AT …". `flex-wrap` lets the caption drop to its own line
+  in a narrow pane.
+- **⚠ GENERAL RULE: any heading in this console that gets wrapped in a flex or grid container loses
+  its full-width section rule and must hand it to the wrapper.** `.tool--errors h3` carries the
+  section rule as its own `border-top`; once the `h3` became a flex *item* it shrank to its content
+  width and the rule stopped mid-page after the word "Context". The `margin`/`padding-top`/
+  `border-top` moved up to the full-width `.context-heading` and are zeroed on the nested `h3`.
+
+The caption renders only inside the branch where the latest event is non-null — an array offset on
+null in 1.0 becomes a rendered red error page.
+
+**"← All issues" is a button**, built on the existing `.btn-secondary-outline` so it inherits the
+console's button vocabulary. The arrow is a separate span moved with `transform` **only** (animating
+a gap or margin reflows the label and makes the control twitch), inside a `prefers-reduced-motion`
+guard where the colour change still carries the hover. It is the only navigation control on the page
+and was previously styled as body copy, indistinguishable from an inline reference to another issue.
+
 ### Neglect indicator (2026-08-04)
 
 Both pages now surface the **neglect** contribution to urgency: the listing computes
@@ -117,6 +173,11 @@ second line — the two halves then read as unrelated fragments. It is now `disp
 > so `nowrap` alone would have traded a wrap for an overflow. `col-urgency` went **96px → 136px**
 > and `.issue-listing` `min-width` **1026px → 1066px** to match. Any future `nowrap` in this table
 > needs the same paired column-width change.
+>
+> **Hit twice in one day.** The detail page's fingerprint hash was `wrap-anywhere` and broke as
+> `424b20ed7` / `5`, reading as two values; the fix is `nowrap` **plus** `.col-fp-hash` **74px →
+> 92px** (ten monospace characters at 11px need ~78px plus cell padding). The full hash stays on the
+> `title` attribute. **Widening the column is part of the fix, never optional.**
 
 **Deliberately scoped to the neglect contribution only.** The console never claims *which* axis is
 winning: computing the full driving axis in Tools would mean copying the volume, sustained and
@@ -236,7 +297,27 @@ They were renamed from plural on 2026-08-01, after the pipeline was already in p
 
 ## Change history
 
-- 2026-08-04 (latest, **uncommitted/undeployed** at time of writing) — **Fixed:** the neglect
+- 2026-08-04 (latest, **uncommitted/undeployed**; CSS/markup/nav only — no PHP logic, schema or
+  worker change) — **Fixed:** the context cards were too narrow and too short. `.context-card-body`
+  `max-height` 340px → 510px, and the grid's `repeat(auto-fit, minmax(320px, 1fr))` (five columns on
+  a wide full-bleed monitor) replaced by a floor of
+  `max(--context-card-min: 480px, (100% - 28px) / 3)` wrapped in `min(100%, …)` — 1/2/3 columns at
+  974px/1468px of **grid** width, never four. **A first attempt using viewport media queries was
+  wrong and is the durable lesson:** these cards sit inside `.issue-split-main`, so a 1180px viewport
+  query drew three columns into a ~540px grid; anything in the two-column issue layout must break on
+  its own width. Verified by computing the column count across eleven grid widths against the
+  developer's screenshots. **Fixed:** the fingerprint hash wrapped to two lines — `nowrap` **with**
+  `.col-fp-hash` 74px → 92px, the same `table-layout: fixed` nowrap/column-width pairing hit earlier
+  today on the neglect note. **Built:** the CONTEXT heading now names the occurrence it came from
+  (`1Q-557 at 2026-08-04 18:07:04`), since the context shown is the most recent event's and nothing
+  said which one; implemented as a `.context-heading` flex row rather than a span inside the
+  uppercase `h3`, which forced the section `border-top` up onto the full-width wrapper — a heading
+  made into a flex item loses its full-width rule. **Built:** "← All issues" is now a
+  `.btn-secondary-outline` button with a `transform`-only arrow shift under a
+  `prefers-reduced-motion` guard. **Changed:** the sidebar's single-link *Error Reporting* section
+  was folded into *Developers* as **Errors** (see
+  [persona-gated-navigation](./persona-gated-navigation.md)) — no access change. (jcardinal)
+- 2026-08-04 (earlier, **uncommitted/undeployed** at time of writing) — **Fixed:** the neglect
   indicator wrapped onto two lines in the listing — `.neglect-note` was `display: inline-block`, so
   "neglect NORMAL · 26h" broke after "neglect" and read as two unrelated fragments. Now
   `display: block` + `white-space: nowrap`, **with `col-urgency` 96px → 136px and `.issue-listing`

package/knowledge/1.0/apps/tools/features/persona-gated-navigation.md

@@ -6,7 +6,7 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-06-26
+updated: 2026-08-04
 owners: [jcardinal]
 files:
   - tools/_/app/nav.php
@@ -14,6 +14,7 @@ files:
 related:
   - ../architecture.md
   - ./saml-sso-auth.md
+  - ./errors-curation-console.md
 ---
 
 ## Summary
@@ -60,6 +61,24 @@ rather than a blank page:
 This is intentional: a valid user is never shown a broken/blank dashboard, and access is granted
 purely by assigning personas — no code change is needed to grant a user access to an existing tool.
 
+### Avoid single-link folders
+
+A folder that holds exactly one action costs a whole rail section for one link. The
+**Error Reporting** folder was removed on 2026-08-04 and its action moved to the top of
+**Developers** (above Generate UUID and Generate Password), relabelled **Issues → Errors**.
+
+> **Moving an action between folders can silently change who sees it** — visibility is the folder
+> gate plus the action gate. This move did not, because both folders carried identical personas
+> `['Development Team', 'TOGa Technology']`. Both `/errors` views also hardcode
+> `App_Auth::requireAuth(['TOGa Technology', 'Development Team'])` rather than calling
+> `personasForRoute()` — deliberate, per the folder-union warning in `nav.php`. **Check both gates
+> before moving an action.**
+
 ## Change history
+- 2026-08-04 (**uncommitted/undeployed** at time of writing) — Removed the single-link *Error
+  Reporting* folder; its action moved to the top of *Developers* and relabelled *Issues* → *Errors*.
+  No access change (both folders carried identical personas, and the `/errors` views hardcode their
+  own `requireAuth`). Recorded that moving an action between folders can change visibility via the
+  folder gate. (jcardinal)
 - 2026-06-26 — Documented the authorization model: authentication (SSO) and authorization (persona-gated nav) are separate — any valid user logs in regardless of personas; a persona-less user gets an empty left rail and an explicit dashboard empty-state ("no tools available", contact-dev card + Log out) instead of a blank page (jcardinal)
 - 2026-06-25 — Built App_Nav: hard-coded two-level persona-gated navigation; render() for the left rail, visibleGroups() for the dashboard, personasForRoute() for page self-guarding; route maps 1:1 to mvc/<route>/get.php (jcardinal)

package/knowledge/2.0/apps/toga25-supply/features/surface-frontend.md

@@ -6,7 +6,7 @@ project: TOGa 2.5 Supply
 client: shared
 type: feature
 status: active
-updated: 2026-08-04
+updated: 2026-08-05
 owners: [jcardinal, apeterson]
 files:
   - toga25-supply/src/pages/SalesOrders/view/SalesOrderRecordModalLayout/helpers/sectionRenderers.tsx
@@ -338,6 +338,33 @@ chrome (title, reason-input required-ness, confirm button, icons, toasts) diverg
 surfaces (`sales-order-approve-action`, `sales-order-deny-action`). Seed side:
 [surface-layer-schema](../../dbchanges2/features/surface-layer-schema.md).
 
+## Approval-details card — staged (approval-chain) value resolution via `config.preferredStage`
+
+The record-modal **approval-details** card resolves several fields off a *specific approval stage*
+rather than off the order root — e.g. **Assigned Manager** must show the same stage-2 manager the
+approval-decision modal shows. The surface declares this with a `config.preferredStage` marker on the
+element (surface-owned binding); the FE owns the *resolution mechanics*.
+
+- The approval-details card uses a **different adapter** than the decision modal —
+  `SalesOrders/helpers/surfaceBundleToTenantFields.ts` — which originally had no staged resolution,
+  so `preferredStage`-bound values came back blank. The staged resolver was **ported from the decision
+  adapter** (`surfaceBundlesToDecisionFields.ts`): `resolvePathInsensitive` + `makePreferredStageResolver`.
+- When `config.preferredStage` is set, the adapter attaches a **`field.getValue(order)`** that resolves
+  the `valueKey` from `order.stages[step === preferredStage]` instead of the order root. The record
+  modal's order carries `stages` via `useSalesOrderRecordModalLayoutModel`. `DetailSection.js` (blox)
+  honors `field.getValue`. Staged `getValue` is attached to the **primary** value, the **`labelSuffix`**
+  (VIP badge), and the **`isConcatenated`** appended value (inline email).
+- **blox dependency (staged concatenated email).** The inline-email `isConcatenated` staged value only
+  renders once blox `renderBaseDetailFieldValue.tsx` / `DetailSection/types.ts` accept an optional
+  `getValue` on the `isConcatenated` descriptor (previously `isConcatenated` dot-path resolved only off
+  the record root — a general off-root seam, backward compatible). That blox change is on branch
+  `feature-new-table` and is **NOT yet published**; the Assigned Manager staged email stays blank until
+  a toga-blox publish + version bump in toga25-supply.
+- **Per-client driver.** Compass + Compass Canada set `preferredStage:'2'` via a `CONFIG` SurfaceOverride
+  on the approval-details `assignedManager` element (whole-blob replace — see resolver override
+  semantics). Quad overrides field sort/visibility on the same card. Core seeds the shared content
+  (shipping-method + currency-charge concat, Order-For inline email path).
+
 ## Two FE rule engines (surface Tier-1 vs legacy named-rule) — do not conflate
 
 There are **two** rule evaluators in this app. As of 2026-07-21 the surface evaluator now has a
@@ -544,6 +571,15 @@ FE/CSS; content/visibility/order/ACL → Surface.**
   treat type-checking as pending. Runtime `GET /v2/surfaces/{slug}/meta` also not yet exercised.
 
 ## Change history
+- 2026-08-05 — **Built/Fixed** staged approval-chain value resolution on the record-modal
+  **approval-details** card. Ported the decision adapter's staged resolver (`resolvePathInsensitive`
+  + `makePreferredStageResolver`) into `surfaceBundleToTenantFields.ts`: a surface `config.preferredStage`
+  marker now drives a `field.getValue` that resolves the `valueKey` from `order.stages[step===preferredStage]`
+  (primary value + `labelSuffix` VIP badge + `isConcatenated` email) so Assigned Manager matches the
+  stage-2 decision manager. Blocked on a **pending, unpublished** toga-blox seam (`isConcatenated` gained
+  an optional `getValue` for off-root resolution, branch `feature-new-table`) before the staged email
+  renders. Per-client: Compass/Compass Canada set `preferredStage:'2'` (CONFIG override); Quad overrides
+  sort/visibility; Core seeds shipping-method+charge concat and the Order-For email path. (apeterson)
 - 2026-08-04 — **Built** a conditional two-layout split for the SalesOrders record modal
   (approval vs standard), driven by `isApprovalDetailsActive` at `SalesOrderView`. In approval
   stages the approval-details card leads (wide), Order Details + Bill To move below the Items

package/package.json

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