Pure permission logic for admin access control.

This namespace contains pure business logic for determining admin access
permissions. All functions are pure (no side effects) and testable without
database or session state.

Week 1 Implementation:
- Simple role-based access control (RBAC) using :admin role
- All permission checks verify user has :admin role
- Foundation for more complex permissions in Week 2+

Week 2+ Roadmap:
- Entity-level permissions (some entities admin-only, others viewable by all)
- Action-level permissions (some users can view but not edit)
- Field-level permissions (hide sensitive fields for certain roles)
- Permission groups and hierarchies

Key responsibilities:
- Determine if user can access admin interface
- Determine if user can perform operations on entities
- Filter entity lists based on permissions
- Provide permission metadata for UI rendering

Pure functions for database schema introspection and entity configuration.

This namespace contains pure business logic for transforming raw database
metadata into UI-friendly entity configurations. All functions are pure
(no side effects) and testable without database connections.

Key responsibilities:
- Parse database column metadata into field configurations
- Infer appropriate UI widgets from database types
- Detect relationships and foreign keys
- Merge auto-detected configuration with manual overrides
- Generate sensible defaults for labels and field ordering

Admin UI components using Hiccup for server-side HTML generation.

This namespace is a thin FACADE: the implementation lives in focused
sibling namespaces under `boundary.admin.core.ui.*`. Every public function
consumers rely on is re-exported here so `admin-ui/entity-list-page`,
`ui/format-field-label`, etc. keep resolving unchanged.

Implementation namespaces:
- `boundary.admin.core.ui.base`           — shared URL/field/column primitives
- `boundary.admin.core.ui.layout`         — shell, sidebar, home, error pages, dialog
- `boundary.admin.core.ui.list`           — entity list page, table, rows, search
- `boundary.admin.core.ui.filters`        — advanced filter builder
- `boundary.admin.core.ui.inline-editing` — inline (double-click) cell editing
- `boundary.admin.core.ui.detail`         — detail/edit page, form, field grouping

See each impl namespace for the original docstrings on these functions.

Shared admin UI primitives used across multiple ui.* sections.

Leaf namespace: URL helpers, field-value rendering, list-column width
heuristics, and small formatting/label utilities. Must NOT require any
other boundary.admin.core.ui.* implementation namespace — it is the
dependency root that the focused sections build on.

Entity detail/edit page components: form widgets, field grouping, the
entity form, parent-context/related-records tables, and the detail page.

Pure Hiccup generators. Depends on `base` for URL and field helpers.

Advanced filter builder components for admin entity lists.

Pure Hiccup generators for the filter UI: operator selection per field
type, value inputs, filter rows, and the overall filter builder.

Inline (double-click) table-cell editing components.

Pure Hiccup generators for the editable-cell display mode, the inline
edit form, and the inline edit form with a validation error.

Admin shell/layout, error pages, confirmation dialog, and URL utilities.

Pure Hiccup generators for the admin chrome: sidebar navigation, the
collapsible shell + topbar, the dashboard home, 403/404 error pages, the
delete-confirmation modal, and the `build-table-url` helper.

Entity list-page components: search form, table rows, table, and the
complete list page (toolbar + filter builder + table).

Pure Hiccup generators. Depends on `base` for URL helpers, field-value
rendering, and column sizing, and on `filters` for the filter builder.