@object-ui/react 17.5.0 → 17.6.0

package/dist/context/HostNavigationContext.js

@@ -0,0 +1,65 @@
+import { jsx as _jsx } from "react/jsx-runtime";
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+/**
+ * HostNavigationContext — the host's own in-app navigate, offered to renderers.
+ *
+ * A published renderer package cannot navigate correctly on its own. Its only
+ * dependency-free option is a browser-level navigation
+ * (`window.location.assign`), which resolves a rooted path such as `/thanks`
+ * against the ORIGIN. Under a host mounted at a sub-path — the framework CLI
+ * configures one for every embedded deployment — that leaves the application
+ * entirely. This is objectui#4989 defect 4, and the same class as
+ * objectui#4190 / #4181.
+ *
+ * The host is the only party that knows its mount, so the host supplies the
+ * navigate. This context is that seam: **optional injection**, ruled by the
+ * maintainer on 2026-08-17. Two mechanisms were rejected in that ruling and are
+ * named here so they are not re-proposed:
+ *
+ *   - **router-presence sniffing** (a renderer reading React Router's context
+ *     when it happens to be there) — implicit magic, and it forces every
+ *     renderer that wants mount-awareness to import `react-router`;
+ *   - **a `react-router` peer requirement** — it imposes module resolution on
+ *     router-less consumers. Two real ones exist in this repo (`apps/site`,
+ *     `packages/plugin-view`), and a published renderer's whole property is
+ *     that it drops into ANY React application.
+ *
+ * Explicit injection keeps every renderer dependency-free and puts
+ * mount-awareness on the type face where a host can see it is missing.
+ *
+ * ## Absent is a supported state, not a degraded one
+ *
+ * The default value is an empty object, so `useHostNavigation()` outside a
+ * provider answers `{ navigate: undefined }` and never throws. A consumer reads
+ * it as "no host navigate — fall back to whatever this renderer did before",
+ * which for a router-less host is already the correct behaviour: with no
+ * router there is no basename, so origin-rooted resolution is right. The seam
+ * changes what a MOUNTED host gets, and changes nothing else.
+ *
+ * ## Relationship to the other navigation seams in this package
+ *
+ * `DrillNavigationContext.openRecordList` is a SEMANTIC navigation — "show me
+ * the records behind this aggregate" — that only the console can turn into a
+ * URL. `ActionProvider`'s `onNavigate` is the ActionRunner's handler for
+ * `type: 'navigate'` actions, reachable only through an action dispatch. This
+ * one is neither: it is the plain "go to this already-resolved in-app path"
+ * that a renderer holds a destination for and cannot perform correctly itself.
+ * All three are supplied by the same shell from the same router `navigate`.
+ */
+import { createContext, useContext } from 'react';
+export const HostNavigationContext = createContext({});
+export const HostNavigationProvider = ({ value, children }) => (_jsx(HostNavigationContext.Provider, { value: value, children: children }));
+/**
+ * Consume the host-provided in-app navigate. Answers `{}` (i.e. `navigate`
+ * undefined) when no host wired one — that is a supported state, see the module
+ * docblock.
+ */
+export function useHostNavigation() {
+    return useContext(HostNavigationContext);
+}

package/dist/context/RelatedRecordActionsContext.d.ts

