@unoverse-platform/studio 0.1.71 → 0.1.73

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unoverse-platform/studio",
-  "version": "0.1.71",
+  "version": "0.1.73",
   "type": "module",
   "description": "Unoverse Studio: the local authoring app. Reads your own rx/ folder, no backend.",
   "scripts": {

package/vendor/sdk/lib/core/types.ts

@@ -111,6 +111,49 @@ export interface UnoverseNode {
    *  exclusive, instead of a `visibleWhen` repeated on every branch. Each branch is a
    *  normal subtree (commonly a `{ "$include": "step-x" }`, expanded at load). */
   cases?: Record<string, UnoverseNode>;
+
+  // ── Declared 2026-08-23 ────────────────────────────────────────────────────────
+  // These were all in live use across shipped definitions, and the renderer handled
+  // them, but this interface never declared them. Definitions arrive as YAML and are
+  // parsed as unknown, so they never met `UnoverseNode` and nothing objected — the
+  // interface quietly fell behind what ships. Found by the per-primitive contract work
+  // (UNOVERSE_CONFORMANCE §2a); the guard is `packages/base/tests/primitive-contract-drift.test.ts`,
+  // which now fails if this list and `vocabulary.mjs` disagree again.
+
+  /** Ref: the atom to compose. Authoring-time only — the server expands every `Ref`
+   *  before serving, so a rendered tree never contains one. */
+  ref?: string;
+  /** Ref: literals written INTO the atom. A bind whose field is a `with` key becomes a
+   *  hardcoded attribute, and a truthy key satisfies a matching `visibleWhen` guard. */
+  with?: Record<string, unknown>;
+  /** Each: the LEGACY spelling of `template`, still read. New definitions write `template`. */
+  app?: UnoverseNode;
+  /** Button: a literal label, when the content is not composed from `children` and not
+   *  bound via `bind.label`. */
+  label?: string;
+  /** STATE-OWNED SIZING: this panel's own width, and therefore its contribution to the
+   *  app's total. A named size from the org's `styles/semantic/app-sizes`, a raw CSS
+   *  width, or `flex` to take the remaining host space. One declaration per panel. */
+  appWidth?: string;
+  /** Box: text-selection behaviour for the subtree. */
+  selection?: string;
+  /** Markdown: render links in the surrounding text colour rather than the link colour,
+   *  for a block that is already inside a coloured surface. */
+  inheritLinkColor?: boolean;
+  /** Input: cap the number of characters accepted. */
+  maxLength?: number;
+  /** Input: render a multi-line field rather than a single line. */
+  multiline?: boolean;
+  /** Input: visible rows when `multiline` is set. */
+  rows?: number;
+  /** Input: the on-screen keyboard hint handed to the platform (`numeric`, `tel`, …).
+   *  Distinct from `inputType`, which says what the field IS. */
+  inputMode?: string;
+  /** Input: the autofill hint handed to the platform (`one-time-code`, `email`, …). */
+  autoComplete?: string;
+  /** Input: move to the next field as soon as this one is full — the OTP behaviour,
+   *  which is only meaningful alongside `maxLength`. */
+  advanceOnFill?: boolean;
 }
 
 export interface UnoverseDefinition {

package/vendor/skills/unoverse-create/references/app.md

@@ -43,8 +43,8 @@ states:
 - **Top-level order IS the priority ladder**, base first. The app can be in ONE
   state at a time: it walks the list top-down and enters the first of its states that
   ANY hosted component currently matches. The ladder is DERIVED from the tree; never
-  author `stateOrder` (that field survives only as the legacy form for apps
-  without a tree).
+  author `stateOrder`. It is now a LINT ERROR beside a tree (`file.mjs`), after two
+  client components ran on one for months because nothing enforced the rule.
 - **Nesting IS containment, enforced by compilation.** A declared base substate
   (`welcome`) is stripped from every non-base arrangement; no hand-written guard ever
   polices it. The substate's file keeps its own condition (`visibleWhen: isEmpty`).
@@ -76,8 +76,9 @@ design/<project>/apps/<name>/
     products.yaml  #   state "products" → core + cards rail
     detail.yaml    #   state "detail"  → core + full record page
   components/      # app-local partials (core, header, composer-bar, turns…)
-  states/          # base substates' drawings (welcome): included plainly by the
-                   # chrome, own condition inside, containment compiled from the tree
+                   # NO states/ folder: every drawing lives in layouts/. A substate's
+                   # drawing is axis-prefixed (step-register, callState-idle) and named
+                   # by its `layout:` key, so layouts/ reads at a glance.
 ```
 
 Each layout = a complete arrangement: `$include: components/core` + that state's