@stechquick/studio-cli 4.1.0-7 → 4.1.1-2

package/dist/studio-cli/{src/.ai-kit/knowledge/04-styling.md → kits/ui-app-kit/.ai-kit/ui-kit/knowledge/styling.md}

@@ -1,10 +1,10 @@
-# 04 · Styling — the `S` (Style) system
+# Styling — the `S` (Style) 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? → [AGENT_GUIDE Step 0](../AGENT_GUIDE.md).
+> ⚠️ **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.** `S` does not render on a legacy page — on a **legacy** page instead → [04-styling-legacy.md](04-styling-legacy.md). Reference examples from [../examples/style/](../examples/style/) only.
+> **This file is the `S` track.** `S` does not render on a legacy page — on a **legacy** page instead → [styling-legacy.md](styling-legacy.md). Reference examples from [../examples/style/](../examples/style/) only.
 
-> The earlier community docs treated styling as "CSS utility classes only" — that is just one mechanism, and **CSS works on Web only**. For the exhaustive schema (every `S` param, editor types, defaults, `SC` inheritance, cross-platform application) see **[../reference/styling-system.md](../reference/styling-system.md)**; the per-component supported `S` params + defaults are in **[../reference/component-styles.json](../reference/component-styles.json)** — the only source to consult when authoring `S`.
+> CSS utility classes are only one mechanism, and **CSS works on Web only**. For the exhaustive schema (every `S` param, editor types, defaults, `SC` inheritance, cross-platform application) see **[../reference/styling-system.md](../reference/styling-system.md)**; the per-component supported `S` params + defaults are in **[../reference/component-styles.json](../reference/component-styles.json)** — the only source to consult when authoring `S`. (Treat that list as generation guidance rather than a hard gate — the editor serializes a few extra composite sub-params beyond it — so when in doubt also check a sibling page or the styling reference.)
 
 > **Why not CSS:** Quick renders on Web, Android, and iOS. CSS exists only on Web. The Style tab serializes into the node's platform-neutral **`S`** object, which each platform applies natively (Web → CSS `@media`+`[q_UID]`; Mobile → flattened to the device's breakpoint range, `col`→flex-basis, via the native bridge). So for cross-platform styling you must use `S`, not a CSS Style File.
 
@@ -63,7 +63,7 @@ On an `S`-system page, layout is **not** a separate mechanism — the Layout box
 
 > The pre-`S` `O.layout` (`dOpt` + compiled `class`) mechanism for the same intents belongs to the legacy era — never author it on an `S`-system page.
 
-### Responsive breakpoints (authoritative pixel ranges)
+### Responsive breakpoints
 | Key | Device | Range |
 |-----|--------|-------|
 | `xs` | Mobile | 0–600px |
@@ -100,7 +100,7 @@ Some visuals are set on the **parent** and pushed into a typed child — e.g. a
   "C": { "default": { "c": [ /* QLabel + VIcon inherit the above */ ], "cType": "slot" } } }
 ```
 
-**`SC` complements the child's own `S` — it does not replace it.** Per rule S3 ([AGENT_GUIDE-s.md](../AGENT_GUIDE-s.md)) the child label/icon inside a `VBtn`/`VChip`/`VTabs` **also** carries its own `S` with its full default set from `component-styles.json`, values matched to the design (e.g. a white-text button label writes `fontColor:#ffffff` — not the generic QLabel default `#000000`). This is what the editor itself produces (see the button label in [../examples/style/MMDelay.qjson](../examples/style/MMDelay.qjson)). Keep the parent's `SC` mapping alongside it.
+**`SC` complements the child's own `S` — it does not replace it.** Per rule S3 ([s-track.md](../s-track.md)) the child label/icon inside a `VBtn`/`VChip`/`VTabs` **also** carries its own `S` with its full default set from `component-styles.json`, values matched to the design (e.g. a white-text button label writes `fontColor:#ffffff` — not the generic QLabel default `#000000`). This is what the editor itself produces (see the button label in [../examples/style/MMDelay.qjson](../examples/style/MMDelay.qjson)). Keep the parent's `SC` mapping alongside it.
 
 Also: legacy props migrate into `S` per each component's `propMigrateList` — e.g. `VBtn`/`VCard` `color` → `backgroundColor`, `VTextField` `color` → `labelDefaultFontColor`. Prefer setting `S` directly.
 
