@ohhwells/bridge 0.1.52 → 0.1.53-next.145

package/README.md

@@ -194,12 +194,23 @@ For links whose **destination URL** is edited in the canvas, use a plain `<a>` w
 </a>
 ```
 
+Section / body CTAs use the same two-phase select + Edit-link toolbar with `data-ohw-role="button"` (preferred). `navbar-button` remains supported as an alias for nav header CTAs:
+
+```tsx
+<a href="/contact" data-ohw-href-key="hero-cta-href" data-ohw-role="button" data-ohw-drag-disabled="true">
+  <span data-ohw-editable="text" data-ohw-key="hero-cta-label">
+    Get started
+  </span>
+</a>
+```
+
 | Attribute | Purpose |
 |-----------|---------|
 | `data-ohw-href-key` | Storage key for the link destination |
 | `href` | Default URL for SSR / first paint |
 | `data-ohw-key` + `data-ohw-editable` on inner span | Editable label text |
-| `data-ohw-role="navbar-button"` | Navbar CTA — two-phase select + link-action toolbar |
+| `data-ohw-role="button"` | Section CTA — two-phase select + link-action toolbar (no reorder/More) |
+| `data-ohw-role="navbar-button"` | Alias of `button` for navbar / header CTAs |
 
 The bridge persists and restores `href` values (including after React re-renders). No template-side wrapper component is required.
 
@@ -344,11 +355,40 @@ import { LinkPopover } from "@ohhwells/bridge";
 The iframe bridge reports page sections on `ow:ready`:
 
 ```json
-{ "type": "ow:ready", "version": "1", "nodes": [...], "sections": [{ "id": "hero", "label": "Hero" }] }
+{ "type": "ow:ready", "version": "1", "bridgeVersion": "0.1.50", "nodes": [...], "sections": [{ "id": "hero", "label": "Hero" }] }
 ```
 
+`version` is the protocol version; `bridgeVersion` is the npm package version (inlined at build time), letting the editor detect sites running an older bridge and gate version-dependent features (e.g. AI prompting) gracefully.
+
 Templates must mark sections with `data-ohw-section` (and optional `data-ohw-section-label`).
 
+### Section-scoped content collection (AI prompt context)
+
+The editor can request a single section's editable content (edit mode only):
+
+```json
+// editor → iframe
+{ "type": "ow:collect-section", "sectionId": "hero" }
+
+// iframe → editor
+{ "type": "ow:section-nodes", "sectionId": "hero", "found": true,
+  "nodes": [{ "key": "hero-headline", "type": "text/rich", "text": "..." }],
+  "rect": { "top": 0, "left": 0, "width": 1280, "height": 720 } }
+```
+
+- `found` is `false` (with empty `nodes`, `rect: null`) when no `[data-ohw-section="<id>"]` exists on the current page.
+- `rect` is the section element's document-relative bounding box — the editor uses it to draw the in-flight overlay over just the target section.
+- The returned set contains pure section content only: structural keys (`__ohw_*`), carousel/video-setting/meta nodes, and keyless editables are never included.
+- Node `type` is normalized to the set `image | bg-image | video | link | plain | text/rich | text` (unknown template-declared types become `text`).
+
+`ow:enter-edit` (iframe → editor, sent when the user clicks into an editable) also carries the enclosing section so the editor can offer that section as the AI prompt target:
+
+```json
+{ "type": "ow:enter-edit", "key": "hero-headline", "sectionId": "hero", "sectionLabel": "Hero" }
+```
+
+`sectionId`/`sectionLabel` are `null` for editables outside any `[data-ohw-section]` (label also when `data-ohw-section-label` is absent).
+
 ### Local link-editor testing (dev fixtures)
 
 Without the canvas editor parent, add `ohw-fixtures=1` to the edit URL. This preloads Re:Bound pages and sections into the link popover: