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

package/dist/common/studioCli/protocolVersion.js

@@ -1,14 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.CLI_INSTALL_COMMAND = exports.CLI_PACKAGE_NAME = exports.GENERATION = void 0;
-// Studio ↔ studio-cli köprü protokol sürümü — TEK KAYNAK (UI ve CLI buradan import eder).
-// Ne zaman artırılır: kırıcı kontrat değişikliği VEYA force update istenen her release.
-// Uyumluluk katı eşitlikle kontrol edilir (min/max aralığı yok); tespit UI tarafında,
-// whoAreYou probe cevabındaki protocol ile yapılır. Detay: studio-cli/docs/PROTOCOL-VERSION-CHECK.md
-exports.GENERATION = 1;
-// Paket adı burada tutulur ki UI, kurulum komutu için studio-cli'a import etmek zorunda kalmasın.
-exports.CLI_PACKAGE_NAME = "@stechquick/studio-cli";
-// Kullanıcıya gösterilen kurulum komutu — bu Studio'nun protokolüne denk gelen dist-tag'i kurar
-// (yayın akışı her CLI publish'inde `gen-<N>` tag'ini taşır; bkz. PROTOCOL-VERSION-CHECK.md Görev 6).
-exports.CLI_INSTALL_COMMAND = `npm i -g ${exports.CLI_PACKAGE_NAME}@gen-${exports.GENERATION}`;
-//# sourceMappingURL=protocolVersion.js.map

package/dist/common/studioCli/protocolVersion.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"protocolVersion.js","sourceRoot":"","sources":["../../../../common/studioCli/protocolVersion.ts"],"names":[],"mappings":";;;AAAA,0FAA0F;AAC1F,wFAAwF;AACxF,sFAAsF;AACtF,qGAAqG;AACxF,QAAA,UAAU,GAAG,CAAC,CAAC;AAE5B,kGAAkG;AACrF,QAAA,gBAAgB,GAAG,wBAAwB,CAAC;AAEzD,gGAAgG;AAChG,sGAAsG;AACzF,QAAA,mBAAmB,GAAG,YAAY,wBAAgB,QAAQ,kBAAU,EAAE,CAAC"}

package/dist/studio-cli/src/.ai-kit/.opencode/opencode.json

@@ -1,61 +0,0 @@
-{
-  
-  "$schema": "https://opencode.ai/config.json",
-  "instructions": [
-    "../.ai-kit/AGENT_GUIDE.md"
-  ],
-  "mcp": {
-    "playwright": {
-      "type": "local",
-      "command": ["npx", "@playwright/mcp@latest"],
-      "enabled": true
-    }
-  },
-  "permission": {
-    "playwright*": "allow"
-  },
-  "agent": {
-    "quick-qjson-author": {
-      "description": "Router: reads root-level opt.V and routes to the right track author — quick-qjson-author-s for S-system pages (new / opt.V >= 2.0), quick-qjson-author-legacy for legacy V<2 pages. Owns the shared structure/containment/events flow.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-qjson-author.md}"
-    },
-    "quick-qjson-author-s": {
-      "description": "Authors/edits .qjson pages on the S (new) style system — new pages, or opt.V >= 2.0. Design (visual AND layout) is authored in the node's S object. For legacy V<2 pages use quick-qjson-author-legacy.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-qjson-author-s.md}"
-    },
-    "quick-qjson-author-legacy": {
-      "description": "Authors/edits .qjson pages on the legacy cssClass style system — opt.V missing or < 2.0, where S does not render. Design via O.layout (dOpt/class) + CSS utility classes. For new pages / opt.V >= 2.0 use quick-qjson-author-s.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-qjson-author-legacy.md}"
-    },
-    "quick-styling": {
-      "description": "Styling AND layout on S-SYSTEM pages (new, or opt.V >= 2.0) via the cross-platform S Style System (S/SC); in the S system layout — grid col/direction/spacing — is also S. CSS is Web-only. For legacy V<2 pages use quick-styling-legacy.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-styling.md}"
-    },
-    "quick-events": {
-      "description": "Writes the E (events) block: TS/QScript handlers, quick.* API, lifecycle, services. Shared across both style systems.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-events.md}"
-    },
-    "quick-styling-legacy": {
-      "description": "Styling AND layout on LEGACY (cssClass) pages — opt.V missing or < 2.0, where S does NOT render. Owns O.layout (dOpt+compiled class) for grid/flex/spacing and CSS utility classes for visual design.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/quick-styling-legacy.md}"
-    },
-    "qjson-legacy-migrator": {
-      "description": "Migrates a single Quick .qjson file from the legacy system (O.layout/dOpt/Vuetify props) to the S-first style system. One file at a time, controlled per-node migration with a decision log; compiles to verify. Use only for a deliberate opt-in migration, not an incidental edit.",
-      "mode": "subagent",
-      "permission": { "edit": "allow", "bash": "allow" },
-      "prompt": "{file:../.ai-kit/agents/qjson-legacy-migrator.md}"
-    }
-  }
-}

