🐛 fix: expose $this->plugin in Console commands

[dansleboby]

• Add protected $plugin property and setPluginAttribute() setter to Command
• Fix loadWordPress() to use $currentDir (plugin root via $_SERVER['PWD']) instead of DIR for vendor/bootstrap paths, which was resolving to the wrong directory inside the vendor tree
• Capture the return value of bootstrap/plugin.php so $this->plugin is populated after calling loadWordPress()
• Add Kernel::setPlugin() to propagate the plugin instance to all registered command instances
• Store plugin in BonesCommandLine and pass it to the kernel before dispatching custom commands

[Copilot]

Pull request overview

This PR aims to make the plugin instance available inside custom console commands (via $this->plugin) by capturing it from bootstrap/plugin.php and propagating it through the console kernel, while also fixing WordPress/bootstrap path resolution when running commands from a plugin root directory.

Changes:

• Add a $plugin property + setter on Console\Command, and populate it from bootstrap/plugin.php during loadWordPress().
• Add Kernel::setPlugin() to inject the plugin instance into registered command instances.
• Track the plugin instance in the bones CLI and pass it into the kernel before dispatching custom commands.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
src/Foundation/Console/Kernel.php	Adds setPlugin() to propagate the plugin instance to registered command objects.
src/Console/bin/bones	Stores plugin instance in the CLI runtime and attempts to pass it to the kernel before handling custom commands.
src/Console/Command.php	Introduces a protected $plugin property + setter and updates loadWordPress() to use the working directory for vendor/bootstrap paths and to capture the plugin instance.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.