audit-panel-types

Auditing Kirby panel types involves comparing Panel augmentation types in kirby-types against Kirby JS and PHP runtime sources using a two-pass swarm. Pass one annotates with @source and reports findings, and pass two verifies each finding and applies fixes.

A two-pass swarm audit for TypeScript panel types is a workflow that first annotates type definitions with @source and generates per-cluster findings, then executes a follow-up pass to verify each finding and apply patches aligning types with the runtime.

Yes, you must provide absolute paths to the kirby-types root and the Kirby root when invoking the audit. These paths are required for the swarm to locate Panel augmentation types and compare them against runtime sources.

Fixing kirby-types panel definitions generates markdown .review reports and patches. The reports detail per-cluster findings from the annotation pass, and the patches are produced during the verification pass for application.

You should run a panel type audit before deployment or during maintenance cycles to ensure Panel type definitions align with the Kirby runtime. This verifies that TypeScript augmentation types match the actual JS and PHP runtime sources.