Public Core Boundary

Parts, runnables, and runnable parts must access headless panel core through its public panel module, or panelTests for test helpers. Keep test exports in the separate panelTests barrel, never in production panel barrels. Never reach into panel core files through relative paths, absolute paths, file URLs, or deep panel imports. This includes tests, fixtures, re-exports, dynamic imports, and filesystem access. Internal file access is permitted inside panel core itself.

Philosophy

Consumers depend on stable public contracts rather than the core repository layout.

Correct

import { List } from 'panel'
import row from './row.jsx'

Incorrect

import verify from '../../../../../panel/test/verifyRecordViewTests.js'
export { List } from 'panel/components/list.jsx'

Fix

Use panel for runtime functionality and panelTests for test helpers. If a required capability is missing, expose it through the appropriate supported core interface instead of importing an internal file.