Overview
Status: Available, audited schema · Kind: package · Tier: premium · Bundle: operations · Contexts: admin, console · Product group: Capell Operations
This page is the consolidated implementation overview for the Diagnostics package. It is extracted from the package README, service providers, migrations, config files, routes, resources, models, actions, and the shared Capell ERD notes where available.
What This Package Adds
Section titled “What This Package Adds”Diagnostics adds operational diagnostics for cache, configuration drift, migrations, packages, registries, queues, permissions, setup health, and Tailwind build status.
- Command palette admin page.
- System health admin pages.
- Developer tools dashboard page.
- Permission audit report.
- Queue health report.
- Health widgets for cache, content, migrations, registry, setup, packages, and Tailwind.
- Secure command palette discovery, execution, feedback, and audit logging for developer tools, system health, queue health, and trusted
capell:*Artisan operations.
Developer Notes
Section titled “Developer Notes”Keeps diagnostics in actions and data objects so admin pages can show health information without hard-coded checks in the UI.
- DiagnosticsServiceProvider and AdminServiceProvider register admin pages and widgets.
- AdminServiceProvider registers
CapellArtisanPaletteCommandProviderandDiagnosticsPaletteCommandProviderthrough thecapell.diagnostics.command-palette-providertag. - Command palette actions discover providers dynamically, authorize commands, validate parameters, execute navigation or Artisan commands, and record audit runs.
- Actions build each health report.
- Data objects describe report rows and dashboard state.
- FailedJob model supports queue reporting.
- CommandPaletteRun model records command palette execution history.
Operational Notes
Section titled “Operational Notes”Helps operators and agencies see setup problems before they become publishing or deployment issues.
- Adds admin pages for developer diagnostics.
- Adds dashboard widgets.
- Adds the
command_palette_runsaudit table. - No public routes are registered by this package.
Data And Retention
Section titled “Data And Retention”- This package owns the
command_palette_runstable for command palette audit history. - It reads existing Laravel and Capell state such as config, migrations, failed jobs, permissions, packages, registries, and Tailwind outputs.
Screenshot Plan
Section titled “Screenshot Plan”- Developer tools dashboard.
- Health widgets on the admin dashboard.
Pitfalls
Section titled “Pitfalls”- Some checks depend on host-app conventions and may need configuration.
- Queue health needs access to failed job data.
- Permission audit output is only useful when permissions are registered.
Verification
Section titled “Verification”- Run
vendor/bin/pest packages/diagnostics/testswhen package tests exist. - Run the relevant host-app migration or package install flow in a disposable database.
- Open the listed admin or frontend surface and compare it with the screenshot plan.
Package Manifest
Section titled “Package Manifest”- Composer name:
capell-app/diagnostics - Product group: Capell Operations
- Kind: package
- Tier: premium
- Bundle: operations
- Contexts:
admin,console - Requires:
capell-app/core,capell-app/admin - Optional dependencies: None listed.
Admin Surfaces
Section titled “Admin Surfaces”- DiagnosticsPage (packages/diagnostics/src/Filament/Pages/DiagnosticsPage.php, slug
diagnostics) - CommandPalettePage (packages/diagnostics/src/Filament/Pages/CommandPalettePage.php, slug
diagnostics/command-palette) - PermissionAuditPage (packages/diagnostics/src/Filament/Pages/PermissionAuditPage.php, slug
dashboard-dashboard_reports/permission-audit) - QueueHealthPage (packages/diagnostics/src/Filament/Pages/QueueHealthPage.php, slug
dashboard-dashboard_reports/queue-health) - SystemHealthPage (packages/diagnostics/src/Filament/Pages/SystemHealthPage.php, slug
system-health)
Commands
Section titled “Commands”- Dynamic command palette metadata for trusted
capell:*Artisan commands. - Dynamic discovery happens through the
capell.diagnostics.command-palette-providerprovider tag. - Commands can be navigation or Artisan commands and can define abilities, confirmation level, and parameters.
- Confirmation is required for cache, clear, and publish commands.
- Install, setup, upgrade, and demo commands are marked dangerous.
Command Palette
Section titled “Command Palette”diagnostics.open: opens DiagnosticsPage.diagnostics.system-health: opens SystemHealthPage.diagnostics.queue-health: opens QueueHealthPage.artisan.capell:*: generated from available Capell Artisan commands, including command parameters.
Diagnostics owns the command palette UI, server-side authorization, validation, execution, notifications, and audit log records. Custom packages can add commands by implementing the package command provider contract and tagging the provider with capell.diagnostics.command-palette-provider.
Routes And Config
Section titled “Routes And Config”- None proven in this package directory.
Permissions And Gates
Section titled “Permissions And Gates”- Gate: CacheHealthWidgetAbstract:
admin,super_admin - Gate: ConfigDriftWidgetAbstract:
super_admin - Gate: ContentHealthWidgetAbstract:
editor,admin,super_admin - Gate: DiagnosticsPage: Gate
accessDiagnostics,viewDiagnostics - Gate: MigrationsHealthWidgetAbstract:
super_admin - Gate: PackagesInstalledWidgetAbstract:
super_admin - Gate: QueueHealthPage: Gate
accessDiagnostics,viewDiagnostics - Gate: RegistryHealthWidgetAbstract:
super_admin - Gate: SetupHealthWidgetAbstract: settings-gated only
- Gate: SiteHealthWidgetAbstract: settings-gated only
- Gate: TailwindBuildStatusWidgetAbstract:
super_admin
Migrations
Section titled “Migrations”create_command_palette_runs_table: stores command id, label, type, user, parameters, status, output, exit code, and executed timestamps.
ERD Excerpt
Section titled “ERD Excerpt”command_palette_runs belongs to an optional user record and records each command palette execution for audit and debugging.
Screenshot Automation
Section titled “Screenshot Automation”Deployment should read screenshots.json, install the package with demo data, resolve each admin surface or frontend URL, and write images to public/docs/screenshots/packages/diagnostics.
- Developer tools dashboard.
- Command palette page.
- System health page.
- Permission audit page.
- Queue health page.
- Health widgets on the admin dashboard.