mosaic-headless 1.32.0 → 1.32.1

package/SKILL.md

@@ -5,7 +5,7 @@ description: |
 license: "MIT"
 metadata:
   author: "moksa (https://moksaweb.com)"
-  version: "1.32.0"
+  version: "1.32.1"
   homepage: "https://github.com/Moksa1123/mosaic-headless"
 ---
 

package/assets/templates/platforms/claude-ai.json

@@ -20,7 +20,7 @@
     "description": "Build and modify Mosaic Pro (Nextend) sites by writing the underlying data model directly - no visual editor, no DOM. Query the real surface (122 node types, 181 node properties, 98 style properties, 53 style states, 151 element classes, 74 dynamic variables, 114 REST routes, 23 tables) instead of guessing, with every node type placed on a live site one at a time and asserted against the delivered HTML, every style and node property swept against the compiled CSS and markup, and 569 responsive declarations checked against the stylesheet the site actually served.",
     "license": "MIT",
     "author": "moksa (https://moksaweb.com)",
-    "version": "1.32.0"
+    "version": "1.32.1"
   },
   "loaderBehaviour": "Upload via Settings -> Skills -> Upload. Claude.ai parses SKILL.md frontmatter and surfaces the skill in your library. The extraction tool (extract-block-schema.php) needs a live WP-CLI connection and won't run in the sandbox; use it from a local terminal against your own site instead.",
   "uploadSteps": [

package/assets/templates/platforms/claude-code.json

@@ -20,7 +20,7 @@
     "description": "Build and modify Mosaic Pro (Nextend) sites by writing the underlying data model directly - no visual editor, no DOM. Query the real surface (122 node types, 181 node properties, 98 style properties, 53 style states, 151 element classes, 74 dynamic variables, 114 REST routes, 23 tables) instead of guessing, with every node type placed on a live site one at a time and asserted against the delivered HTML, every style and node property swept against the compiled CSS and markup, and 569 responsive declarations checked against the stylesheet the site actually served.",
     "license": "MIT",
     "author": "moksa (https://moksaweb.com)",
-    "version": "1.32.0"
+    "version": "1.32.1"
   },
   "loaderBehaviour": "Auto-loads on session start when SKILL.md frontmatter parses successfully.",
   "verified": true,

package/assets/templates/platforms/codex-cli.json

@@ -20,7 +20,7 @@
     "description": "Build and modify Mosaic Pro (Nextend) sites by writing the underlying data model directly - no visual editor, no DOM. Query the real surface (122 node types, 181 node properties, 98 style properties, 53 style states, 151 element classes, 74 dynamic variables, 114 REST routes, 23 tables) instead of guessing, with every node type placed on a live site one at a time and asserted against the delivered HTML, every style and node property swept against the compiled CSS and markup, and 569 responsive declarations checked against the stylesheet the site actually served.",
     "license": "MIT",
     "author": "moksa (https://moksaweb.com)",
-    "version": "1.32.0"
+    "version": "1.32.1"
   },
   "loaderBehaviour": "Confirmed (2026-07-11): Codex CLI natively supports the SKILL.md spec. Place SKILL.md under .codex/skills/<name>/ (project) or ~/.codex/skills/<name>/ (personal) and Codex loads the name+description at session start, then the full body on demand. A parallel, broader convention .agents/skills/ (searched from cwd up to repo root, then ~/.agents/skills/) also exists across multiple tools - if your Codex CLI version prioritizes that path instead, mirror the same SKILL.md there.",
   "verified": true,

package/assets/templates/platforms/copilot.json

@@ -20,7 +20,7 @@
     "description": "Build and modify Mosaic Pro (Nextend) sites by writing the underlying data model directly - no visual editor, no DOM. Query the real surface (122 node types, 181 node properties, 98 style properties, 53 style states, 151 element classes, 74 dynamic variables, 114 REST routes, 23 tables) instead of guessing, with every node type placed on a live site one at a time and asserted against the delivered HTML, every style and node property swept against the compiled CSS and markup, and 569 responsive declarations checked against the stylesheet the site actually served.",
     "license": "MIT",
     "author": "moksa (https://moksaweb.com)",
-    "version": "1.32.0"
+    "version": "1.32.1"
   },
   "loaderBehaviour": "CHANGED as of 2026-07-11: GitHub Copilot added a proper '.github/skills/' Agent Skills directory (December 2025), alongside the older single-file .github/copilot-instructions.md convention. This config targets the new skills-directory form. If your Copilot version predates this (pre Dec 2025), use the instructions-append fallback instead (see fallback below).",
   "fallback": {

package/assets/templates/platforms/gemini-cli.json

@@ -20,7 +20,7 @@
     "description": "Build and modify Mosaic Pro (Nextend) sites by writing the underlying data model directly - no visual editor, no DOM. Query the real surface (122 node types, 181 node properties, 98 style properties, 53 style states, 151 element classes, 74 dynamic variables, 114 REST routes, 23 tables) instead of guessing, with every node type placed on a live site one at a time and asserted against the delivered HTML, every style and node property swept against the compiled CSS and markup, and 569 responsive declarations checked against the stylesheet the site actually served.",
     "license": "MIT",
     "author": "moksa (https://moksaweb.com)",
-    "version": "1.32.0"
+    "version": "1.32.1"
   },
   "loaderBehaviour": "CHANGED as of 2026-07-11: Gemini CLI now natively supports the same SKILL.md standard as Claude Code and Codex CLI - the same directory-based skill works unmodified. Gemini CLI discovers skills in this precedence order: built-in, extension skills, ~/.gemini/skills/ (personal), .gemini/skills/ (project, shared via version control). At session start Gemini injects each discovered skill's name+description into the system prompt and calls activate_skill when a task matches.",
   "verified": true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mosaic-headless",
