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

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

@@ -1,10 +1,10 @@
-# QJSON Schema — Authoritative Reference (`S` system)
+# QJSON Schema (`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? → [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.** Design is authored in the node's `S` object; `O.layout` is not authored. On a **legacy** page instead (where `S` does not render) → [qjson-schema-legacy.md](qjson-schema-legacy.md).
 >
-> Source of truth: `common/shrimp/interfaces/ComponentInterfaces/ICompJson.ts` and `IQJson.ts`. These are the actual TypeScript interfaces the Quick runtime/compiler use. The earlier community docs described a smaller subset — this is the full schema.
+> Extracted from the TypeScript interfaces the Quick runtime and compiler use.
 
 ## 1. File envelope (`IQJSon`)
 
@@ -19,7 +19,7 @@ let pjson = {
 export default pjson
 ```
 
-An **AI-authored file carries only these three keys** (`pJson`, `lrids`, `opt`). The compiled twins `cJson` (compiled tree) and `clrids` (compiled localization) are generated by the editor/compiler on import — **omit them entirely**: never write them into a new file, and strip them from any downloaded file you edit.
+An **AI-authored file carries only these three keys** (`pJson`, `lrids`, `opt`). The compiled twins `cJson` (compiled tree) and `clrids` (compiled localization) are generated by the editor/compiler on import — **omit them entirely**: never write them into a new file, and strip them from any existing file you edit.
 
 Full `IQJSon` interface fields:
 
@@ -67,13 +67,13 @@ interface ICompJson {
 Required for a valid node: `T`, `P.ID.H`, `_Editor.eID`, and **`C`** (use `{}` for leaf components — omitting `C` is an error). `E` is typically present (often `{}`). `O` carries `cType` and layout.
 
 ### Styling fields: `S`, `SA`, `SC` (the Style System)
-These are produced by Studio's **Style tab** (the modern styling mechanism). The earlier community docs ignored them.
+These are produced by Studio's **Style tab**.
 
 - **`S`** (`StyleValue = Record<string, string | boolean | Record<string,string>>`): inline styles keyed by **resolution range** (e.g. `"xs-xl"`, `"md-xl"`), each a map of CSS-camelCase properties: `width`/`height`, `fontColor`/`fontFamily`/`fontSize`/`fontStyle`/`fontWeight`/`lineHeight`/`textAlign`, `backgroundColor`/`color`/`iconColor`, `border*`/`boxShadow`/`boxSizing`, margins/paddings, and (on containers) `col`/`flexDirection`/`alignItems`/`justifyContent`. Empty `""` = unset.
 - **`SA`**: array of applied **Styled Component** names (reusable named styles shared across pages).
 - **`SC`** (`IStyleChild`): style overrides targeting a component's child sub-elements.
 
-You hand-write `S` for **all** per-component design here — layout included (grid `col`, `flexDirection`/`alignItems`/`justifyContent`, spacing); `SA`/`SC` are normally produced by applying Styled Components in Studio. The `O.layout` field (§6) exists in the schema but belongs to the legacy era — **do not author it** on an `S`-system page. Full guidance: [knowledge/04-styling.md](../knowledge/04-styling.md).
+You hand-write `S` for **all** per-component design here — layout included (grid `col`, `flexDirection`/`alignItems`/`justifyContent`, spacing); `SA`/`SC` are normally produced by applying Styled Components in Studio. The `O.layout` field (§6) exists in the schema but belongs to the legacy era — **do not author it** on an `S`-system page. Full guidance: [knowledge/styling.md](../knowledge/styling.md).
 
 `CP` (CompPath for Named components) and `D` (directives) are advanced/editor-managed; hand-authoring rarely needs them.
 
@@ -92,7 +92,7 @@ interface IPropertyJson {
 }
 ```
 
-`PType` enum (how the value is applied at render — from `RenderingManager`):
+`PType` enum (how the value is applied at render):
 
 | `T` | Destination | Use for |
 |-----|-------------|---------|
@@ -130,7 +130,7 @@ interface IEventJson {
 - Custom events you call with `quick.MM.trigger('name', [payload])` must be declared with `"C": true`.
 - Events callable from another page/parent need `"EV": true`.
 - Lifecycle init events are often marked `"I": true`.
-- Use `quick.return` (never native `return`); see [scripting knowledge](../knowledge/02-events-and-scripting.md).
+- Use `quick.return` (never native `return`); see [scripting knowledge](../knowledge/events-and-scripting.md).
 
 ## 5. Children & slots (`IChildJson` / `CType`)
 
@@ -168,11 +168,11 @@ interface IOptJson {
 interface ILayoutJson { dOpt: IDictionary<Array<string>>; class: string; }
 ```
 
-- **`O.layout` — do not author it here.** It's the pre-`S` legacy layout mechanism (`dOpt` keyed by breakpoint → prefixed tokens, flattened into a synced `class` string). It exists in the schema and the compiler still accepts it, but on an `S`-system page grid width, flex direction/align/justify, and spacing are all `S` params (`col`, `flexDirection`, `alignItems`, `justifyContent`, margins/paddings) — see [knowledge/03-layout-and-slots.md](../knowledge/03-layout-and-slots.md) and [knowledge/04-styling.md](../knowledge/04-styling.md). (If you are actually editing a legacy page, you are in the wrong doc — see [qjson-schema-legacy.md](qjson-schema-legacy.md).)
+- **`O.layout` — do not author it here.** It's the pre-`S` legacy layout mechanism (`dOpt` keyed by breakpoint → prefixed tokens, flattened into a synced `class` string). It exists in the schema and the compiler still accepts it, but on an `S`-system page grid width, flex direction/align/justify, and spacing are all `S` params (`col`, `flexDirection`, `alignItems`, `justifyContent`, margins/paddings) — see [knowledge/layout-and-slots.md](../knowledge/layout-and-slots.md) and [knowledge/styling.md](../knowledge/styling.md). (If you are actually editing a legacy page, you are in the wrong doc — see [qjson-schema-legacy.md](qjson-schema-legacy.md).)
 
 ## 7. Compiled form (`cJson`) — do not author
 
-When compiled, handler `H` values get wrapped with sentinel delimiters (e.g. `╬...╩╩`) and `cJson`/`clrids` are populated. **AI-authored files omit `cJson`/`clrids` entirely** — never write them into a new file, and strip them from any downloaded file you edit. Author `pJson`/`lrids`, then let the editor (or the official compiler CLI) regenerate the compiled twins on import. See [validation & sync](../knowledge/10-validation-and-sync.md).
+When compiled, handler `H` values get wrapped with sentinel delimiters (e.g. `╬...╩╩`) and `cJson`/`clrids` are populated. **AI-authored files omit `cJson`/`clrids` entirely** — never write them into a new file, and strip them from any existing file you edit. Author `pJson`/`lrids`; the editor regenerates the compiled twins on import. See [validation](../knowledge/validation.md).
 
 ## 8. Minimal valid node