@ohhwells/bridge 0.1.113 → 0.1.114

package/README.md

@@ -23,6 +23,14 @@ npm install @ohhwells/bridge
 
 ---
 
+## Template conventions and checker
+
+The full contract a template must follow for this bridge (every `data-ohw-*` attribute, editable mode, key and section rule, brand CSS variable, form, map, carousel and socials pattern, and the reserved names templates must never author) is documented and mechanically checked in the public repo **[TheFlowOps-Eng/vibecoder-guidelines](https://github.com/TheFlowOps-Eng/vibecoder-guidelines)**. External vibecoders and the templates repo's CI run the same checker. The steps below cover only the plumbing.
+
+Changing what templates must do (a new attribute, mode, injected attribute or key, hook, detection rule, CSS variable or version gate) is not complete until that repo's docs (`2-CONVENTIONS.md`), constants (`check/lib/constants.mjs`), rule files (`check/rules/`) or AI specs (`check/ai/rules/`) reflect it. See `CLAUDE.md` in this repo for the checklist.
+
+---
+
 ## Template setup (required steps)
 
 ### 1. Import styles

package/dist/index.cjs

@@ -22763,7 +22763,7 @@ function OhhwellsBridge() {
       postToParent2({
         type: "ow:ready",
         version: "1",
-        bridgeVersion: "0.1.112",
+        bridgeVersion: "0.1.113",
         path: pathname,
         nodes: collectEditableNodes(editContentRef.current),
         sections

package/dist/index.js

@@ -22696,7 +22696,7 @@ function OhhwellsBridge() {
       postToParent2({
         type: "ow:ready",
         version: "1",
-        bridgeVersion: "0.1.112",
+        bridgeVersion: "0.1.113",
         path: pathname,
         nodes: collectEditableNodes(editContentRef.current),
         sections

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ohhwells/bridge",
-  "version": "0.1.113",
+  "version": "0.1.114",
   "private": false,
   "type": "module",
   "main": "./dist/index.cjs",