-  "version": "1.32.0",
+  "version": "1.32.1",
   "description": "AI-agent skill: build Mosaic Pro (Nextend) WordPress sites by writing the underlying data model directly - 23 custom tables, no visual editor, no DOM. Every node type, style property and node property swept against a live install and asserted on the delivered HTML and compiled CSS. Installs into Claude Code, Cursor, Codex CLI, Gemini CLI, Copilot, Continue, Windsurf and Claude.ai.",
   "keywords": [
     "wordpress",

package/references/design-system.md

@@ -213,18 +213,34 @@ only the slots that differ:
                "cs-name": {"text": "…"}}}
 ```
 
-**An instance's ids are prefixed with the instance's own attrID.** The definition's
-`cs-card` becomes `cs-0-cs-card`, `cs-1-cs-card`, and so on, so the definition's
-attrID is a SUFFIX in the delivered page and `getElementById` on it finds nothing.
-Address instances with `[id$="-cs-card"]`.
+**Mosaic copies the definition's ids into every instance verbatim; `build_site.py`
+is what makes them unique.** Mosaic has no id-prefixing of its own - an element's
+id is its `attrID` (`ElementAttrID.php`), and every instance renders the
+definition's nodes with the definition's attrIDs, so two instances put every id
+into the document twice. `build_site.py`'s override pass writes an `attrID` of
+`<instance attrID>-<definition attrID>` into each instance's override node: the
+definition's `cs-card` becomes `cs-0-cs-card`, `cs-1-cs-card`, and so on, so the
+definition's attrID is a SUFFIX in the delivered page and `getElementById` on it
+finds nothing. Address instances with `[id$="-cs-card"]`.
+
+Until 1.32.1 that pass ran only for instances that HAD overrides, so an instance
+written with none - a contact block placed as-is in a footer and in a page body -
+kept the definition's ids, and a client build found every one of them twice. It runs
+for every instance now; measured on the demo, two override-less instances gave
+`ft-a-cs-card` and `ft-b-cs-card` and no duplicates. A tool other than
+`build_site.py` that writes instances has to do the same, or accept duplicate ids.
 
 Four more things a build that leans on components runs into:
 
-- **The instance element itself carries no id.** Its `attrID` exists only as that
-  prefix, so a selector aimed at the instance's own attrID finds nothing - aim at
-  `<instance>-<definition id>`. Two instances given the SAME attrID (or none) get
-  the same prefix and so duplicate every id inside; give each a distinct attrID. A
-  page with two `case-card` instances, `cs-0` and `cs-1`, measured zero duplicates.
+- **The instance element itself carries no id.** Its `attrID` exists only as the
+  prefix `build_site.py` writes, so a selector aimed at the instance's own attrID
+  finds nothing - aim at `<instance>-<definition id>`. Two instances given the SAME
+  attrID (or none) get the same prefix and so duplicate every id inside; give each a
+  distinct attrID.
+- **A loop repeats ids too, and that one is Mosaic's.** Every `loop-item` renders
+  the same attrIDs, so a list of six cards carries six of each id (reported from a
+  client build). `ElementAttrID.php` evaluates an attrID per loop item, which is the
+  hook for making them unique; that has not been measured here.
 - **A component's id is its name.** `build_site.py` derives it with
   `uuid5(COMPONENT_NAMESPACE, name)` so rebuilds update the same row; renaming the
   key in `site["components"]` therefore creates a new component and leaves the old

package/tools/build_site.py

@@ -262,7 +262,11 @@ def apply_overrides(client, instance, key, uses, comps, envelope="templateDocume
     `strpos($type, 'component-instance')`, and strpos returns 0 for a needle at
     offset 0, so the condition is false for every instance there will ever be.
     """
-    wanted = [u for u in uses if u.get("overrides")]
+    # EVERY instance, not only the ones with overrides: this pass is also what gives
+    # each instance's inner nodes their own ids (below). Filtering on overrides left
+    # an instance without any as a verbatim copy of the definition's ids - a client
+    # build put the same component in a footer and a page body and got every id twice.
+    wanted = list(uses)
     if not wanted:
         return 0
     doc = unwrap(client.get(instance), envelope)