package/dist/studio-cli/src/.ai-kit/AGENTS.md

@@ -1,18 +0,0 @@
-# AGENTS.md — Quick QJSON workspace
-
-> Template: copy this file to the **root of the downloaded qjson folder** (next to `.ai-kit/`). `AGENTS.md` is auto-read by many AI coding agents; it routes them into the kit. If `.ai-kit/` lives elsewhere, fix the paths below.
-
-This workspace contains **Quick / Plateau Studio `.qjson`** UI pages exported from Studio (a web IDE). You may be asked to create or edit pages; the user syncs them back to Studio.
-
-**Before editing any `.qjson`, read [`.ai-kit/AGENT_GUIDE.md`](.ai-kit/AGENT_GUIDE.md).** It is your operating procedure and links to the full knowledge base and authoritative reference.
-
-Essentials:
-- A `.qjson` is a JS module `let pjson = { ... }; export default pjson`. Author `pJson`/`lrids` — an AI-authored file carries only `{ pJson, lrids, opt }`. `cJson`/`clrids` are compiled twins (compiled output): **omit them entirely** — never write them into a new file, and **strip them if present** when editing a downloaded file (Studio regenerates them on import).
-- Knowledge (how-to): [`.ai-kit/knowledge/`](.ai-kit/knowledge/). Reference (exact API/schema/components): [`.ai-kit/reference/`](.ai-kit/reference/).
-- **Compile before you finish:** `studio buildQjson <file-or-folder>` (compiles with the bundled Quick compiler, reports any errors, and reports `S`/`SC` gaps as errors; it never edits the file — apply every fix yourself from `.ai-kit/reference/component-styles.json` and re-run until clean; see tools/README.md) — fix all remaining errors.
-- **Compiling is not the finish line — push and render-check.** If `.studio/server.json` exists (the CLI bridge is running), run `studio push` yourself after a clean compile; the pushed page lands in the user's open Studio session as unsaved work. Then, if the `playwright` MCP server is available, verify the page actually *runs*: open `http://127.0.0.1:<port>/render` (port from `.studio/server.json`) and check the rendered page + browser console — full loop in [`.ai-kit/knowledge/12-render-check.md`](.ai-kit/knowledge/12-render-check.md). When you're done, close the browser with `browser_close` — the Playwright MCP leaves it running otherwise. Report the render-check result; if the bridge or browser isn't available, say so instead of skipping silently.
-- Don't rename downloaded files (Studio matches them back by name/id).
-
-**Two style systems:** `.ai-kit` docs are split by style era. `AGENT_GUIDE.md` (Step 0) reads the page's root-level `opt.V` and routes you to the **`S`** track (new page / `opt.V >= 2.0`) or the **legacy** track (`opt.V` missing / `< 2.0`); each track has its own guide (`AGENT_GUIDE-s.md` / `AGENT_GUIDE-legacy.md`) and doc set. Follow one track — don't mix.
-
-**opencode users:** also copy `.ai-kit/opencode.jsonc` to this folder as `opencode.json` — it always loads the operating guide and registers the `quick-qjson-author` router (+ `quick-qjson-author-s` / `quick-qjson-author-legacy`), `quick-styling` / `quick-styling-legacy`, `quick-events`, and `qjson-legacy-migrator` subagents.

package/dist/studio-cli/src/.ai-kit/AGENT_GUIDE-legacy.md

@@ -1,29 +0,0 @@
-# Agent Operating Guide — 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.)
-
-## 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)
-- **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)
-- **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**.
-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.
-
-## 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.)
-- **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/src/.ai-kit/AGENT_GUIDE-s.md

