Shared Panel Routing

Every panel UI must reuse the routing engine from panel core, including complexPanel, simplePanel, and headless panels. Core owns route collection, permissions, query handling, and router execution. The consuming UI supplies layouts, loading and not-found views, component presentation, and special-page composition. Do not create a second routing engine in a UI repository or runnable.

Philosophy

A different panel design must not require a separate routing implementation.

Fix

Compose the shared core router and supply UI-specific presentation through its supported composition interface.