@cocoar/vue-ui 3.1.0 → 3.2.0-beta.6

package/skills/cocoar-vue-ui/references/components/page-builder/authoring-contract.md

@@ -0,0 +1,271 @@
+<!-- Generated from apps/docs/components/page-builder/authoring-contract.md by apps/docs/scripts/sync-skill.mjs. Do not edit; edit the docs page. -->
+
+# Authoring contract
+
+Every capability the renderer honours must be reachable from an authoring
+surface. This page is the inventory: each part of the document grammar, the
+surface that writes it, and — where a surface is missing — whether that is a
+**named exception** or an **open gap**.
+
+## The rules
+
+1. **Nothing is JSON-only.** Every capability is reachable through Element Code
+   / Page Code or a panel control. Editing raw JSON is a convenience, never a
+   requirement.
+2. **Nothing rewrites the document behind the author's back.** Problems are
+   reported, not silently healed.
+3. **Code is the truth.** Element Code, Page Code and Page State are the
+   authored artifact; the document follows from them. A Quick Property is
+   nothing but a fixed Element Code block — not editable as text, placed before
+   the element's custom code, so custom code can override it. Quick Properties
+   are a convenience for frequently-touched properties, not a second model.
+4. **Renderer ⊆ Builder.** `CoarPageRenderer` supports exactly what the builder
+   can write. It cannot do more than the editor can author.
+
+An exception to any of these is legitimate **only if it is named on this
+page**. An unnamed exception is a bug.
+
+## Two modes, one of them on the way out
+
+`authoringMode="properties"` is the **legacy** mode. It writes values directly
+into the document (`node.style`, `node.props`, `node.visibleWhen`) through
+per-element inspectors, a Style section, a Visibility section and a Field
+section. It is scheduled for removal.
+
+`authoringMode="code"` is the target. Everything is authored as code:
+
+| Surface | Writes | Notes |
+|---|---|---|
+| **Element Code** | `props`, `style`, `responsive`, `validation`, `visibleWhen`, `bindings`, `defaultValue` | Computed per render. Cannot change `type` or `name`. |
+| **Quick Properties** | locked assignments inside `elementCode`, ahead of the custom-code slot | Paths limited to `props.*`, `style.*`, `validation.*` |
+| **Page Root Code** | `style`, `responsive`, `enterSubmits` on the root | |
+| **Page Code / Page State** | shared state, repeat `items`, cross-element logic | |
+| **Structure section** | `type` (representation switch), `name` (free or contract-bound) | Structural — deliberately not code |
+| **Canvas / Outline** | `children`, tree order, `id` | Structural |
+| **Logic tab** | `bindings`, expressions | |
+| **Translations tab** | `translations` | |
+| **JSON tab** | everything, as a paste-and-apply convenience | Never the only way |
+
+The inventory below is written against the **target** state. Where a capability
+today has only a legacy-mode control, that is called out — it is a gap that
+opens the day properties mode is removed, not a gap you can see now.
+
+## The sandbox is mandatory
+
+If code is the truth, then the code has to run. `CoarPageRenderer` never
+evaluates it: the host runs `usePageCodeRuntime()` against an isolated Worker
+session and passes the data-only result as `pageCodeValues`.
+
+Leaving it out does **not** produce an error. `applyPageCodeValues` returns the
+schema untouched when it gets no values, so the renderer draws the persisted
+document — a different page, silently. And the difference is not small, because
+Quick Properties write **only** into `elementCode`; no write path touches
+`node.style` or `node.props`. A page whose author set anything in code mode
+renders unconfigured without the runtime.
+
+There is no realistic document that avoids this. A Quick Property *is* Element
+Code, and a page with a button or a validated field has one.
+
+```ts
+const runtime = usePageCodeRuntime({ schema, pageId, /* … */ });
+```
+```vue
+<CoarPageRenderer :schema :config :page-code-values="runtime.values.value" />
+```
+
+**Consequence to know about:** the persisted JSON on its own no longer
+describes the page. Static `style` values left over from earlier authoring can
+disagree with the code that overrides them, and the code wins. Read a document
+through the runtime, not by eye.
+
+## Node grammar
+
+### Every node
+
+| Field | Target-state surface |
+|---|---|
+| `id` | Canvas / Outline, builder-assigned — **named exception** |
+| `style` | Element Code (`element.style`), Quick Properties for the common keys |
+| `responsive` | Element Code (`element.responsive`) — **no Quick Property**, see gaps |
+| `composition`, `compositionOrigins` | Compositions library — **named exception** |
+
+`NodeStyle` in full: presentation (`surface`, `foreground`, `borderTone`,
+`borderWidth`, `radius`, `elevation`), typography (`fontFamily`, `fontSize`,
+`fontWeight`, `fontStyle`, `fontVariationSettings`, `lineHeight`,
+`letterSpacing`, `textAlign`, `textDecoration`), layout (`gap`, `padding`,
+`justify`, `align`, `direction`, `wrap`, `alignSelf`, `size`, `width`,
+`minWidth`, `maxWidth`, `height`, `minHeight`, `maxHeight`, `aspectRatio`,
+`overflow`, `hidden`). All of it is writable from Element Code. Quick Properties
+cover the layout subset plus `hidden`; the token-backed keys are deliberately
+code-only, because they carry design-system semantics that a free-text field
+would invite authors to bypass.
+
+### Elements
+
+| Field | Target-state surface |
+|---|---|
+| `type` | Palette; Structure section for a representation switch |
+| `name` | Structure section (free text, or a select over the field contract) |
+| `props` | Element Code; Quick Properties for the common ones |
+| `defaultValue` | Element Code (`element.defaultValue`) — no Quick Property |
+| `validation` | Element Code; Quick Property for `required` only |
+| `bindings` | Logic tab and the per-property *fx* buttons; Element Code |
+| `visibleWhen` | Element Code (`element.visibleWhen`), full grammar |
+| `elementCode` | Element Code dialog |
+| `children` | Canvas / Outline |
+
+### Page root
+
+| Field | Target-state surface |
+|---|---|
+| `enterSubmits` | Page Root Code (`page.enterSubmits`) |
+| `style`, `responsive` | Page Root Code, Quick Properties |
+| `pageCode`, `rootCode`, `stateCode` | Their own editors |
+| `translations` | Translations tab |
+| `children` | Canvas / Outline |
+| `schemaVersion` | Builder-managed — **named exception** |
+| `style.width`, `style.height` | Not authorable — **named exception** |
+
+## Named exceptions
+
+Each states what it costs.
+
+### The page is exactly its host container
+
+Size values on the page root are dropped, and the root offers no size fields.
+The page is one element inside the host's viewport, and the host container owns
+its box; `overflow` stays authorable and defaults to `auto`. The contract for
+the host is that the container must have a determinable height — for `body`
+that means `html, body { height: 100% }`.
+
+**Cost:** a document cannot make itself taller than its host. That is the
+intent: a page that fights its container breaks in every second embedding.
+
+### Structure is not code
+
+`type`, `name`, `id` and `children` are authored visually, never by Element
+Code — the runtime patch deliberately drops them. A program that could rename
+or retype its own node would break every binding and Page Code reference that
+points at it, at render time, with no way for the builder to see it coming.
+
+**Cost:** generating elements from data is not possible per element. The
+`repeat` element covers the case that motivates it.
+
+### Identity is builder-managed
+
+`id` is a UUID the builder assigns; `schemaVersion` is the wire format. A
+hand-picked id collides, and a hand-picked version lies about the shape of the
+document.
+
+**Cost:** none for authors. Existing ids are preserved — the builder only
+assigns missing ones.
+
+### Composition metadata is repository-owned
+
+`composition` and `compositionOrigins` record which reusable definition a
+subtree came from and at which pinned version. Written by the Compositions
+library, stripped by `compilePageCompositions()` before runtime delivery, never
+hand-edited.
+
+**Cost:** hand-editing them detaches an instance from its definition. The
+builder then treats the subtree as ordinary nodes.
+
+### Legacy ingest may rewrite the document
+
+A document from an older `schemaVersion` is migrated on entry. This is the one
+place where rule 2 does not hold, and it is bounded to documents the current
+builder could not otherwise open.
+
+**Cost:** a v1–v4 document saved by this builder comes back as v5. Round-trips
+within one version rewrite nothing.
+
+### Host CSS never reaches the document
+
+There is no way for a document to carry a CSS class or a stylesheet. Styling is
+`NodeStyle` per node, `CoarTheme` for brand colours, radii and fonts, and the
+`visual-markup` element for free-form decoration inside its sealed iframe.
+
+`config.stylePresets` used to be a fourth channel — a host-registered catalogue
+of named classes the author could pick from. It was removed: the author who
+builds a page owns the realm it renders in, so the restriction protected
+nobody, and a class name written into a document couples it to one application's
+stylesheet forever. A leftover `stylePreset` key in an old document is reported
+as a warning, never stripped.
+
+**Cost:** a vendor cannot ship a catalogue of ready-made looks. If that becomes
+a product requirement, it is a new feature with its own design — not a revival
+of this one.
+
+### Host data has one channel
+
+Everything the host knows travels through `runtimeContext`, allow-listed by
+`config.contextFields`. There is no separate view-state input and no named
+preview fixtures: "which screen is this right now" is ordinary host data, and
+a fixture was a bundle of the very props the host already passes.
+
+A context field may declare `values: string[]`, and the condition editor then
+offers them as a dropdown instead of a free-text box. That is what makes a
+host state, tier or status authorable without a second mechanism carrying it.
+
+Three channels remain, each with one owner: `runtimeContext` (host), Page State
+via `definePageState` (the page author), and the field values — `defaultValue`
+authored, `initialValues` supplied by the host and winning over it.
+
+**Cost:** a host wanting an "empty / typical / 50 items" preview picker builds
+it in its own chrome and binds the chosen sample to `previewContext`. The
+builder no longer draws that control.
+
+### The document is not policed
+
+There is no way for a host to pin a node as present, placed or visually
+untouchable. `config.requiredNodes` did that and was removed: a page author
+owns the realm the page renders in, and the mechanism did not hold anyway — a
+locked node still vanished when the container above it was hidden, with the
+document reporting no issue.
+
+**Cost:** a host that must guarantee a notice — a compliance line on a consent
+screen — enforces it where activation happens. The IDP contract already puts
+publication behind trusted server validation; that check runs on the document
+about to go live and cannot be reached from the browser.
+
+### Token-backed style keys are code-only
+
+`surface`, `radius`, `elevation` and the typography keys have no Quick
+Property. They carry design-system semantics: a token name picked in passing
+next to the canvas is how a page ends up with six subtly different card looks.
+Element Code still writes them, so nothing is out of reach.
+
+**Cost:** changing a card's surface needs the code editor. Deliberate friction.
+
+## Open gaps
+
+These violate the rules and are not exceptions.
+
+### Blocking the removal of properties mode
+
+| Gap | Evidence | Consequence |
+|---|---|---|
+| `visibleWhen` has no code-mode control | The Visibility section is legacy-only | Conditions become text-only. Acceptable under rule 1, but it is the single most-used non-style property. |
+| Element inspectors are legacy-only | Only `visual-markup` sets `inspectorInCodeMode` | Every per-element prop not covered by a Quick Property becomes text-only: `heading.level`, `note.variant`, `otp.length`, `select.options`, `button.icon`/`validates`/`default`, `image.alt`/`assetId`, `repeat.*`, action wiring. |
+
+### Renderer beyond the builder
+
+| Gap | Evidence | Consequence |
+|---|---|---|
+| `repeat.maxItems` is not authorable anywhere | Renderer clamps to it (default 100, ceiling 500); no inspector field | A list longer than 100 items truncates and the author cannot say otherwise |
+| `repeat.itemAlias` is not authorable | Only read, to label the binding picker | Cosmetic; the alias is stuck at its default |
+| `feedback.emptyText` exists in the schema and nothing reads it | Neither renderer nor inspector | Dead field: implement it or remove it |
+
+### Rule 2
+
+| Gap | Evidence |
+|---|---|
+| Normalization heals instead of reporting | Duplicate names renamed, ids reassigned, heading levels clamped, legacy containers converted, non-object children dropped — on `v-model` assignment, initial value and JSON apply alike |
+
+### Legacy-mode wording, dying with the mode
+
+The Visibility section tells the author to "edit it in the JSON tab" for an
+`in` condition and for an `equals` against a multi-value field, and its operator
+list omits `in` / `notIn` although `conditions.ts` evaluates both. All three
+live only in properties mode. They are wrong today — Element Code expresses all
+of it — but they disappear with the mode rather than needing their own fix.