@@ -142,8 +142,8 @@ For locally-exported projects, custom fonts need the `@font-face` rule added to
   | `maxWidth` / `minWidth` / `maxHeight` as props | `S.maxWidth` / `S.minWidth` / `S.maxHeight` |
   | `elevation` prop | `S.boxShadow` |
 
-- **Never leave a component you placed with no `S` at all, and emit every default** — see [AGENT_GUIDE-s.md](../AGENT_GUIDE-s.md) rule S3. A `default` value listed in `component-styles.json` for a param is only the Style-tab's pre-filled suggestion — it is not silently applied unless you write that `S` key yourself. Therefore a placed component's `S` must include **every param that carries a `default` in its `component-styles.json` block** (the default value, or your design's override). Params whose JSON entry has no default (empty `{}`) are optional — set them only when the design needs them.
-- **A multi-child `VCol` does not stack for free.** `VCol` is itself a flex container, but its flex-direction is **not** column unless you set it — left unset it lays children out as a row, so two components dropped straight into a `VCol` render side-by-side instead of stacked (true in both eras — see [03-layout-and-slots.md](03-layout-and-slots.md)). The fix here is `S.flexDirection: "column"` on that `VCol` — a real, supported `S` param (`componentStyleList`'s `layout-chooser`/`content-direction` group; see the `VCol` block in [../reference/component-styles.json](../reference/component-styles.json)).
+- **Never leave a component you placed with no `S` at all, and emit every default** — see [s-track.md](../s-track.md) rule S3. A `default` value listed in `component-styles.json` for a param is only the Style-tab's pre-filled suggestion — it is not silently applied unless you write that `S` key yourself. Therefore a placed component's `S` must include **every param that carries a `default` in its `component-styles.json` block** (the default value, or your design's override). Params whose JSON entry has no default (empty `{}`) are optional — set them only when the design needs them.
+- **A multi-child `VCol` does not stack for free.** `VCol` is itself a flex container, but its flex-direction is **not** column unless you set it — left unset it lays children out as a row, so two components dropped straight into a `VCol` render side-by-side instead of stacked (true in both eras — see [layout-and-slots.md](layout-and-slots.md)). The fix here is `S.flexDirection: "column"` on that `VCol` — a real, supported `S` param (the `layout-chooser`/`content-direction` group; see the `VCol` block in [../reference/component-styles.json](../reference/component-styles.json)).
 
   Canonical **stacked label + value field** (label on top, value/input below):
 
@@ -172,6 +172,6 @@ For locally-exported projects, custom fonts need the `@font-face` rule added to
 ## Common theme utility classes (via `class` prop — Web-only last resort)
 These exist and work on Web, but most have an `S` equivalent that also works on Mobile — always check [../reference/mapping-S-vuetify-class.md](../reference/mapping-S-vuetify-class.md) first and prefer the `S` param (e.g. `fontSize`+`fontWeight` over `text-h5`, `fontColor` over `primary--text`, `borderRadius`/`backgroundColor` over `rounded-lg`/`transparent`, `paddingTop` over `pt-N`, `height:"100%"` over `fill-height`). Only reach for these classes when you specifically need a Web-only effect or are confirmed to not need Mobile parity. Typography: `text-h5`, `text-h6`, `text-body-1`, `text-body-2`, `text-caption` + `font-weight-bold|medium|regular`. Color: `primary`/`primary--text`, `secondary`/`secondary--text`, `success--text`, `error--text`, `white`/`white--text`, `secondary lighten-4`. Card: `rounded-lg`, `transparent` (for a flat card use `S.boxShadow:"none"`, **not** the `elevation` prop — the `elevation` prop is legacy-only). Icons: name in `VIcon.text` (PType `text`).
 
-## Pre-sync checklist
+## Final checklist
 
-The full pre-sync checklist (shared core + the `S`-system style checks — `S` on every visual node, no `O.layout`, the `class`-prop audit) is in [10-validation-and-sync.md](10-validation-and-sync.md). Run it before syncing.
+The full final checklist (shared core + the `S`-system style checks — `S` on every visual node, no `O.layout`, the `class`-prop audit) is in [validation.md](validation.md). Run it before finishing.

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

@@ -0,0 +1,49 @@
+# Validation — 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.** Shared-core checks are identical across tracks; only the style checklist (§B) differs. On a new page / `opt.V >= 2.0` instead → [validation.md](validation.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 compiler errors
+
+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. 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.
+
+## Final checklist
+
+### A) Shared core — every page
+- [ ] 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) Legacy style checklist
+- [ ] **No `S` introduced** — it won't render on `V < 2`; design stays in `O.layout` / CSS classes, matching how the page already does it.
+- [ ] `O.layout.dOpt` ↔ `O.layout.class` in sync — recompile `class` per the algorithm in [../reference/layout-system.md](../reference/layout-system.md) after any `dOpt` change (`xs` as-is; `sm/md/lg/xl` infixed).
+- [ ] `class` prop used freely for design (typography/color/spacing/elevation) is expected here — it is the legacy styling mechanism, Web-only, and is NOT audited against `S`.
+
+## `<<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/knowledge/validation.md

@@ -0,0 +1,55 @@
+# 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).
+
+## 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.
+- [ ] Vuetify style-affecting props not used where `S` has an equivalent (`VCol.cols/sm/md/lg/xl` → `S.col`; `VBtn/VCard.color` → `S.backgroundColor`; `elevation` prop → `S.boxShadow`).
+
+## `<<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/{src/.ai-kit/AGENT_GUIDE-legacy.md → kits/ui-app-kit/.ai-kit/ui-kit/legacy-track.md}

@@ -1,28 +1,27 @@
-# Agent Operating Guide — legacy `cssClass` system track
+# 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 [AGENT_GUIDE-s.md](AGENT_GUIDE-s.md) instead. Shared workflow, shared docs, and shared rules are in the dispatcher [AGENT_GUIDE.md](AGENT_GUIDE.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.)
+> **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/00-qjson-structure-legacy.md](knowledge/00-qjson-structure-legacy.md)
-- **Layout & slots** → [knowledge/03-layout-and-slots-legacy.md](knowledge/03-layout-and-slots-legacy.md)
-- **Styling how-to (`O.layout` + CSS classes)** → [knowledge/04-styling-legacy.md](knowledge/04-styling-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/09-page-skeletons-legacy.md](knowledge/09-page-skeletons-legacy.md)
-- **Validation & sync (pre-sync checklist)** → [knowledge/10-validation-and-sync-legacy.md](knowledge/10-validation-and-sync-legacy.md)
+- **Page skeletons / structure references** → [knowledge/page-skeletons-legacy.md](knowledge/page-skeletons-legacy.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)
-- **Styling+layout specialist subagent** → `quick-styling-legacy`
 
 ## 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/09-page-skeletons-legacy.md](knowledge/09-page-skeletons-legacy.md) and the `examples/cssClass/` pages. For large edits, add **1–3 sections per edit**.
+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/04-styling-legacy.md](knowledge/04-styling-legacy.md).
-3. **Validate** against [knowledge/10-validation-and-sync-legacy.md](knowledge/10-validation-and-sync-legacy.md) (shared core + legacy style checklist), then compile.
+   - **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 — the `qjson-legacy-migrator` agent, [agents/qjson-legacy-migrator.md](agents/qjson-legacy-migrator.md) — not an incidental edit.)
+- **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.

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

