nodality 1.3.15 → 1.3.17

package/scripts/generate-schema.mjs

@@ -361,6 +361,15 @@ for (const type of TYPES) {
   // Read off the element by every mapper regardless of component.
   for (const p of ["type", "id"]) contributed(p, MAPPER);
 
+  // Options the BASE CLASS applies to every component built on it, after the
+  // component's own set() — currently `loop`. Component scans never see them,
+  // because they are read in animator.js. Credited only where the type has no
+  // parameter of that name already: `video` has its own boolean `loop`.
+  const ANIMATOR = join(ROOT, "layout", "animator.js");
+  const onAnimator = files.some((f) => { try { return /extends\s+Animator\b/.test(readFileSync(f, "utf8")); } catch { return false; } });
+  // And only where the element's options reach the component at all.
+  if (onAnimator && forwardsElement) for (const p of ["loop"]) if (!params.has(p)) contributed(p, ANIMATOR);
+
   // NOTE. A `settable` flag was attempted here and removed. The question it
   // was meant to answer -- which of these parameters an AUTHOR can set on the
   // element, as opposed to which the components READ -- is real and still
@@ -385,8 +394,15 @@ for (const type of TYPES) {
       const unit = (UNIT_BY_TYPE[type] && UNIT_BY_TYPE[type][name])
         || where.map((f) => (UNIT_BY_FILE.get(f) || {})[name]).find(Boolean)
         || UNIT_GLOBAL[name];
+      // Where the name is read. "mapper": the type reads it off the element
+      // by name — its own vocabulary. "component": only reachable because the
+      // mapper forwards the element to a component that reads it — real, but
+      // inherited, and the bulk of a composite's list. Reported so a reader
+      // (or get_schema) can put the type's own parameters first.
+      const via = where.includes(MAPPER) ? "mapper" : "component";
       return {
         name,
+        via,
         ...(unit ? { unit } : {}),
         ...(description ? { description } : {}),
         ...(deprecated ? { deprecated } : {}),

package/skills/nodality/SKILL.md

@@ -42,6 +42,10 @@ drift. If the MCP is not configured, add it:
 { "mcpServers": { "nodality": { "command": "npx", "args": ["nodality", "mcp"] } } }
 ```
 
+Or let the CLI write it: `npx nodality mcp --register` in the project, or
+`--root=<folder>` when sessions start in a folder above it — the tools only
+appear in sessions started where `.mcp.json` lives.
+
 1. **`list_ops` first.** Never guess an op name, a parameter, an easing
    name, a transition preset, or an element type. One call returns all
    of them as data.
@@ -58,7 +62,8 @@ drift. If the MCP is not configured, add it:
    against real ids and E itself is validated. The report never throws;
    repair from its `did-you-mean` suggestions and re-validate until
    clean.
-4. **`preview` to render.** It writes a self-contained HTML file through
+4. **`preview` to render.** Pass `viewport: "desktop"` to see the wide side of anything chosen by width (the default is a phone); the report lists ids that rendered `empty` instead of leaving a blank page to look finished.
+    It writes a self-contained HTML file through
    the jsdom prerenderer. Know the boundary: the file is prerendered DOM
    and morph scaffolding only and carries no runtime, so raster effects
    and transitions will not run from it. To see them, put the pair in a
@@ -76,6 +81,8 @@ does not do what you wrote:
 |---|---|
 | `BAD_PARAM_VALUE` | the value is not the shape the parameter takes — `width: 7` is not a CSS length, `mar: 7` is not `[{a: 7}]`. As an *error* where the value is provably inert; as a warning otherwise. |
 | `PARAM_NOT_ON_TYPE` | a real parameter name that THIS type does not read, so it is accepted and dropped — `keySet` on a `table`. |
+| `PARAM_INERT` | a parameter the type DOES list, and is known to ignore (the library's conformance baseline) — `size` on a `p`, `color` on a `checkbox`. The hint says what to use instead. |
+| `STORE_AFTER_PRODUCT` / `NO_STORE` | a commerce `product` placed before the page's `store`, or with none: it renders empty. |
 
 `get_schema <type>` carries a `unit` on every parameter whose shape the
 source declares, which is where those checks come from, and a
@@ -198,6 +205,11 @@ A complete navigation graph is one node:
   element/op (extend the library), or the `keySet` option on an element
   (`keySet: { key, value }`) for one custom CSS property. Note the
   spelling: `keySet`, capital S.
+- **No CSS in the page either.** No `<style>` rules, no `@keyframes`, no
+  stylesheet files. Anything that moves on its own takes `loop` on the element —
+  `loop: { keyframes: [{…}, {…}], duration }` runs forever through the Web
+  Animations API and holds still for reduced motion. If something cannot be
+  expressed, extend the library.
 - **Elements take `text`, never `value`.**
 - **Every element that a node targets needs an `id`.** Short and stable
   (`"hero"`, `"topnav"`); ids are the joint between the two arrays and
@@ -314,6 +326,9 @@ document is untrusted input.
 
 ## Verifying your work
 
+- **Read `FAINT_TEXT` from `check_page`.** It reports small text that passes
+  WCAG and still reads faint (APCA), the usual case on mid-tone backgrounds.
+  Fix with weight, a lighter or darker ground, or size; not by ignoring it.
 - **Verify a morph by progress, not by DOM presence.** The destination
   view is inserted before capture begins, so "the element exists" passes
   even when the transition hangs. Assert that the animation *progressed*