@@ -1,30 +0,0 @@
-# Agent Operating Guide — `S` system track
-
-> **Style system: `S` (new).** Follow this guide when the target is an `S`-system page — a new page, or one whose root-level `opt.V >= 2.0`. If the page is legacy (`opt.V` missing or `< 2.0`), stop and use [AGENT_GUIDE-legacy.md](AGENT_GUIDE-legacy.md) instead. Shared workflow, shared docs, and shared rules are in the dispatcher [AGENT_GUIDE.md](AGENT_GUIDE.md); this guide adds the `S`-track doc set and the styling/layout rules.
-
-## The `S`-track doc set (open only these + the shared docs)
-- **Schema** → [reference/qjson-schema.md](reference/qjson-schema.md)
-- **Structure (start here)** → [knowledge/00-qjson-structure.md](knowledge/00-qjson-structure.md)
-- **Layout & slots** → [knowledge/03-layout-and-slots.md](knowledge/03-layout-and-slots.md)
-- **Styling how-to** → [knowledge/04-styling.md](knowledge/04-styling.md)
-- **Styling reference (`S`/`SC`/`SA` schema)** → [reference/styling-system.md](reference/styling-system.md)
-- **Component catalog** → [reference/component-catalog.md](reference/component-catalog.md)
-- **Page skeletons** → [knowledge/09-page-skeletons.md](knowledge/09-page-skeletons.md)
-- **Validation & sync (pre-sync checklist)** → [knowledge/10-validation-and-sync.md](knowledge/10-validation-and-sync.md)
-- **Examples** → [examples/style/](examples/style/) only
-- **Styling+layout specialist subagent** → `quick-styling`
-
-## Build & style
-1. **Build from a skeleton**, top-down (`Messaging` → optional service component → `VContainer` → rows/cols/cards → content). **A new page's `VContainer` content root is required** (rule S4 below), and **set the new page's `opt.V: 2.5`** (the current schema version — this is what makes it an `S`-system page). For large/visual pages, add **1–3 sections per edit** — never rewrite a whole page in one shot. Copy a skeleton from [knowledge/09-page-skeletons.md](knowledge/09-page-skeletons.md).
-2. **Style every component you add — set its `S` tag. Don't skip this.** `S` is the mechanism for *all* per-component design, layout included — size, spacing, grid column, flex direction/align/justify, colors, fonts, borders, shadows — keyed by resolution range (`"xs-xl"` = all sizes). For each node, set its `S` params from [reference/component-styles.json](reference/component-styles.json) — **including every param that carries a `default` in that component's block** (rule S3 below: write the default or your override, never omit it). If the component's block carries an `inheritedChildList`, copy it into the node's `SC` as-is (styles a child through its parent — `VBtn`/`VChip`/`VTabs` labels/icons) *in addition to* the child's own `S`, not instead of it. How-to: [knowledge/04-styling.md](knowledge/04-styling.md). **This is the single most-skipped step — a page returned without `S` is unstyled. Treat it as required.** Only when a component's `S` schema genuinely has no param for what you need: on **Web** you may set the `class` prop directly, as a last resort; on **Mobile** there is **no** `class` fallback — restructure with an `S`-capable component instead.
-   - **Token-by-token `class` justification (before writing any `class` prop):** list every CSS token you are about to write; check the `class → S` table in [reference/styling-system.md](reference/styling-system.md) §9 — if an `S` equivalent exists, write the `S` param and drop the token. Only tokens with confirmed no `S` equivalent belong in `class`. Never bulk-copy a class string. **Violation example:** `class: 'fill-height'` when `S.height:"100%"` is set — `fill-height` = `height:100%`, so drop the class token.
-   - **Mandatory delegation threshold:** if the page has more than ~15 visual components, or is a dashboard/landing/hero recreating a visual design, do **not** self-style inline. Finish the structural pass, then make a separate Agent call with `subagent_type: "quick-styling"`, passing the file path + the node IDs needing styling. Only self-style inline (reading [knowledge/04-styling.md](knowledge/04-styling.md) yourself) for small pages or single-component tweaks.
-3. **Validate** against [knowledge/10-validation-and-sync.md](knowledge/10-validation-and-sync.md) (shared core + `S` style checklist), then compile.
-
-## Non-negotiable `S`-track rules
-- **S1 — Don't author `O.layout`.** It's the legacy mechanism and does not belong on an `S` page. Size columns and any flex/grid/spacing intent via `S` instead: `S.col` for grid width, `S.flexDirection`/`alignItems`/`justifyContent` where the component's `componentStyleList` supports them (check [reference/component-styles.json](reference/component-styles.json)). **Do NOT use Vuetify's responsive column props** (`VCol.cols`/`.sm`/`.md`/`.lg`/`.xl`) — use `S.col` + resolution ranges (e.g. `"xs-sm": {"col":"12"}, "md-xl": {"col":"6"}`). Do NOT use `VRow.justify`/`VRow.align` props as style substitutes — if `S` can't express it on those components, that is the Web-only `class`-last-resort case.
-- **S2 — Prefer `S` over a Vuetify style-prop even when the prop is valid.** E.g. don't set `cols`/`sm`/`md`/`lg`/`xl` on `VCol` when `S.col` covers it; don't set `color` on `VBtn`/`VCard` when `S.backgroundColor` covers it; don't set the `elevation` prop when `S.boxShadow` covers it.
-- **S3 — Don't ship structure-only pages, and emit every default.** Every component you place gets an `S` object (range-keyed), and that `S` must include **ALL params that carry a `default` in the component's [reference/component-styles.json](reference/component-styles.json) block** — write the default value as-is, or your design's value where it differs. Never omit a default-valued param on the assumption it applies anyway (it does not — nothing merges defaults at render). For a component with a text/icon child (`VBtn`, `VChip`, `VTab`, …): the parent's own `S` still carries its full default set (fonts included), the child label/icon **also** carries its own `S` with its full default set (values matched to the design — e.g. white label text on a primary button), and the parent gets an **`SC`** — **copy the component's `inheritedChildList` block from [reference/component-styles.json](reference/component-styles.json) into `SC` as-is — the WHOLE block, never a hand-picked subset** (`VBtn`'s has 14 params, not just `fontColor`+`backgroundColor`; the validator reports `incomplete-SC`). Only components whose JSON block has an `inheritedChildList` get an `SC`; never invent mappings, never put `SC` on a component without one. Skipping `S` is the most common miss — it is not optional.
-- **S4 — New-page content root = `VContainer`.** A newly-created page must wrap all UI/visual content in a single top-level `VContainer`; the only non-`VContainer` top-level `pJson` siblings allowed are the non-visual `Messaging` event hub and an optional service component — `pJson: [Messaging, service?, VContainer{ … }]`. **New pages only:** when editing an existing page, keep its current root and do NOT insert a `VContainer` unless the user asks (real pages legitimately root on `VAppBar`, `VDataTable`, etc.).
-- **S5 — A multi-child `VCol` doesn't stack for free.** `VCol`'s flex direction defaults to row unless set — fix stacking with `"S": {"xs-xl": {"flexDirection": "column"}}` on that `VCol`. See the gotcha + copy-paste label/value pattern in [knowledge/03-layout-and-slots.md](knowledge/03-layout-and-slots.md).
-- **S6 — CSS Style Files are a Web-only true last resort** (project-level CSS, `@font-face`) — for cross-cutting rules neither `S` nor a component's `class` prop can express. Never rely on CSS for anything that must work on Mobile (no CSS there).

