/**
 * FieldRow — a single column row inside an EntityNode.
 *
 * Reference: `docs/plans/20260501-universal-wysiwyg-schema-ux-v1.00W.md`
 * §3.6 item 1 (column-level handles).
 *
 * Each row exposes FOUR React Flow Handles (left-target, left-source,
 * right-target, right-source) so the user can drag from any column to any
 * other column's handle. Handle IDs follow the canonical pattern
 * `${entityId}.${fieldId}.${side}-${kind}` so SchemaCanvas#onConnect can parse
 * them back into `source_field_id` / `target_field_id` on the relation row.
 *
 * Phase 2 edit affordance:
 *   - A real `<button>` child (pencil icon) with `aria-label="Edit field X"`
 *     is rendered on editable rows. This is the canonical focusable element
 *     assistive tech and Playwright use to trigger the edit flow.
 *   - A whole-row `onDoubleClick` handler fires the same event for mouse
 *     users who remember the "double-click to edit" convention.
 *   - The outer `<div>` does NOT have `role="button"`. ARIA forbids
 *     interactive descendants (React Flow Handles) inside a role=button,
 *     and the browser cannot compute an accessible name from a wrapper
 *     that also contains truncated text + badges. The inner button is the
 *     correct accessibility surface.
 *   - The outer `<div>` DOES carry `role="listitem"`. EntityNode wraps the
 *     rows in a `role="list"` container, and `list` requires `listitem`
 *     children — without it every entity card raised a critical axe
 *     `aria-required-children` violation (crm7#1770).
 *
 * Handle accessibility (crm7#1770):
 *   The four Handles are `aria-hidden="true"`, NOT labelled. @xyflow/react
 *   12.11.2 renders `<Handle>` as a role-less `<div>` and spreads caller
 *   props straight onto it (node_modules/@xyflow/react/dist/esm/index.js —
 *   the Handle return is `jsx("div", { "data-handleid": ..., ...rest })`;
 *   it adds NO aria-label of its own). `aria-label` on a generic-role
 *   element is prohibited by ARIA and is never exposed by assistive tech,
 *   so the labels we used to pass were inert — they announced nothing while
 *   producing ~14k serious axe `aria-prohibited-attr` violations on
 *   /settings/schema-builder (four per field row, on every entity).
 *   `aria-hidden` states the truth: these are mouse-drag-only affordances
 *   with no keyboard or AT path. `title` is retained for the mouse tooltip.
 *   NOTE: there is currently NO accessible (keyboard/AT) way to create a
 *   relationship — RelationshipConfigDialog only opens from a pointer-drag
 *   `onConnect`. That gap is real and tracked separately; hiding the
 *   handles does not shrink it, it just stops the DOM from claiming an
 *   affordance assistive tech could never reach.
 *
 * Memoised — large entities with 30+ fields would otherwise re-render every
 * row on every node drag.
 */
import type { EntityField } from '../schemas.js';
/**
 * Row shape for a column inside an EntityNode. Aliased to the Zod-derived
 * `EntityField` type so that the FieldRow view and the Zod schema source of
 * truth never drift. If you need to extend the field shape, update
 * `EntityFieldSchema` in `schemas.ts`.
 */
export type FieldRowField = EntityField;
export interface FieldRowProps {
    entityId: string;
    field: FieldRowField;
    isSystemEntity?: boolean;
}
export declare function handleSizing(zoom: number): {
    hit: number;
    dot: number;
};
declare function FieldRowImpl({ entityId, field, isSystemEntity }: FieldRowProps): import("react").JSX.Element;
export declare const FieldRow: import("react").MemoExoticComponent<typeof FieldRowImpl>;
export {};
//# sourceMappingURL=FieldRow.d.ts.map