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

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

@@ -0,0 +1,56 @@
+# Validation — `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.** Shared-core checks are identical across tracks; only the style checklist (§B) differs. On a **legacy** page instead → [validation-legacy.md](validation-legacy.md).
+
+The loop: **author or edit the page → self-check & fix → finish clean.** Check your own output and fix errors before the user ever sees them.
+
+## Self-check, and the compiler's error codes
+
+Validation is a checklist discipline: walk §A and §B below and fix every issue before finishing.
+
+The **official Quick compiler** (the same one the Studio editor runs) compiles `pJson → cJson` and reports **QScript/TypeScript syntax & type errors** in your handlers, plus structural and `S`-style checks. Whenever compiler output reaches you, treat it as a fix-loop: read the errors, apply every fix yourself, re-check until clean — the compiler never edits the qjson. Its `S`/`SC` style errors each name the exact params so you know precisely what to write:
+
+- **`missing-S` / `incomplete-S`** — the node's `S` lacks default-valued params from the component's [`component-styles.json`](../reference/component-styles.json) block. Fix: add each listed param to the `"xs-xl"` range with its default value from that block (or your design's override) — rule S3. (`VCol.flexDirection` is exempt: its editor default `column` does not match the runtime-unset `row` behavior — write it deliberately when you want stacking, per rule S5.)
+- **`missing-SC` / `incomplete-SC` / `wrong-SC-target` / `unknown-SC*`** — the node's `SC` does not match the component's `inheritedChildList` in `component-styles.json`. Fix: copy that block into `SC` **as-is** (the whole block, never a subset); remove `SC` entirely from components whose block has no `inheritedChildList`.
+- **`unknown-S-param`** — the param doesn't exist for this component; rename per the suggestion or remove it (the compiler silently drops it).
+- **`css-prop-in-S`** — the node sets a prop marked `cssProp: "true"` in [`component-contracts.json`](../reference/component-contracts.json). Those are legacy CSS props: legal on a legacy page, **not** in the `S` system. Fix: remove the prop and express the styling through the component's `S` params. (Components whose block is absent from `component-styles.json` are exempt — with no `S` params, the prop is the only way to style them.)
+
+## Final checklist
+
+### A) Shared core — every page, both style systems
+- [ ] Module shape: three authored keys present (`pJson`, `lrids`, `opt`); ends with `};` + `export default pjson`.
+- [ ] `cJson`/`clrids` **absent** — omitted from new files, stripped from any existing file you edited (Studio regenerates the compiled twins on import).
+- [ ] Every node: `T` valid; `P.ID.H` present + unique; `_Editor.eID` present + unique (equal to ID when new; may differ after a Studio rename — not required to match); **`C` present** (use `{}` for leaves — omitting `C` is a validator error).
+- [ ] Props: strings single-quoted in `H`; QScript object literals use `=`; `QLabel.text`=`prop`, `VIcon.text`=`text`.
+- [ ] Events: no native `return` (use `quick.return`); object literals closed with `};`; no browser globals; custom events have `C:true`; `P` matches payload.
+- [ ] Localization: `lrids` per language; keys exist in all languages; `LR` in props / `quick.LR` in events.
+- [ ] Containment: `VCol` only inside `VRow`; `VRow` holds only `VCol`; item components inside their container.
+- [ ] Charts: only `Bar`/`Line`/`Doughnut`; no `visible` on the chart.
+- [ ] Alerts include `actionButtons`.
+
+### B) `S`-system style checklist
+
+- [ ] Every visually-intentful node has an `S` object (range-keyed); child text/icons via the parent's `SC`. No structure-only nodes.
+- [ ] **No `O.layout`** (`dOpt`/`class`) on any node — grid width, flex direction/align/justify, and spacing all live in `S`.
+- [ ] **Class-prop audit:** if any `class` prop is present, verify each token individually against the `class → S` table in [../reference/styling-system.md](../reference/styling-system.md) §9 (full table: [../reference/mapping-S-vuetify-class.md](../reference/mapping-S-vuetify-class.md)). Tokens that have an `S` equivalent must NOT appear in `class` (e.g. `fill-height` when `S.height:"100%"` is set, `pt-2` when `S.paddingTop:"8px"` is set, `flex-column` when `S.flexDirection:"column"` is set). `class` here is a Web-only last resort, only for tokens with confirmed no `S` equivalent — and has no Mobile effect.
+- [ ] **No CSS props:** no prop marked `cssProp: "true"` in [`../reference/component-contracts.json`](../reference/component-contracts.json) is set on any node — those props are legacy-page-only and do not belong to a component's prop surface here. Express the styling in `S` instead (`VCol.cols/sm/md/lg/xl` → `S.col`; `VBtn/VCard.color` → `S.backgroundColor`; `elevation` → `S.boxShadow`; `height`/`width` → `S.height`/`S.width`; `rounded` → `S.border*Radius`). The only exception is a component with no block in `component-styles.json` — with no `S` params, its props stay the only way to style it.
+
+## `<<qjson:path>>` — inter-page references
+Inter-page references (e.g. `CustomComponent.QJsonPath`) are written as project-relative paths wrapped in `<<qjson:...>>`. In Studio's own model they are stable internal IDs; in files you always write the path form.
+
+**When authoring locally:**
+- Always write `'<<qjson:path>>'` — never a raw model ID.
+- The path is relative to the project root, without the `.qjson` extension (e.g. `<<qjson:sari-buton>>` for a root-level page, `<<qjson:forms/login>>` for a nested one).
+- If you see a UUID-style `<<qjson:...>>` in an existing file, the reference target wasn't found locally — do not copy that ID format into new authoring.
+
+### Renaming / moving / deleting a referenced page — update the referrers yourself
+Locally the link between two pages is the **path/name** inside `<<qjson:path>>`; in Studio it is a stable model id. So on the Studio side a rename/move needs no extra work — but **locally every file that referenced the old path goes stale** and breaks when imported back into Studio. When **you** (the agent) rename, move, or delete a `.qjson`, you must fix the referrers in the same change:
+
+1. **Find referrers first.** Grep the whole project for the target's current path *before* you touch it:
+   `grep -rln "<<qjson:sari-buton>>" .` (use the exact path the referrers use — root-level is just the name, nested is `folder/name`, module-owned is `ModuleName/.../name`, no `.qjson`).
+2. **Rename / move** → replace `<<qjson:oldPath>>` with `<<qjson:newPath>>` in every referrer.
+3. **Delete** → the reference target no longer exists; do not leave a dangling `<<qjson:path>>`. Remove or repoint the component instance that used it in each referrer (e.g. the `CustomComponent` whose `QJsonPath` pointed there), then validate.
+4. **Validate every file you edited** — referrers included, not just the renamed page.
+

package/dist/studio-cli/kits/ui-app-kit/.ai-kit/ui-kit/legacy-track.md

@@ -0,0 +1,29 @@
+# Quick qjson — legacy `cssClass` system track
+
+> **Style system: legacy (`cssClass`).** Follow this guide when the target is a legacy page — root-level `opt.V` missing or `< 2.0`, where the `S` object does not render. If the page is `S`-system (a new page, or `opt.V >= 2.0`), stop and use [s-track.md](s-track.md) instead. Shared workflow, shared docs, and shared rules are in the dispatcher [index.md](index.md); this guide adds the legacy-track doc set and the styling/layout rules. (Note: a **new** page is always `S` — a legacy page is always an existing page you are editing.)
+
+## The legacy-track doc set (open only these + the shared docs)
+- **Schema** → [reference/qjson-schema-legacy.md](reference/qjson-schema-legacy.md)
+- **Structure (start here)** → [knowledge/qjson-structure-legacy.md](knowledge/qjson-structure-legacy.md)
+- **Layout & slots** → [knowledge/layout-and-slots-legacy.md](knowledge/layout-and-slots-legacy.md)
+- **Styling how-to (`O.layout` + CSS classes)** → [knowledge/styling-legacy.md](knowledge/styling-legacy.md)
+- **Layout reference (`dOpt` grammar + `dOpt → class` rule)** → [reference/layout-system.md](reference/layout-system.md)
+- **Component catalog** → [reference/component-catalog-legacy.md](reference/component-catalog-legacy.md)
+- **Page skeletons / structure references** → [knowledge/page-skeletons-legacy.md](knowledge/page-skeletons-legacy.md)
+- **Repeated rows/cards from data** → [knowledge/dynamic-components.md](knowledge/dynamic-components.md)
+- **Validation (final checklist)** → [knowledge/validation-legacy.md](knowledge/validation-legacy.md)
+- **Examples** → [examples/cssClass/](examples/cssClass/) only (the `S` examples in `examples/style/` will mislead you here)
+
+## Edit & style
+1. **You are editing an existing tree.** Keep the page's current root (real legacy pages root on `VContainer`, `VAppBar`, `VDataTable`, …) — do **not** retrofit a `VContainer` root unless the user asks. Match the page's conventions (token style, ID style, `class` usage); reference [knowledge/page-skeletons-legacy.md](knowledge/page-skeletons-legacy.md) and the `examples/cssClass/` pages. For large edits, add **1–3 sections per edit**.
+2. **Style through the two legacy mechanisms — do NOT author `S`** (it won't render on `V < 2`):
+   - **`O.layout`** (`dOpt` + compiled `class`) — grid width (`c:col-N`), flex direction/align/justify (`fd:`/`a:`/`j:`), spacing (`sp:`). Keep `dOpt` and `class` **in sync** (compile rule: `xs` as-is; `sm/md/lg/xl` infix the breakpoint after the first `-`). Grammar + algorithm: [reference/layout-system.md](reference/layout-system.md).
+   - **The `class` prop** — CSS utility classes for typography/color/elevation/rounding, used freely. How-to: [knowledge/styling-legacy.md](knowledge/styling-legacy.md).
+3. **Validate** against [knowledge/validation-legacy.md](knowledge/validation-legacy.md) (shared core + legacy style checklist), then compile.
+
+## Non-negotiable legacy-track rules
+- **L1 — Do NOT introduce `S`.** It won't render on `V < 2` and would silently break styling. Keep all design in `O.layout` / `class`, matching how the page already does it. (A deliberate, full migration to `S` is a separate opt-in task — not an incidental edit.)
+- **L2 — Keep `O.layout.dOpt` and `O.layout.class` in sync.** The runtime applies `class`, so recompile it after any `dOpt` change per the algorithm in [reference/layout-system.md](reference/layout-system.md). Get this wrong and the class won't match the `dOpt`.
+- **L3 — Size columns with `c:col-N`** (1–12; `col-auto`; `0`→`d-none`) in `dOpt` + the synced `col-N` class — not `P.cols` alone (unreliable across editor/runtime).
+- **L4 — `VCol` does not auto-stack children** — add `fd:flex-column` to its `dOpt` (+ synced `flex-column` class) when multiple children must stack.
+- **L5 — Don't retrofit a `VContainer` root** onto an existing page unless the user explicitly asks.

package/dist/studio-cli/kits/ui-app-kit/.ai-kit/ui-kit/reference/component-catalog-legacy.md

@@ -0,0 +1,121 @@
+# Component Catalog — `T` Names & Contracts (legacy `cssClass` system)
+
+> **Style system: legacy (`cssClass`).** For legacy pages only — root-level `opt.V` missing or `< 2.0`, where `S` does not render. Component identity (`T` names, props, events) is the same in both eras; only the `VContainer`/`VRow`/`VCol` styling note below is legacy-specific. On a new page, or one with `opt.V >= 2.0`? Use [component-catalog.md](component-catalog.md) instead.
+>
+> Extracted from the Quick runtime's component registry. The machine-readable list lives in [component-index.json](component-index.json). Vuetify components follow Vuetify 2 prop/event/slot semantics unless noted.
+
+## 1. Lifecycle / system (non-visual or embedding)
+
+| `T` | Role |
+|-----|------|
+| `Messaging` | Page event hub. Holds lifecycle hooks (`PreRender`, `EndRender`, `PostRender`, `Restored`) and custom events. Prop `masterPath`; can declare `ExternalProps`/`ExternalEvents`. `O.cType: "child"`. |
+| `CustomComponent` | Embeds another `.qjson` via prop `QJsonPath`; cascades `readonly`/`disabled` to children. `O: { cType:"child", dynProps:true }`. |
+| `RenderingComponent` | Root embedder for a qjson view (props `QJsonPath`, `readonly`, `disabled`). |
+| `Ghost` | Empty placeholder div; used as a structural child / insertion anchor. |
+
+## 2. Charts (Chart.js) — only three exist
+
+| `T` | Notes |
+|-----|-------|
+| `Bar` | vertical/horizontal bars (`indexAxis: 'x'|'y'`) |
+| `Line` | has `fill`, `tension`, point styling |
+| `Doughnut` | `cutoutPercentage: 0` renders a **pie** shape |
+
+> **There is no `Pie` runtime component.** The chart library registers exactly `{ Doughnut, Bar, Line }`. `QPieChart` is a mobile-only placeholder. Use `Doughnut` for pie charts.
+
+Chart prop vocabulary: `labels` (array of axis/segment labels), `data` (number array), `label` (singular dataset name), `backgroundColor`/`borderColor` (array or string), `borderWidth`, `width`/`height`, axis (`xDisplay`/`yDisplay`), legend (`legendDisplay`/`legendPosition`), data labels (`labelDisplay`, ...). Charts have **no `visible` prop** — wrap in a `VCol` and toggle that. Runtime updates: mutate `components.<id>.data` then `(<any>components.<id>).update()`.
+
+## 3. Quick-native components
+
+`QLabel`, `Ghost`, `VContainer`, `VCol`, `VRow` (layout wrappers — note these three layout names are V-prefixed but implemented by Quick), `QFrame`, `QPhoneInput`, `QOtp`, `QMenu`, `QAnimation`, `QVideo`, `QMap`, `QRichText`, `QRichContent`, `QImgZoom`, `QLightBox`, `QDocumentViewer`, `QReCaptcha`, `QTableCell`, `QTutorial`, `QAppointmentCalendar`, `GroupBox`, `InfiniteScroll`, `LiveConnection`, `Tooltip`, `CustomAvatarComp`, `VInlineDatepicker`, `VInlineTimePicker`, `VPdfFileViewer`, `VSubElement`, `GoldenLayout`.
+
+## 4. Vuetify components (V-prefixed)
+
+See [component-index.json](component-index.json) `vuetify` array for the full list (80+). Common: `VBtn`, `VCard`, `VTextField`, `VTextarea`, `VSelect`, `VCombobox`, `VAutocomplete`, `VCheckbox`, `VSwitch`, `VRadio`/`VRadioGroup`, `VSlider`/`VRangeSlider`, `VDataTable`, `VDataIterator`, `VDialog`, `VIcon`, `VImg`, `VChip`, `VAlert`, `VSnackbar`, `VTabs`/`VTab`/`VTabItem`, `VStepper*`, `VExpansionPanel*`, `VPagination`, `VBreadcrumbs`, `VDivider`, `VAvatar`, `VBadge`, `VProgressCircular`/`VProgressLinear`, `VCarousel`/`VCarouselItem`, `VSkeletonLoader`, `VNavigationDrawer`, `VAppBar`, `VToolbar`, `VFooter`, `VSheet`, `VList*`, `VMenu`, `VTooltip`, `VDatePicker`/`VTimePicker`, `VFileInput`, `VRating`, `VSparkline`, `VTreeview`, `VForm`.
+
+## 5. Special Quick props injected on every component
+
+These are handled by the rendering layer, not plain Vuetify props:
+
+| Prop | `T` | Meaning |
+|------|-----|---------|
+| `ID` | `prop` | required unique runtime id; reference as `components.<ID>`. `_Editor.eID` is a separate unique editor id (equal to ID when auto-generated, may differ after rename — not required to match) |
+| `visible` | `prop` | show/hide (injected getter/setter; simple equality expressions allowed) |
+| `Render` | `prop` | if falsey, the component is not rendered at all (`Render:true` + `eager:true` to pre-build dialog contents) |
+| `qValue` | `prop` | Quick value binding; normalized to Vuetify's `value` at render. Use for inputs and to open/close dialogs (`components.dlg.qValue=true`). |
+| `class` | `class` | CSS classes (`T:"class"`) |
+
+> Some Vuetify components map `value` to an internal name (`VTextField`/`VExpansionPanels` → `internalValue`; `VSwitch`/`VCheckbox` → `inputValue`). Setting `qValue` handles this for you — prefer `qValue`.
+
+## 6. Per-component criticals
+
+### `QLabel` — text is a PROP
+```json
+{ "T": "QLabel", "P": {
+    "ID": { "H": "lblTitle", "T": "prop" },
+    "text": { "H": "'Page Title'", "T": "prop" } },
+  "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "lblTitle" } }
+```
+`text` uses `T: "prop"`. `HL` defaults to `QS`, so localized/expression text works directly: `"H": "LR('title')"`. Do **not** use `T: "text"` for QLabel.
+
+### `VIcon` — icon name is `text` with PType `"text"` ⚠️
+```json
+{ "T": "VIcon", "P": {
+    "ID": { "H": "icHome", "T": "prop" },
+    "text": { "H": "'mdi-home'", "T": "text" } },
+  "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "icHome" } }
+```
+The icon name goes in `text` with **`T: "text"`**. PType `text` renders as slot content, which Vuetify reads as the icon. (This corrects older docs that said `T:"prop"`.)
+
+### `VBtn`
+- No text prop — put a child `QLabel`/`VIcon`/`VImg` in the `default` slot.
+- Flat style: `depressed:true`, `elevation:0`.
+
+### `VCard`
+- Flat style: `elevation:0`. Slots: `default` (+ Vuetify `title`/`subtitle`/`actions`).
+
+### `VContainer` / `VRow` / `VCol`
+- Layout wrappers (Quick-implemented) — the grid is `VContainer > VRow > VCol`. Structural props: `VContainer` has `fluid`, `noGutters`, `eager`. `VCol` carries its own `layout-chooser` (nested flex). See [../knowledge/layout-and-slots-legacy.md](../knowledge/layout-and-slots-legacy.md).
+- **Column width:** `c:col-N` (1–12) in the `VCol`'s `O.layout.dOpt` + the matching `col-N` in the compiled `O.layout.class` (deterministic; `P.cols` alone is not) — see [layout-system.md](layout-system.md).
+- **Do NOT rely on `P.cols` alone** — it is unreliable across editor/runtime. Use `c:col-N` in `dOpt` with the synced class.
+- Flex direction/align/justify come from `dOpt` tokens (`fd:`/`a:`/`j:`) on the node, mirrored into the compiled `class`.
+
+### `VTextField` / inputs
+- `dense:true`, `outlined:true`, usually `hideDetails:true`.
+- Masking via `format` (`T:"attr"`): e.g. `number`, `email`, `iban`, `turkishMobilePhone`, `creditcard`, `regex`, `alphaNumeric`, ... Validation via `rules` (QScript array of `quick.Quick.validation.*`).
+
+### `VSelect` / `VCombobox` / `VAutocomplete`
+- `items` is QScript: `[{text='A', value=1}]` (use `=`). For service data prefer raw items + `itemText`/`itemValue`/`returnObject:true`.
+
+### `VDataTable`
+- `headers` and static `items` are **props** (QScript `=` literals); dynamic rows assigned in a callback (`components.tbl.items = rows;`).
+- Custom cells: scoped slot keyed `item.<columnValue>`, `cType:"scopedSlot"`; `item` is available in child bindings.
+- `click:row` params: `"P": "index:any,row:any"` — `index` is the row data.
+- `itemsPerPage` commonly `10`.
+
+### `VDialog`
+- Open/close: `components.<id>.qValue = true/false`.
+- Add `Render:true` + `eager:true` to access inner components before opening.
+- Non-persistent dialogs: handle `click:outside` to set `qValue=false`.
+
+### `VPagination`
+- `length`/`totalVisible` are string values; `input` handler's first line: `quick.this.qValue = number;` (param `"P":"number:number"`).
+
+### `VChip`
+- `color`: for per-row variation use static colors + sibling toggling with `visible` (so rows aren't blocked on conditional color expressions). Allowed: `default|primary|secondary|accent|success|error|info|warning`.
+
+## 7. Valid props, events & style params per component
+The exhaustive per-component contract is in [component-contracts.json](component-contracts.json). For each prop it gives:
+- `pType` — `prop` / `class` / `text` / `attr` (the qjson kind)
+- `type` — the **value type** (`string`, `boolean`, `number`, `number | string`, `Array<any>`, `Function`, `object`, …)
+- `options` — allowed **enum values** (quoted as they appear in `H`, e.g. `color`: `'primary'`,`'secondary'`,…)
+- `default` — the editor default
+- `cssProp` — This decides whether the prop is legal in the **S style system**. In **legacy (css) style qjsons** the prop is always usable, regardless of its `cssProp` value.
+
+And the component's **events** as `{ name, params?: [{name, type}] }` — the real event names plus the exact param signature to put in a handler's `P` (e.g. `VDataTable.click:row` → `index:any, row:IVDataTableClickRow`). Use it to pick a real prop/event, the right value **type and quoting** (a `boolean` is bare `true`, not `'true'`), valid enum values, and correct handler params. Treat it as the safe subset (real prop/event, correct PType, unquoted boolean); `options` are guidance. Regenerated from the Quick runtime sources when the runtime changes.
+
+**Style params** live in [component-styles.json](component-styles.json) — per `T`, the Style-tab (`S`) params the component supports, each with value `type` and editor `default`. Read it before writing `S` so you only set supported params (generation guidance; not hard-validated, since the editor expands composite border/shadow/font widgets into extra sub-params).
+
+## 8. Editor names vs runtime names
+
+The web editor may present friendlier names (e.g. "Text/Label" for `QLabel`, "Button" for `VBtn`). When **authoring the `T` field**, always use the runtime name from [component-index.json](component-index.json). When unsure whether a `T` is valid, check that file.

package/dist/studio-cli/kits/ui-app-kit/.ai-kit/ui-kit/reference/component-catalog.md

@@ -0,0 +1,140 @@
+# Component Catalog — `T` Names & Contracts (`S` system)
+
+> **Style system: `S` (new).** For `S`-system pages only — a new page, or one whose root-level `opt.V >= 2.0`. Component identity (`T` names, props, events) is the same in both eras; only the `VContainer`/`VRow`/`VCol` styling note below is `S`-specific. Editing a **legacy** page (`opt.V` missing or `< 2.0`)? Use [component-catalog-legacy.md](component-catalog-legacy.md) instead.
+>
+> Extracted from the Quick runtime's component registry. The machine-readable list lives in [component-index.json](component-index.json). Vuetify components follow Vuetify 2 prop/event/slot semantics unless noted.
+
+## 1. Lifecycle / system (non-visual or embedding)
+
+| `T` | Role |
+|-----|------|
+| `Messaging` | Page event hub. Holds lifecycle hooks (`PreRender`, `EndRender`, `PostRender`, `Restored`) and custom events. Prop `masterPath`; can declare `ExternalProps`/`ExternalEvents`. `O.cType: "child"`. |
+| `CustomComponent` | Embeds another `.qjson` via prop `QJsonPath`; cascades `readonly`/`disabled` to children. Two distinct usages — see § 6 below. |
+| `RenderingComponent` | Root embedder for a qjson view (props `QJsonPath`, `readonly`, `disabled`). |
+| `Ghost` | Empty placeholder div; used as a structural child / insertion anchor. |
+
+## 2. Charts (Chart.js) — only three exist
+
+| `T` | Notes |
+|-----|-------|
+| `Bar` | vertical/horizontal bars (`indexAxis: 'x'|'y'`) |
+| `Line` | has `fill`, `tension`, point styling |
+| `Doughnut` | `cutoutPercentage: 0` renders a **pie** shape |
+
+> **There is no `Pie` runtime component.** The chart library registers exactly `{ Doughnut, Bar, Line }`. `QPieChart` is a mobile-only placeholder. Use `Doughnut` for pie charts.
+
+Chart prop vocabulary: `labels` (array of axis/segment labels), `data` (number array), `label` (singular dataset name), `backgroundColor`/`borderColor` (array or string), `borderWidth`, `width`/`height`, axis (`xDisplay`/`yDisplay`), legend (`legendDisplay`/`legendPosition`), data labels (`labelDisplay`, ...). Charts have **no `visible` prop** — wrap in a `VCol` and toggle that. Runtime updates: mutate `components.<id>.data` then `(<any>components.<id>).update()`.
+
+## 3. Quick-native components
+
+`QLabel`, `Ghost`, `VContainer`, `VCol`, `VRow` (layout wrappers — note these three layout names are V-prefixed but implemented by Quick), `QFrame`, `QPhoneInput`, `QOtp`, `QMenu`, `QAnimation`, `QVideo`, `QMap`, `QRichText`, `QRichContent`, `QImgZoom`, `QLightBox`, `QDocumentViewer`, `QReCaptcha`, `QTableCell`, `QTutorial`, `QAppointmentCalendar`, `GroupBox`, `InfiniteScroll`, `LiveConnection`, `Tooltip`, `CustomAvatarComp`, `VInlineDatepicker`, `VInlineTimePicker`, `VPdfFileViewer`, `VSubElement`, `GoldenLayout`.
+
+## 4. Vuetify components (V-prefixed)
+
+See [component-index.json](component-index.json) `vuetify` array for the full list (80+). Common: `VBtn`, `VCard`, `VTextField`, `VTextarea`, `VSelect`, `VCombobox`, `VAutocomplete`, `VCheckbox`, `VSwitch`, `VRadio`/`VRadioGroup`, `VSlider`/`VRangeSlider`, `VDataTable`, `VDataIterator`, `VDialog`, `VIcon`, `VImg`, `VChip`, `VAlert`, `VSnackbar`, `VTabs`/`VTab`/`VTabItem`, `VStepper*`, `VExpansionPanel*`, `VPagination`, `VBreadcrumbs`, `VDivider`, `VAvatar`, `VBadge`, `VProgressCircular`/`VProgressLinear`, `VCarousel`/`VCarouselItem`, `VSkeletonLoader`, `VNavigationDrawer`, `VAppBar`, `VToolbar`, `VFooter`, `VSheet`, `VList*`, `VMenu`, `VTooltip`, `VDatePicker`/`VTimePicker`, `VFileInput`, `VRating`, `VSparkline`, `VTreeview`, `VForm`.
+
+## 5. Special Quick props injected on every component
+
+These are handled by the rendering layer, not plain Vuetify props:
+
+| Prop | `T` | Meaning |
+|------|-----|---------|
+| `ID` | `prop` | required unique runtime id; reference as `components.<ID>`. `_Editor.eID` is a separate unique editor id (equal to ID when auto-generated, may differ after rename — not required to match) |
+| `visible` | `prop` | show/hide (injected getter/setter; simple equality expressions allowed) |
+| `Render` | `prop` | if falsey, the component is not rendered at all (`Render:true` + `eager:true` to pre-build dialog contents) |
+| `qValue` | `prop` | Quick value binding; normalized to Vuetify's `value` at render. Use for inputs and to open/close dialogs (`components.dlg.qValue=true`). |
+| `class` | `class` | CSS classes (`T:"class"`) |
+
+> Some Vuetify components map `value` to an internal name (`VTextField`/`VExpansionPanels` → `internalValue`; `VSwitch`/`VCheckbox` → `inputValue`). Setting `qValue` handles this for you — prefer `qValue`.
+
+## 6. Per-component criticals
+
+### `CustomComponent` — two distinct usages
+
+**A. Block Component (UI embedding)** — the standard way to embed another page as a UI block. Placed at `pJson` root level (not inside VContainer). Minimal node — no Ghost, no `dynProps`.
+```json
+{ "T": "CustomComponent", "P": {
+    "ID": { "H": "blockMyPage", "T": "prop" },
+    "QJsonPath": { "H": "'<<qjson:path/to/page>>'", "T": "prop" } },
+  "E": {}, "C": {}, "O": {}, "_Editor": { "eID": "blockMyPage" } }
+```
+The embedded page must itself be a block component in Studio — if it isn't one yet, it must be converted on the Studio side via the workspace's tooling (details: [knowledge/components.md](../knowledge/components.md#block-component-embedding-another-qjson-page)). Does not apply to usage B.
+
+**B. Service Caller (project-specific proxy)** — only if the project provides a dedicated service-caller qjson. Has event handlers, a `Ghost` child, and `O: { cType:"child", dynProps:true }`. See [services.md](../knowledge/services.md) Pattern B.
+
+**`QJsonPath` format:** always `'<<qjson:path>>'` where `path` is the page's project-relative path without extension (e.g. `<<qjson:sari-buton>>` for a root-level page, `<<qjson:folder/page-name>>` for a nested one). Studio stores model IDs internally; in files you always write the path form — never a raw model ID.
+
+### `QLabel` — text is a PROP
+```json
+{ "T": "QLabel", "P": {
+    "ID": { "H": "lblTitle", "T": "prop" },
+    "text": { "H": "'Page Title'", "T": "prop" } },
+  "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "lblTitle" } }
+```
+`text` uses `T: "prop"`. `HL` defaults to `QS`, so localized/expression text works directly: `"H": "LR('title')"`. Do **not** use `T: "text"` for QLabel.
+
+### `VIcon` — icon name is `text` with PType `"text"` ⚠️
+```json
+{ "T": "VIcon", "P": {
+    "ID": { "H": "icHome", "T": "prop" },
+    "text": { "H": "'mdi-home'", "T": "text" } },
+  "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "icHome" } }
+```
+The icon name goes in `text` with **`T: "text"`**. PType `text` renders as slot content, which Vuetify reads as the icon. (This corrects older docs that said `T:"prop"`.)
+
+### `VBtn`
+- No text prop — put a child `QLabel`/`VIcon`/`VImg` in the `default` slot.
+- Flat style: set `S.boxShadow:"none"` (on an `S` page, not the `elevation`/`depressed` props).
+
+### `VCard`
+- Flat style: set `S.boxShadow:"none"` (on an `S` page, not the `elevation` prop). Slots: `default` (+ Vuetify `title`/`subtitle`/`actions`).
+
+### `VContainer` / `VRow` / `VCol`
+- Layout wrappers (Quick-implemented) — the grid is `VContainer > VRow > VCol`. Structural props: `VContainer` has `fluid`, `eager`. `VCol` is the one component whose flex axis (`flexDirection`/`alignItems`/`justifyContent`) is controllable as a real style param — see [../knowledge/layout-and-slots.md](../knowledge/layout-and-slots.md).
+- **Column width:** `S.col` on the `VCol` (1–12, range-keyed, e.g. `"xs-xl": {"col":"3"}`) — see [styling-system.md](styling-system.md).
+- **Do NOT use Vuetify responsive column props** (`VCol.cols`/`.sm`/`.md`/`.lg`/`.xl`): they set width via the Vuetify prop system, which `S` does not read. Use `S.col` + resolution ranges.
+- **Do NOT use `VRow.justify`/`VRow.align` props** as design intent — `VRow` exposes no `justifyContent`/`alignItems` `S` param; put alignment on a `VCol` (which supports those params), or fall back to the Web-only `class` last resort.
+
+### `VTextField` / inputs
+- usually `hideDetails:true`.
+- Masking via `format` (`T:"attr"`): e.g. `number`, `email`, `iban`, `turkishMobilePhone`, `creditcard`, `regex`, `alphaNumeric`, ... Validation via `rules` (QScript array of `quick.Quick.validation.*`).
+
+### `VSelect` / `VCombobox` / `VAutocomplete`
+- `items` is QScript: `[{text='A', value=1}]` (use `=`). For service data prefer raw items + `itemText`/`itemValue`/`returnObject:true`.
+
+### `VDataTable`
+- `headers` and static `items` are **props** (QScript `=` literals); dynamic rows assigned in a callback (`components.tbl.items = rows;`).
+- Custom cells: scoped slot keyed `item.<columnValue>`, `cType:"scopedSlot"`; `item` is available in child bindings.
+- `click:row` params: `"P": "index:any,row:any"` — `index` is the row data.
+- `itemsPerPage` commonly `10`.
+
+### `VDialog`
+- Open/close: `components.<id>.qValue = true/false`.
+- Add `Render:true` + `eager:true` to access inner components before opening.
+- Non-persistent dialogs: handle `click:outside` to set `qValue=false`.
+
+### `VPagination`
+- `length`/`totalVisible` are string values; `input` handler's first line: `quick.this.qValue = number;` (param `"P":"number:number"`).
+
+// BB 
+### `VChip`
+- `color`: for per-row variation use static colors + sibling toggling with `visible` (so rows aren't blocked on conditional color expressions). Allowed: `default|primary|secondary|accent|success|error|info|warning`.
+
+## 7. Valid props, events & style params per component
+The exhaustive per-component contract is in [component-contracts.json](component-contracts.json). For each prop it gives:
+- `pType` — `prop` / `class` / `text` / `attr` (the qjson kind)
+- `type` — the **value type** (`string`, `boolean`, `number`, `number | string`, `Array<any>`, `Function`, `object`, …)
+- `options` — allowed **enum values** (quoted as they appear in `H`, e.g. `color`: `'primary'`,`'secondary'`,…)
+- `default` — the editor default
+- `cssProp` — `"true"` when the prop is a **legacy css/styling property**. This decides whether the prop is legal in the **S style system**:
+  - `cssProp: "true"` → the prop **cannot** be used in the S style system (styling must be expressed through S).
+  - `cssProp` is `"false"` **or absent** → the prop **can** be used in the S style system.
+  - In **legacy (css) style qjsons** the prop is always usable, regardless of its `cssProp` value.
+
+And the component's **events** as `{ name, params?: [{name, type}] }` — the real event names plus the exact param signature to put in a handler's `P` (e.g. `VDataTable.click:row` → `index:any, row:IVDataTableClickRow`). Use it to pick a real prop/event, the right value **type and quoting** (a `boolean` is bare `true`, not `'true'`), valid enum values, and correct handler params. Treat it as the safe subset (real prop/event, correct PType, unquoted boolean); `options` are guidance. Regenerated from the Quick runtime sources when the runtime changes.
+
+**Style params** live in [component-styles.json](component-styles.json) — per `T`, the Style-tab (`S`) params the component supports, each with value `type` and editor `default`. Read it before writing `S` so you only set supported params (generation guidance; not hard-validated, since the editor expands composite border/shadow/font widgets into extra sub-params).
+
+## 8. Editor names vs runtime names
+
+The web editor may present friendlier names (e.g. "Text/Label" for `QLabel`, "Button" for `VBtn`). When **authoring the `T` field**, always use the runtime name from [component-index.json](component-index.json). When unsure whether a `T` is valid, check that file.