@@ -1,8 +1,8 @@
-# Component Catalog — Authoritative `T` Names & Contracts (legacy `cssClass` system)
+# 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.
 >
-> Source of truth: the Quick runtime component registry (`packages/websdk/src/components/providers/VuetifyComponents.ts`, `LocalComponents.ts`, `ChartComponents.ts`, `common/shrimp/constants/knownComps.ts`). The machine-readable list lives in [component-index.json](component-index.json). Vuetify components follow Vuetify 2 prop/event/slot semantics unless noted.
+> 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)
 
@@ -47,7 +47,7 @@ These are handled by the rendering layer, not plain Vuetify props:
 
 > 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 (verified against runtime + real files)
+## 6. Per-component criticals
 
 ### `QLabel` — text is a PROP
 ```json
@@ -65,7 +65,7 @@ These are handled by the rendering layer, not plain Vuetify props:
     "text": { "H": "'mdi-home'", "T": "text" } },
   "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "icHome" } }
 ```
-The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g. `VDataTableIconExample.qjson`). PType `text` renders as slot content, which Vuetify reads as the icon. (This corrects older docs that said `T:"prop"`.)
+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.
@@ -75,7 +75,7 @@ The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g.
 - 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/03-layout-and-slots-legacy.md](../knowledge/03-layout-and-slots-legacy.md).
