Thanks for this @hirasso, very true I've struggled to get to updating it to latest versions of stuff so your efforts are appreciated!

Not sure what you mean on the 'weird comments', I couldn't see anything in the changes that take out anything that looked odd. That said, I did at some point use IDEs other than VS Code, in particular I remember one of them (PHP Storm maybe?) that used to do something odd with comments.

You mention Actions too, there's some already, aren't they doing what you suggest? Or did I miss something?

Hey @markheydon! Great to know you're open to my contribution! I saw the action notification about the failing tests. Could we update the PHP version in the action to 8.2? Since Monolog ^3 requires at least PHP 8.1, I figure most users of this package likely keep their PHP updated.

Regarding the code comments I deleted, I also believe they're related to PHP Storm. One example:

//<editor-fold desc="Magic Methods">

Also, it's possible the code coverage dropped below 100% in my PR since I'm not familiar with coverage tools. However, I prioritize writing tests for critical components, so I don't think it's a big issue. I prefer keeping my repos free of coverage report batches.

I've ditched the idea of using WP_CLI together with Monolog logs, so I'll close this PR. Turns out there is a much simpler solution with simply using php://output. That also makes it pretty straightforward to dump the context of a LogRecord using Symphony's VarDumper package. I've posted my new solution over at StackOverflow: https://stackoverflow.com/a/78447765/586823

Thanks for the update @hirasso, was good to have some interest in the project while it lasted though!