feat(plugin): discover and list plugin-provided commands

Port Application::getPluginCommands: resolve the local composer with
plugins force-enabled, fall back to Factory::createGlobal, and collect
commands from CommandProvider capability adapters. PhpCommandProxy now
mirrors name/description/aliases/hidden over RPC so `list` output
matches upstream; input definitions remain TODO(plugin).

PhpClass::php_class_name returns an owned String because PHP-backed
proxies only know their class at runtime (the override-skip warning
prints get_class). CommandProvider::getCommands hands out shared
Rc<RefCell> handles since the commands are stored in the application.

Factory::createGlobal now propagates createConfig errors instead of
swallowing them, and Application::getComposer only catches the
exception classes upstream catches, so a ParsingException reaches
doRun's GithubActionError path as in Composer.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

1 files changed, 2 insertions, 1 deletions

diff --git a/crates/shirabe/src/plugin/capability/command_provider.rs b/crates/shirabe/src/plugin/capability/command_provider.rs
index 2453860a..9deb1bce 100644
--- a/crates/shirabe/src/plugin/capability/command_provider.rs
+++ b/crates/shirabe/src/plugin/capability/command_provider.rs
@@ -9,5 +9,6 @@ use crate::plugin::capability::Capability;
 /// The sole implementor is the PHP capability proxy (Composer itself never implements a
 /// capability), so the method is fallible: the answer crosses the RPC boundary.
 pub trait CommandProvider: Capability {
-    fn get_commands(&self) -> anyhow::Result<Vec<Box<dyn BaseCommand>>>;
+    fn get_commands(&self)
+    -> anyhow::Result<Vec<std::rc::Rc<std::cell::RefCell<dyn BaseCommand>>>>;
 }