+- 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`.
@@ -105,13 +105,13 @@ The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g.
 - `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, authoritative per-component contract is in [component-contracts.json](component-contracts.json). For each prop it gives:
+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
 
-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`). Generated by merging the editor PIM (`ComponentPims.ts` → prop existence + PType + event names), `componentList.js` (`componentOptions` → value type + options + default), and `eventParamDict.ts` (per-event params). 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.
+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).
 

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

@@ -1,8 +1,8 @@
-# Component Catalog — Authoritative `T` Names & Contracts (`S` system)
+# 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.
 >
-> Source of truth: the Quick runtime component registry (`packages/websdk/src/components/providers/VuetifyComponents.ts`, `LocalComponents.ts`, `ChartComponents.ts`, `common/shrimp/constants/knownComps.ts`). The machine-readable list lives in [component-index.json](component-index.json). Vuetify components follow Vuetify 2 prop/event/slot semantics unless noted.
+> 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)
 
@@ -47,7 +47,7 @@ These are handled by the rendering layer, not plain Vuetify props:
 
 > 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 (verified against runtime + real files)
+## 6. Per-component criticals
 
 ### `CustomComponent` — two distinct usages
 
@@ -58,11 +58,11 @@ These are handled by the rendering layer, not plain Vuetify props:
     "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 its frontmatter lacks `blockComponent: true`, run `studio convertToBlock <embedded-file>` (details: [knowledge/05-components.md](../knowledge/05-components.md#block-component-embedding-another-qjson-page)). Does not apply to usage B.
+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 [06-services.md](../knowledge/06-services.md) Pattern 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; `studio pull` converts ID→path and `studio push` converts path→ID automatically — never write a raw model ID here.
+**`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
@@ -80,7 +80,7 @@ The embedded page must itself be a block component in Studio: if its frontmatter
     "text": { "H": "'mdi-home'", "T": "text" } },
   "E": {}, "C": {}, "O": { "cType": "slot" }, "_Editor": { "eID": "icHome" } }
 ```
-The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g. `VDataTableIconExample.qjson`). PType `text` renders as slot content, which Vuetify reads as the icon. (This corrects older docs that said `T:"prop"`.)
+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.
@@ -90,7 +90,7 @@ The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g.
 - 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/03-layout-and-slots.md](../knowledge/03-layout-and-slots.md).
+- 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.
@@ -120,13 +120,13 @@ The icon name goes in `text` with **`T: "text"`** (verified in real files, e.g.
 - `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, authoritative per-component contract is in [component-contracts.json](component-contracts.json). For each prop it gives:
+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
 
-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`). Generated by merging the editor PIM (`ComponentPims.ts` → prop existence + PType + event names), `componentList.js` (`componentOptions` → value type + options + default), and `eventParamDict.ts` (per-event params). 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.
+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).
 

package/dist/studio-cli/{src/.ai-kit → kits/ui-app-kit/.ai-kit/ui-kit}/reference/component-contracts.json

@@ -1,11 +1,6 @@
 {
-  "$comment": "Per-component contract: props { name: { pType (prop|class|text|attr), type? (value type), options? (allowed enum values, quoted), default? } } and events [{ name, params?: [{name,type}] }]. Merged from the Quick PIM (ComponentPims.ts: prop existence + PType + event names/params), the editor componentList.js (componentOptions: value type + options + default), and eventParamDict.ts (supplemental per-event params). Regenerated from those Quick runtime sources when the runtime changes. The AI reads this AT GENERATION TIME to pick real props/events/params, correct PType, and valid value types.",
+  "$comment": "Per-component contract: props { name: { pType (prop|class|text|attr), type? (value type), options? (allowed enum values, quoted), default? } } and events [{ name, params?: [{name,type}] }]. Read this AT GENERATION TIME to pick real props/events/params, the correct PType, and valid value types.",
   "version": 3,
-  "sources": {
-    "pim": "apps/cli/src/generated/ComponentPims.ts",
-    "options": "apps/qeditor/.../static/js/componentList.js",
-    "events": "ComponentPims.ts (Events[].Parameters — primary) + eventParamDict.ts (supplement)"
-  },
   "components": {
     "CustomAvatarComp": {
       "editorName": "CustomAvatarComp",