@bert-w this solves the issue you where having with route files missing context for $this.

The proposed change sets $this within the entire routes/console.php file to be an instance of Illuminate\Console\Command.

However, $this is an instance of Illuminate\Foundation\Console\Kernel in the routes/console.php file.

<?php

use Illuminate\Foundation\Inspiring;
use Illuminate\Support\Facades\Artisan;

Artisan::command('inspire', function () {
    $this->comment(Inspiring::quote());
})->purpose('Display an inspiring quote');

dd($this::class);

If this was wanted, the docblock would need to be contained within each command's anonymous Closure, otherwise it is invalid and would remove the tooling's ability to help.

- /** @var Illuminate\Console\Command $this */
Artisan::command('inspire', function () {
+   /** @var Illuminate\Console\Command $this */
    $this->comment(Inspiring::quote());
})->purpose('Display an inspiring quote');

Hmm I se what's happening is that the context is rebound between the function being defined and later being executed:

https://github.com/laravel/framework/blob/7b8e12d8f4218615370d329a258f0b7c4afc6237/src/Illuminate/Foundation/Console/ClosureCommand.php#L64

This change is going to be obscure to a lot of tools which expects the context to be bound at the time the closure is being defined and so expect that it's using the context of the file. I don't think your solution of adding the docblock inside of the anonymous function is going to work in general for the same reason.

I'll close this PR for now.