@@ -61,6 +61,21 @@ export interface RelatedRecordHandlers {
      * argument is needed here (增).
      */
     onCreate?: () => void;
+    /**
+     * [#4646] Offer "+ New", but GREYED — the `userActions.create.disabledWhen`
+     * verdict for the scope this toolbar sits in (the host parent record on a
+     * record page's related list).
+     *
+     * A separate channel from omitting {@link onCreate} because hidden and
+     * disabled are different answers, exactly as they are for the row Edit/Delete
+     * predicates (objectui#2614) and for the record header's (objectui#4419 /
+     * PR #4515): `visibleWhen` decides whether the affordance exists at all,
+     * `disabledWhen` decides whether the existing affordance can be pressed. The
+     * host still supplies `onCreate` in the disabled case, so the button keeps
+     * its label and tooltip and the user can see that creating is a thing this
+     * list does — just not right now.
+     */
+    createDisabled?: boolean;
     /** Open an edit form for an existing child record (改). */
     onEdit?: (recordId: string | number, record?: unknown) => void;
     /**

package/dist/context/index.d.ts

@@ -1,12 +1,13 @@
-export * from './SchemaRendererContext';
-export * from './PreviewModeContext';
-export * from './ActionContext';
-export * from './ThemeContext';
-export * from './NotificationContext';
-export * from './DndContext';
-export * from './AppShellContext';
-export * from './RecordContext';
-export * from './InlineEditContext';
-export * from './DiscussionContext';
-export * from './DrillNavigationContext';
-export * from './RelatedRecordActionsContext';
+export * from './SchemaRendererContext.js';
+export * from './PreviewModeContext.js';
+export * from './ActionContext.js';
+export * from './ThemeContext.js';
+export * from './NotificationContext.js';
+export * from './DndContext.js';
+export * from './AppShellContext.js';
+export * from './RecordContext.js';
+export * from './InlineEditContext.js';
+export * from './DiscussionContext.js';
+export * from './DrillNavigationContext.js';
+export * from './HostNavigationContext.js';
+export * from './RelatedRecordActionsContext.js';

package/dist/context/index.js

@@ -1,12 +1,13 @@
-export * from './SchemaRendererContext';
-export * from './PreviewModeContext';
-export * from './ActionContext';
-export * from './ThemeContext';
-export * from './NotificationContext';
-export * from './DndContext';
-export * from './AppShellContext';
-export * from './RecordContext';
-export * from './InlineEditContext';
-export * from './DiscussionContext';
-export * from './DrillNavigationContext';
-export * from './RelatedRecordActionsContext';
+export * from './SchemaRendererContext.js';
+export * from './PreviewModeContext.js';
+export * from './ActionContext.js';
+export * from './ThemeContext.js';
+export * from './NotificationContext.js';
+export * from './DndContext.js';
+export * from './AppShellContext.js';
+export * from './RecordContext.js';
+export * from './InlineEditContext.js';
+export * from './DiscussionContext.js';
+export * from './DrillNavigationContext.js';
+export * from './HostNavigationContext.js';
+export * from './RelatedRecordActionsContext.js';

package/dist/element-data-source/ElementDataSourceGate.d.ts

@@ -59,6 +59,17 @@
  * therefore leaves `limit` unmapped rather than parking it somewhere plausible,
  * and the gap is recorded at the call site instead of being papered over here.
  *
+ * ## A block with no ADAPTER fails loudly too (objectui#5378)
+ *
+ * The section below is about an unresolvable view NAME. The coarser failure —
+ * no runtime adapter reached the block at all — used to render an empty shell
+ * in exactly the same silence, and that is what `requiresDataSource` +
+ * {@link NoDataSourcePanel} now report. Measured on the published
+ * getting-started guide: all five of its blocks resolved no adapter, fetched
+ * nothing, and said nothing. The two panels are deliberately the same shape;
+ * they answer "which view?" and "which data source?", and an author who sees
+ * either one is being told where to look.
+ *
  * ## An unresolvable `view` fails loudly
  *
  * When the named view does not exist the gate renders a configuration error
@@ -69,7 +80,7 @@
  */
 import * as React from 'react';
 import { type ElementDataSourceConfig } from '@object-ui/core';
-import { type ElementDataSourceStatus } from '../hooks/useElementDataSource';
+import { type ElementDataSourceStatus } from '../hooks/useElementDataSource.js';
 /**
  * Where a block's row cap lives. Three spellings are real in this repo and each
  * is the ONLY one its block reads: `list-view`/`object-grid` read
@@ -169,6 +180,51 @@ export declare function ElementDataSourceErrorPanel({ testId, title, message, }:
  * would flash a configuration error on every mount.
  */
 export declare function ElementDataSourceLoadingPanel({ testId, }: Pick<ElementDataSourceStatusPanelProps, 'testId'>): React.ReactElement;
+/**
+ * The adapter this block would use, resolved the one way every block in the
+ * family resolves it: an explicit value first, the `SchemaRendererProvider`
+ * context second.
+ *
+ * The `isElementDataSourceConfig` guard is the same one
+ * {@link useElementDataSourceSchema} applies — a host handing us the spec
+ * BINDING under this name is handing us metadata, not an adapter, and counting
+ * it as one is how "no data source" reads as "resolved".
+ *
+ * `T` is what the CALLER expects to have been injected, and the assertion is
+ * the caller's, not this hook's: an adapter arrives here as a `dataSource` prop
+ * or a context value that nothing in this package can narrow, so the type has
+ * to be declared by whoever knows which interface their block consumes. Leave
+ * it off and you get `unknown`, which is the honest default.
+ */
+export declare function useResolvedDataSource<T = unknown>(explicit?: unknown): T | undefined;
+/**
+ * The author-facing sentence a block with no adapter says out loud.
+ *
+ * One wording for the whole object-bound family, because the reader's mistake
+ * is the same one every time and the fix is the same one every time: the
+ * adapter is injected by an ANCESTOR (`SchemaRendererProvider`), so nothing
+ * written on the block itself can supply it. Naming the block and the object
+ * it was about to read is what turns "nothing happened" into an address.
+ */
+export declare function noDataSourceMessage(blockKey: string, objectName?: unknown): string;
+/**
+ * The "this block resolved no adapter" panel — objectui#5378 item 2, and the
+ * #5349 shape it belongs to.
+ *
+ * Until this existed, a block that resolved no adapter rendered an EMPTY SHELL:
+ * `object-grid` painted a header-only table, `object-form` a field-less card,
+ * `detail-view` nothing at all — no error, no warning, no empty state that
+ * explained itself. Measured on the published getting-started guide
+ * (`content/docs/guide/building-crud-app.md`), every one of its five blocks was
+ * in that state and the page reported success while fetching nothing.
+ *
+ * The empty shell is the defect, not a side effect of it: it is indistinguishable
+ * from "the query ran and matched no rows", which is the reading an author (very
+ * often an AI author) takes, and it points at the DATA when the fault is in the
+ * WIRING one level up. Same posture as {@link ElementDataSourceErrorPanel}: the
+ * metadata is answerable, so the answer is rendered where the author can see it.
+ */
+export declare function NoDataSourcePanel({ testId, title, message, }: ElementDataSourceStatusPanelProps): React.ReactElement;
 export interface ElementDataSourceGateProps<S> {
     /** The block's schema node. */
     schema: S;
@@ -180,6 +236,23 @@ export interface ElementDataSourceGateProps<S> {
     testId: string;
     /** Heading for the unresolvable-view panel. */
     errorTitle?: string;
+    /**
+     * Whether THIS placement cannot do its job without a runtime adapter — when
+     * true and none resolves, the gate renders {@link NoDataSourcePanel} instead
+     * of the block (objectui#5378 item 2).
+     *
+     * The gate cannot compute this and does not try. "Needs an adapter" is a
+     * statement about the block's own fallbacks, and every block in the family
+     * has different ones: an `object-grid` carrying inline `data` rows needs no
+     * adapter, an `object-form` with inline `customFields` needs none, a
+     * `detail-view` handed a `data` record needs none. A predicate guessed HERE
+     * would paint a configuration error over a block that is working, which is a
+     * worse failure than the silence this replaces — so the call site, which
+     * knows its own fallbacks, states it.
+     */
+    requiresDataSource?: boolean;
+    /** Explanation for the no-adapter panel; see {@link noDataSourceMessage}. */
+    noDataSourceMessage?: string;
     /**
      * Renders the block with the bound schema. Called during the gate's own
      * render, so it must RETURN AN ELEMENT and never call hooks itself — the
@@ -196,4 +269,4 @@ export interface ElementDataSourceGateProps<S> {
  * against a half-resolved query is how a page shows a wider answer than the one
  * that was authored.
  */
-export declare function ElementDataSourceGate<S>({ schema, mapping, dataSource, testId, errorTitle, children, }: ElementDataSourceGateProps<S>): React.ReactElement | null;
+export declare function ElementDataSourceGate<S>({ schema, mapping, dataSource, testId, errorTitle, requiresDataSource, noDataSourceMessage: noDataSourceText, children, }: ElementDataSourceGateProps<S>): React.ReactElement | null;

package/dist/element-data-source/ElementDataSourceGate.js

@@ -60,6 +60,17 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
  * therefore leaves `limit` unmapped rather than parking it somewhere plausible,
  * and the gap is recorded at the call site instead of being papered over here.
  *
+ * ## A block with no ADAPTER fails loudly too (objectui#5378)
+ *
+ * The section below is about an unresolvable view NAME. The coarser failure —
+ * no runtime adapter reached the block at all — used to render an empty shell
+ * in exactly the same silence, and that is what `requiresDataSource` +
+ * {@link NoDataSourcePanel} now report. Measured on the published
+ * getting-started guide: all five of its blocks resolved no adapter, fetched
+ * nothing, and said nothing. The two panels are deliberately the same shape;
+ * they answer "which view?" and "which data source?", and an author who sees
+ * either one is being told where to look.
+ *
  * ## An unresolvable `view` fails loudly
  *
  * When the named view does not exist the gate renders a configuration error
@@ -70,7 +81,8 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
  */
 import * as React from 'react';
 import { isElementDataSourceConfig, mergeFilterNodes, } from '@object-ui/core';
-import { useElementDataSource, } from '../hooks/useElementDataSource';
+import { useElementDataSource, } from '../hooks/useElementDataSource.js';
+import { SchemaRendererContext } from '../context/SchemaRendererContext.js';
 const readLimit = (base, key) => {
     if (key === 'pagination.pageSize')
         return base.pagination?.pageSize;
@@ -174,6 +186,64 @@ export function ElementDataSourceErrorPanel({ testId, title = 'This component’
 export function ElementDataSourceLoadingPanel({ testId, }) {
     return (_jsx("div", { className: "p-2 text-sm text-muted-foreground animate-pulse", role: "status", "aria-live": "polite", "data-testid": `${testId}-resolving-view`, children: "Loading view\u2026" }));
 }
+/**
+ * The adapter this block would use, resolved the one way every block in the
+ * family resolves it: an explicit value first, the `SchemaRendererProvider`
+ * context second.
+ *
+ * The `isElementDataSourceConfig` guard is the same one
+ * {@link useElementDataSourceSchema} applies — a host handing us the spec
+ * BINDING under this name is handing us metadata, not an adapter, and counting
+ * it as one is how "no data source" reads as "resolved".
+ *
+ * `T` is what the CALLER expects to have been injected, and the assertion is
+ * the caller's, not this hook's: an adapter arrives here as a `dataSource` prop
+ * or a context value that nothing in this package can narrow, so the type has
+ * to be declared by whoever knows which interface their block consumes. Leave
+ * it off and you get `unknown`, which is the honest default.
+ */
+export function useResolvedDataSource(explicit) {
+    const context = React.useContext(SchemaRendererContext);
+    const named = isElementDataSourceConfig(explicit) ? undefined : explicit;
+    return (named ?? context?.dataSource ?? undefined);
+}
+/**
+ * The author-facing sentence a block with no adapter says out loud.
+ *
+ * One wording for the whole object-bound family, because the reader's mistake
+ * is the same one every time and the fix is the same one every time: the
+ * adapter is injected by an ANCESTOR (`SchemaRendererProvider`), so nothing
+ * written on the block itself can supply it. Naming the block and the object
+ * it was about to read is what turns "nothing happened" into an address.
+ */
+export function noDataSourceMessage(blockKey, objectName) {
+    const target = typeof objectName === 'string' && objectName.trim().length > 0
+        ? `“${objectName}”`
+        : 'its object';
+    return (`“${blockKey}” has no data source, so it cannot read ${target}. ` +
+        `Inject one from an ancestor — <SchemaRendererProvider dataSource={…}> from ` +
+        `@object-ui/react — or hand this block a dataSource of its own.`);
+}
+/**
+ * The "this block resolved no adapter" panel — objectui#5378 item 2, and the
+ * #5349 shape it belongs to.
+ *
+ * Until this existed, a block that resolved no adapter rendered an EMPTY SHELL:
+ * `object-grid` painted a header-only table, `object-form` a field-less card,
+ * `detail-view` nothing at all — no error, no warning, no empty state that
+ * explained itself. Measured on the published getting-started guide
+ * (`content/docs/guide/building-crud-app.md`), every one of its five blocks was
+ * in that state and the page reported success while fetching nothing.
+ *
+ * The empty shell is the defect, not a side effect of it: it is indistinguishable
+ * from "the query ran and matched no rows", which is the reading an author (very
+ * often an AI author) takes, and it points at the DATA when the fault is in the
+ * WIRING one level up. Same posture as {@link ElementDataSourceErrorPanel}: the
+ * metadata is answerable, so the answer is rendered where the author can see it.
+ */
+export function NoDataSourcePanel({ testId, title = 'No data source resolved', message, }) {
+    return (_jsxs("div", { className: "p-4 border border-red-500 rounded text-red-500 bg-red-50 my-2", role: "alert", "data-testid": `${testId}-no-data-source`, children: [_jsx("p", { className: "font-medium", children: title }), message ? _jsx("p", { className: "text-sm mt-1", children: message }) : null] }));
+}
 /**
  * Wrap an object-bound block so its `dataSource` binding reaches the keys it
  * reads, and so the two non-final resolution states render once, the same way,
@@ -183,8 +253,17 @@ export function ElementDataSourceLoadingPanel({ testId, }) {
  * against a half-resolved query is how a page shows a wider answer than the one
  * that was authored.
  */
-export function ElementDataSourceGate({ schema, mapping, dataSource, testId, errorTitle, children, }) {
+export function ElementDataSourceGate({ schema, mapping, dataSource, testId, errorTitle, requiresDataSource, noDataSourceMessage: noDataSourceText, children, }) {
     const bound = useElementDataSourceSchema(schema, mapping, dataSource);
+    const adapter = useResolvedDataSource(dataSource);
+    // Reported BEFORE the view state, because with no adapter every downstream
+    // answer is a symptom of this one: `useElementDataSource` cannot list the
+    // object's saved views either, so a block carrying a `view` would otherwise
+    // report "this data source cannot list the saved views" — true, and pointing
+    // at the view name instead of at the missing injection.
+    if (requiresDataSource && adapter == null) {
+        return _jsx(NoDataSourcePanel, { testId: testId, message: noDataSourceText });
+    }
     if (bound.status === 'missing') {
         return _jsx(ElementDataSourceErrorPanel, { testId: testId, title: errorTitle, message: bound.error });
     }

package/dist/hooks/index.d.ts

@@ -5,38 +5,38 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-export * from './useExpression';
-export * from './useFilterScope';
-export * from './useActionRunner';
-export * from './useNavigationOverlay';
-export * from './usePageVariables';
-export * from './usePageVariableActionBridge';
-export * from './useViewData';
-export * from './useElementDataSource';
-export * from './useDynamicApp';
-export * from './useDiscovery';
-export * from './useFocusTrap';
-export * from './useFocusManagement';
-export * from './useKeyboardShortcuts';
-export * from './useCrudShortcuts';
-export * from './useReducedMotion';
-export * from './useAnimation';
-export * from './useDensityMode';
-export * from './useViewSharing';
-export * from './useClientNotifications';
-export * from './useOffline';
-export * from './usePerformance';
-export * from './usePerformanceBudget';
-export * from './usePageTransition';
-export * from './useViewTransition';
-export * from './useETagCache';
-export * from './useSchemaPersistence';
-export * from './useGlobalUndo';
-export * from './useDebugMode';
-export * from './useActionEngine';
-export * from './useActionTextLocalizer';
-export * from './useCapabilityGate';
-export * from './useDatasetDimensionLabels';
-export * from './useDataRefresh';
-export * from './usePageAssignment';
-export * from './useRecordSearch';
+export * from './useExpression.js';
+export * from './useFilterScope.js';
+export * from './useActionRunner.js';
+export * from './useNavigationOverlay.js';
+export * from './usePageVariables.js';
+export * from './usePageVariableActionBridge.js';
+export * from './useViewData.js';
+export * from './useElementDataSource.js';
+export * from './useDynamicApp.js';
+export * from './useDiscovery.js';
+export * from './useFocusTrap.js';
+export * from './useFocusManagement.js';
+export * from './useKeyboardShortcuts.js';
+export * from './useCrudShortcuts.js';
+export * from './useReducedMotion.js';
+export * from './useAnimation.js';
+export * from './useDensityMode.js';
+export * from './useViewSharing.js';
+export * from './useClientNotifications.js';
+export * from './useOffline.js';
+export * from './usePerformance.js';
+export * from './usePerformanceBudget.js';
+export * from './usePageTransition.js';
+export * from './useViewTransition.js';
+export * from './useETagCache.js';
+export * from './useSchemaPersistence.js';
+export * from './useGlobalUndo.js';
+export * from './useDebugMode.js';
+export * from './useActionEngine.js';
+export * from './useActionTextLocalizer.js';
+export * from './useCapabilityGate.js';
+export * from './useDatasetDimensionLabels.js';
+export * from './useDataRefresh.js';
+export * from './usePageAssignment.js';
+export * from './useRecordSearch.js';

package/dist/hooks/index.js

@@ -5,46 +5,46 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-export * from './useExpression';
+export * from './useExpression.js';
 // Session scope for filter placeholders ({current_user_id}/{current_org_id}).
-export * from './useFilterScope';
-export * from './useActionRunner';
-export * from './useNavigationOverlay';
-export * from './usePageVariables';
-export * from './usePageVariableActionBridge';
-export * from './useViewData';
+export * from './useFilterScope.js';
+export * from './useActionRunner.js';
+export * from './useNavigationOverlay.js';
+export * from './usePageVariables.js';
+export * from './usePageVariableActionBridge.js';
+export * from './useViewData.js';
 // PageComponentSchema.dataSource — the spec's per-element data binding.
-export * from './useElementDataSource';
-export * from './useDynamicApp';
-export * from './useDiscovery';
-export * from './useFocusTrap';
-export * from './useFocusManagement';
-export * from './useKeyboardShortcuts';
-export * from './useCrudShortcuts';
-export * from './useReducedMotion';
-export * from './useAnimation';
-export * from './useDensityMode';
-export * from './useViewSharing';
-export * from './useClientNotifications';
-export * from './useOffline';
-export * from './usePerformance';
-export * from './usePerformanceBudget';
-export * from './usePageTransition';
-export * from './useViewTransition';
-export * from './useETagCache';
-export * from './useSchemaPersistence';
-export * from './useGlobalUndo';
-export * from './useDebugMode';
-export * from './useActionEngine';
+export * from './useElementDataSource.js';
+export * from './useDynamicApp.js';
+export * from './useDiscovery.js';
+export * from './useFocusTrap.js';
+export * from './useFocusManagement.js';
+export * from './useKeyboardShortcuts.js';
+export * from './useCrudShortcuts.js';
+export * from './useReducedMotion.js';
+export * from './useAnimation.js';
+export * from './useDensityMode.js';
+export * from './useViewSharing.js';
+export * from './useClientNotifications.js';
+export * from './useOffline.js';
+export * from './usePerformance.js';
+export * from './usePerformanceBudget.js';
+export * from './usePageTransition.js';
+export * from './useViewTransition.js';
+export * from './useETagCache.js';
+export * from './useSchemaPersistence.js';
+export * from './useGlobalUndo.js';
+export * from './useDebugMode.js';
+export * from './useActionEngine.js';
 // The ONE application of `useObjectLabel`'s action resolvers over the three
 // authored strings an action carries (label / confirmText / successMessage).
-export * from './useActionTextLocalizer';
-export * from './useCapabilityGate';
+export * from './useActionTextLocalizer.js';
+export * from './useCapabilityGate.js';
 // The analytics label net's React glue, consumed by BOTH plugin-dashboard's
 // `DatasetWidget` and plugin-report's dataset block (objectui#4389). It lives
 // here rather than in `@object-ui/core` because it reads `SchemaRendererContext`
 // — see the file header for the measured dependency direction.
-export * from './useDatasetDimensionLabels';
-export * from './useDataRefresh';
-export * from './usePageAssignment';
-export * from './useRecordSearch';
+export * from './useDatasetDimensionLabels.js';
+export * from './useDataRefresh.js';
+export * from './usePageAssignment.js';
+export * from './useRecordSearch.js';

package/dist/hooks/useActionEngine.js

@@ -23,7 +23,7 @@
  */
 import { useCallback, useContext, useMemo } from 'react';
 import { ActionEngine, } from '@object-ui/core';
-import { ActionCtxReact } from '../context/ActionContext';
+import { ActionCtxReact } from '../context/ActionContext.js';
 export function useActionEngine(options = {}) {
     const { actions = [], context = {} } = options;
     // When wrapped in an <ActionProvider>, reuse its ActionRunner so that:

package/dist/hooks/useCapabilityGate.js

@@ -23,13 +23,14 @@
  *
  * **Fail-OPEN when unknown.** No runner, no user, no `systemPermissions` array:
  * the action shows. Unknown is not denied, the server is the authority
- * (ADR-0057 D10), and hiding a permitted user's button on missing client data
- * is the worse failure. An EMPTY array is not unknown — it means "holds
- * nothing" and gates normally.
+ * (the framework's ADR-0124 D1 — server enforces, client is courtesy), and
+ * hiding a permitted user's button on missing client data is the worse
+ * failure. An EMPTY array is not unknown — it means "holds nothing" and gates
+ * normally.
  */
 import { useCallback, useContext } from 'react';
-import { ActionCtxReact } from '../context/ActionContext';
-import { usePredicateScope } from './useExpression';
+import { ActionCtxReact } from '../context/ActionContext.js';
+import { usePredicateScope } from './useExpression.js';
 /**
  * The caller's system capabilities, or `undefined` when the host never supplied
  * them (→ callers must fail open).

package/dist/hooks/useClientNotifications.js

@@ -26,8 +26,8 @@
  * server side exists.
  */
 import { useCallback, useContext, useEffect, useRef, useState } from 'react';
-import { SchemaRendererContext } from '../context/SchemaRendererContext';
-import { useNotifications } from '../context/NotificationContext';
+import { SchemaRendererContext } from '../context/SchemaRendererContext.js';
+import { useNotifications } from '../context/NotificationContext.js';
 /* ------------------------------------------------------------------ */
 /*  Helpers                                                           */
 /* ------------------------------------------------------------------ */

package/dist/hooks/useCrudShortcuts.js

@@ -6,7 +6,7 @@
  * LICENSE file in the root directory of this source tree.
  */
 import { useMemo } from 'react';
-import { useKeyboardShortcuts, } from './useKeyboardShortcuts';
+import { useKeyboardShortcuts, } from './useKeyboardShortcuts.js';
 /**
  * Registers standard CRUD keyboard shortcuts using the useKeyboardShortcuts hook.
  *

package/dist/hooks/useDatasetDimensionLabels.js

@@ -61,7 +61,7 @@
 import { useContext, useEffect, useMemo, useState } from 'react';
 import { deriveDimensionLabelMaps, loadDimensionFieldMeta, } from '@object-ui/core';
 import { useSafeFieldLabel } from '@object-ui/i18n';
-import { SchemaRendererContext } from '../context/SchemaRendererContext';
+import { SchemaRendererContext } from '../context/SchemaRendererContext.js';
 /**
  * Resolve one dataset query's dimension field metadata — the LOCALE-FREE half.
  *

package/dist/hooks/useDiscovery.js

@@ -6,7 +6,7 @@
  * LICENSE file in the root directory of this source tree.
  */
 import { useState, useEffect, useContext } from 'react';
-import { SchemaRendererContext } from '../context/SchemaRendererContext';
+import { SchemaRendererContext } from '../context/SchemaRendererContext.js';
 /**
  * The backward-compatible "can I actually use this service?" check
  * (ADR-0076 D12 console slice):

package/dist/hooks/useElementDataSource.js

@@ -21,7 +21,7 @@
  */
 import { useContext, useEffect, useMemo, useState } from 'react';
 import { collectSavedViews, composeElementDataSource, elementDataSourceViewNotFoundMessage, isElementDataSourceConfig, resolveSavedView, } from '@object-ui/core';
-import { SchemaRendererContext } from '../context/SchemaRendererContext';
+import { SchemaRendererContext } from '../context/SchemaRendererContext.js';
 const isRecord = (v) => !!v && typeof v === 'object';
 /**
  * Read every saved view for `object` from the two places they live, in the same
@@ -45,7 +45,10 @@ async function fetchSavedViews(dataSource, object) {
     if (!canReadObjectDef && !canReadOverlay)
         return { capable: false, views: {} };
     const embedded = canReadObjectDef
-        ? dataSource.getObjectSchema(object).then((def) => (isRecord(def) ? (def.listViews ?? def.list_views) : undefined), () => undefined)
+        ? dataSource.getObjectSchema(object).then(
+        // `listViews` is canonical (#5362); the snake leg is a compatibility READ for
+        // stored pre-settlement documents (never censused: objectstack#7917).
+        (def) => (isRecord(def) ? (def.listViews ?? def.list_views) : undefined), () => undefined)
         : Promise.resolve(undefined);
     const overlay = canReadOverlay
         ? dataSource.listViews(object).then((rows) => rows, () => undefined)