feat: add runningInConsole() method to Application

[binaryfire]

Summary

Implements Laravel-compatible app()->runningInConsole() detection for Hypervel, using coroutine-local Context to correctly distinguish between CLI commands and HTTP/queue contexts

Problem

In traditional Laravel, app()->runningInConsole() checks PHP_SAPI === 'cli'. This doesn't work in Swoole/Hypervel because both HTTP servers and console commands run via CLI.

Common use cases that need this detection:

• Model global scopes that should behave differently in the CLI
• Observers that skip certain behavior during CLI commands

Solution

Uses Hyperf\Context\Context to store a coroutine-local flag that tracks whether code is executing within a console command context.

How it works

1. Kernel::handle() (the CLI entry point, e.g., php artisan foo) calls markAsRunningInConsole() before executing any command

2. Kernel::call() (programmatic command execution) does NOT set the flag - it inherits whatever context already exists

3. Command::execute() propagates the flag across coroutine boundaries when commands spawn new coroutines

Behavior matrix

Context	runningInConsole()
php artisan migrate	true
Code inside CLI command	true
Nested command via Artisan::call() from CLI	true
Scheduled command (via schedule:run)	true
HTTP request	false
Artisan::call() from HTTP controller	false
Queue job	false

Changes

• Application.php - Added runningInConsole() and markAsRunningInConsole() methods using Context
• Application.php (Contract) - Added method signatures to interface
• Kernel.php - Calls markAsRunningInConsole() in handle() (CLI entry point only)
• Command.php - Propagates console context across coroutine boundaries
• App.php (Facade) - Regenerated docblocks to include new methods

Tests

10 tests covering:

• Default state returns false
• markAsRunningInConsole() sets state to true
• Idempotent marking
• Kernel::handle() sets the flag
• Artisan::call() alone doesn't set the flag
• Code inside CLI commands sees true
• Code inside Kernel::call() without prior handle() sees false
• Nested commands inherit console context
• app() helper reflects state
• Scheduled commands inherit context from schedule:run

[albertcht]

Hi @binaryfire , the current implementation of this PR seems to return false when using app()->runningInConsole() in both unit tests and tinker environments? This doesn't seem to match the expected behavior?

[albertcht]

Are these two lines duplicated code?

[binaryfire]

@albertcht Closing this, because I've implemented a cleaner solution in the refactor branch.

The new approach defaults to true (every Hypervel entry point is CLI) and the serve command explicitly flips it to false before starting the HTTP server. Workers forked by Swoole inherit that value, so all HTTP request handling sees false. One-shot commands (migrate, queue:work, schedule:run, tests) never flip it, so they correctly remain true.

APP_RUNNING_IN_CONSOLE env var is supported as an override for testing, matching Laravel's convention.

Files to review in the hyperf-decouple branch:

• src/contracts/src/Foundation/Application.php - added runningInConsole() and runningConsoleCommand() to the contract
• src/foundation/src/Application.php - implementation + setRunningInConsole() setter + updated detectEnvironment() to gate argv
• src/server/src/Commands/StartServer.php - flips the flag before $serverFactory->start()
• tests/Foundation/ApplicationRunningInConsoleTest.php - 27 tests covering all scenarios

This is a much cleaner and less brittle implementation that returns the same value as Laravel for every scenario (http server, unit tests, tinker, commands, queue workers etc)