@stechquick/studio-cli 4.2.0-0 → 4.2.0-1

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/page-skeletons.md

@@ -0,0 +1,111 @@
+# Page Skeletons — `S` system
+
+> ⚠️ **STOP — before applying any rule below, confirm which style system the target page is on.** Read its root-level `opt.V` (and whether its nodes carry an `S` object): **`opt.V >= 2.0` / has `S` → S system**; **`opt.V` missing or `< 2.0` → legacy**. The two systems are not interchangeable on a page. Unsure how to route? → [index.md Step 0](../index.md).
+>
+> **This file is the `S` track** (starting a brand-new page). A new page's `opt.V` is always the current version — **author it as `opt.V: 2.5`** (this marks the page as `S`-system; the skeleton below already sets it). Adding a section to an **existing legacy page** instead → [page-skeletons-legacy.md](page-skeletons-legacy.md).
+
+Start every new page from one of these. Structure: `Messaging` (event hub) → optional service `CustomComponent` (only if the project uses one) → `VContainer` (layout root). For a **new page the `VContainer` content root is required** (not merely canonical): wrap all UI content in a single top-level `VContainer`, with `Messaging` and the optional service component as the only other top-level `pJson` siblings. This is a **new-page rule only** — when editing an existing page, keep its current root and do **not** add a `VContainer` unless the user asks.
+
+## Skeleton — framework-native (no service component)
+```javascript
+let pjson = {
+  "pJson": [
+    {
+      "T": "Messaging",
+      "P": { "ID": { "H": "msg", "T": "prop" } },
+      "E": {
+        "PreRender": { "H": "quick.MM.trigger('fetchData');\r\n", "I": true, "HL": "TS" },
+        "fetchData": { "H": "let req=<any>{};\r\nreq.url='/api/data';\r\nreq.http='GET';\r\nreq.data=null;\r\nreq.blockRender=false;\r\nreq.responseField='data';\r\nreq.onSuccess='onData';\r\nreq.onFail='onFail';\r\nquick.Request.async(req);\r\n", "C": true, "HL": "TS" },
+        "onData": { "H": "let resData = response.data;\r\n/* process resData */\r\n", "C": true, "HL": "TS" },
+        "onFail": { "H": "quick.Quick.alert({ title:'Hata', text:'Bir hata oluştu.', category:'Error', actionButtons:[{ name:'Tamam', type:'Confirm' }] });\r\n", "C": true, "HL": "TS" }
+      },
+      "C": {}, "O": { "cType": "child" }, "_Editor": { "eID": "msg" }
+    },
+    {
+      "T": "VContainer",
+      "P": { "ID": { "H": "pageContainer", "T": "prop" },
+             "class": { "H": "'container container--fluid'", "T": "class" } },
+      "E": {},
+      "C": { "default": { "c": [ /* PAGE CONTENT */ ], "cType": "slot" } },
+      "O": { "cType": "child" }, "_Editor": { "eID": "pageContainer" }
+    }
+  ],
+  "lrids": {}, "opt": { "V": 2.5 }
+};
+export default pjson
+```
+
+## Skeleton — with project ServiceCaller (only if the project provides one)
+Same as above, plus a `CustomComponent` after `Messaging` (see [services.md](services.md) Pattern B), with init in its `onLoad`.
+
+## Centered content scaffold (drop into PAGE CONTENT)
+
+> **VCard children do not stack automatically** — `VCard`'s default slot is a flex-row container. Always place a `VRow > VCol(flexDirection:column)` inside `VCard` before adding content; otherwise labels/inputs render side-by-side instead of stacked.
+
+```json
+{ "T": "VRow", "P": { "ID": { "H": "rowMain", "T": "prop" } }, "E": {},
+  "C": { "default": { "c": [
+    { "T": "VCol", "P": { "ID": { "H": "colMain", "T": "prop" } },
+      "S": { "xs-xl": { "col": "12", "justifyContent": "center", "paddingTop": "0px", "paddingRight": "0px", "paddingBottom": "0px", "paddingLeft": "0px" } },
+      "E": {},
+      "C": { "default": { "c": [
+        { "T": "VCard", "P": { "ID": { "H": "cardMain", "T": "prop" } },
+          "S": { "xs-xl": { "backgroundColor": "#ffffff", "boxShadow": "none", "paddingTop": "16px", "paddingRight": "16px", "paddingBottom": "16px", "paddingLeft": "16px", "borderTopLeftRadius": "8px", "borderTopRightRadius": "8px", "borderBottomLeftRadius": "8px", "borderBottomRightRadius": "8px" } },
+          "E": {}, "C": { "default": { "c": [
+            { "T": "VRow", "P": { "ID": { "H": "rowCardContent", "T": "prop" } },
+              "S": { "xs-xl": { "marginTop": "0px", "marginRight": "0px", "marginBottom": "0px", "marginLeft": "0px" } },
+              "E": {}, "C": { "default": { "c": [
+                { "T": "VCol", "P": { "ID": { "H": "colCardContent", "T": "prop" } },
+                  "S": { "xs-xl": { "col": "12", "flexDirection": "column", "paddingTop": "0px", "paddingRight": "0px", "paddingBottom": "0px", "paddingLeft": "0px" } },
+                  "E": {}, "C": { "default": { "c": [
+                    { "T": "QLabel", "P": { "ID": { "H": "lblPageTitle", "T": "prop" },
+                        "text": { "H": "'Page Title'", "T": "prop" } },
+                      "S": { "xs-xl": { "fontSize": "24px", "fontWeight": "700", "fontColor": "#1976D2", "fontFamily": "", "fontStyle": "", "combinedFont": "", "ThemeFont": "", "lineHeight": "" } },
+                      "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "lblPageTitle" } }
+                  ], "cType": "slot" } },
+                  "O": { "cType": "slot" }, "_Editor": { "eID": "colCardContent" } }
+              ], "cType": "slot" } },
+              "O": { "cType": "slot" }, "_Editor": { "eID": "rowCardContent" } }
+          ], "cType": "slot" } },
+          "O": { "cType": "slot" }, "_Editor": { "eID": "cardMain" } }
+      ], "cType": "slot" } },
+      "O": { "cType": "slot" },
+      "_Editor": { "eID": "colMain" } }
+  ], "cType": "slot" } },
+  "O": { "cType": "slot" }, "_Editor": { "eID": "rowMain" } }
+```
+
+## Styling — every component carries an `S` (don't skip it)
+The skeletons above are intentionally minimal: **structure + `class` only**. They are *not* a finished page. A real page also sets each component's visual design in its top-level **`S`** object — the cross-platform Style tag the editor serializes (sibling to `T`/`P`/`E`/`C`/`O`/`_Editor`). After you drop in a section, give its components their `S`:
+
+```json
+{ "T": "VCard", "P": { "ID": { "H": "cardMain", "T": "prop" } },
+  "S": { "xs-xl": {
+      "backgroundColor": "#ffffff",
+      "borderTopLeftRadius": "8px", "borderTopRightRadius": "8px",
+      "borderBottomLeftRadius": "8px", "borderBottomRightRadius": "8px",
+      "paddingTop": "16px", "paddingRight": "16px", "paddingBottom": "16px", "paddingLeft": "16px",
+      "boxShadow": "0 2px 8px rgba(0,0,0,0.08)" } },
+  "E": {}, "C": { "default": { "c": [
+    { "T": "VRow", "P": { "ID": { "H": "rowCardContent", "T": "prop" } },
+      "S": { "xs-xl": { "marginTop": "0px", "marginRight": "0px", "marginBottom": "0px", "marginLeft": "0px" } },
+      "E": {}, "C": { "default": { "c": [
+        { "T": "VCol", "P": { "ID": { "H": "colCardContent", "T": "prop" } },
+          "S": { "xs-xl": { "col": "12", "flexDirection": "column", "paddingTop": "0px", "paddingRight": "0px", "paddingBottom": "0px", "paddingLeft": "0px" } },
+          "E": {}, "C": { "default": { "c": [ /* content here */ ], "cType": "slot" } },
+          "O": { "cType": "slot" }, "_Editor": { "eID": "colCardContent" } }
+      ], "cType": "slot" } },
+      "O": { "cType": "slot" }, "_Editor": { "eID": "rowCardContent" } }
+  ], "cType": "slot" } },
+  "O": { "cType": "slot" }, "_Editor": { "eID": "cardMain" } }
+```
+
+- `S` is **range-keyed** (`"xs-xl"` = all sizes; narrower ranges like `"md-xl"` override for larger screens). Values are strings; `""` = unset.
+- Pull the supported param names + editor defaults for each `T` from [../reference/component-styles.json](../reference/component-styles.json) — don't invent params.
+- Style a child's text/icon (e.g. a `VBtn` label color) through the **parent's `SC`**, not the child's own `S`.
+- **Everything goes in `S`** — layout (flex/grid/spacing/direction, where the component's style block in [../reference/component-styles.json](../reference/component-styles.json) supports it) and visuals (color/font/border/shadow/exact size) alike. `O.layout` (`dOpt`+`class`) is legacy; don't author it. Reach for the component's `class` prop only as a Web-only last resort when `S` truly has no param for it — never on Mobile.
+
+Full how-to: [styling.md](styling.md). **A page delivered with no `S` is unstyled — the styling pass is part of authoring, not an optional extra.**
+
+## Large-page policy (incremental)
+Don't rewrite a whole page in one shot. Write the skeleton + scaffold, then add **1–3 sections per edit**, validate, and report progress. Reuse examples from [../examples/style/](../examples/style/) (the `S`-system set) and neighboring project pages rather than re-deriving structures.

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/properties.md

@@ -0,0 +1,77 @@
+# Properties (`P`)
+
+Each prop is `{ "H": value/expression, "T": kind, "HL": language? }`.
+
+```json
+"P": {
+  "ID":      { "H": "btnSave",      "T": "prop" },
+  "color":   { "H": "'primary'",    "T": "prop" },
+  "visible": { "H": "true",         "T": "prop" },
+  "class":   { "H": "'rounded-lg'", "T": "class" },
+  "items":   { "H": "[{text='A', value=1}]", "T": "prop", "HL": "QS" }
+}
+```
+
+## `T` — prop kind (PType)
+| `T` | Applied as | Use for |
+|-----|-----------|---------|
+| `"prop"` | Vue prop | the default case incl. `QLabel.text`, `items`, `color`, `visible` |
+| `"class"` | CSS class | `class` |
+| `"text"` | slot text content | `VIcon` icon name; raw text — `H` is still a QScript string, so single-quote it: `"'mdi-home'"` |
+| `"attr"` | DOM attribute | `data-*`, `aria-*`, input `format` masks |
+
+## `HL` — language (defaults to `QS`)
+`HL` is optional and **defaults to QScript**. Set `"HL": "TS"` only if a prop expression needs TypeScript (rare — props are usually QScript). The vast majority of real props omit `HL` and are therefore QScript.
+
+## Quoting inside `H`
+| Value | Write | Example |
+|-------|-------|---------|
+| string | single-quoted | `"'primary'"` |
+| number / bool | bare | `"10"`, `"true"` |
+| expression / binding | bare | `"item.name"`, `"data.title"`, `"components.x.qValue"` |
+| array | bracketed | `"[1,2,3]"`, `"['Jan','Feb']"` |
+| object array (QScript) | `=` keys | `"[{text='A', value=1}]"` |
+
+Apostrophe inside a QScript string → double it: `'Premium''u Keşfet'`.
+
+## QScript expression power (corrected vs older docs)
+Prop `H` values are **QScript expressions** and **can include conditionals**. Real files do this routinely:
+
+```json
+"color": {
+  "H": "if(data.statusColor == 1){'red'}else if(data.statusColor == 2){'orange'}else{'blue'}",
+  "T": "prop"
+}
+```
+The `if/else` block returns the last evaluated value — conditionals are fully supported in props.
+
+Available bare in QScript props: `LR(...)`, `components.*`, `data.*` (in dynamic templates), `item.*` (in scoped slots), `Math`, `Date`, `Number`, `JSON`, `string`, `regex`, `typeOf`. Framework namespaces drop the `quick.` prefix: `store.get('x')`, `Quick.go(...)`, `MM.trigger(...)`. See [reference/quick-api.md](../reference/quick-api.md) for the full list.
+
+> **QScript ≠ JS in two key ways:** (1) `||` returns a boolean, not a fallback value — use `if(a){a}else{b}` for a conditional fallback. (2) Property access is always null-safe (`a.b.c` won't throw if `a` is undefined), so `|| ''` guards are both wrong and unnecessary.
+
+### When to still pre-compute instead of expression-in-prop
+Conditionals work, but for **heavy** per-row formatting (date parsing, concatenation, lookups across rows) it's cleaner and faster to pre-format in the service/load callback and read a plain field in the prop:
+
+```typescript
+rows.forEach(r => { r.displayDate = quick.Quick.toShortDate(quick.Quick.toDate(r.date)); });
+components.tbl.items = rows;
+```
+```json
+"text": { "H": "item.displayDate", "T": "prop" }
+```
+This keeps prop expressions simple and avoids repeating logic per render.
+
+## Localization in props
+Use bare `LR('key')` (never `quick.LR` in a prop):
+```json
+"text": { "H": "LR('save')", "T": "prop" }
+```
+See [localization.md](localization.md).
+
+## Special Quick props
+`ID` (required, unique), `visible`, `Render`, `qValue`, `class` — see your track's component catalog §5 ([S](../reference/component-catalog.md) / [legacy](../reference/component-catalog-legacy.md)). Use `qValue` for input values and to open/close dialogs.
+
+## The two text gotchas
+- `QLabel.text` → `T: "prop"`.
+- `VIcon` icon name → `text` with `T: "text"`. The `H` value is still a QScript string — always single-quote it: `"H": "'mdi-home'"`, never bare `"H": "mdi-home"`.
+(See your track's catalog §6.)

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/qjson-structure-legacy.md

@@ -0,0 +1,65 @@
+# QJSON Structure (start here) — legacy `cssClass` system
+
+> ⚠️ **STOP — before applying any rule below, confirm which style system the target page is on.** Read its root-level `opt.V` (and whether its nodes carry an `S` object): **`opt.V >= 2.0` / has `S` → S system**; **`opt.V` missing or `< 2.0` → legacy**. The two systems are not interchangeable on a page. Unsure how to route? → [index.md Step 0](../index.md).
+>
+> **This file is the `legacy` track** (`opt.V` missing or `< 2.0`, where `S` does not render). Design is authored through `O.layout` (`dOpt` + compiled `class`) and CSS utility classes. On a new page / `opt.V >= 2.0` instead → [qjson-structure.md](qjson-structure.md). (A new page is always `S`, so legacy = an existing page you are editing.)
+
+A `.qjson` file is a **JavaScript module** describing one UI page as a tree of components. You author `pJson` (the tree) and `lrids` (localization); the editor/compiler generates the compiled twins `cJson`/`clrids`.
+
+```javascript
+let pjson = {
+  "pJson": [ /* component tree — you write this */ ],
+  "lrids": {},     // localization you write
+  "opt": {}        // page options (QL default language, V version)
+};
+export default pjson
+```
+
+Rules: an AI-authored file carries these **three** keys (`pJson`, `lrids`, `opt`); the file ends with `};` then `export default pjson`. The compiled twins `cJson`/`clrids` are **omitted entirely** — don't write them into a new file, and strip them from any existing file you edit (see "What you never author" below). Full envelope (incl. optional `description`, `files`, `namedViews`, `opt.QL/V`) is in [reference/qjson-schema-legacy.md](../reference/qjson-schema-legacy.md).
+
+## The component node — same six fields at every depth
+
+```json
+{
+  "T": "ComponentType",
+  "P": { "ID": { "H": "myId", "T": "prop" } },
+  "E": {},
+  "C": {},
+  "O": { "cType": "slot" },
+  "_Editor": { "eID": "myId" }
+}
+```
+
+| Field | Holds | Detailed in |
+|-------|-------|-------------|
+| `T` | component type name | [reference/component-catalog-legacy.md](../reference/component-catalog-legacy.md) |
+| `P` | props | [properties.md](properties.md) |
+| `E` | events | [events-and-scripting.md](events-and-scripting.md) |
+| `C` | children grouped by slot | [layout-and-slots-legacy.md](layout-and-slots-legacy.md) |
+| `O` | options: `cType` (always authored) **and `layout`** (`dOpt`/`class`) — `layout` is where grid/flex/spacing design lives on a legacy page | [layout-and-slots-legacy.md](layout-and-slots-legacy.md) |
+| `_Editor.eID` | equals `P.ID.H` when auto-generated, but **may differ** after a Studio rename — equality is *not* required (both must be present + unique) | this file |
+
+`CP`, `D`, `SA` are advanced editor-managed fields you normally don't hand-author. **`S`/`SC` are the modern Style-tab fields and do NOT render on a legacy page — do not author them here.** Design instead through `O.layout` and the `class` prop — see [styling-legacy.md](styling-legacy.md). Introducing `S` on a legacy page silently breaks styling.
+
+## The ID rules
+1. Every component has `P.ID.H`, **unique** within the page.
+2. Every component has `_Editor.eID`, also **unique**.
+3. `P.ID.H` is the runtime/reference id (`components.<ID>`); `_Editor.eID` is the editor's stable internal id.
+
+These two are **equal for auto-generated components** (both `EdtrComp_42`) but legitimately **differ** once the ID is renamed in Studio (e.g. `ID:"btnSave"`, `eID:"EdtrComp_42"`) — real files contain both cases, so a mismatch is **not** an error. When you hand-author a new component, the simplest valid choice is to set `eID` = `ID` (one unique value). Never reuse an `eID` or an `ID`.
+
+## Structure (editing an existing legacy page)
+A legacy page already has its root and tree (real pages legitimately root on `VContainer`, `VAppBar`, `VDataTable`, etc.). You are editing that tree, not starting fresh — **keep the current root** and do **not** insert a `VContainer` root unless the user explicitly asks. The canonical grid, where present, is:
+
+```
+pJson
+ ├─ Messaging            (event hub; no UI)
+ ├─ [service component]  (optional; only if the project uses one)
+ └─ <existing root>      (VContainer / VAppBar / VDataTable / …)
+     └─ VRow → VCol → VCard → content (labels, buttons, tables, inputs, charts)
+```
+
+For each node decide, in order: `T` → `P` → `E` → `C` → `O` (`cType` + `layout`) → copy ID into `_Editor.eID`. Mirror the page's existing conventions (token style, `class` usage). Reference legacy structures in [page-skeletons-legacy.md](page-skeletons-legacy.md) and the `examples/cssClass/` pages.
+
+## What you never author
+`cJson` and `clrids` are **compiled output** (handler strings get wrapped in `╬…╩╩` sentinels). Author `pJson`/`lrids` only, and **leave the compiled twins out of the file entirely** — don't write them into a new page, and strip them if the file already has them. Studio/the compiler regenerates them on import — see [validation-legacy.md](validation-legacy.md).

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/qjson-structure.md

@@ -0,0 +1,67 @@
+# QJSON Structure (start here) — `S` system
+
+> ⚠️ **STOP — before applying any rule below, confirm which style system the target page is on.** Read its root-level `opt.V` (and whether its nodes carry an `S` object): **`opt.V >= 2.0` / has `S` → S system**; **`opt.V` missing or `< 2.0` → legacy**. The two systems are not interchangeable on a page. Unsure how to route? → [index.md Step 0](../index.md).
+>
+> **This file is the `S` track** (new page, or `opt.V >= 2.0`). Design — visual **and** layout — is authored in each node's `S` object; `O.layout` is not authored here. On a **legacy** page instead → [qjson-structure-legacy.md](qjson-structure-legacy.md).
+
+A `.qjson` file is a **JavaScript module** describing one UI page as a tree of components. You author `pJson` (the tree) and `lrids` (localization); the editor/compiler generates the compiled twins `cJson`/`clrids`.
+
+```javascript
+let pjson = {
+  "pJson": [ /* component tree — you write this */ ],
+  "lrids": {},     // localization you write
+  "opt": { "V": 2.5 }  // page options — a NEW page sets V to the current schema version (2.5); this marks it as S-system
+};
+export default pjson
+```
+
+Rules: an AI-authored file carries these **three** keys (`pJson`, `lrids`, `opt`); the file ends with `};` then `export default pjson`. The compiled twins `cJson`/`clrids` are **omitted entirely** — don't write them into a new file, and strip them from any existing file you edit (see "What you never author" below). Full envelope (incl. optional `description`, `files`, `namedViews`, `opt.QL/V`) is in [reference/qjson-schema.md](../reference/qjson-schema.md).
+
+## The component node — same six fields at every depth
+
+```json
+{
+  "T": "ComponentType",
+  "P": { "ID": { "H": "myId", "T": "prop" } },
+  "E": {},
+  "C": {},
+  "O": { "cType": "slot" },
+  "_Editor": { "eID": "myId" }
+}
+```
+
+| Field | Holds | Detailed in |
+|-------|-------|-------------|
+| `T` | component type name | [reference/component-catalog.md](../reference/component-catalog.md) |
+| `P` | props | [properties.md](properties.md) |
+| `E` | events | [events-and-scripting.md](events-and-scripting.md) |
+| `C` | children grouped by slot | [layout-and-slots.md](layout-and-slots.md) |
+| `O` | options: `cType` (always authored). The `layout` sub-field (`dOpt`/`class`) is the legacy mechanism — **not authored here**; grid/flex/spacing go in `S` | [layout-and-slots.md](layout-and-slots.md) |
+| `_Editor.eID` | equals `P.ID.H` when auto-generated, but **may differ** after a Studio rename — equality is *not* required (both must be present + unique) | this file |
+
+`CP`, `D`, `SA` are advanced editor-managed fields you normally don't hand-author. **`S`/`SC` are the exception: you must hand-author them** — see [s-track.md](../s-track.md) rule S3 and [styling.md](styling.md). A component left without an `S` (when it carries visual or layout-flow intent) is the most common authoring miss, not an optional editor step.
+
+## The ID rules
+1. Every component has `P.ID.H`, **unique** within the page.
+2. Every component has `_Editor.eID`, also **unique**.
+3. `P.ID.H` is the runtime/reference id (`components.<ID>`); `_Editor.eID` is the editor's stable internal id.
+
+These two are **equal for auto-generated components** (both `EdtrComp_42`) but legitimately **differ** once the ID is renamed in Studio (e.g. `ID:"btnSave"`, `eID:"EdtrComp_42"`) — real files contain both cases, so a mismatch is **not** an error. When you hand-author a new component, the simplest valid choice is to set `eID` = `ID` (one unique value). Never reuse an `eID` or an `ID`.
+
+## Build order (top-down)
+```
+pJson
+ ├─ Messaging            (event hub; no UI)
+ ├─ [service component]  (optional; only if the project uses one)
+ └─ VContainer           (layout root)
+     └─ VRow → VCol → VCard → content (labels, buttons, tables, inputs, charts)
+```
+
+For each node decide, in order: `T` → `P` → `E` → `C` → `O` → copy ID into `_Editor.eID`.
+
+> **New page: the `VContainer` layout root is required, not optional.** Wrap all UI/visual content in a single top-level `VContainer`; the only non-`VContainer` top-level `pJson` siblings allowed are `Messaging` (event hub) and an optional service component. This applies to **new pages only** — when editing an existing page, keep its current root and do **not** insert a `VContainer` unless the user explicitly asks (see [s-track.md](../s-track.md) rule S4).
+
+Copy a full starting skeleton from [page-skeletons.md](page-skeletons.md).
+
+## What you never author
+`cJson` and `clrids` are **compiled output** (handler strings get wrapped in `╬…╩╩` sentinels). Author `pJson`/`lrids` only, and **leave the compiled twins out of the file entirely** — don't write them into a new page, and strip them if the file already has them. Studio/the compiler regenerates them on import — see [validation.md](validation.md).

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/services.md

@@ -0,0 +1,68 @@
+# Services (REST)
+
+Two patterns. **Check existing project pages first** and follow whichever the project uses.
+
+## Pattern A — `quick.Request.async` (framework-native, default)
+Call from any event; success/fail route to custom events on the same component (usually `Messaging`).
+
+```typescript
+let req = <any>{};
+req.url = '/api/products/list';
+req.http = 'GET';                 // GET|POST|PUT|DELETE|PATCH|MULTIPART|POSTBLOB|GETBLOB
+req.data = null;                  // body for POST/PUT
+req.blockRender = false;
+req.responseField = 'productList';
+req.onSuccess = 'onProductsSuccess';
+req.onFail = 'onProductsFail';
+quick.Request.async(req);
+```
+
+Read the result in the success event as `response.<responseField>`:
+```json
+"onProductsSuccess": {
+  "H": "if (response.productList != null) {\r\n  let resData = response.productList;\r\n  components.tblProducts.items = resData.resultList;\r\n}\r\n",
+  "C": true, "HL": "TS"
+}
+"onProductsFail": {
+  "H": "quick.Quick.alert({ title:'Hata', text:'İstek başarısız', category:'Error', actionButtons:[{ name:'Tamam', type:'Confirm' }] });\r\n",
+  "C": true, "HL": "TS"
+}
+```
+
+`IRequest` fields: `url`, `http`, `data`, `responseField`, `onSuccess`, `onFail`, `blockRender`, `showSuccessMessage`, `showErrorMessage`, `headers`, `withCredentials`, `timeout`, `args`. Inline `await` form also works:
+```typescript
+const respo = await quick.Request.async(req);
+let result = (<any>respo).data;
+```
+
+## Pattern B — project ServiceCaller `CustomComponent`
+Some projects centralize calls in a reusable `CustomComponent` (a service proxy) with `onLoad` / `onServiceSuccessCallBack` / `onServiceFailCallBack`. Use it **only if the project already provides one** (copy its `QJsonPath` from an existing page).
+
+```json
+{ "T": "CustomComponent", "P": {
+    "ID": { "H": "serviceCallerComp", "T": "prop" },
+    "QJsonPath": { "H": "'<<qjson:path/to/ServiceCallerCustomComponent>>'", "T": "prop" } },
+  "E": {
+    "onLoad": { "H": "quick.store.set('page', 0);\r\nquick.MM.trigger('getProducts', [{ page: 0 }]);\r\n", "HL": "TS" },
+    "onServiceSuccessCallBack": { "H": "/* capture → null → process */", "C": true, "P": "serviceResponse:any", "HL": "TS" },
+    "onServiceFailCallBack": { "H": "/* alert with actionButtons */", "C": true, "P": "serviceResponse:any", "HL": "TS" }
+  },
+  "C": { "default": { "c": [ { "T": "Ghost", "P": { "ID": { "H": "ghostComp", "T": "prop" } }, "E": {}, "C": {}, "O": { "cType": "child" }, "_Editor": { "eID": "ghostComp" } } ], "cType": "child" } },
+  "O": { "cType": "child", "dynProps": true }, "_Editor": { "eID": "serviceCallerComp" } }
+```
+Each call is a custom event on `Messaging` that builds a `requestObj` and calls `(<any>components.serviceCallerComp).serviceCall(requestObj)`. In the success callback, **capture → null → process**:
+```typescript
+if (serviceResponse.getProducts != null) {
+  let resData = serviceResponse.getProducts;  // capture
+  serviceResponse.getProducts = null;         // null immediately
+  components.tblProducts.items = resData.resultList; // process
+}
+```
+
+## Rules that prevent the common failures
+- Close the request object literal with `};` before the next call (missing `;` → "not callable").
+- Triggered custom events need `"C": true`; declare `P` to match the trigger payload.
+- `responseField` / event names must match exactly across trigger, request, and callback.
+- Fail alerts must include `actionButtons`.
+- Initialize in **one** place (service `onLoad` or `Messaging.PreRender`).
+- Don't assign `VDataTable.headers`/static `items` in callbacks — those are component props; assign only dynamic rows.

package/dist/studio-cli/kits/wf-app-kit/.ai-kit/ui-kit/knowledge/styling-legacy.md

@@ -0,0 +1,73 @@
+# Legacy styling — the `cssClass` system (`O.layout` / CSS utility classes)
+
+> ⚠️ **STOP — before applying any rule below, confirm which style system the target page is on.** Read its root-level `opt.V` (and whether its nodes carry an `S` object): **`opt.V >= 2.0` / has `S` → S system**; **`opt.V` missing or `< 2.0` → legacy**. The two systems are not interchangeable on a page. Unsure how to route? → [index.md Step 0](../index.md).
+>
+> **This file is the `legacy` track.** Style through `O.layout` (`dOpt` tokens + compiled `class`) and CSS utility classes, exactly as the page already does; never introduce `S` (it won't render on `V < 2`). On a new page / `opt.V >= 2.0` instead → [styling.md](styling.md). Reference examples from [../examples/cssClass/](../examples/cssClass/) only — the `S` examples in `examples/style/` will mislead you here.
+
+## When you are here
+
+You have opened a production page that predates the `S` system and needs a small change (the common case: "add a column", "nudge spacing", "change a text color"). Do **not** migrate it to `S` as a side effect of an edit — `S` won't render, so it would silently break the styling. Match the mechanism the page already uses. (A deliberate, full migration to `S` is a separate, opt-in task — not something to do inline.)
+
+## The two legacy mechanisms
+
+### 1. `O.layout` — the per-node Layout box (`dOpt` + compiled `class`)
+
+Layout intent (grid width, flex direction/align/justify, spacing) is expressed as prefixed Vuetify utility tokens in a node's `O.layout.dOpt`, keyed by breakpoint, and mirrored into a compiled `O.layout.class` string that the runtime actually applies.
+
+```json
+"O": {
+  "cType": "slot",
+  "layout": {
+    "dOpt": { "xs": ["d:d-flex", "fd:flex-column", "c:col-12", "a:align-center"],
+              "md": ["fd:flex-row", "c:col-6"] },
+    "class": "d-flex flex-column col-12 align-center flex-md-row col-md-6"
+  }
+}
+```
+
+**`dOpt` and `class` must stay in sync** — the runtime applies `class`, so after any `dOpt` change you must recompile the `class` string by the exact rule below. The full prefix grammar (`d, fd, a, j, w, c, sp, tt, tc, te, fi`), the breakpoint table, the `dOpt → class` compilation algorithm (xs as-is; `sm/md/lg/xl` infix the breakpoint after the first `-`), and the containment rules live in **[../reference/layout-system.md](../reference/layout-system.md)** — read that before editing any `O.layout`.
+
+Quick reference (see layout-system.md for the complete set):
+
+| Prefix | Meaning | Example token → class |
+| --- | --- | --- |
+| `d:` | display | `d:d-flex` → `d-flex` |
+| `fd:` | flex direction | `fd:flex-column` → `flex-column` |
+| `a:` | align-items | `a:align-center` → `align-center` |
+| `j:` | justify-content | `j:justify-center` → `justify-center` |
+| `c:` | grid column (1–12, `auto`, `d-none`) | `c:col-6` → `col-6` |
+| `sp:` | spacing (`N × 4px`) | `sp:pa-4` → `pa-4` (16px) |
+| `tt:`/`tc:`/`te:`/`fi:` | typography / text-color / weight / italic | `tc:primary--text` → `primary--text` |
+
+Compilation gotcha: a non-`xs` breakpoint token infixes the breakpoint — `fd:flex-row` under `md` → `flex-md-row`, `c:col-6` under `md` → `col-md-6`, `sp:pa-4` under `md` → `pa-md-4`. Get this wrong and the class won't match the `dOpt`.
+
+### 2. CSS utility classes on the `class` prop
+
+Direct Vuetify utility classes on a node's `class` prop (Web-only). On a legacy page these are used freely for design — typography, color, spacing, elevation, rounding:
+
+```json
+"class": { "H": "'text-center elevation-2 text-h5 primary--text'", "T": "class" }
+```
+
+Common utilities: typography `text-h1`…`text-h6`, `text-body-1/2`, `text-caption` + `font-weight-bold|medium|regular`; color `primary`/`primary--text`, `secondary--text`, `success--text`, `error--text`, `white--text`; spacing `pa-N`/`px-N`/`mt-N`… (`N × 4px`); appearance `elevation-0…24`, `rounded-lg`, `transparent`; alignment `d-flex`, `justify-center`, `align-center`. The `class` → `S` mapping table in [../reference/mapping-S-vuetify-class.md](../reference/mapping-S-vuetify-class.md) documents each token (useful here for understanding a token, and later if the page is ever migrated to `S`).
+
+**Gotcha — `VCol` does not auto-stack its children (see [layout-and-slots-legacy.md](layout-and-slots-legacy.md)).** Left without an explicit direction, a `VCol` lays children out as a row, so two components dropped straight into it render side-by-side instead of stacked. Fix here: add `fd:flex-column` to that `VCol`'s `O.layout.dOpt` (and recompile the synced `class`, e.g. `flex-column`). Don't leave a multi-child `VCol` without an explicit direction.
+
+**Equal-height cards in a row:** `VCard` has no flex `S`/`dOpt` mechanism of its own, so add `d-flex` to the `VCol`'s `class` and `flex-grow-1 d-flex flex-column` to the card's `class` (the `VRow`'s default `align-items:stretch` already gives the `VCol` full height).
+
+## Rules for editing a legacy page
+
+1. **Do not introduce `S`.** It won't render on `V<2`. Keep design in `O.layout` / `class`.
+2. **Keep `O.layout.dOpt` and `O.layout.class` in sync** — recompile `class` per the algorithm in [../reference/layout-system.md](../reference/layout-system.md) after any `dOpt` change.
+3. **Respect containment**: `VCol` only inside `VRow`; `VRow` holds only `VCol`; canonical wrapper `VContainer > VRow > VCol > content`.
+4. **Omit `cJson`/`clrids` entirely** — author `pJson`/`lrids` only; never write the compiled twins into a new file, and strip them from any existing file you edit. Studio/the compiler regenerates them on import.
+5. **Match the page's conventions** — mirror sibling nodes' token style, ID style, and class usage. Reference [../examples/cssClass/](../examples/cssClass/) for real legacy patterns.
+6. **Validate before finishing** against [validation-legacy.md](validation-legacy.md); fix all errors.
+
+## Migrating a legacy page to `S` (separate task)
+
+If the goal is genuinely to modernize a page (not just edit it), that means moving it onto the `S` system — a controlled, per-file conversion done as its own dedicated task, not an incidental edit. The `dOpt`/`class` → `S` conversion table is [../reference/mapping-S-vuetify-class.md](../reference/mapping-S-vuetify-class.md). A migrated page only styles correctly once its runtime/`opt.V` supports `S`.
+
+## Final checklist
+
+The full final checklist (shared core + the legacy style checks — no `S`, `dOpt`↔`class` in sync, `class` used freely) is in [validation-legacy.md](validation-legacy.md). Run it before finishing.