package/dist/studio-cli/src/.ai-kit/AGENT_GUIDE.md

@@ -1,86 +0,0 @@
-# Agent Operating Guide — dispatcher
-
-You are an AI coding agent working on **Quick / Plateau Studio `.qjson` files** on a user's local filesystem. The user exported these files from Studio (the web IDE), wants you to create or edit pages, and will sync them back to Studio. This kit is your complete, source-of-truth knowledge of Quick. Follow this guide.
-
-## Step 0 — determine the style system, then follow your track guide
-
-Quick has **two style systems**, and they are not interchangeable on a page. Decide which one the target page is on **before** you style, lay out, or validate — then follow that track's guide and doc set for the rest of the task.
-
-**Read the target's root-level `opt.V`:**
-
-| Condition | Track | Guide to follow |
-|-----------|-------|-----------------|
-| **Creating a new page** | **`S` (new)** — new pages are always created at the current `V` | [AGENT_GUIDE-s.md](AGENT_GUIDE-s.md) |
-| **`opt.V >= 2.0`** | **`S` (new)** — the `S` object renders; author design in `S` | [AGENT_GUIDE-s.md](AGENT_GUIDE-s.md) |
-| **`opt.V` missing OR `< 2.0`** | **legacy (`cssClass`)** — `S` does NOT render; author `O.layout` + CSS classes | [AGENT_GUIDE-legacy.md](AGENT_GUIDE-legacy.md) |
-
-There is no in-between: a page is either fully `S` or fully legacy. **Do not mix mechanisms** (never introduce `S` on a legacy page — it silently won't render; never author `O.layout` on an `S` page). **The presence of an `S` object is the ground truth for which system a page is on**, and `opt.V` should agree with it (`>= 2.0` ⇔ uses `S`). If the two disagree — `opt.V >= 2.0` but the nodes carry `O.layout`, or `opt.V` missing/`< 2.0` but the nodes carry an `S` object — the page is mid-migration or mis-tagged: go by whether an `S` object is actually present, and flag the mismatch to the user.
-
-Your track guide lists the exact doc set to use (schema, structure, layout, styling, catalog, skeletons, validation, examples, specialist subagent) — **open only your track's docs plus the shared docs below.**
-
-## What a `.qjson` is (one paragraph)
-A JS module exporting `pjson = { ... }`. You author `pJson` (a tree of component nodes) and `lrids` (localization) — so an **AI-authored file carries only `{ pJson, lrids, opt }`**. The editor/compiler generates the compiled twins `cJson`/`clrids`; **omit them entirely from files you author** — never write them into a new file, and **strip them if present** when editing a downloaded file (Studio regenerates them on import). Each node is `{ T, P, E, C, O, _Editor }` plus styling fields — `S`/`SA`/`SC` on `S`-system pages, `O.layout` on legacy pages. Full schema: `S` → [reference/qjson-schema.md](reference/qjson-schema.md); legacy → [reference/qjson-schema-legacy.md](reference/qjson-schema-legacy.md).
-
-## Where to look — shared docs (both tracks)
-These carry no style-era content; use them regardless of track:
-- **Task-oriented how-to (shared topics)** → [knowledge/01-properties.md](knowledge/01-properties.md), [02-events-and-scripting.md](knowledge/02-events-and-scripting.md), [05-components.md](knowledge/05-components.md), [06-services.md](knowledge/06-services.md), [07-localization.md](knowledge/07-localization.md), [08-dynamic-components.md](knowledge/08-dynamic-components.md), [11-cli-bridge.md](knowledge/11-cli-bridge.md), [12-render-check.md](knowledge/12-render-check.md) (see your pushed page rendered + its console errors, via Playwright MCP).
-- **Exact API of `quick.*`** (store, alert, request, navigation, validation, dates…) → [reference/quick-api.md](reference/quick-api.md).
-- **Events deep dive** → [reference/events-system.md](reference/events-system.md); **events specialist** → `quick-events`.
-- **Which `T` exists + registry** → [reference/component-index.json](reference/component-index.json) (machine-readable; era-agnostic).
-- **Valid props/events for a component (so you don't invent them)** → [reference/component-contracts.json](reference/component-contracts.json) (per `T`: each prop's `pType` prop/class/text/attr, value `type`, allowed `options` (enum), `default`; and `events` as `{ name, params?: [{name,type}] }`).
-- **Valid Style-tab (`S`) params for a component** → [reference/component-styles.json](reference/component-styles.json) (per `T`: supported style param → value `type` + editor `default`).
-
-> **Do NOT read these two big files whole.** `component-contracts.json` (~82k tokens) and `component-styles.json` (~37k tokens) are keyed per `T`, one component block each. Reading either whole wastes context and the file tools cap at 2000 lines — so a whole-file read silently truncates and you'd miss most components without knowing. Instead, **for each component you place, grep its block and read only that slice**: `grep -n '"VIcon":' reference/component-contracts.json` → a line number → `Read` that offset for ~30–60 lines. Batch the lookups a section needs before writing it.
-
-> **Why read these first (the core principle):** these dictionaries are *generation inputs*. Pick the prop/event/param/style from the contract **before** you write — then you never invent something the editor rejects. The compiler is the backstop for the rare miss; it is **not** the way to discover the valid set (a raw error says *what's wrong*, not *what's right*). Look it up up front.
-
-- **Component-specific deep detail / anything the distilled docs don't cover** → the full official documentation in [docs/](docs/) (index: [docs/README.md](docs/README.md)).
-- **Building a page *from a Figma design*** → the `figma-to-qjson` skill ([skills/figma-to-qjson/SKILL.md](skills/figma-to-qjson/SKILL.md)).
-
-**Everything else — the schema, structure, layout, styling how-to, component catalog, page skeletons, validation checklist, examples folder, and the styling/layout specialist subagent — is era-specific and listed in your track guide** ([AGENT_GUIDE-s.md](AGENT_GUIDE-s.md) / [AGENT_GUIDE-legacy.md](AGENT_GUIDE-legacy.md)).
-
-> **Subagents only become real, invokable subagents if also present in `.claude/agents/`** (Claude Code auto-discovers project subagents from that folder, not from `.ai-kit/agents/`). Check `.claude/agents/` first; if the persona is there, call it via the Agent tool (`subagent_type: "quick-styling"`, etc.). If missing, copy it there from `.ai-kit/agents/` (the source of truth; keep both in sync) before relying on delegation.
-
-## Workflow for every task
-1. **Read the target + neighbors.** Open the `.qjson` you'll edit and 1–2 sibling pages in the same folder. The kit gives you the *rules*; sibling pages give you *project conventions* (ID style, service URLs, `QJsonPath` of any service component, navigation `<<qjson:id>>` references). Mirror them.
-2. **Classify the work** — static layout / service / table / dialog-form / chart / navigation / localization / dynamic component. Read the matching shared `knowledge/` file(s).
-3. **Determine the style system (Step 0) and open your track guide.** Everything about *how* you build the tree's design, style, lay out, and validate lives there — follow it.
-4. **Compile** before finishing: `studio buildQjson <file>` (bundled Quick compiler; see tools/README.md). Fix all errors. (Full pre-sync checklist is in your track's `10-validation…` doc.)
-5. **Push, then render-check.** If `.studio/server.json` exists (the CLI bridge is running), run `studio push` yourself once the compile is clean — that places the page in the user's open Studio session (as unsaved work; nothing is saved or published). Then, when the `playwright` MCP server is available, open the page in the authenticated test browser and fix what the render and console show — see [knowledge/12-render-check.md](knowledge/12-render-check.md). Compiling clean does not prove the page runs clean.
-6. **Report**: changed file(s), what changed (including styling), compile result, render-check result (or that the bridge/browser wasn't available — never skip it silently), any project assumption you made.
-
-## Non-negotiable rules — shared (both tracks)
-These apply on every page regardless of era. (Style/layout-mechanism rules are in your track guide.)
-1. **Omit `cJson`/`clrids` entirely from AI-authored files.** Author `pJson`/`lrids` only; never write the compiled twins into a new file, and **strip them if present** when editing a downloaded one. Studio regenerates them on import.
-2. Every node: valid `T` (check the index), unique `P.ID.H`, unique `_Editor.eID`. (eID need not equal ID.) Don't invent props **or events** — use the props/events listed for that `T` in [reference/component-contracts.json](reference/component-contracts.json), with the PType it specifies and the event `params` it gives.
-3. Strings in prop `H` are single-quoted (`"'primary'"`); booleans/numbers/expressions are bare; QScript object literals use `=` (`{text='A', value=1}`).
-4. `QLabel.text` → PType `"prop"`. `VIcon` icon name → `text` with PType `"text"` — `H` is still a QScript string, so single-quote it: `"H": "'mdi-home'"` (never bare `"mdi-home"`).
-5. Events: never native `return` (use `quick.return`); close object literals with `};`; no browser globals (`window`/`document`/`console`/`setTimeout`) — use `quick.*`. **Event handlers are always TypeScript — set `"HL":"TS"` on every handler.** (Property/binding expressions are the ones that default to `QS`.)
-6. Props use bare `LR('key')`; events use `quick.LR('key')`.
-7. **Containment** (editor-enforced, era-agnostic): `VCol` only inside `VRow` (never at root); `VRow` holds only `VCol`; `VFooter` holds only `VContainer`; canonical wrapper `VContainer > VRow > VCol > content`.
-8. Charts: only `Bar`/`Line`/`Doughnut` (no `Pie`); no `visible` prop on charts.
-9. `quick.Quick.alert({...})` always includes `actionButtons`.
-10. `VBtn` label is a child `QLabel`/`VIcon`/`VImg`, not a text prop.
-
-## Things the previous-generation community docs got wrong (now corrected here)
-- **Props *can* contain `if/else` conditionals** (QScript returns the last value). They are not forbidden.
-- **`VIcon` icon uses PType `"text"`**, not `"prop"` — and `H` is still a single-quoted QScript string: `"H": "'mdi-home'"`, never `"H": "mdi-home"`.
-- **`_Editor.eID` need not equal `P.ID.H`** (equal when auto-generated; differs after a rename).
-- **Property/binding default language is `QS`** (not TS) — but **event handlers are always authored as `TS`** (`"HL":"TS"` on every handler). The old docs' mistake was calling TS the default for *properties*; it is not. Handlers, however, are TS-only.
-- **`quick.store` prefixes** are Page/Bag(`#`)/Global(`$`)/Shared(`&`) — for cross-session persistence use `quick.permanentStore`.
-- **`quick.Quick.validation`** has `required/minLength/maxLength/email/iban/regex/tckn/vkn` (no `phone` rule — use input `format` + `regex`).
-- **Styling is the Style tab, not just CSS utility classes.** How per-component design serializes depends on the page's era — see your track guide. The previous community docs treated styling as CSS-utility-classes only; that was incomplete.
-
-## Studio sync-back
-The user round-trips files Studio → local → Studio. So:
-- **Never rename** downloaded files or change embedded page ids — Studio matches them back by name/id.
-
-- **If you do rename/move/delete a page that others reference**, update every referrer's `<<qjson:path>>` in the same change (local links are path-based, so they go stale) — see [knowledge/10-validation-and-sync.md](knowledge/10-validation-and-sync.md#renaming--moving--deleting-a-referenced-page--update-the-referrers-yourself).
-- Omit `cJson`/`clrids` so Studio recompiles cleanly on import (it regenerates the twins whether they're absent or empty); never paste compiled (`╬…╩╩`) content. Strip them from any downloaded file you edit.
-
-- Validate the whole folder before syncing if you touched multiple files.
-- A file pulled from Studio may be **readonly** (`0444`) if it is locked/checked-out by someone else in Studio. To edit it locally, run `studio startWorking <file>` — do not `chmod` it manually.
-- **If you added a page into another page as a block component**, the embedded page must be converted in Studio: run `studio convertToBlock <embedded-file>` unless its frontmatter already has `blockComponent: true`. For a newly created page, run it **after** `studio push`. Details: [knowledge/05-components.md](knowledge/05-components.md#block-component-embedding-another-qjson-page).
-
-## When unsure
-Don't invent props/events/slots/values. Check [reference/component-index.json](reference/component-index.json) and your track's component catalog; for Vuetify components Vuetify 2 semantics apply; otherwise find a real example in a sibling page or ask the user. If a `T` isn't in the index, it's probably wrong (or the index needs updating from a newer runtime).

package/dist/studio-cli/src/.ai-kit/CLAUDE.md

@@ -1,12 +0,0 @@
-# CLAUDE.md — Quick QJSON workspace
-
-> Template: copy to the **root of the downloaded qjson folder** (next to `.ai-kit/`). Claude Code auto-reads `CLAUDE.md`. (Same content as `AGENTS.md`; keep whichever your agent reads, or both.)
-
-This workspace contains **Quick / Plateau Studio `.qjson`** UI pages. To create or edit them, **first read [`.ai-kit/AGENT_GUIDE.md`](.ai-kit/AGENT_GUIDE.md)** — the operating procedure for authoring qjson correctly.
-
-- Author `pJson`/`lrids` only. **AI-authored files omit `cJson`/`clrids` entirely** — never write these compiled twins into a new file, and **strip them if present** when editing a downloaded file (Studio regenerates them on import). Authored envelope = `{ pJson, lrids, opt }`.
-- How-to: [`.ai-kit/knowledge/`](.ai-kit/knowledge/) · Exact API/schema/components: [`.ai-kit/reference/`](.ai-kit/reference/).
-- Always compile before finishing: `studio buildQjson <file-or-folder>` (compiles with the bundled Quick compiler, reports any errors, and reports `S`/`SC` gaps as errors; it never edits the file — apply every fix yourself from `.ai-kit/reference/component-styles.json` and re-run until clean; see tools/README.md).
-- **Compiling is not the finish line — push and render-check.** If `.studio/server.json` exists (the CLI bridge is running), run `studio push` yourself after a clean compile; the pushed page lands in the user's open Studio session as unsaved work. Then, if the `playwright` MCP server is available, verify the page actually *runs*: open `http://127.0.0.1:<port>/render` (port from `.studio/server.json`) and check the rendered page + browser console — full loop in [`.ai-kit/knowledge/12-render-check.md`](.ai-kit/knowledge/12-render-check.md). When you're done, close the browser with `browser_close` — the Playwright MCP leaves it running otherwise. Report the render-check result; if the bridge or browser isn't available, say so instead of skipping silently.
-- **Two style systems:** `AGENT_GUIDE.md` (Step 0) reads the page's root-level `opt.V` and routes you to the **`S`** track (new page / `opt.V >= 2.0`) or the **legacy** track (`opt.V` missing / `< 2.0`) — each with its own guide (`AGENT_GUIDE-s.md` / `AGENT_GUIDE-legacy.md`) and doc set. Follow one track; don't mix.
-- A `quick-qjson-author` router subagent (+ per-track `quick-qjson-author-s` / `quick-qjson-author-legacy`) is available in [`.ai-kit/agents/`](.ai-kit/agents/) if you want to delegate page authoring.

package/dist/studio-cli/src/.ai-kit/README.md

@@ -1,81 +0,0 @@
-# Quick AI Kit
-
-Everything an AI coding agent needs to **create, edit, and validate Quick / Plateau Studio `.qjson` UI pages** on a local filesystem — then sync them back to Studio.
-
-This kit ships alongside the `.qjson` files a user downloads from Studio. Any agent (Claude Code, Copilot, Cursor, …) that reads these files can author correct qjson without prior Quick knowledge. It is **grounded in the actual Quick runtime source** (scripting API, qjson schema, component registry, official compiler), not reverse-engineered guesses.
-
-## Quick start (for the AI agent)
-1. Read **[AGENT_GUIDE.md](AGENT_GUIDE.md)** — your operating procedure.
-2. Use **[knowledge/](knowledge/)** to author, **[reference/](reference/)** for exact API/schema/components.
-3. Compile before finishing: `studio buildQjson <file-or-folder>` (compiles with the bundled Quick compiler and reports any errors; see tools/README.md).
-
-## Setup per agent (drop-in)
-The kit is agent-agnostic. Copy the matching entry file(s) to the **root of the downloaded qjson folder** (next to `.ai-kit/`):
-
-- **opencode** → copy [`opencode.jsonc`](opencode.jsonc) to the root as `opencode.json` (it auto-loads `AGENT_GUIDE.md` and registers the `quick-*` subagents from the kit) **and** keep [`AGENTS.md`](AGENTS.md) at the root (opencode reads it natively). Then run opencode in that folder; ask the main agent or `@quick-qjson-author` to build/edit a page.
-- **Claude Code** → keep [`CLAUDE.md`](CLAUDE.md) at the root; the `agents/*.md` work as Claude subagents.
-- **Cursor / Copilot / others** → keep [`AGENTS.md`](AGENTS.md) at the root (the emerging cross-agent standard). The knowledge/reference/tools are plain files any agent can read and run.
-
-**Activate the skill (opencode + Claude Code).** Both auto-discover [Agent Skills](https://opencode.ai/docs/skills/) only from `.claude/skills/`, `.opencode/skills/`, or `.agents/skills/` at the workspace root — there's no config path for it. Place the kit's skill at the shared `.claude/skills/` location (read by both):
-```
-cp -r .ai-kit/skills/quick-qjson .claude/skills/
-```
-The agent then sees a `quick-qjson` skill in its `skill` tool and loads the kit on demand. (Without this the kit still works via `AGENT_GUIDE.md`/`AGENTS.md` + the subagents — the skill is the native, invokable entry point.)
-
-**Optional — Figma import.** To build qjson pages *from a Figma design*, also install the add-on skill:
-```
-cp -r .ai-kit/skills/figma-to-qjson .claude/skills/
-```
-It runs the `studio figmaPull` command (part of the studio CLI) to pull a Figma selection (URL + token) into a local `.figma/` folder, then maps that design to qjson — delegating page authoring back to `quick-qjson`.
-
-Compile and validate with **`studio buildQjson <file-or-folder>`** — no build or install step; it runs the bundled compiler plus the structural and S-style checks. See [`tools/README.md`](tools/README.md).
-
-## Layout
-```
-.ai-kit/
-  README.md                  ← you are here
-  AGENT_GUIDE.md             ← dispatcher: Step-0 opt.V routing + shared workflow/rules
-  AGENT_GUIDE-s.md           ← S-track guide (new / opt.V≥2.0)
-  AGENT_GUIDE-legacy.md      ← legacy-track guide (opt.V missing / <2.0)
-  knowledge/                 ← task-oriented how-to (read what you need)
-    SHARED (both tracks):  01-properties.md  02-events-and-scripting.md  05-components.md
-                           06-services.md  07-localization.md  08-dynamic-components.md  11-cli-bridge.md
-    STYLE-SPLIT (S = base name, legacy = -legacy sibling):
-      00-qjson-structure(.md / -legacy.md)    03-layout-and-slots(.md / -legacy.md)
-      09-page-skeletons(.md / -legacy.md)     10-validation-and-sync(.md / -legacy.md)
-      04-styling.md (S)  ·  04-styling-legacy.md (legacy)
-  reference/                 ← authoritative, source-extracted ground truth
-    SHARED:  quick-api.md  events-system.md  component-index.json  component-contracts.json  component-styles.json
-    STYLE-SPLIT:
-      qjson-schema(.md / -legacy.md)          component-catalog(.md / -legacy.md)
-      styling-system.md (S)  ·  layout-system.md (legacy)
-    mapping-S-vuetify-class.md ← legacy→S migration bridge (references both eras)
-  tools/                     ← compile + validate via `studio buildQjson`
-    README.md                ← the fix-loop + reference-data notes for `studio buildQjson`
-  examples/                  ← curated example pages, split by style system (see examples/README.md)
-    style/                   ← S-system pages — reference for new / V≥2 pages
-    cssClass/                ← legacy pages — reference for V<2 edits only
-  agents/                    ← subagent definitions (Claude-style; usable as personas elsewhere)
-    quick-qjson-author.md    ← router (reads opt.V, routes to the track author)
-    quick-qjson-author-s.md  quick-qjson-author-legacy.md   ← per-track authors
-    quick-styling.md  quick-styling-legacy.md  quick-events.md   ← S styling+layout / legacy O.layout+CSS / events (shared)
-    qjson-legacy-migrator.md ← opt-in legacy→S migration (one file at a time)
-  skills/                    ← Agent Skill entry points (opencode + Claude Code)
-    quick-qjson/SKILL.md     ← invokable skill; install to .claude/skills/ (see Setup)
-    figma-to-qjson/SKILL.md  ← (add-on) build a qjson page from a Figma design; install to .claude/skills/
-  docs/                      ← the full official Quick UI documentation (deep fallback)
-    README.md                ← topic → official-doc index
-    UI-Screens/  UI-Module/  ← components, layout-design, logic, ui-settings
-```
-
-**Two style systems:** most style/layout docs exist as an `S` variant (base name) and a `-legacy` sibling. `AGENT_GUIDE.md` Step 0 reads the page's `opt.V` and routes you to one track; open only that track's docs plus the shared ones. Don't mix eras on a page.
-
-**Two-layer knowledge:** `knowledge/` + `reference/` are the distilled primary path; `docs/` is the full official documentation for deep, component-specific detail (see [docs/README.md](docs/README.md)).
-
-## Why this is the authoritative version
-Built directly from the Quick monorepo source, it corrects several long-standing mistakes in earlier community/agent docs — e.g. `VIcon` uses PType `text` (not `prop`); props *can* use `if/else`; `_Editor.eID` need not equal `P.ID.H`; the default scripting language is QScript; `quick.store` prefixes are Page/Bag/Global/Shared; only `Bar`/`Line`/`Doughnut` charts exist. See [AGENT_GUIDE.md](AGENT_GUIDE.md#things-the-previous-generation-community-docs-got-wrong-now-corrected-here).
-
-## For maintainers (the Quick team)
-- `reference/component-index.json` is the component registry the agent authors against. When the runtime adds/removes components, regenerate it from `packages/websdk/src/components/providers/*` so authoring stays current.
-- Compilation uses the official `apps/cli` compiler, bundled into studio-cli and exposed as `studio buildQjson` (deep TS/QScript diagnostics, in sync with the editor) — see [tools/README.md](tools/README.md).
-- Place a copy of `AGENTS.md` and/or `CLAUDE.md` at the root of the downloaded qjson folder (pointing at this kit) so agents auto-discover it. Templates are in this folder.