Chronos Laravel Package

Product Decisions This Supports

• Adopt or retain Chronos as a Laravel-native operations control plane for scheduled commands, manual runs, logs, metrics, and real-time command execution from a panel.
• Security and governance decisions: 1.9.1 changes the default posture to deny system commands. PMs should treat command access as an explicit allowlist capability, not a default admin convenience.
• Operational roadmap: support self-service actions such as cache:clear and queue:restart only after listing them in chronos.system_commands; expect existing schedules for non-allowed commands to be skipped.
• Environment strategy: test/debug commands (chronos:test, chronos:answer, chronos:dd, etc.) are local-only by default; staging visibility requires deliberate CHRONOS_TEST_COMMANDS=true.
• Build vs buy: reduces custom admin-panel work for scheduling and command observability, while introducing configuration and access-control work.
• Platform readiness: Laravel 10–13 support via illuminate/support ^10.0|^11.0|^12.0|^13.0, including fixes for Laravel 13 apps and real-time run reliability.

When to Consider This Package

• Consider it when a Laravel 10–13 application needs a panel for app/Chronos command execution, scheduling, logs, metrics, and real-time runs without custom tooling.
• Consider it when the team can manage explicit command allowlists per environment and can audit existing schedules before upgrading.
• Consider it when reliable process behavior matters: 1.9.1 fixes SIGTERM/SIGKILL handling, killed run state, lost answers, new-log-only loading, and command metric aggregation.
• Look elsewhere if the product requires arbitrary artisan/vendor command execution immediately without an allowlist, if the stack is not Laravel/PHP, or if the team cannot operationalize environment flags and config changes.
• Be cautious if existing schedules rely on system commands that are not allowlisted; those schedules will be skipped after upgrade until configured.

How to Pitch It (Stakeholders)

Chronos 1.9.1 is a security- and reliability-focused release. Executives should see it as safer default operations: system commands are disabled unless explicitly allowed, test commands are local-only unless enabled, and real-time runs use the running PHP binary for consistency. Engineering should plan an upgrade review: audit scheduled commands, add required names/classes to chronos.system_commands, set CHRONOS_TEST_COMMANDS=true only where needed, and configure CHRONOS_PHP_BINARY if required. The release also improves signal handling, metrics accuracy, Laravel 13 compatibility, and real-time log behavior, with no migrations required.