@agent-native/core 0.30.6 → 0.31.1

package/dist/client/AgentPanel.js

@@ -121,8 +121,6 @@ function useCliSelection(keyPrefix) {
     };
     return [selected, select];
 }
-// Detect dev mode at build time (Vite replaces this)
-const IS_DEV = import.meta.env?.DEV === true;
 // ─── Settings panel components moved to ./settings/ ────────────────────────
 function IconTooltip({ content, children, }) {
     return (_jsx(TooltipPrimitive.Provider, { delayDuration: 250, children: _jsxs(TooltipPrimitive.Root, { children: [_jsx(TooltipPrimitive.Trigger, { asChild: true, children: children }), _jsx(TooltipPrimitive.Portal, { children: _jsxs(TooltipPrimitive.Content, { side: "bottom", sideOffset: 8, className: "z-[300] overflow-hidden rounded-md border border-border bg-popover px-2 py-1 text-[11px] text-foreground shadow-md", children: [normalizeTooltipText(content), _jsx(TooltipPrimitive.Arrow, { className: "fill-popover" })] }) })] }) }));
@@ -648,24 +646,6 @@ function ResizeHandle({ position, onDrag, }) {
     }, [position]);
     return (_jsx("div", { ref: ref, className: cn("relative z-20 shrink-0 w-px touch-none select-none transition-colors", "bg-border hover:bg-accent active:bg-accent"), style: { cursor: "col-resize" } }));
 }
-/**
- * Remounts its children whenever the framework's `refresh-screen` tool is
- * invoked. Used inside AgentSidebar so the main content area re-fetches
- * without disturbing the chat sidebar's in-flight state.
- *
- * Two mechanisms work together here:
- *
- *  1. Before the remount, every react-query cache entry is marked stale
- *     via `invalidateQueries({ refetchType: "none" })`. This does NOT
- *     trigger a refetch on its own, so active queries elsewhere (chat
- *     sidebar, left nav) keep their current data — they'll refetch only
- *     on their next natural trigger.
- *  2. The React `key` then bumps, unmounting and remounting the subtree.
- *     On remount, child components re-subscribe to their queries, see
- *     the data is stale, and refetch — regardless of configured
- *     `staleTime`. This is what makes the dashboard pick up the agent's
- *     edits even when the query uses `staleTime: 30_000` or similar.
- */
 /**
  * Syncs the current URL (pathname + search + hash) to application_state
  * under `__url__`, and processes one-shot URL-update commands the agent
@@ -839,6 +819,24 @@ function URLSync({ browserTabId }) {
     }, [command, navigate, queryClient, setUrlQueryKey]);
     return null;
 }
+/**
+ * Remounts its children whenever the framework's `refresh-screen` tool is
+ * invoked. Used inside AgentSidebar so the main content area re-fetches
+ * without disturbing the chat sidebar's in-flight state.
+ *
+ * Two mechanisms work together here:
+ *
+ *  1. Before the remount, every react-query cache entry is marked stale
+ *     via `invalidateQueries({ refetchType: "none" })`. This does NOT
+ *     trigger a refetch on its own, so active queries elsewhere (chat
+ *     sidebar, left nav) keep their current data — they'll refetch only
+ *     on their next natural trigger.
+ *  2. The React `key` then bumps, unmounting and remounting the subtree.
+ *     On remount, child components re-subscribe to their queries, see
+ *     the data is stale, and refetch — regardless of configured
+ *     `staleTime`. This is what makes the dashboard pick up the agent's
+ *     edits even when the query uses `staleTime: 30_000` or similar.
+ */
 function ScreenRefreshBoundary({ children }) {
     const key = useScreenRefreshKey();
     const queryClient = useQueryClient();