@archie/devtools 0.0.24 → 0.0.26

package/dist/client/client.js

@@ -9595,15 +9595,14 @@ function installDomMetaSanitizer() {
     _origError(msg, ...rest);
   };
 }
-installDomMetaSanitizer();
 
 // src/client/useArchieDevToolsRuntime.ts
-installDomMetaSanitizer();
 function useArchieDevToolsRuntime({
   router,
   inspector,
   inspectorOptions
 }) {
+  installDomMetaSanitizer();
   const stableOptionsKey = JSON.stringify(inspectorOptions ?? null);
   const inspectorOptionsRef = (0, import_react20.useRef)(inspectorOptions);
   inspectorOptionsRef.current = inspectorOptions;

package/dist/client/client.mjs

@@ -9560,15 +9560,14 @@ function installDomMetaSanitizer() {
     _origError(msg, ...rest);
   };
 }
-installDomMetaSanitizer();
 
 // src/client/useArchieDevToolsRuntime.ts
-installDomMetaSanitizer();
 function useArchieDevToolsRuntime({
   router,
   inspector,
   inspectorOptions
 }) {
+  installDomMetaSanitizer();
   const stableOptionsKey = JSON.stringify(inspectorOptions ?? null);
   const inspectorOptionsRef = useRef11(inspectorOptions);
   inspectorOptionsRef.current = inspectorOptions;

package/dist/inspector.standalone.js

@@ -424,6 +424,35 @@
         }
       }
 
+      // ARCH-906 — the DURABLE `data-agent-id` anchors on the ANCESTOR chain,
+      // innermost first. This is a DOM-attribute walk, not a fiber walk (no twin
+      // in fiber-bridge.ts to mirror): it reads the semantic anchors the render
+      // stamps (`row:<id>`, `data:<Entity>`, `screen:<slug>`, `job:<id>`) and
+      // forwards them so the host can resolve a slice DATA cell.
+      //
+      // WHY THE ANCESTOR CHAIN, and why it is not `editorInstance`. Clicking a
+      // table cell resolves the INNERMOST collection — the `<td key={c.key}>` map
+      // — so `editorInstance.fiberKey` already carries the FIELD. The ROW it
+      // belongs to lives one level up on `<tr data-agent-id="row:<id>">`, and the
+      // ENTITY on a container above that (`data-agent-id="data:<Entity>"`).
+      // Neither can be the innermost collection key, so the host cannot recover
+      // them from `editorInstance` — it needs the ancestor anchors verbatim.
+      // Strict ancestors only (the selected node's own anchor is already in
+      // `attributes`); the host picks the nearest `row:`/`data:` by namespace.
+      var MAX_ANCHOR_CHAIN = 24
+      function collectAncestorAnchors(el) {
+        var anchors = []
+        var node = el && el.parentElement ? el.parentElement : null
+        for (var depth = 0; node && depth < MAX_ANCHOR_CHAIN; depth++) {
+          if (node.nodeType === 1 && typeof node.getAttribute === "function") {
+            var id = node.getAttribute("data-agent-id")
+            if (typeof id === "string" && id !== "") anchors.push(id)
+          }
+          node = node.parentElement
+        }
+        return anchors
+      }
+
       if (window._inspectorSharedTargetObserver) {
         try {
           window._inspectorSharedTargetObserver.disconnect()
@@ -1655,6 +1684,30 @@
       // misread by the host as a stale mode (see runtimeBridgeHandler).
       var hostCommandedEditorMode = "off"
 
+      // ARCH-886 — per-page runtime feature-detection for the unified
+      // inspect+arrange coexistence. This inspector build is served fresh
+      // from the CDN (same URL, overwritten in place — see
+      // docs/deploy-order.md) to EVERY published prototype, old and new
+      // alike, so it cannot assume the PAGE it is currently inspecting was
+      // built with a @archie/devtools new enough to understand
+      // `set-design-mode`'s unified role. The page's own DndProvider
+      // registers `window.__ARCHIE_DESIGN_MODE__` synchronously on mount —
+      // well before a user can trigger SET_EDITOR_MODE from the host — so
+      // its presence at message-handling time is an accurate, live,
+      // per-page signal (no version number or capability handshake needed).
+      // Pages built before this bridge existed (pre-PR#12, e.g. the 0.0.21
+      // release) already handle the legacy `set-design-mode` command (that
+      // handler predates the bridge and is unchanged by it) — so
+      // unconditionally dispatching it there does not no-op, it ARMS that
+      // page's design-mode/arrange overlay with no selection routing,
+      // producing a second, uncoordinated hit-area layer on top of the
+      // inspector's own hover/selection UI. Gating on the bridge avoids
+      // that: an old page just gets clean inspect-only behavior, same as
+      // before unification shipped.
+      function pageSupportsUnifiedDesignMode() {
+        return typeof window.__ARCHIE_DESIGN_MODE__ !== "undefined"
+      }
+
       function setEditorModeFromHost(mode, options) {
         var historyMode =
           options && options.hostControlledHistory ? "host" : "local"
@@ -1675,11 +1728,14 @@
         hostCommandedEditorMode = mode === "inspect" || mode === "design" ? mode : "off"
 
         if (mode === "inspect") {
-          // Unified mode: visual editor (inspect) + arrange (design) coexist.
-          // The arrange overlay stays passive until the inspector publishes a
+          // Unified mode: visual editor (inspect) + arrange (design) coexist
+          // — gated on pageSupportsUnifiedDesignMode() (ARCH-886). The
+          // arrange overlay stays passive until the inspector publishes a
           // single-element selection (via publishSelectionToDesignMode), at
           // which point it lights up the resize/drag controls on that element.
-          dispatchHostCommand({ type: "set-design-mode", enabled: true })
+          if (pageSupportsUnifiedDesignMode()) {
+            dispatchHostCommand({ type: "set-design-mode", enabled: true })
+          }
           if (isInspecting) {
             // Recovery re-send (focus/visibility/online): the session is
             // already live. Activating again would wipe the user's current
@@ -2240,6 +2296,13 @@
             editorMeta ? editorMeta.element : element
           ),
           editorInstance: resolveInstanceIdentity(element),
+          // ARCH-906 — the ancestor `data-agent-id` chain (innermost first). A
+          // slice DATA cell needs the ROW id (`row:<id>` on the `<tr>`) and the
+          // ENTITY (`data:<Entity>` above it), neither of which is the innermost
+          // collection key `editorInstance` carries. Plain string data, so an
+          // already-published copy of this script forwards it unchanged through
+          // structured clone; a host that does not read it is unaffected.
+          ancestorAnchors: collectAncestorAnchors(element),
           computedStyles: {
             display: computed.display,
             position: computed.position,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@archie/devtools",
-  "version": "0.0.24",
+  "version": "0.0.26",
   "description": "DevTools for Archie generated applications - Route synchronization and editor communication",
   "repository": {
     "type": "git",