docs(plugin): record dispositions of plugin-boundary open questions

The Package family settles on pure rust-proxy: it is genuinely mutable
(60+ setters, and Composer itself mutates packages in flight), so the
planned snapshot-with-writeback treatment is dropped rather than filed
as an override. The other open questions remain open with their interim
behavior pinned instead of resolved: proxy-side getLoop() access and the
ConsoleIO table/progress-bar members are explicit errors, and the
InstalledVersions state a plugin observes after a Rust-side dump is
undefined, marked TODO(plugin) at the reload site.

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

1 files changed, 4 insertions, 0 deletions

diff --git a/crates/shirabe/src/repository/filesystem_repository.rs b/crates/shirabe/src/repository/filesystem_repository.rs
index 151cf2d3..32e4022a 100644
--- a/crates/shirabe/src/repository/filesystem_repository.rs
+++ b/crates/shirabe/src/repository/filesystem_repository.rs
@@ -343,6 +343,10 @@ impl FilesystemRepository {
             );
 
             // make sure the in memory state is up to date with on disk
+            // TODO(plugin): whether this reload must also be pushed to the plugin PHP child
+            // process is undecided; the InstalledVersions state a plugin observes after this
+            // dump is undefined (docs/dev/plugin-class-classification.md, "Bootstrap classes
+            // cannot be stub-shadowed").
             InstalledVersions::reload(versions);
 
             // make sure the selfDir matches the expected data at runtime if the class was loaded from the vendor dir, as it may have been