maintain-dynamic-plugins

# Maintain Dynamic Plugins ## Companion Guidance Use `karpathy-guidelines`, `validate-change`, `maintain-packaging`, and `contribute-docs` alongside this skill when implementation, packaging, CI, or documentation changes are involved. Use this skill for `plugin.kind = "rust_dynamic"`, `plugin.kind = "worker"`, `nemo-relay-plugin`, `nemo-relay-worker`, `nemo-relay-worker-proto`, `nemo-relay-types`, and the Python `nemo-relay-plugin` package. ## Rules - Keep the stable boundary explicit: native plugins cross a C ABI; worker plugins cross `grpc-v1`. - Do not pass Rust runtime types, trait objects, futures, or allocator-owned strings across the native dynamic-library boundary. - Typed native middleware futures run on the SDK-owned Tokio executor. Keep subscribers synchronous and preserve raw synchronous ABI registrations. - Define closed worker transport structures in protobuf when generated clients must enforce their fields. Keep open application payloads lossless by using `JsonValue` or `JsonEnvelope` rather than `google.protobuf.Value`. - Keep `relay-plugin.toml` dynamic records separate from generic runtime components. Enabled dynamic records may synthesize internal component specs; disabled records stay inspectable but unloaded. - Relay 0.8 establishes the native API 1 and `grpc-v1` canonical `ToolExecutionResult` baseline. Require every dynamic plugin to rebuild and declare a `compat.relay` range that excludes versions before 0.8. Recommend `>=0.8.0...