feat(plugin): let a Rust-implemented plugin cross into the worker

PluginManager::getPluginCapability hands the plugin itself to the
capability constructor. Only a PHP-implemented plugin had an entity the
child could receive, so a Rust-implemented one bailed out; it now crosses
as a handle to an R-table entity behind Shirabe\RustPluginStub, or its
Capable flavour, since `$plugin instanceof Capable` is what decides
whether Composer asks a plugin for capabilities at all.

This is what the two capability tests of PluginInstallerTest were waiting
on: the mocked Capable plugin is Rust-side, and one of them asserts the
identity of the plugin read back out of $capability->args.

1 files changed, 8 insertions, 0 deletions

diff --git a/crates/shirabe-php-rpc/src/lib.rs b/crates/shirabe-php-rpc/src/lib.rs
index 6dfdebf5..a4742664 100644
--- a/crates/shirabe-php-rpc/src/lib.rs
+++ b/crates/shirabe-php-rpc/src/lib.rs
@@ -969,6 +969,14 @@ const RUNTIME_FILES: &[(&str, &str)] = &[
         "Shirabe/RustCommandStub.php",
         include_str!("../php/runtime/Shirabe/RustCommandStub.php"),
     ),
+    (
+        "Shirabe/RustPluginStub.php",
+        include_str!("../php/runtime/Shirabe/RustPluginStub.php"),
+    ),
+    (
+        "Shirabe/RustCapablePluginStub.php",
+        include_str!("../php/runtime/Shirabe/RustCapablePluginStub.php"),
+    ),
 ];
 
 struct Worker {